Direct answer
Start with the work a team needs to do, then evaluate software against specific evidence, usability and maintenance needs.
Define the workflow
Write a short list of real tasks. A product comparison is meaningful only when the same test can be applied to every candidate.
Ask for an evidence trail
Can users see where inputs came from, review an output and export their work? Can a team reverse an assumption when its source changes?
| Area | What to test |
|---|---|
| Data | Import, validation and lineage. |
| People | Access, review and handover. |
| Outputs | Format and transparency. |
| Support | Onboarding and update handling. |
Separate product facts from judgement
Document criteria, disclose relationships and avoid describing a tool as approved by a body without independent proof.