Hiring operations
October 17, 2026
How to build a candidate review scorecard with usable evidence
Turn job requirements into observable assessment criteria. Use evidence, defined ratings, and a not-assessed option to make interview feedback easier to compare.
HRvana editorial team
2 min read
"Strong candidate" is a conclusion. It does not tell another interviewer what the person did or which requirement they met.
A candidate review scorecard should connect the role's requirements to observable evidence. Keep it short enough that interviewers can complete it accurately after the conversation.
Start with work the person will do
Take the job brief and identify the capabilities needed to perform the role. For a support position, that might include diagnosing a customer problem and explaining the next step clearly. Avoid a vague criterion such as "good personality."
Assign each capability to an interview or assessment. If no part of the process can produce evidence for a criterion, change the process or remove the criterion from the scorecard.
Define what a rating means
For a fictional support exercise, the rubric could read:
| Rating | Evidence in this assessment |
|---|---|
| Below requirement | Suggests an action without checking the relevant facts |
| Meets requirement | Identifies the issue, asks useful questions, and explains a workable next step |
| Above requirement | Meets the requirement and anticipates a relevant follow-up problem |
| Not assessed | The conversation did not provide enough evidence |
Adapt the descriptions to the actual role. A numerical score without a shared interpretation creates an appearance of precision while hiding different standards.
Record the observation before the recommendation
Ask interviewers to note the question or exercise, the candidate's relevant response, and how it relates to the criterion. Separate a direct observation from an inference that needs checking.
For example: "Asked which devices were affected before proposing a reset" is evidence. "Naturally analytical" is an interpretation. The evidence helps another reviewer understand why the interviewer reached the conclusion.
Use fictional examples during interviewer training and compare how colleagues rate them. Differences expose ambiguous definitions before those differences affect real candidates.
Leave space for uncertainty
An unanswered question should stay visible. Do not force a low score simply because the interviewer ran out of time. Ask the decision owner whether the missing evidence can be gathered through an existing assessment or a focused follow-up.
Avoid averaging scores mechanically when some criteria are essential and others are optional. Agree how the team will use the rubric before seeing candidates.
Keep completed feedback attached to the correct application with appropriate access. During the debrief, return to the evidence and the role requirements rather than treating the total score as an automatic hiring decision.
Further reading
Related guides
Related Articles
Hiring operations
Build a candidate communication timeline your team can keep
Plan application acknowledgments, interview updates, delays, and decisions with clear owners. Give candidates useful information without promising dates you cannot meet.
Hiring operations
How to update a candidate when a hiring decision is delayed
Write a hiring-delay update that explains the current stage, gives a realistic next contact date, and avoids suggesting an offer or decision that has not been approved.
Hiring operations
How to choose hiring pipeline stages that people understand
Define recruiting stages by the decision, owner, and exit condition. Keep candidate outcomes separate and avoid pipelines that add steps without adding evidence.
Ready to Transform
Your Career?
Create your profile, explore jobs, or find candidates. Start with HRvana today.