Interview Scorecard Template by Competency (Ready to Copy)
An interview scorecard template lists the few competencies a role needs, gives each a 1 to 5 scale with a plain description of what each score looks like, and leaves room for evidence and an overall recommendation. Copy the blocks below, keep five to seven competencies, and have every interviewer score before they discuss.
What a scorecard is for
A scorecard turns an interview from a feeling into a record. Without one, each interviewer remembers different things, weighs different traits and writes comments that cannot be compared. With one, every interviewer answers the same questions about the same competencies using the same scale, and you can lay the results side by side. That is the whole value. It does not make the decision for you, and it does not remove judgment. It makes judgment visible, so a hiring manager can see why one candidate scored a 4 on problem solving and another scored a 2. This guide gives you competency blocks you can copy into a document or spreadsheet today. Each block has anchors, which are short descriptions of what a 1, a 3 and a 5 look like. Anchors matter more than the numbers, because a bare number means something different to every person. If you also need the form interviewers fill in after the conversation, see our page on an /interview-feedback-form, and for the evaluation form for panels see the separate guide in this series.
Choose competencies before you write questions
Pick the competencies from the job, not from a generic list. Open the job description and ask what a person must be able to do in the first six months for the hire to count as a success. Turn those answers into five to seven competencies. Fewer than five and you miss things. More than seven and interviewers rush, copy ratings across lines or skip the lower ones. Each competency should be something an interviewer can actually observe in a conversation, such as how someone breaks down a problem, not a vague trait such as being a go-getter. Write each in a few words and attach a one-line definition. If your job description is vague, fix that first, and our /job-description-template can help you list the must-haves. A useful test: if two interviewers would disagree about what a competency means, it is not defined well enough yet. Rewrite it until a new interviewer could read the line and know what to listen for.
The rating scale and how to use it
Use a 1 to 5 scale with no half points and no zero. Define each end in words so people stop clustering at 3 and 4. The scale below is the one the competency blocks use.
| Score | Meaning | How to use it |
|---|---|---|
| 1 | Clear gap | The answer showed little or no evidence, or showed a worrying pattern |
| 2 | Below the bar | Some evidence, but weaker than the role needs |
| 3 | Meets the bar | Solid, specific evidence that the role needs |
| 4 | Above the bar | Strong evidence with good judgment and examples |
| 5 | Exceptional | Rare depth, clear impact and ability to teach others |
Two rules keep the scale honest. First, score only what you saw in this interview, not what the CV says or what you assume. Second, a 3 is a good score. If every candidate gets a 4, the scale has stopped telling you anything. Ask interviewers to write one line of evidence next to every score. A score without evidence is a guess, and a later reader cannot tell the difference.
Block 1: Role skill and craft
This block covers the hard skills the job depends on. Name the skill in the first column when you copy it, for example financial modelling, copywriting or backend design. The anchors stay the same, so the block works for many roles.
| Score | What you would hear or see |
|---|---|
| 1 | Cannot explain the core method, or describes it in a way that would cause errors |
| 2 | Knows the terms, but examples are shallow or borrowed from a team |
| 3 | Describes the method clearly and gives one real example with their own part in it |
| 4 | Explains trade-offs, says what they would do differently and handles a follow-up change |
| 5 | Teaches the method well, handles an edge case on the spot and has a track record of improving it |
Prompts to try: Tell me about the last time you did this from start to finish. What went wrong and how did you notice? What would you change if the volume doubled? Evidence line: write the example they chose, what they personally did and the result they described. Avoid scoring this block on confidence alone. A fluent speaker with a thin example should land at 2, and a quiet candidate with a specific, well-reasoned example can land at 4.
Block 2: Problem solving
This block covers how the person approaches an unclear problem. It works best with a live scenario drawn from the real job rather than a puzzle.
| Score | What you would hear or see |
|---|---|
| 1 | Jumps to an answer with no questions, or freezes when information is missing |
| 2 | Asks some questions but misses the main constraint or ignores the data given |
| 3 | Clarifies the goal, breaks the problem into parts and reaches a workable answer |
| 4 | Tests assumptions, weighs options aloud and names the risks of the chosen path |
| 5 | Reframes the problem, finds a simpler route and explains how they would check it worked |
Prompts to try: Here is a situation we faced last quarter. What would you want to know first? What would you do in the first week? What could make that plan fail? Evidence line: note the questions they asked, the assumption they challenged and the point where they changed their mind. Interviewers often reward polish here. Score the thinking, not the delivery, and let the candidate go slowly.
Block 3: Communication and collaboration
This block covers clarity, listening and how the person works with others. It is easy to inflate, so the anchors are concrete.
| Score | What you would hear or see |
|---|---|
| 1 | Answers wander, talks over the interviewer or blames others for every problem |
| 2 | Understandable, but needs repeated prompting or skips the point of the question |
| 3 | Answers the question asked, listens and gives a balanced account of a past disagreement |
| 4 | Adapts the explanation to the listener, checks understanding and credits others fairly |
| 5 | Makes a hard topic simple, invites challenge and describes turning conflict into agreement |
Prompts to try: Describe a time you disagreed with a colleague about priorities. How did you explain a technical or complex point to someone outside your field? Evidence line: note one sentence that was unusually clear or unclear, and how they described the other person. Remember that communication style varies across cultures and languages. Score clarity and listening, not accent, speed or small talk, and give non-native speakers time to think.
Block 4: Ownership and reliability
This block covers whether the person follows through, owns mistakes and manages their own work. Many teams care about it most and measure it least.
| Score | What you would hear or see |
|---|---|
| 1 | Cannot name a mistake, or describes every setback as someone else's fault |
| 2 | Owns outcomes only when asked, with vague details about what changed afterward |
| 3 | Gives a real example of a miss, what they did to fix it and what they do differently now |
| 4 | Raises problems early, tracks their own commitments and helps others recover |
| 5 | Builds routines others adopt and describes taking on unowned work with clear results |
Prompts to try: Tell me about a deadline you missed. When did you first know it was at risk and who did you tell? What is a task you took on without being asked? Evidence line: write the date or moment they raised the risk, and what they did next. Be careful not to penalise candidates who had unreliable managers or unstable jobs. Look for the part they controlled.
Block 5: Learning and adaptability, plus an optional block
This block covers how fast someone picks up new tools, feedback and changes in direction.
| Score | What you would hear or see |
|---|---|
| 1 | Resists feedback or relies only on what they already know |
| 2 | Learns when told to, with no example of learning on their own |
| 3 | Describes one skill they picked up recently and how they practised it |
| 4 | Seeks feedback, applies it quickly and can show before and after |
| 5 | Learns across areas, shares what they learn and adapts calmly when plans change |
Prompts to try: What is something you learned in the last six months that you did not know how to do? Tell me about feedback that stung and what you did. Evidence line: note the specific skill and the way they practised it. Add an optional sixth block when the role needs it. For people managers, add Leading others, with anchors about setting expectations, giving feedback and developing people. For customer-facing roles, add Customer focus, with anchors about understanding needs and handling a difficult request. Keep the same five-level structure so the form stays quick to complete.
The overall recommendation and decision rule
After the competency blocks, add four fixed lines: strongest evidence, biggest concern, overall recommendation and the reason in one or two sentences. Use a four-level recommendation such as strong yes, yes, no and strong no, with no middle option, so interviewers must commit. Then agree a decision rule before the first interview, for example: no hire if any must-have competency scores 1, and hire only if the average of must-haves is at least 3. These numbers are examples, and you should set your own. Write the rule on the form so nobody argues about it afterward. A rule does not replace the final conversation. It sets the starting point, and the group can still decide to override it, as long as the reason is written down. Keep a copy of the filled forms with the candidate record, because they are your evidence if someone later asks why a hire or a rejection happened. Rules about records and candidate data differ by country, so check local law for how long to keep them.
Worked example with example numbers. Here is an example with made-up numbers for a customer support lead role. Three interviewers each score the five blocks on their own, and the scores are combined afterward.
| Competency | Interviewer A | Interviewer B | Interviewer C | Average |
|---|---|---|---|---|
| Role skill | 4 | 3 | 4 | 3.7 |
| Problem solving | 3 | 3 | 2 | 2.7 |
| Communication | 5 | 4 | 4 | 4.3 |
| Ownership | 3 | 4 | 3 | 3.3 |
| Learning | 4 | 3 | 4 | 3.7 |
The group sees a clear spread on problem solving, where interviewer C wrote that the candidate did not question the scenario. The decision rule says every must-have should average at least 3, and problem solving is a must-have at 2.7. Rather than hire or reject, the group schedules a short follow-up scenario with the same prompt and a different interviewer. This is the scorecard doing its job. It points the discussion at one gap with evidence, instead of leaving three people to trade overall impressions.
Common mistakes
These are the errors that make scorecards useless, with a fix for each.
| Mistake | Why it hurts | Fix |
|---|---|---|
| Too many competencies | Interviewers rush and copy scores | Keep five to seven |
| No anchors | A 3 means different things to everyone | Write what 1, 3 and 5 look like |
| Scoring after the debrief | Early opinions pull everyone along | Score alone, then discuss |
| Scoring from the CV | Mixes old information with live evidence | Score only what you saw |
| Everyone gives 4 | The scale stops separating candidates | Remind that 3 meets the bar |
| No evidence line | Scores cannot be checked later | Require one line per score |
| Changing the form per candidate | Results cannot be compared | Fix the form before round one |
If you only fix one thing, fix the order: write scores before talking. It costs nothing and removes the biggest source of distortion.
Checklist to review a template. Use this checklist to judge a template you found online, built in a spreadsheet or offered by a tool. Give zero, one or two points per line.
| Line | Question to ask | Score (0 to 2) |
|---|---|---|
| Fit to the job | Are competencies taken from this role, not a generic list? | |
| Count | Are there five to seven competencies? | |
| Anchors | Does each score have a written description? | |
| Evidence | Is there a required line of evidence per score? | |
| Independence | Are scores submitted before the group sees them? | |
| Decision rule | Is there a written rule for combining scores? | |
| Records | Can you keep and find filled forms by candidate? |
Twelve or more means the template is ready to use. Eight to eleven means fix the weak lines first. Below eight, start again from the blocks above.
Who this is not for
A competency scorecard is not for every hiring situation. For a single quick conversation with an obvious hire, such as a trusted referral for a short contract, a full form is more effort than the decision needs. It is also not a substitute for a structured process: if nobody agrees what the job needs, no template will fix it. And it should never be the only input, since work samples and references add evidence the interview cannot.
Where Rezumz fits
Rezumz is an AI hiring workspace for small and mid-size hiring teams. On a job you set the interview scorecard once, with up to 10 items rated 1 to 5 and an optional note on what a strong answer shows. By default it is the job's must-have skills plus Communication. Every new interview link starts from it, and each interviewer gets a private link with a one-time email code. Submitted feedback is locked, and changes are saved as new versions with a reason. Rezumz flags feedback that looks copied between interviewers and can rank candidates from the written evidence, with names hidden. People decide. Rezumz does not make the hiring call. It suits small and mid-size teams, and the Team plan is for 4 or more recruiters. It does not suit large enterprises needing deep HRIS or payroll connections, and it does not do one-click multiposting to job boards. Prices: a free plan with 2 free candidate analyses, $29 a month, $199 a year, or a limited $499 lifetime option. Team is $79 a month or $699 a year for up to 10 teammates. See /pricing, compare options at /compare, and try the scorecard in the live demo at /demo.
Frequently asked questions
How many competencies should an interview scorecard have?
Five to seven is a good range. Fewer than five misses parts of the role, and more than seven makes interviewers rush, copy scores or skip the lower lines. Choose competencies from the job description, give each a one-line definition, and make sure each can be observed in a conversation rather than guessed from a CV.
Should a scorecard use a 1 to 5 scale or a 1 to 3 scale?
Either can work if every level has a written description. A 1 to 5 scale gives more room to separate candidates, but only when the anchors are clear. Without descriptions, people cluster around 3 and 4. Whatever scale you choose, keep it the same for every interviewer and every candidate in the same hiring round.
When should interviewers fill in the scorecard?
As soon as possible after the interview and always before the group debrief. Scoring alone first stops the most confident voice from pulling everyone else along. If you need to take notes during the conversation, write facts and quotes, then convert them to scores once the candidate has left.
Can I reuse the same scorecard for different roles?
Reuse the structure and the anchors, but change the competencies to fit each role. A generic form tends to measure generic traits. Keep a base template with the rating scale, evidence lines and recommendation block, then swap in role skills and any extra blocks such as leading others.
Does Rezumz provide an interview scorecard?
Yes. On each job you can set the items every interviewer rates from 1 to 5, up to 10, with an optional note on what a strong answer shows. Each interviewer gets a private link, feedback is locked once submitted, and edits are saved as new versions with a reason. People make the hiring decision.