Most small business hiring decisions come down to gut feel — and gut feel has a terrible track record. You interview three candidates, like two of them, and then spend a week second-guessing yourself before picking whoever felt "right" in the moment. Three months later, you're not sure you made the right call.
An interview scorecard fixes this. It's a simple tool that forces you to evaluate every candidate against the same criteria, before you start comparing people to each other. It takes maybe 10 minutes to set up and makes your hiring process dramatically more consistent.
Here's a free template, plus exactly how to use it.
What is an interview scorecard?
An interview scorecard is a structured form you fill out immediately after each interview. It lists the specific skills, traits, and qualities that matter for the role, and gives you a way to rate each candidate on those criteria while the conversation is still fresh.
The key word is before. You define what "good" looks like before you start interviewing — not after you've already been charmed by someone's personality or rattled by a bad handshake.
A scorecard typically includes:
- The criteria you're evaluating (usually 4–7 things)
- A rating scale for each criterion (1–4 or 1–5 works well)
- A space for notes on each criterion
- An overall recommendation (hire / no hire / strong hire)
That's it. No fancy software required.
The free interview scorecard template
Copy this into a Google Doc or spreadsheet and adapt it for any role.
Interview Scorecard
Candidate name: Role: Interviewer: Date: Interview format: (phone / video / in-person)
Rating scale: 1 = Strong no — clear gap or red flag 2 = Leaning no — some concerns 3 = Leaning yes — meets expectations 4 = Strong yes — exceeds expectations
| Criterion | Rating (1–4) | Notes |
|---|---|---|
| [Criterion 1] | ||
| [Criterion 2] | ||
| [Criterion 3] | ||
| [Criterion 4] | ||
| [Criterion 5] | ||
| Culture / values fit | ||
| Communication |
Total score: ___ / 28
Overall recommendation: ☐ Strong hire ☐ Hire ☐ No hire ☐ Strong no hire
Top strength:
Biggest concern:
Would you work with this person again if you could? (yes / no / maybe)
The last question — "would you work with this person again" — is one of the most useful gut-check questions in hiring. It surfaces instinctive hesitation that ratings alone sometimes miss.
How to set your criteria (the part most people skip)
The template above has placeholder criteria because the right criteria depend entirely on the role. A scorecard for a customer support hire looks nothing like one for a bookkeeper or an operations manager.
Here's how to pick yours.
Start with the actual job
Write down the 3–5 things this person absolutely must be able to do in the first 90 days. Not the full job description — just the core deliverables that define success or failure in the role.
For a customer support rep, that might be:
- Handles 40+ tickets per day without quality slipping
- Resolves complaints without escalating to a manager
- Maintains a 4.5+ CSAT score
Those outcomes tell you what to evaluate in an interview.
Translate outcomes into interview criteria
For each outcome, ask: what skill, trait, or experience predicts whether someone can do this?
Using the customer support example:
- Speed + accuracy → evaluate attention to detail and prioritization
- Complaint resolution → evaluate emotional regulation and judgment
- CSAT → evaluate empathy and communication style
Those become your scorecard criteria.
Keep it to 5–7 criteria max
More than 7 and you end up averaging things out anyway — you lose the signal. Pick the criteria that truly differentiate a good hire from a mediocre one, and leave the rest out.
How to use the scorecard in practice
Fill it out immediately after the interview
Not the next day. Not after your next meeting. Right after the interview, while specific moments and answers are still in your head. Ratings get murkier fast — after 24 hours, you're mostly remembering your overall impression, not the details that should inform it.
Block 10 minutes after every interview specifically for this.
Rate before you discuss with others
If you have multiple people interviewing the same candidate, everyone should fill out their scorecard independently before comparing notes. The moment you talk to someone else first, your ratings start drifting toward theirs — especially if they're more senior than you.
This is called anchoring bias, and it quietly ruins a lot of panel interviews. Independent scoring prevents it.
Use the notes field, not just the numbers
A rating of "2" on communication doesn't mean much by itself. A note that says "gave one-word answers to follow-up questions, struggled to explain past decisions clearly" means something. When you're comparing three candidates a week later, you'll thank yourself for writing it down.
Compare candidates against the role, not each other
This is the most important shift a scorecard enables. Instead of asking "who was better," ask "who meets the bar for this role." Those are different questions — and the second one is the right one.
If you're hiring a bookkeeper and your bar is a score of 18+ out of 28, then any candidate above that threshold is a viable hire. If two candidates both score 22, you don't need to agonize over which is "better" — you pick based on availability, start date, or comp. If nobody hits 18, you keep looking.
Common mistakes with interview scorecards
Setting criteria after you've already interviewed someone. This defeats the whole purpose. Define criteria before the first call.
Using vague criteria like "culture fit" without defining what that means. Culture fit is worth evaluating, but you need to define it. Is it someone who works well independently? Someone who gives direct feedback? Be specific.
Overweighting the final interview. Candidates who make it to round three have often been briefed by recruiters or prepped by friends who know your company. Their polish in the final round doesn't always reflect how they'll perform on the job. Weight criteria consistently across rounds.
Ignoring a bad score because you like the person. The scorecard is supposed to create friction here. If someone scores a 1 on a critical criterion, that's a red flag — not something to rationalize away because they were likeable in person.
Adapting the scorecard by role type
Here are example criteria for three common small business hires:
Operations / generalist hire
- Problem-solving under ambiguity
- Process thinking (can they explain how they'd organize something complex)
- Comfort with changing priorities
- Written communication
- Track record of ownership (did they drive things to completion, or just participate)
Sales hire
- Ability to qualify leads quickly
- Objection handling
- Coachability (did they take feedback during the interview itself)
- Pipeline discipline and CRM habits
- Motivation and energy level
Customer support hire
- Empathy and tone
- Speed of information processing
- De-escalation instinct
- Written clarity
- Resilience to repetitive work
In each case, you're trying to operationalize what "good" looks like — so you can recognize it in a 45-minute conversation.
One more thing: keep a record
Store your completed scorecards. Even if you don't hire someone now, you may want to reach out in six months. Even more useful: after 6–12 months, compare your hiring scorecards to how people are actually performing. Are the criteria you're evaluating actually predicting success? Adjust them if not.
This is how you build a hiring process that gets smarter over time — instead of starting from scratch every time you have an opening.
Where Penroll fits
Penroll is an AI hiring copilot built for founders making a small number of hires per year — exactly the situation where a consistent, structured process matters most. It helps you define the role clearly, generate interview questions tied to your actual criteria, and keep candidates organized so nothing falls through the cracks. If you want a starting point before you even build your scorecard, generate a job post in Penroll to clarify what you're actually hiring for — that clarity makes your scorecard criteria much easier to define.