Recruiting guides · 6 minutes read
Interview scorecard template: turn answers into useful evidence
By ReclyraUpdated
What an interview scorecard should do
An interview scorecard is a short evaluation sheet based on a job's requirements. It helps make interview notes comparable before memories and general impressions replace specific answers. The sheet organises your assessment. It does not decide who gets hired or turn a conversation into an objective suitability test.
For a small team, one page per interview is often enough. When preparing the interview, choose criteria you can discuss in the available time. General qualities such as ‘dynamic’ or ‘fits our culture’ make weak rows. Translate them into observable behaviour, such as structuring an unclear request or explaining a technical issue in accessible language.
The template: six fields for each criterion
Copy this structure into a document or your interview notes: criterion; shared core question; expected features of an answer; specific observation; assessment; open follow-up. Add the role, interview date and participants at the top. Put the recommended next step underneath the criteria, keeping the evidence separate from the recommendation rather than mixing both into one comment.
For an IT support position, a row could read: criterion: investigate incidents systematically. Core question: ‘Describe an incident where the cause was initially unclear. What did you check first, and why?’ Expected features: understand the impact, test explanations, check the result and document the approach. Ask about the person's own contribution if the answer mainly describes a team's work.
Use rating anchors instead of arbitrary grades
A small scale can help the discussion if its levels are described beforehand. For example: 1 = the example leaves important steps unexplained; 2 = a coherent approach with some open points; 3 = a clear approach with reasons for the steps and a check of the outcome. Adapt these anchors to the experience level expected in the role.
Always include ‘not sufficiently discussed’ as a separate state outside the scale. If time ran out or the question was unclear, there is no reliable rating yet. For an entry-level role, an example from training or a project may be appropriate. Assess what the person did rather than relying on the size of the employer or project.
A completed example for the team discussion
Observation: ‘The person described a failed print job. They asked which users were affected, compared a working workstation and then checked the queue. After fixing the issue, they asked the user to confirm a successful test print. Whether they documented the incident was not discussed.’ This records a specific answer, not every support task the person has handled.
Assessment: ‘2 – the described approach is coherent; documentation remains unclear.’ Follow-up: ‘What did you record afterwards for other team members?’ The later answer may change the assessment. Preserve the connection between observation and rating. When notes are summarised, ‘documentation not discussed’ must not accidentally turn into ‘does not document their work’.
Calibrate the scorecard before the first interview
Walk through the sheet as a team using an invented answer. Would you assess the same observation similarly? If not, the criterion probably needs a shared definition. Clarify whether you are assessing technical depth, independent problem-solving or clear communication. These can be connected without necessarily deserving the same rating, and separating them makes disagreements easier to understand.
Also decide what the interview can reasonably establish. A single story does not automatically demonstrate confident use of a tool. If that skill is essential, a suitable work sample may help. Agree the process beforehand and explain it to applicants so the requirements, preparation and time commitment are clear rather than emerging unexpectedly during the conversation.
Use it carefully during and after the conversation
Take brief notes during the interview and complete them soon afterwards. One person can ask questions while another records relevant examples. Leave room for follow-ups and the applicant's own questions. The scorecard should support your attention; it is not a script to finish regardless of the answers or the useful issues raised in the discussion.
Each team member should add their assessment independently first. Then compare the differences and the evidence behind them. Do not simply average conflicting scores into a number that appears conclusive. A different memory, a different interpretation of an anchor and a genuinely unanswered technical question each call for a different next step.
Connect the scorecard to a reasoned decision
Finish with three short entries: what supports this person's suitability for the role; what still needs clarification; and which next step is recommended, with an owner. An interview may also reveal that the job advert contains unclear expectations. If those change, make the change deliberately and review what it means for the other applications already in the process.
With Reclyra’s recruiting features, you can use this template to structure internal application notes and consult existing analysis findings when preparing. The scorecard described here is a working template for your team. Keep the assessment beside the interview evidence so colleagues can understand your recommendation without needing to have attended every conversation themselves.
Your checklist
- Each criterion describes a task or observable behaviour.
- Question, observation and assessment are recorded separately.
- Rating anchors match the role's expected experience level.
- Undiscussed points do not receive a negative rating.
- Team members record their assessments independently first.
- Open questions and next steps are specific and documented.