How many roles should a succession plan cover?

Fewer than most teams think. Start with the roles where a sudden vacancy would cost real money or stall decisions: usually the executive team, one or two levels below it, and any single point of failure regardless of title. For a 500-person company that is typically 15 to 30 roles, not 200.

How long does it take to build a first succession plan?

A usable first pass takes two to four weeks: one week to agree on critical roles and criteria, one to score candidates, and one or two to pressure-test the results with the leaders involved. The version that earns board confidence comes from the review cycles after that, not from a longer first draft.

Who should own the succession plan?

HR runs the process; line leaders own the assessments; the CEO owns the outcome for executive roles. Plans fail when HR owns all three, because managers treat the plan as HR paperwork instead of their own bench.

How to Build a Succession Plan That Survives Reality

Most succession plans get built the same way: a board meeting is coming, someone asks "what's our succession plan?", and HR produces a spreadsheet over a long weekend. Names go in boxes. The deck gets presented. Everyone exhales.

Then a VP resigns in March and nobody opens the spreadsheet, because everyone already knows it was a guess.

If that describes your organization, you have company: a SHRM survey found only 21% of organizations have a formal succession plan, another 24% run an informal one, and 56% have nothing at all. That figure sits with the rest of the succession planning statistics we keep sourced and dated, which is the page to raid when you need numbers a board will accept.

This guide is about building the other kind of plan: one with criteria you can defend, readiness calls you actually believe, and a review rhythm that keeps it matched to the org as people move. None of it requires software, though the last section covers where software earns its keep.

You will also run into named frameworks while researching this, from the five Ds of succession planning to Maxwell's rule of 5. They are mnemonics rather than methods, useful for remembering the shape of the work and no substitute for the criteria and evidence below. If you want the plain definitions first, the glossary entries for succession and succession planning are the short version of everything that follows, and succession management is the umbrella term for the same work once it becomes an ongoing practice instead of a one-time exercise.

One scoping note before starting. What follows is succession planning, not replacement planning: a replacement list names who covers a seat tomorrow if it empties, and stops there. Succession adds criteria, development, and a readiness timeline. Both are worth having, and confusing them is the reason a lot of "plans" turn out to be a list of names, so the difference between the two is worth being deliberate about.

Key takeaways

Scope by cost of vacancy, not seniority. For a 300 to 1,000 person company that usually means 15 to 30 critical roles, including single points of failure no org chart flags.
Define five to eight observable, weighted dimensions per role before naming any candidates. Names come fast; agreement on what the names mean is the actual work.
Score candidates against the role profile, never against each other, and require a sentence of evidence per score.
Ready Now means you would hand this person the role rather than open an external search. If a search would still happen, they belong in a later window.
Every development action needs an owner and a deadline, and the whole plan needs a fixed review cadence, or it quietly becomes fiction.

Start with the roles that would actually hurt

The first mistake is scope. A plan that tries to cover every manager becomes a data-entry project, stalls around the 60% mark, and dies with its credibility. A plan that covers only the CEO misses where most of the damage actually happens.

The filter is cost of vacancy, not seniority. Ask three questions about each role:

If this seat went empty tomorrow, what stops moving? Revenue, releases, regulatory filings, a key account relationship?
How long would an external search take, realistically? Six months for a niche VP is normal. What breaks in those six months?
Does critical knowledge live only in this person's head? A principal engineer who owns the billing system can out-rank a VP on this list. This is key person risk, and it is the most commonly missed entry on a first-draft list.

For a 300 to 1,000 person company, this usually produces 15 to 30 critical roles: the executive team, a slice of the level below it, and a handful of single points of failure that no org chart flags. Write down why each role made the list. That sentence becomes useful every time someone asks why their role isn't on it.

Decide what ready means before naming names

Here is where most plans quietly go wrong. If you ask a room of leaders "who could take over for Maria?", you will get names in thirty seconds. What you won't get is agreement on what the names mean. One leader is answering "who could survive the first month," another is answering "who deserves it," and a third is answering "who I'd pick if I had to decide today."

So before any names: define what success in the role requires. Keep it to five to eight dimensions per role. A workable set for a sales VP might be: builds and retains a leadership team, forecasts within a defensible range, handles board exposure, manages cross-functional conflict, and knows the market cold. For a head of engineering the list looks different, and it should.

Two properties matter more than the specific labels:

Each dimension is observable. "Executive presence" is a horoscope. "Has run a QBR in front of customers without an executive in the room" is evidence.
The dimensions are weighted. Every role needs judgment; not every role needs board exposure. If everything counts equally, the scores flatten into mush.

This step feels bureaucratic and slow. It is also the entire difference between a succession plan and a popularity list. Budget a working session per role family and get the incumbent's input, because they know which parts of the job the org can't see.

Score candidates against the role, not each other

With a profile in hand, identify candidates. Cast wider than instinct suggests: the obvious successor is sometimes the incumbent's mirror image, and the role may need the opposite. Peers in adjacent functions, strong leaders a level down, and the person running the biggest cross-functional program all belong on the first-pass list. If the wider net is the part you find hardest, how to identify high-potential employees covers the signals worth trusting and the ones that just track visibility.

