An interview scorecard template gives hiring teams a shared way to rate candidates after interviews. Instead of comparing vague notes like "strong communicator" or "good energy," recruiters can score the same competencies, record evidence, and make cleaner decisions across the shortlist.
Use this guide to build a practical scorecard, copy the template, and avoid the common scoring mistakes that make interview feedback hard to trust.
Interview Scorecard Template: Copy This Structure
A good interview scorecard template should be short enough for interviewers to complete during or right after the interview. If it takes 30 minutes to fill out, people will skip details or complete it from memory later.
Start with this structure:
| Section | What to capture | Example |
|---|---|---|
| Candidate details | Candidate name, role, stage, interviewer, date | Maria Lopez, Account Executive, first interview |
| Competencies | 4 to 6 job-related areas to rate | Discovery, objection handling, written communication |
| Rating scale | Same scoring system for every candidate | 1 to 5 with clear anchors |
| Evidence notes | Specific examples from candidate answers | "Explained how she recovered a delayed renewal" |
| Recommendation | Next step and confidence level | Advance, hold, pass, with high/medium/low confidence |
Here is a simple free interview scorecard template you can adapt:
| Competency | What good looks like | Rating 1-5 | Evidence notes |
|---|---|---|---|
| Role knowledge | Understands the role, market, customers, and core tasks | ||
| Problem solving | Breaks down ambiguous problems and explains tradeoffs | ||
| Communication | Gives clear, concise answers with relevant examples | ||
| Ownership | Shows follow-through, accountability, and learning from mistakes | ||
| Collaboration | Works well with peers, managers, and cross-functional teams | ||
| Motivation | Has a realistic reason for wanting this role | ||
| Overall recommendation | Advance, hold, or pass |
This works as a candidate interview scorecard template for most non-technical roles. For technical, clinical, sales, or leadership roles, change the competencies before you start interviewing. Do not force every job into the same generic form.
What to Include in a Job Interview Scorecard Template
The best job interview scorecard template has five parts: role criteria, rating anchors, notes, a recommendation, and a decision rule.
Role criteria
Pick the competencies before interviews begin. The list should come from the job requirements, not from whatever the last interviewer happened to care about.
For most roles, 4 to 6 competencies are enough. The U.S. Office of Personnel Management says structured interviews often assess between four and six competencies, and that higher-structure interviews improve interviewer agreement because they limit unchecked discretion. Its structured interview guidance is written for federal hiring, but the logic applies to private hiring too.
Good competency names are specific:
- Customer discovery
- Clinical judgment
- Territory planning
- Data analysis
- Stakeholder communication
- Safety awareness
Weak competency names are fuzzy:
- Culture fit
- Smart
- Professional
- Nice attitude
- High potential
If you keep a broad area like "culture add" or "work style," define the behaviors you are rating. Otherwise, it becomes a container for personal preference.
Rating anchors
A number is only useful when every interviewer knows what it means. A 4 from one interviewer should not mean "seems good" while another uses 4 only for rare standout answers.
Use a 1 to 5 scale with written anchors:
| Score | Meaning | How to interpret it |
|---|---|---|
| 1 | Does not meet the bar | Little or no evidence of the competency |
| 2 | Partially meets the bar | Some relevant evidence, but gaps are clear |
| 3 | Meets the bar | Adequate evidence for the role level |
| 4 | Strong | Clear evidence above the expected level |
| 5 | Exceptional | Rare evidence that changes the hiring case |
Do not use 5 as "I liked them." Use it only when the answer gives unusually strong evidence against the role requirements.
Evidence notes
The notes field matters as much as the score. A score tells the team what the interviewer thought. Evidence explains why.
Good notes include candidate examples, quotes, outcomes, constraints, and follow-up answers. Weak notes include labels with no proof.
| Weak note | Better note |
|---|---|
| Great communicator | Explained a billing issue in plain language and checked whether the customer understood the next step |
| Bad fit | Wants fully remote work, but the role requires three onsite days per week |
| Strong sales skills | Described a stalled renewal, mapped the buyer group, and recovered the deal after procurement delayed approval |
| Not strategic | Could describe monthly tasks but could not explain how priorities were chosen or measured |
Train interviewers to write what happened, not what they inferred. "Interrupted twice when asked about handoffs" is more useful than "poor teamwork."
Recommendation and confidence
The final section should force a clear decision, but it should not replace the scorecard.
Use simple options:
- Advance
- Hold
- Pass
Then add confidence:
- High confidence
- Medium confidence
- Low confidence
A low-confidence "advance" is normal when the candidate shows promise but needs another interview focused on one gap. A high-confidence "pass" should point to specific evidence, especially when the candidate looked strong on paper.
Decision rule
Before interviews start, decide how scores will be used. Otherwise, the team may collect structured feedback and then ignore it in the debrief.
Common rules include:
- Candidates must score at least 3 on every must-have competency.
- A 1 or 2 on a must-have requires a documented reason to advance.
- Nice-to-have competencies cannot outweigh a missing must-have.
- Interviewers submit scorecards before the debrief.
- The hiring manager reviews evidence before changing a panel recommendation.
This keeps the scorecard connected to the hiring decision instead of becoming paperwork.
How to Build a Structured Interview Scorecard Template
A structured interview scorecard template should match the interview plan. If interviewers ask different questions and score different traits, the scorecard will not fix the process.
Build it in this order.
1. Start with the role outcomes
Ask the hiring manager what the person must be able to do in the first 6 to 12 months. Keep this grounded in work output.
For a customer success manager, outcomes might include:
- Run onboarding calls without manager support
- Identify renewal risk before it escalates
- Explain product limits clearly to non-technical customers
- Coordinate handoffs with sales, support, and product
Those outcomes turn into competencies: customer communication, risk diagnosis, product judgment, and cross-functional follow-through.
2. Choose questions for each competency
Each competency should have at least one planned question. For stronger evidence, use two: one behavioral question and one scenario question.
Example:
| Competency | Behavioral question | Scenario question |
|---|---|---|
| Problem solving | Tell me about a time you had to solve a problem with incomplete information. | A client reports a serious issue, but the data is unclear. What do you do first? |
| Communication | Tell me about a time you had to explain a complex topic to someone outside your function. | Explain this product limitation to a frustrated customer. |
| Ownership | Tell me about a project that went off track. What did you do? | You notice a deadline will slip. Who do you tell and what do you bring them? |
If you need question ideas, use a structured set like interview questions to ask candidates, then map each question to one competency.
3. Write anchors before interviews begin
Do this before seeing candidates. Once interviewers meet a strong candidate, it is tempting to reverse-engineer the rubric around that person.
For each competency, define what a 1, 3, and 5 look like. You do not need long descriptions for every number.
Example for communication:
| Score | Anchor |
|---|---|
| 1 | Gives unclear answers, avoids specifics, or cannot adapt explanation to the audience |
| 3 | Explains the situation and action clearly, with enough detail to understand the outcome |
| 5 | Explains complex information simply, adapts to the audience, and checks for understanding |
This turns the interview scorecard form template into a real evaluation tool.
4. Decide whether to weight competencies
Equal weighting is the safest default. OPM's FAQ on scoring structured interviews recommends equal weights unless there is a clear, documented reason to do otherwise.
Use weights only when one competency truly matters more for performance. For example, a senior data engineer scorecard may weight technical design more than presentation style. A support manager scorecard may weight coaching and escalation judgment more than tool knowledge.
If you use weights, keep the math simple:
| Competency | Weight | Rating | Weighted score |
|---|---|---|---|
| Technical judgment | 40% | 4 | 1.6 |
| Problem solving | 25% | 3 | 0.75 |
| Communication | 20% | 4 | 0.8 |
| Collaboration | 15% | 3 | 0.45 |
| Total | 100% | 3.6 / 5 |
For many hiring teams, weights create more complexity than value. If the team is new to scorecards, start equal.
Interview Scorecard Template Excel or Google Sheets Setup
An interview scorecard template Excel file or Google Sheets version works well when the team does not have scorecards built into the ATS.
Use one tab per role and one row per candidate. Keep the full scoring guide in a second tab so interviewers can check anchors without opening a separate document.
Suggested columns:
| Column | Example |
|---|---|
| Candidate name | Alex Chen |
| Role | Customer Success Manager |
| Interview stage | Hiring manager screen |
| Interviewer | Nina Patel |
| Date | Interview date |
| Competency ratings | Communication 4, problem solving 3, ownership 4 |
| Evidence notes | Short factual notes for each rating |
| Overall score | Average or weighted average |
| Recommendation | Advance, hold, pass |
| Confidence | High, medium, low |
| Follow-up needed | Probe technical depth in next round |
Protect the anchor tab so people do not edit the definitions mid-process. If the rubric needs a change, apply it to the next role opening or the next hiring round, not halfway through the current candidate pool.
For teams using candidate screening software or ATS scorecards, the same structure still applies. Software can store the form, remind interviewers to complete it, and show side-by-side feedback. It cannot decide which competencies matter for the role. That is still recruiting work.
How to Use Scorecards in the Hiring Debrief
Scorecards are most useful when they shape the debrief. If the meeting starts with "So, what did everyone think?" the loudest person can still pull the group away from evidence.
Use this debrief flow instead:
- Collect all scorecards before discussion.
- Review must-have competency scores first.
- Ask interviewers to read evidence for high and low ratings.
- Discuss score differences only after evidence is visible.
- Decide whether gaps can be tested in another round.
- Record the final decision and reason.
This is especially useful when the hiring team has mixed signals. One interviewer may rate communication low because the candidate rambled. Another may rate it high because the candidate wrote an excellent case exercise. The notes show whether they assessed the same thing or different parts of the role.
If your team already uses a candidate screening process, connect the scorecard to each stage. Early screening might check must-have requirements. First interviews might rate communication, motivation, and baseline role fit. Later interviews can rate deeper technical or leadership competencies.
For high-volume roles, scorecards can also connect to AI candidate screening. Candidates answer the same first-round questions, recruiters review summaries and evidence, then interviewers use the scorecard for the live or async evaluation step. The point is consistency, not removing human judgment.
Mistakes That Make Interview Scorecards Less Useful
Most scorecard problems come from design choices that look harmless.
Too many competencies
A scorecard with 12 categories feels thorough, but interviewers will not score all of them carefully. Use fewer categories and better notes.
Generic traits
"Leadership," "culture," and "communication" are too broad unless you define them. Write the behavior you want to see.
Scores without evidence
A row of numbers is not enough. Require notes for every score, especially 1s, 2s, and 5s.
Group discussion before scoring
Interviewers should submit scorecards before the debrief. Otherwise, people anchor on the first opinion and adjust their feedback to match the room.
Changing the scorecard mid-search
If you change criteria after meeting candidates, comparisons get messy. If the role requirements truly changed, restart the evaluation standard and document why.
Treating the total score as the whole decision
The total score is a signal, not the hiring decision. A candidate with a high average may still fail a must-have. A candidate with a medium score may deserve another round if the gaps are testable and the must-have evidence is strong.
The EEOC's guidance on employment tests and selection procedures reminds employers that selection procedures should be job-related and used consistently. Scorecards help with that only when the criteria are tied to the role and applied the same way for every candidate.
Key Takeaways
- An interview scorecard template should rate 4 to 6 job-related competencies, not vague personality traits.
- Use a 1 to 5 scale with written anchors so interviewers score candidates against the same standard.
- Evidence notes are part of the scorecard, not an optional comment box.
- Submit scorecards before debriefs to reduce anchoring and groupthink.
- Start with equal weighting unless the team has a documented reason to weight one competency more heavily.
- Use the scorecard throughout the structured interview process, from planned questions to final debrief.