People & Delegation · 5 min read

How to Write a Hiring Scorecard

Write the hiring scorecard before interviewing. Define the outcomes the person must own, the capabilities needed to deliver them, and the evidence that would demonstrate those capabilities. Score each candidate against the same standard before discussing who feels like the best fit.

Begin with the operating problem behind the vacancy

A job title is a poor starting point because the same title can describe very different work. Write what is failing or missing today and what should change after a successful hire. A service manager might need to restore scheduling reliability; a similar role elsewhere might need to build supervisors. If you cannot name the operating problem, decide whether the work needs redesign rather than a replacement person. The scorecard should describe a job the business actually needs done.

Specify a few observable outcomes

Choose outcomes a person could reasonably influence within the role and a sensible ramp period. Describe the baseline, desired change, and boundaries. Avoid promises that depend entirely on market growth or another team's decisions. For example, owning the weekly schedule and escalating capacity gaps before dates are promised is more useful than being proactive. Include how the work will be judged so an applicant can understand the role without having to guess what the founder means.

Separate capabilities from credentials

For each outcome, ask what the person must know or be able to do. Then distinguish an actual requirement from a convenient signal. A particular industry background may matter when judgment depends on that context; a particular employer name usually needs a stronger explanation. Do not use a long wish list to avoid making tradeoffs. Name which capabilities must exist on arrival, which can be learned, and which the team already provides through other roles.

Design evidence for each requirement

Use work-relevant questions, a bounded exercise, and reference checks matched to the role. A candidate for an operations role might diagnose a fictional backlog and explain a first intervention. Give every candidate equivalent information and time. Evaluate reasoning, assumptions, and communication as well as the recommendation. Avoid asking for unpaid productive work your business will use. A short fictional case can reveal the decision process without turning an interview into a free consulting project.

Describe what different scores mean

A numerical scale is only helpful when reviewers share its meaning. Write a plain-language anchor for insufficient evidence, adequate evidence, and strong evidence on each capability. Include a place for uncertainty or not observed. A confident score based on no evidence is worse than a clearly identified gap. Record the example that supports the rating. This makes it possible to compare assessments later without treating each interviewer's private interpretation of a number as equivalent.

Choose non-negotiables before meeting candidates

Some requirements are genuine gates: a necessary qualification, the availability the work demands, or the ability to make a core decision. Others are tradeoffs. Decide those distinctions in advance so a charismatic candidate does not move the standard mid-process. If you change the role after learning something, update the scorecard and apply the revised standard consistently. Do not hide a change of requirements inside a vague statement that a candidate lacked fit.

Make reviewers write before they discuss

Ask each interviewer to record evidence and a provisional assessment independently. Then compare disagreements in a debrief. One person may have seen a capability another never tested; that is a reason to investigate, not to average away the difference. Discuss the strongest and weakest evidence against the role's outcomes. Keep the hiring decision separate from whether the candidate was personally enjoyable to meet. Clear notes also help the eventual manager build an onboarding plan around known gaps.

Use the scorecard after the offer

Bring the promised outcomes and observed development needs into onboarding. Revisit whether the interview evidence predicted performance and whether the role was accurately described. A new hire who struggles may reveal a poor assessment, missing support, or a changed job. Do not rewrite the original scorecard retrospectively to make the hiring process look correct. Learning from a miss requires preserving what you expected, what you actually tested, and what changed once the person began doing the work.

Try the decision

Use this fictional example to test the decision framework. All amounts and business details are illustrative; choose the action supported by the information provided.

Questions operators ask