Every failed search I have been asked to rescue started the same way: no executive job scorecard, just a job description someone pulled from the last time the role was open. Below are the questions CHROs, presidents, and P&L owners actually ask me about scorecards — asked in their words, answered without the consulting varnish. If you read nothing else, read the first two.
"Isn't a scorecard just a job description with different formatting?"
No. They are different documents built for different purposes, and confusing them is the root cause of most bad senior hires.
A job description describes activity. It lists responsibilities, reporting lines, and required years of experience. It is written to be posted, and it is written to be defensible in the blandest possible way. It tells a candidate what they will do.
A scorecard describes results. It has three parts: a mission (one paragraph on why this seat exists in the next 24 to 36 months), outcomes (four to seven dated, measurable results the person must produce), and competencies (the behaviors and capabilities required to produce those outcomes, ranked). The format was popularized by Geoff Smart and Randy Street's work on hiring method, and it has become the common language in board-level hiring for one reason: it forces disagreement to happen before candidates are contacted rather than after.
Here is the practical test. Take your current job description and ask: could two members of the interview panel read this and be looking for opposite people? With a job description, almost always yes. With a proper scorecard, no — because the outcomes are numbers with dates attached.
"Who actually has to sign it?"
Three signatures, minimum, before candidate one is approached:
- The hiring executive — the person the role reports to. They own the outcomes.
- The board or committee chair, for any role the board interviews. For a CFO, that is the audit chair. For a COO or divisional president, that is usually the comp committee chair or lead director.
- The search partner, internal or external. If your search partner will not put their name on the outcomes, they are telling you the role is not searchable as written, and you should listen.
I would add a fourth in most cases: the peer who will be most affected. If you are hiring a CFO and the CRO is not consulted on the outcomes, you are going to hire someone who wins the interview and loses the first commercial argument. That dynamic is covered in more depth in our guide to building a finance leadership team.
Signing is not ceremonial. The scorecard becomes the reference document for the slate, the interview debrief, the offer conversation, and the first-year review. If it changes mid-search — and sometimes it should — it gets re-signed, and the search restarts from the revised version.
"How specific do the outcomes have to be? Give me a real one."
Specific enough that a candidate could refuse the job on the basis of it.
Weak outcome: "Strengthen the finance organization and improve reporting."
Usable outcome, mid-market manufacturer preparing for a sale: "Close the FY26 audit with zero material weaknesses and no more than two significant deficiencies; compress close from 19 business days to 8 by Q3; stand up a 13-week cash forecast with variance under 5% by end of Q2; deliver a quality-of-earnings-ready data room within 90 days of a mandate."
Notice what the second version does. It tells a controller-profile candidate they are underqualified, tells a pure capital-markets CFO the job is heavier on plumbing than they want, and tells a private-equity-seasoned operator that this is squarely their work. The outcome sorts the market before you spend a dollar of anyone's time. Our board-ready playbook on hiring a CFO works through more of these variants.
The same discipline applies outside finance. An industrial VP of Operations scorecard without a TRIR target and an OTIF target is not a scorecard — those two numbers are the language plant leadership actually speaks, and a candidate who cannot discuss both fluently will not survive the first plant walk. A SaaS CRO scorecard should name net revenue retention, CAC payback in months, and the Rule of 40 threshold the board is holding you to. Candidates will argue with your definitions. Let them. The argument is the interview.
"What about roles where the regulation defines the job?"
Then the regulation goes in the scorecard, by name, with a date.
For a company that has recently listed or is preparing to, the CFO scorecard has to be dated against filing mechanics rather than against ambition. Whether SOX 404(b) auditor attestation applies depends on filer status, and a newly public company's first management report on internal control over financial reporting is generally not due until its second annual report. That single fact determines whether the mission is "remediate and industrialize controls" or "tell the equity story" — and those are two different people. The SEC's own guidance for companies going public is a better starting point for this section than any recruiter's opinion.
In mining and minerals, the regulatory shift is more recent and more often missed. Regulation S-K subpart 1300 replaced Industry Guide 7 for fiscal years beginning on or after January 1, 2021, and it requires a qualified person behind technical report summaries. A Chief Geologist or VP Technical Services scorecard for a US-listed issuer therefore carries a named regulatory competency, not a soft "strong technical credibility" bullet. The final rule text is worth handing to your hiring panel before they interview anyone. Get this wrong and you will slate excellent geologists who cannot sign what you need signed.
"Does the scorecard create legal exposure?"
Written carelessly, yes. Written properly, it reduces exposure.
Selection criteria are subject to the EEOC's guidance on employment tests and selection procedures, which sits on the Uniform Guidelines at 29 CFR Part 1607. The core requirement is job-relatedness. A scorecard that says "10+ years in the industry" invites a challenge. A scorecard that says "has closed and integrated at least two acquisitions of comparable scale" is anchored to work product and survives scrutiny far better.
Two rules I hold to. First, every competency must trace to an outcome — if you cannot draw the line, delete the competency. Second, counsel reviews the competency section on any role where the slate will be documented, which at this level is all of them. The document you built to make a good decision is the same document that explains the decision two years later.
"How long should this take, and who writes the first draft?"
Two to three weeks of elapsed time, six to ten hours of executive time. The search partner writes the draft; the company edits it. That order matters. When the company writes first, you get the internal consensus document — everyone's priority included, nothing prioritized. When the search partner drafts after interviewing stakeholders separately, the contradictions surface on paper where they can be resolved.
A workable sequence:
- Stakeholder interviews, individually. Six to ten people, 45 minutes each, never in a group. Group sessions produce agreement, not truth.
- Draft mission and outcomes. Search partner writes. Outcomes get owners and dates.
- Contradiction review. The partner presents the places stakeholders disagreed. This is the meeting that saves the search.
- Rank the competencies. Not a list of twelve. Five, in order, with the top two treated as non-negotiable.
- Sign, then define the market. Target company list, off-limits constraints, compensation philosophy. AESC member firms work under a published Code of Professional Practice governing confidentiality and off-limits obligations, and the signed scorecard is what justifies the approach strategy.
If step three produces no contradictions, the interviews were too shallow. Go back.
"We already started the search. Is it too late?"
It is late, not too late. Stop the slate and build the scorecard against the candidates you have already seen — reverse-engineering it is uncomfortable but honest, and you will usually find that two of your four finalists were being measured against different jobs. That discovery is worth the pause.
The warning sign that you needed one and skipped it: the debrief where two credible executives describe the same candidate as "exactly right" and "not close." That is never a candidate problem. It is a definition problem, and no amount of additional interviewing fixes it. The mechanics of how this gets handled inside a properly run process are covered in our overview of how retained executive search actually works, and if you are still selecting a partner, the evaluation framework for choosing a search firm includes the scorecard question you should be asking in the pitch.
"What does a good scorecard look like when the hire is working out?"
It gets used after the offer. The best version of this document becomes the new executive's first-90-days plan on day one, the basis of their first board update, and the reference point for their year-one review. When the outcomes on the scorecard and the outcomes in the compensation plan are the same outcomes, alignment stops being a word and becomes an arithmetic fact.
When a search goes wrong, the post-mortem almost never finds a sourcing failure. It finds a definition failure that sourcing was asked to solve. Write the scorecard first. It is the cheapest hour of the entire engagement and the only one that determines the rest.
Questions we get after the first draft
A few that come up on nearly every engagement.
Frequently asked questions
How many outcomes should an executive job scorecard have?
Four to seven. Fewer than four usually means the role has not been thought through; more than seven means nothing has been prioritized and the executive will optimize for whichever outcome their manager mentions most often.
Should the scorecard be shared with candidates?
Yes, at the appropriate stage. Serious senior candidates treat the scorecard as evidence the company knows what it wants. Share it once a candidate is past first interview. Candidates who push back on specific outcomes are giving you free diligence on whether the targets are realistic.
What if the board and the CEO disagree on the mission?
Then you do not have a search yet. That disagreement will resurface at the offer stage or, worse, in the new executive's first six months. Resolve it in the contradiction-review meeting before any candidate is contacted.
Can we use the same scorecard if the search stalls and restarts six months later?
Rarely without revision. Dated outcomes go stale, and a six-month gap usually means the business context changed. Re-date the outcomes, re-rank the competencies, and get the signatures again.
Does a scorecard work for a first-time role that has never existed?
It works better there than anywhere. For a net-new seat there is no incumbent to anchor on and no prior job description to recycle, so the mission paragraph is doing all the work of defining why the seat exists. Expect the first draft to be wrong and to need two full revisions.