Then score each candidate against each dimension of the role profile. Not against each other. Ranking people head-to-head produces a horse race and a lot of politics; scoring against fixed criteria produces gaps you can act on. "Elena is a 2 of 4 on board exposure" leads directly to "get Elena in front of the board twice this year." A ranking leads nowhere except to a bruised ego when it leaks.

Practical rules that keep scoring honest:

Use a small scale. Four points is plenty. Ten-point scales generate false precision and hour-long debates about the difference between a 6 and a 7.
Require a sentence of evidence per score. Scores without receipts revert to reputation.
Record who scored, and when. Assessments age. A score from two years ago describes a different person.
Calibrate across raters before you trust cross-team comparisons. One manager's 3 is another's 4; a calibration pass in a talent review is how you find out. If that gap shows up every cycle, the fix is training the raters themselves, not adding another column to the spreadsheet.

Put readiness windows on every candidate

A list of scored candidates still isn't a plan. The plan emerges when you translate scores into readiness: who could take the role now, who needs about a year, who is two to three years out.

The standard readiness windows are Ready Now, Ready in 1 Year, and Ready in 2 to 3 Years, and the discipline is refusing to inflate them. A Ready Now call means this: if the incumbent resigned this afternoon, you would give this person the job rather than open an external search. If the honest answer is "we'd probably run a search anyway," they are not Ready Now, and pretending otherwise is how boards lose faith in the whole exercise.

Seen across all critical roles, the windows become your bench strength picture: which roles have real cover today, which have cover coming, and which are exposed. Expect the first pass to be uncomfortable, and know that the discomfort is normal: in DDI's Global Leadership Forecast 2025, only 20% of HR leaders reported having leaders ready now for their most critical roles, and internal candidates could immediately fill just 49% of critical positions. A first-draft plan showing half your critical roles with no Ready Now cover is not a failed plan. It is an accurate one, and accuracy is what makes the next step worth funding.

Close the gap with development that has a deadline

Every scored gap implies an action, and this is where plans separate into the two kinds. The failing kind writes "develop strategic thinking" next to a name and moves on. The working kind writes: "Owns the pricing-model overhaul in Q3. Presents the result at the January board meeting. Readiness review in December."

The pattern is exposure plus deadline. People close readiness gaps by doing pieces of the bigger job under real conditions: running the budget cycle, holding the room in an escalation, carrying an initiative that crosses functions. Courses and coaching support that work; they don't replace it.

Put a date on every development action and a name next to every date. Written down per person, that set of actions is an individual development plan, and it is the part of succession planning that survives contact with a busy quarter. Undated development intentions have roughly the shelf life of New Year's resolutions, and for the same reason.

Review on a cadence the calendar enforces

Plans decay. People get promoted, resign, burn out, and change their minds about what they want. A plan reviewed annually is wrong for most of the year, and everyone senses it, which is why nobody consults it when a real vacancy hits. Staleness is the most common single reason succession plans fail, well ahead of anything to do with the scoring model.

The cadence that works in practice:

Quarterly, 30 minutes, per executive-team role: did anything change? Any flight risk? Development actions on track?
Twice yearly, half a day, full plan: rescore where there's new evidence, recalibrate across leaders, update readiness windows, and retire stale actions.
Immediately, on trigger events: a resignation, a reorg, or a candidate leaving forces a review of every plan that person touched. This is where a stress test earns its place: model the departure, watch which other plans go thin, and fix the cascade before it happens for real. A departure with no notice is a different problem again, and emergency succession is the named stand-in you should already have for every critical seat.

The reviews only happen if they are on a calendar with an owner. "We review continuously" means never.

Reviews also need something to review against, which is where a short set of succession planning metrics earns its place: bench coverage on critical roles, how many readiness calls proved right when a seat actually opened, and how much of the plan changed since last quarter. Three numbers you check every review beat a dashboard nobody opens.

What a finished plan looks like

Finished is the wrong word, but a plan that works has a recognizable shape:

| Component | Failing version | Working version | | --- | --- | --- | | Scope | Every manager, or only the CEO | 15 to 30 roles chosen by cost of vacancy | | Criteria | "Gut feel," refreshed annually | Weighted, observable dimensions per role | | Scores | Unattributed numbers | Evidence-backed, dated, calibrated | | Readiness | Everyone is "ready with support" | Honest windows someone would act on | | Development | Themes without dates | Exposure assignments with deadlines | | Maintenance | Rebuilt before each board meeting | Quarterly touch, twice-yearly deep review |

On tooling: a spreadsheet can genuinely hold all of this for a while, and our free succession planning templates are the version of that spreadsheet with the criteria and readiness windows already laid out. If you want just the pieces this guide describes, the succession planning template covers scoping and scoring, the board succession checklist covers what a board will ask for, and the succession planning policy template covers the standing document: who decides, how often it's reviewed, and what gets written down. What a spreadsheet can't do is remember why a score changed, show you bench depth across thirty roles at a glance, or model what happens to four other plans when one person leaves. When the review meetings start spending more time reconstructing history than making decisions, that is the moment purpose-built succession planning software stops being a luxury.

But the order matters: criteria first, honest scores second, software third. A tool pointed at a popularity list just makes the popularity list load faster.