Without one, interviewers come out of conversations with vague feelings ("I really liked her") and the team makes decisions on the strongest opinion in the room. With one, every interviewer has documented what they observed, scored each competency, and recorded the evidence. The team makes decisions based on shared data.

This article gives you the scorecard template and how to use it. It's short for a reason: scorecards aren't complicated, but they have to actually be used.

For the deeper context on why scorecards matter, see Interview Scorecard Template: How to Evaluate Candidates Fairly. This article is the practical companion.

What a scorecard is

A scorecard is a document, one per candidate per interview round, that captures:

The competencies being assessed in this round
A score for each competency (typically 1-4)
Specific evidence supporting each score
The interviewer's overall recommendation (advance, decline, debate)

That's it. The whole document for a 60-minute interview should fit on a page.

The template

Here's the structure to use.

Candidate: [Name]
Role: [Title]
Interviewer: [Name]
Date: [Date]
Round: [Phone screen / Hiring manager / Functional / etc.]

Competency 1: [Competency name]

Score: [1-4]

Evidence:

[Specific example or quote from the interview]
[Specific example or quote from the interview]

Competency 2: [Competency name]

Score: [1-4]

Evidence:

[Specific example or quote from the interview]
[Specific example or quote from the interview]

[Repeat for each competency assessed in this round]

Overall recommendation: [Strong advance / Advance / Debate / Decline / Strong decline]

Summary: [2-3 sentences explaining the recommendation]

Open questions or concerns: [What you'd want a later interviewer to probe]

What each section is for

Scores

Use a 4-point scale. Avoid 5-point scales (the middle option becomes a cop-out) and 10-point scales (too much false precision).

Scoring definitions should be role-specific and tied to your interview guide. A typical scale:

4: Significantly above standard. Would raise the team's level.
3: At standard. Solid hire, would match team's level.
2: Below standard. Real gaps. Would be a stretch.
1: Significantly below standard. Clear no.

The 4 should be rare. The 1 should be specific. Most candidates land at 2 or 3 for any given competency.

Evidence

This is the most important part of the scorecard. Don't write impressions. Write what the candidate actually said or did.

Bad evidence: "Strong communication skills"
Good evidence: "When asked about explaining a complex topic to a non-technical audience, walked through specific example of explaining database migration to head of sales. Drew an analogy to changing tires on a moving car. Sales lead was able to engage with the trade-offs."

The evidence is what makes the score defensible. Without it, you're back to impressions.

Overall recommendation

Use a 5-point scale:

Strong advance: Would actively want to hire
Advance: Would not block a hire
Debate: Needs more information, has specific concerns to discuss
Decline: Would not hire based on this interview
Strong decline: Active opposition to hire

Recommendations should come from the scores. If you scored every competency a 4 but your overall recommendation is "debate," you have a conflict you should resolve before submitting.

Summary and open questions

A few sentences summarizing your view, and any questions you couldn't fully answer in your interview that you'd want a later interviewer to probe.

How to use a scorecard well

Three rules.

Fill it in within 15 minutes of the interview. Memory degrades fast. Specific quotes and examples get blurry within an hour. Block 15 minutes after every interview to complete the scorecard while it's fresh.

Score before discussing with other interviewers. The single biggest scorecard antipattern is interviewers comparing notes before scoring. This creates anchoring effects where the most assertive interviewer's view spreads. Score independently first. Discuss after.

Use evidence, not impressions. If you find yourself writing "great vibes" or "felt off" as evidence, stop. Either you saw something specific that prompted the impression (write that), or you didn't (and the impression is bias).

What to do in the debrief

The scorecard's value is realized in the debrief. The debrief format that works:

Each interviewer states their overall recommendation (no discussion yet)
For each competency, each interviewer shares their score and evidence
Where interviewers disagree, the discussion focuses on what evidence each saw, not on whose impression is "right"
Final decision is made, with notes on why

The point of the debrief isn't to average scores. It's to surface evidence and resolve disagreements. Sometimes one interviewer saw something the others missed. Sometimes one interviewer was anchored by something irrelevant. The debrief is how you sort the difference.

For more, see Hiring Process Stages: What Each Step Should Actually Include.

A note on calibration

Scorecards work better when the team is calibrated. That means:

Everyone uses the same definition of what a 3 looks like
Everyone applies the same scoring rigor (some interviewers default to high scores, others default to low)
Disagreements about scores are surfaced and discussed, not smoothed over

You calibrate by debriefing together, looking at past hires, and over time, comparing scores from the same interviewer to actual performance after hiring. Calibration takes a few cycles. Most teams underinvest in it.

Build your scorecard with Oryx

Building scorecards manually for every role and round is tedious. Our Interview Guide Builder generates the scorecard alongside the guide, with role-specific competencies and scoring rubrics built in.

Try the free Interview Guide Builder

Previously in this series: Free Interview Guide Template (How to Build One)
Next in this series: XXXXJob Offer Letter Template (For SMB Teams)