A shortlist should help a reviewer understand why someone is relevant and what still needs checking. A match score is a summary of a comparison against a requirement. It is not a probability that someone will succeed in the role.
Turn the role into a clear requirement
Begin with the work to be done, the context and the outcome expected. Separate essential criteria from preferences. A professional qualification required for the assignment has a different role from experience in a particular industry that the hiring manager would merely prefer.
Review the requirement before searching. Vague descriptions and contradictory conditions make the resulting shortlist harder to interpret. Natural-language input can help express the need, but the team should still be able to inspect the criteria used for the comparison.
Show the evidence behind the comparison
A useful candidate view connects each relevant criterion to a profile response, work example or other authorised source. It should show missing or dated information as well as apparent strengths. The person with the most complete record is not automatically the strongest candidate.
Keep screening, matching and final selection distinct. Screening collects answers and checks stated conditions; matching compares candidates against requirements; the selection process brings further judgement and evidence. Passing one stage does not settle the others.
Make weighting a deliberate choice
Weighting expresses which preferences matter most within an agreed comparison. It should not quietly override an essential condition. Review the effect of changing a preference before accepting a ranking as a stable conclusion.
If small weight changes produce a very different shortlist, that is a useful discussion for the team. The requirement may need clarification, or the candidates may have different strengths that a single ordered list conceals. Keep the rationale with the review.
Close the gap between shortlist and action
Confirm interest, availability and any missing evidence before progressing the candidate. Internal moves may also require manager release and source-team cover; external recruitment has its own agreed review and communication process.
EVA Talent Matching can be scoped around existing candidate pools, internal opportunities or contingent requirements. Agree accessible sources and the review process for the actual use case. A competency-mapping project is not a prerequisite for discussing a matching requirement.
The strongest-looking record is not always ready
Illustrative requirement: lead a six-week assignment with a confirmed start date.
Relevant delivery example · start date confirmed
How to read it
This person has evidence against the requirement and a usable availability response.
The next useful action
Review the evidence and confirm interest before progressing.
Compare all 3 cases
| Case | Known information | Next action |
|---|---|---|
| Strong evidence | Relevant delivery example · start date confirmed | Review the evidence and confirm interest before progressing. |
| Missing evidence | Relevant title · no delivery example | Request a targeted example instead of treating the missing information as either a pass or a failure. |
| Unavailable | Strong delivery evidence · start date conflicts | Consider a revised start date or another candidate; retain the reason in the review. |
Illustrative example. These controls explain the method; they do not access client records or execute workforce actions.
Use matching to make a comparison explainable, then resolve what the comparison cannot establish.
Explore the relevant EVA capabilitiesSources & further reading
This guide explains EVA's approach and illustrative methods. Follow the current offering and methodology pages for scope and examples.