Reduce the list before comparing detail
A shortlist should make a decision easier, not create a tournament of brands. Start by removing options that clearly fail an essential condition, then assess the smaller group against the same plan, region, workload and evidence standard.
Apply your red lines before scoring preferences. Compare the exact plan, user count, region, integrations and support terms that you would actually buy. Record the evidence date, source and unresolved risk for each option, including why a plausible alternative was excluded.
Filter before you score
- Set the scope: user, workflow, geography, scale, budget range and decision date.
- Remove options that fail a confirmed non-negotiable such as required export, permission model or integration.
- Check that the remaining options are comparable at the plan and usage level.
- Collect current, attributable evidence for each requirement; mark a gap as unknown.
- Score preferences only after the viable options meet the red lines.
Keep a visible exclusion record
Reason for inclusion
State the workflow or requirement the option appears capable of meeting.
Reason for exclusion
State the verified red line, scope mismatch or evidence gap—without claiming a product is universally unsuitable.
What could change the result
Record the trial, contract answer, product change or current documentation needed to reconsider.
Ask for supplier evidence, then keep checking
The NCSC advises software customers to request relevant supplier assurance information, assess the claims and maintain ongoing assurance. A supplier statement is useful input, but it does not replace a check that the claim applies to the plan, configuration and use case you are considering.
Shortlisting FAQs
Should the shortlist include the market leader?
Only if it meets the stated scope and non-negotiables. Familiarity or market presence may justify research, but it is not proof that an option fits your workflow or risk.
How many options should reach a trial?
Usually the few viable options where a material uncertainty remains. Desk research can remove clear mismatches; a focused pilot should answer the questions evidence alone cannot settle.
Can we use online reviews to shortlist?
Use them as a lead, not proof. Check the reader context, date, incentives, plan, region and recurring pattern, then verify material claims with current supplier evidence or a trial.
Continue the software decision
Keep the workflow, evidence, people and exit route visible until the decision is made. The next useful step is usually the one that reduces the uncertainty most likely to cause expensive rework later.
