Free guide

Interview Scorecard Template: A Free Example and How to Use It

An interview scorecard is a simple document that tells every interviewer exactly what to evaluate, how to rate it, and how to record evidence. It sounds like bureaucracy, but it is the single cheapest upgrade most small companies can make to their hiring. Without one, interviews drift into friendly conversations, each interviewer judges something different, and the final decision is made on whoever "felt right." With one, you compare candidates on the same criteria, you can explain why you hired someone, and you make fewer expensive mistakes.

This guide explains what belongs on a scorecard, gives you a free template you can copy right now, and walks through how to run a scoring and debrief process that actually works for a team of any size.

Why use an interview scorecard at all?

Decades of research on employee selection point the same way: structured interviews, where every candidate is asked comparable questions and rated against the same standards, predict job performance considerably better than unstructured conversations. The scorecard is the tool that creates that structure. It delivers three concrete benefits:

• Consistency. Every candidate is measured against the same four to six competencies, so you compare like with like rather than comparing a great conversation with a nervous one.
• Less bias. When interviewers must write down evidence for each rating, it becomes harder for first impressions, shared hobbies or a similar background to dominate the decision.
• Faster decisions. Debriefs that start from written scores take fifteen minutes instead of an hour of "so, what did everyone think?"

Scorecards also protect you. If a rejected candidate ever questions a decision, a documented, job-related evaluation is far better than "we just didn't click."

What goes on a good scorecard

Keep it short enough to complete in five minutes after the interview. A good scorecard has five parts:

1. Header: candidate name, role, interviewer, date, and interview stage (phone screen, technical, final).
2. Competencies: four to six skills or behaviors that genuinely predict success in this role. Derive them from the job's real outcomes, not from a generic list.
3. Questions per competency: one or two prepared questions, ideally behavioral ("Tell me about a time…") or situational ("What would you do if…").
4. Rating scale with anchors: a 1–5 scale where each number has a written description, so a "4" means the same thing to every interviewer.
5. Evidence and recommendation: space for notes, an overall recommendation (strong no / no / yes / strong yes), and any concerns to probe in the next round.

Free mini interview scorecard template

Copy this into a document or spreadsheet and adapt the competencies to your role.

Rating anchors to use with it

• 1 — No evidence: could not give an example or the answer was off-topic.
• 2 — Weak: vague or hypothetical answer; little personal contribution.
• 3 — Meets the bar: a specific, relevant example with a reasonable outcome.
• 4 — Strong: specific example, clear personal actions, measurable result, some reflection.
• 5 — Exceptional: multiple strong examples, high complexity, and lessons applied later.

How to choose the right competencies

The most common scorecard mistake is copying a generic list ("team player, detail-oriented, passionate"). Instead, ask: what will this person need to accomplish in their first year, and what skills does that require? For example, a customer support lead might need to cut first-response time, train two new agents and build a help-center. That suggests competencies like prioritization under pressure, coaching, and written communication. A junior developer might need to ship features in an existing codebase, which suggests code reading, debugging, and asking for help early.

Limit yourself to the few competencies that genuinely separate good hires from poor ones. If everything matters, nothing does. Also split them across interviewers: one person covers technical skill, another covers collaboration and ownership. This keeps interviews focused and avoids candidates answering the same question four times.

Running the process step by step

1. Before the interview: share the scorecard with all interviewers and assign competencies. Agree on what a "3" looks like for this role.
2. During the interview: ask the prepared questions in the same order for every candidate. Use follow-ups like "What did you specifically do?" and "What was the result?" Take short notes of what the candidate says, not your opinion of it.
3. Immediately after: score each competency within an hour while memory is fresh. Write evidence first, then the number.
4. Submit independently: interviewers should submit scores before talking to each other. Otherwise the most senior or most confident voice anchors everyone.
5. Debrief: review the scores side by side. Discuss only the competencies where ratings diverge by two or more points. Decide based on evidence against the bar, not against the other candidates' charisma.

Common mistakes to avoid

• Scoring "culture fit." It quickly becomes "people like us." Score specific behaviors such as giving feedback or working under ambiguity instead.
• Averaging blindly. A 5 in communication does not compensate for a 1 in a skill the job cannot do without. Mark must-have competencies and treat a low score there as decisive.
• No anchors. Without written descriptions, one interviewer's 3 is another's 4, and the numbers become noise.
• Changing questions per candidate. Small follow-ups are fine; replacing core questions destroys comparability.
• Filling in the card days later. Memory fades and reconstructs. Late scorecards mostly record a general impression.

Adapting the scorecard to different stages

A phone screen scorecard can be tiny: two or three knockout criteria (work authorization, salary range, a core skill) and a yes/no. Technical or work-sample stages should score the output itself, for example "quality of solution," "approach and trade-offs," and "explanation." Final interviews typically cover ownership, collaboration and motivation. Keep the 1–5 scale constant across stages so a hiring manager can scan the whole picture quickly.

Keeping records

Store completed scorecards with the candidate's record in your applicant tracking system or a simple recruiting pipeline tracker. Over time you can check whether high interview scores actually predicted strong performance and refine your questions. Check your local data-protection rules for how long you may keep candidate data.

Frequently asked questions

How many competencies should a scorecard have? Four to six. Fewer than four rarely covers the role; more than six cannot be assessed properly in a one-hour interview.

Should candidates see the scorecard? You don't need to share the card itself, but telling candidates which areas you'll cover improves their experience and the quality of their answers.

Can a small business without HR use scorecards? Absolutely. In fact a five-person company benefits most, because one bad hire is a much bigger share of the team.

The free template above covers the essentials. If you'd rather not build role-specific questions and anchors from scratch, our Interview Scorecard Pack includes ready-made, editable scorecards for five common roles. You may also like our guide to structured interview questions by role.

← More hiring guides