A few months ago I sat in on a debrief for a role. Four interviewers. Same candidate. One person said she was "clearly the strongest we've seen." Another said she "seemed fine but nothing special." A third couldn't remember which candidate she was because he'd interviewed six people that week and didn't take notes.
The hiring manager stared at the ceiling for a while, then said, "So... do we move her forward or not?"
Nobody had scored anything. Nobody had agreed on what "good" looked like before the interviews started. That's what happens without an interview scorecard. You get opinions instead of evidence, and the hiring decision comes down to whoever argues loudest in the debrief.
An interview scorecard fixes this by giving every interviewer the same criteria, the same scale, and the same format. This guide walks you through how to build one, with examples and a free template.
What is an interview scorecard?
An interview scorecard is a standardized document that interviewers use to rate candidates against predetermined, job-specific criteria. Each criterion gets a numerical score on a consistent scale. The result is comparable data across every candidate and every interviewer.
The difference between "I liked her" and "She scored 4/5 on communication, 5/5 on technical depth, and 3/5 on collaboration, with notes on each." The first gives you a feeling. The second gives you something you can compare, discuss, and defend.
Interview scorecard vs interview rubric vs evaluation form
The best scorecards have a rubric built in. The scorecard is where you record ratings. The rubric tells you what a 3 versus a 5 actually means.
What to include in an interview scorecard
- Job-specific criteria and competencies. The skills, behaviors, and qualifications you're evaluating. They should come from the job description and the intake conversation with the hiring manager. Aim for 5 to 10 criteria. "Communication skills" is too broad. "Ability to explain a complex technical decision to a non-technical stakeholder" is evaluable.
- Rating scale. A numerical scale every interviewer uses the same way. A 1-5 scale is common. A 4-point scale (no middle option) forces interviewers to lean positive or negative rather than defaulting to "fine." If your team tends to rate everyone a 3, try dropping the middle.
- Weighted categories. A "must-have" skill should carry more weight than a "nice-to-have." If quota attainment is twice as important as presentation skills, give it a 2x weight. When you calculate the final score, the weighted criteria pull the total toward what actually matters.
- Space for comments. Numbers tell you what. Comments tell you why. "Scored 4/5 on problem-solving. Described how she identified a bottleneck in the onboarding flow and reduced drop-off by 22% in one quarter" is evidence you can discuss in a debrief.
How to create an interview scorecard step by step
1. Define the role requirements. Start with the job description. Talk to the hiring manager. Get specific about what success looks like in the first 6 to 12 months. If you skip this and pull generic competencies off a list, your scorecard will produce generic results.
2. Identify 5 to 10 key competencies. Mix hard skills and soft skills. A candidate who's technically brilliant but can't work with the team isn't a good hire. Each competency should map to a specific interview question.
3. Choose your rating scale. Pick 1-4 or 1-5 and stick with it across all roles. Define what each number means. Without definitions, one interviewer's 3 is another's 4.
4. Assign weights. Most criteria get 1x. Your top 2 to 3 must-haves get 2x or 3x. This prevents a candidate from scoring high on nice-to-haves but low on what actually matters.
5. Create consistent questions. Behavioral questions ("Tell me about a time when...") work best. Map every question to a specific scorecard criterion.
6. Build the format. Spreadsheet, PDF, or built into your ATS. Include criteria, scale definitions, weights, comment fields, and an overall recommendation (advance, hold, or pass).
7. Test with your team. Have interviewers independently score the same mock interview. If scores are wildly different, refine the criteria. This calibration takes 30 minutes and saves hours later.
Interview scorecard example
Overall recommendation: ☐ Advance ☐ Hold ☐ Pass
Customize the criteria for each role. A sales scorecard would weight quota attainment and objection handling higher. A technical scorecard would weight coding proficiency and system design.
How to use an interview scorecard effectively
- Complete it immediately. Memory degrades fast. Interviewers should fill out scores within 10 minutes of the conversation ending. Block time on their calendar if they consistently forget.
- Require the same scorecard for every interviewer. No exceptions. If one person uses the scorecard and another uses their own notes doc, you're comparing structured data against unstructured opinions.
- Collect scores before the debrief. Every interviewer submits ratings before seeing anyone else's. If the VP says "I loved her" first, the junior interviewer's honest 3/5 suddenly becomes a 4/5. Independence is what makes the data useful.
- Calculate weighted totals to compare candidates. Multiply each score by its weight, sum the results, compare side by side. The candidate who "felt" strongest isn't always the one who scored highest on must-have criteria.
How to set up interview scorecards in Truffle
Truffle is a candidate screening platform that combines resume screening, one-way video interviews, and talent assessments into one workflow you design. Its new Reviews & Scorecards feature turns your evaluation process into a structured, bias-resistant system. Here is how to set it up.
1. Define your scorecard criteria. Go to your position settings and add the criteria you want every reviewer to evaluate against. These could be communication skills, role-specific knowledge, problem-solving ability, or whatever matters for the role. Every reviewer sees the same list.
2. Invite your team to review. Add team members to the position. Each reviewer opens a candidate profile, watches the video responses, and submits their own star rating and recommendation: Move forward, Unsure, or Pass. If you set up a scorecard, they also rate the candidate against each criterion.
3. Reviews stay independent. The Team section is locked until you submit your own evaluation. Nobody sees anyone else's ratings or recommendations first. Every opinion is honest.
4. Compare results. Once everyone weighs in, the Team section unlocks. You see recommendation distribution, average star ratings, and per-criterion averages across all reviewers. You can spot exactly where your team agrees and where opinions diverge.
5. Track progress from the candidate table. A Reviews column shows which candidates still need your review at a glance. No need to open each profile to check.
AI transcribes, analyzes, and scores every response against your criteria before your team reviews. Truffle surfaces match percentages, summaries, and 30-second Candidate Shorts so reviewers can orient before watching full recordings. Your team still makes every decision.
FAQs about interview scorecards
What is the best rating scale for an interview scorecard?
A 4-point or 5-point scale works best. It provides enough granularity without overwhelming interviewers. A 4-point scale (no neutral middle) forces clearer decisions. Define what each number means so everyone scores consistently.
How many criteria should an interview scorecard include?
Between 5 and 10. Fewer than 5 and you're not capturing enough signal. More than 10 and interviewers rush through or skip criteria.
Should interview scorecard ratings be anonymous?
Yes, until everyone has submitted. Anonymous initial ratings prevent senior voices from anchoring junior interviewers' assessments. Open the discussion after scores are collected.
Can hiring teams use the same scorecard for different roles?
Reuse the format, but customize the criteria. A sales scorecard and an engineering scorecard share the same skeleton, but the competencies and weights should reflect each role's requirements.
How should teams handle disagreement among interviewers?
Disagreements are a feature, not a bug. Focus on the specific evidence behind each score rather than averaging the numbers. Often, the disagreement reveals that interviewers saw different sides of the candidate or are interpreting a criterion differently.
