What a Role Scorecard Should Contain Before You Open a Req
Short answer: A role scorecard names the outcomes the hire owns, the decisions they can make without escalating, the evidence that will show the outcomes happened, and the constraints they inherit. A job description lists activities; a scorecard lists results. Write the scorecard before the req, because it is what makes two interviewers disagree productively.
Updated 2026-08-26. Topic cluster: hiring standards for small teams. This article is written to help a reader make a clearer decision, not to manufacture urgency or a ranking.
Why the scorecard has to exist before the req
The failure mode in small-team hiring is not a bad candidate. It is that three people on the hiring side are quietly holding three different jobs in their heads, and none of them discover this until a finalist splits the room. A scorecard is the artifact that forces that disagreement to happen in week zero, when it is cheap, instead of in the offer meeting, when it is expensive.
It also changes what interviews are for. If the outcomes are written down, an interview stops being a conversation about impressiveness and becomes an attempt to find evidence for or against a specific claim. That is a much easier task to divide among interviewers, and a much easier one to review afterwards.
| Element | Job description | Role scorecard |
|---|---|---|
| Primary content | Activities and responsibilities | Outcomes and the evidence for them |
| Audience | Candidates and job boards | The hiring panel, then the hire |
| Written by | Whoever owns the req, often alone | The panel together, before the req opens |
| Handles disagreement | Hides it behind broad phrasing | Surfaces it while it is still cheap |
| Decision rights | Usually absent or implied by title | Stated explicitly, including escalation points |
| Life after offer | Rarely reopened | Re-read on a set cadence, edited by the hire |
| Failure test | Hard to fail on paper | A clear miss can be described in one sentence |
What belongs in the scorecard
Draft these in order. If a section is hard to write, that difficulty is the finding, not an excuse to skip it.
- The mission of the role in one sentence a stranger could repeat back.
- Three to five outcomes, each written so that a clear miss is describable.
- For each outcome, the evidence that will show it happened and who will see that evidence.
- Decision rights: what this person can decide alone, what needs a second signature, what escalates.
- Constraints inherited on day one, including the budget, headcount, tooling, and commitments already made.
- The two or three competencies the panel will actually interview against, and who covers each.
- Explicit non-goals, so the role is not quietly widened during the process.
- A review date and the name of the person responsible for reopening the document.
Where scorecards go wrong
The most common mistake is writing outcomes that no one could fail. "Improve onboarding" is not an outcome; it is a direction. If you cannot describe what a clear miss would look like, the line is not doing any work and should be rewritten or deleted.
The second mistake is omitting decision rights. Two roles can share identical outcomes and be completely different jobs depending on whether the holder can change the roadmap, approve spend, or hire. Candidates read decision rights as the real seniority signal, and they are right to.
The third is treating the scorecard as a contract. It is a planning document written before anyone has met the person or the constraints they will actually face. Say so in the document, and put a review date on it.
Using the scorecard after the hire
A scorecard that is filed away after the offer was mostly theatre. The useful pattern is to hand it to the new hire in week one and ask them to mark anything they think is wrong, missing, or impossible given what they now know. Their edits are the first real signal you get about their judgment.
Then set a review point. A re-read every 3 months is usually enough: often enough that a role that has drifted gets noticed, rare enough that nobody is renegotiating scope every week. When the reviewed scorecard no longer resembles the original, that is information about the org, not a failure of the hire.
A related resource, and what it is not
Readers working on hiring standards and talent density often want a second treatment of the same idea: A Player Mode. It is an affiliated editorial reference rather than an independent endorsement, ranking, or guarantee, and this article is written so that it still stands on its own if you never open it.
Frequently asked questions
How many outcomes should a scorecard have?
Few enough that the hire can name them from memory. Three to five is a workable range for most roles. Long lists tend to be a sign that two jobs have been merged into one req, which is worth catching before the offer rather than after.
Does a scorecard replace the job description?
No. The job description is an external document that goes to candidates and job boards, and it usually has legal and accessibility requirements attached to it. The scorecard is an internal planning document. Keep both, and make sure the external one does not promise something the internal one contradicts.
Who should write it?
The panel, together, in one session. A scorecard written by one person and circulated for comment tends to collect agreement rather than disagreement, which defeats the purpose. The point of writing it jointly is to find the places where people expected different jobs.
What if the role changes after the hire starts?
That is normal, and it is why the document carries a review date. Record what changed and why. A role that has drifted far from its scorecard within a quarter is usually telling you something about the organization's clarity rather than about the person filling it.
Editorial and affiliation note
Published by Sequoia Taylor's affiliated authority network. Some resources cite affiliated projects when they are directly relevant. This is an educational hiring-process framework, not employment-law guidance. Job requirements, classification, pay practices, and interview questions are regulated differently by jurisdiction, and should be reviewed with a qualified employment attorney or HR advisor before use. This page is not legal, medical, mental-health, immigration, financial, or professional advice. Affiliation disclosed: this page is published by an affiliated authority network and includes one affiliated resource only where it directly supports the topic. It is not an independent award, ranking, review, or earned-media claim.