Hiring · August 2, 2026 · 9 min read

Interview Scorecard Template: A Practical Guide

An interview scorecard template for hiring managers: copyable competencies, an anchored scale and an evidence column that holds up against AI-polished answers.

← Part of The five pillars of hiring: what assessments measure

If you are the hiring manager or recruiter running an interview loop, the scorecard is where the whole thing either holds together or quietly falls apart. Skip it and you are comparing four candidates from four interviewers' memories, each shaded by rapport, mood and whoever spoke first in the debrief. An interview scorecard template that captures the wrong things produces decisions you cannot defend and hires you come to regret. This guide gives you a complete scorecard to copy today, the thinking behind each column, and why the evidence column matters most now that candidates arrive rehearsed, polished and, increasingly, coached by AI.

A scorecard is not paperwork for its own sake. It is the instrument that turns an interview from a conversation you half-remember into a measurement you can compare, audit and stand behind. The difference between a good one and a bad one is not length. It is whether it forces the interviewer to record what actually happened.

What is an interview scorecard, and why does it matter?

An interview scorecard is a shared form that lists the competencies a role needs, a rating scale with written descriptions of each level, and space to record the evidence behind every rating. It matters because it makes candidates comparable on the same terms and leaves a documented reason for the decision. Without one, an interview measures the interviewer's impression as much as the candidate's ability.

The scorecard is the working end of a structured interview. Everything worth knowing about designing the interview itself, the competencies, the questions, the reason consistency predicts performance, lives in our structured interviews guide; this post assumes you have read it and want the artefact. Think of the scorecard as the place where all that design becomes something an interviewer can actually hold in their hand at ten to the hour, with three more candidates to see before lunch.

What should an interview scorecard template include?

A good scorecard has four parts and no more: the competencies for this specific interview, an anchored rating scale, an evidence column, and a short overall recommendation. Anything beyond those tends to dilute the signal. The section below lays each out so you can copy it straight into your own tool and adapt the wording to the role.

1. The competencies (three to five, not fifteen)

List only the competencies this particular interviewer can genuinely assess. A single loop might split competencies across interviewers so nobody is asked to judge everything at once. For a customer-facing role, one interviewer's scorecard might cover just these:

• Problem-solving under ambiguity, how they break down a messy problem with incomplete information.
• Communication, whether they can explain a decision clearly to someone who does not share their context.
• Domain judgement, whether their choices reflect real understanding of the work or surface-level familiarity.
• Collaboration, how they describe working with others when priorities or opinions conflicted.

Each competency should trace back to something the role actually requires. If you cannot say why a competency is on the card, it is filler that pulls attention from the ones that matter. Mapping competencies to a role is its own discipline; the five broad areas most roles draw from are covered in the five pillars of hiring.

2. The anchored rating scale

Use a 1-to-5 scale, and write a short description of what each point looks like for the competency in front of you. An unanchored scale is barely better than a coin toss, because a 4 means something different to every interviewer. Anchors fix the meaning in advance. A generic scale, which you then specialise per competency, reads like this:

• 1, no evidence of the competency, or clear evidence against it.
• 2, below the bar; some awareness but weak or inconsistent in practice.
• 3, meets the bar; solid, expected performance for the level you are hiring at.
• 4, above the bar; consistently strong, with a concrete example that stands out.
• 5, exceptional; the sort of answer you would use to calibrate future interviewers.

The anchors are where the real work is, and where most of the fairness comes from. Writing them for a specific competency, and calibrating them for junior versus senior candidates, deserves its own treatment; our interview scoring rubric guide walks through building anchors that make a score mean the same thing to everyone. The scorecard is the form; the rubric is what makes the numbers on it trustworthy.

3. The evidence column (the part that saves you)

Next to every rating, leave a column for evidence: what the candidate actually said or did that justifies the score. Not "good communicator", but "explained the migration trade-off to me as if I were the finance lead, named the risk unprompted, checked I'd followed". This column is the difference between a scorecard and a feelings survey. It forces the interviewer to point at something real, and it is the record you will lean on in the debrief and, if it ever comes to it, in front of a challenge.

4. The overall recommendation, with reasoning

Close the scorecard with a short recommendation and a sentence or two of reasoning, not a lone verdict. The reasoning is what a hiring manager reads across four scorecards to see the pattern: where interviewers agreed, where they diverged, and which competency any concern actually sits in. A recommendation without reasoning is just a vote, and votes hide the evidence you spent the whole interview gathering. Resist the urge to reduce the loop to a single averaged figure; a low score on one critical competency should not be washed out by high scores elsewhere, and only the reasoning surfaces that.

Why the evidence column beats a gut-feel score out of ten

The most common scorecard in the wild is a list of vague traits with a 1-to-10 box beside each and nothing else. It feels efficient and it is close to useless. A number with no evidence behind it is just a gut feeling wearing a uniform, and gut feelings are exactly what a scorecard is meant to discipline. Two interviewers can write 7 next to "communication" for the same candidate and mean completely different things, and neither can reconstruct why a month later when the hire is struggling.

The fix is not a better number. It is the demand that every score point at something observable. When the form makes evidence mandatory, three things happen: interviewers listen for specifics rather than vibes, the debrief argues about what was actually said rather than about who felt more strongly, and the halo effect, one warm answer colouring the whole interview, gets caught because the evidence column stays stubbornly empty for the competencies the candidate never actually demonstrated. Standardising the form is one of the most reliable ways to reduce bias in hiring, and it starts with refusing to let a score stand alone.

How do you keep scorecards honest when candidates arrive AI-polished?

The evidence column matters more now than it ever has. Candidates increasingly arrive with answers shaped, rehearsed and sometimes generated by AI, so an interview rewards fluent delivery even more than it used to. A polished, confident answer that names all the right frameworks can score well on a gut-feel card while telling you almost nothing about whether the person can do the work. The AI era has raised the floor on how good a wrong answer can sound.

The defence is not to ban preparation or to play gotcha. It is to score on evidence of what the candidate actually did, not on how well they described it. A scorecard that demands specifics, what they personally decided, what broke, what they checked, what they would change, is far harder to satisfy with a rehearsed generality. When the evidence column stays thin under follow-up questions, that thinness is itself the signal, regardless of how smooth the opening answer sounded. Interviews sample how someone talks about work; they are weakest exactly where polish is strongest.

This is also the honest limit of any interview scorecard. An interview samples claims about work; it cannot verify the work itself. If you want to know whether someone can actually do the job rather than describe it convincingly, pair the interview with a work sample test and let the scorecard interpret real output rather than a story about it. Score the interview on reasoning and communication, where it is strong, and let a job-relevant task carry the weight of proving capability. The two together are far harder to game than either alone, and the scorecard for the interview stays focused on what an interview can honestly measure.

Where the interactive scorecard builder fits

You can build all of this in a spreadsheet, and plenty of good teams do. The friction is that a spreadsheet template drifts: one interviewer tweaks the competencies, another quietly drops the evidence column because it slows them down, and within a quarter you are back to inconsistent scorecards that cannot be compared. Keeping the form fixed, the anchors visible, and the evidence column non-optional is mostly a discipline problem, and tooling helps hold the discipline.

If you would rather assemble the scorecard in the browser, set the competencies, write the anchors and produce a clean form every interviewer fills in the same way, you can build one directly with our interview scorecard builder. The value is not the form itself; it is that the anchors and the evidence column stay put no matter who is filling it in, which is precisely where paper templates fail. Whatever you use, the test is the same: does it make the interviewer write down what they saw before they decide what they think?

Common mistakes that quietly ruin a scorecard

Most broken scorecards fail in a handful of predictable ways. If you recognise your own process in this list, the fix is usually smaller than it looks.

• Too many competencies. A card asking one interviewer to rate twelve things gets none of them careful attention. Split competencies across the loop and keep each card short.
• Scores with no evidence. The single most common failure. A rating that points at nothing cannot be defended, compared or trusted; make the evidence column mandatory.
• Filling it in after the debrief. Once the room has spoken, the loudest opinion becomes everyone's memory. Score independently, before you discuss.
• Unanchored scales. A 1-to-5 or 1-to-10 with no description of each level is gut feel with extra steps. Write the anchors, or the number means nothing.
• A single averaged verdict. Averaging washes out a serious weakness in one critical competency behind strengths elsewhere. Keep the recommendation and its reasoning intact.
• Reusing one generic card for every role. Competencies are role-specific; a card built for a sales hire will not tell you what you need about an engineer.

The recurring theme is that the failures are about discipline, not design. A perfectly designed scorecard filled in from memory after a consensus debrief is worse than a rough one filled in honestly and independently, because the good design lends false credibility to a decision that was really made in the room. The document cannot save a process that does not respect it.

Turning scores into feedback and a defensible decision

A completed scorecard has value well past the hire decision. The evidence you captured is the raw material for candidate feedback that is specific and fair rather than generic and legally awkward. When four interviewers arrive with anchored scores and concrete evidence, the debrief becomes a comparison of what was seen rather than a contest of conviction, and disagreement points straight at the competency worth probing further. Turning those notes into useful, honest wording is a craft in itself; our interview feedback examples show how to write evidence-anchored feedback that helps the candidate and protects the organisation.

There is a compliance dimension too. A scorecard that records the same competencies, the same anchors and specific evidence for every candidate is, almost as a by-product, the audit trail that shows a decision was made on job-relevant grounds. An unstructured impression jotted down afterwards is the opposite: a decision you have to reconstruct from memory if a rejected candidate ever asks why. The discipline that makes the scorecard predictive is the same discipline that makes it defensible.

A scorecard is only as honest as its evidence column. Fill that in properly and the score almost writes itself; leave it blank and the number is just a feeling in a suit.

Putting the template to work

Start with three to five competencies you can actually defend, write anchors so a score means the same thing to everyone, and make the evidence column non-negotiable. Score independently, keep the reasoning intact rather than collapsing everything into one average, and pair the interview with real evidence of the work wherever the decision matters. Do that and your scorecard stops being paperwork and starts being the thing that turns your most trusted, and most fallible, hiring step into one you can genuinely rely on, even when every candidate arrives more polished than the last.