People Management
Build a Succession Plan for a Critical Role Without Promising a Promotion
A complete fictional team plan separates emergency coverage from longer-term readiness and future appointment. Two development paths, protected capacity, and a mixed checkpoint review keep unsupported promises out of the plan.
A succession plan should make a critical role less vulnerable while giving several people a fair, supported way to develop relevant skills. Keep three decisions separate: who covers an interruption now, what evidence would demonstrate broader readiness later, and who has authority to appoint someone to a future position. Being named in a development plan does not automatically grant coverage authority, establish full-role readiness, or decide an appointment.
This LandOffer guide develops a complete fictional engineering-team plan and a mixed-outcome review. Public USGS and OPM guidance was checked on October 25, 2026. The USGS desk guide is dated May 2018 and describes a federal context; its tools are examples, not rules for a private employer. All people, work evidence, capacity agreements, and reviews below are authored scenarios. No personnel records, appointments, or actual work assignments were changed.

Define the role's interruption risk before discussing successors
Describe the work that would become unowned before discussing any employee’s next title. List the role's recurring decisions, exceptional decisions, dependencies, and knowledge that currently sits with one person. Specify what must continue during an absence and what can safely wait for the responsible authority.
The USGS Succession Planning Desk Guide describes developing broad talent pools able to compete for essential positions. It identifies critical tasks and concentrated expertise among reasons to target a role. This supports examining continuity risk and development needs; it does not supply a private company's selection policy.
Avoid planning around rumors about an incumbent leaving. An interruption can arise without a resignation, and a role can change before any vacancy exists. Describe the operational dependency without collecting personal family, health, retirement, or other private information to justify it. Ask the incumbent to explain the work and knowledge-transfer needs through the organization's appropriate process.
For each responsibility, state the authority required. Someone who can assemble a decision packet may not be allowed to approve a vendor commitment, change a production setting, or make a staffing decision. Writing the authority boundary prevents a training activity from being mistaken for permission to approve work or commit the organization. Where the emergency plan needs a delegated authority, record its owner and approval as a separate requirement.
Keep a role-level continuity document separate from individual development notes. Team members need to know the contact and escalation path; they do not need access to every colleague's career interests or readiness assessment. Share each document with the audience that needs it, following the employer's personnel-information practices.
Case one: a filled continuity and readiness table
The fictional team depends on its Localization Platform Lead, Lina, to connect technical import checks, vendor handoffs, and exception decisions. This is an operational coordination role, not a universal job level. The plan's purpose is to keep essential localization work moving during a five-working-day interruption while building more than one development path.
Manager Rosa records the following role profile. The thresholds are invented operating assumptions for this example, not recommended service-level targets for every team.
| Critical responsibility | Interruption risk | Proposed immediate coverage | Broader readiness evidence still needed |
|---|---|---|---|
| Review translation-import evidence | Missing checks delay a scheduled handoff | Farah assembles the checklist and flags missing fields; authorized technical owner keeps acceptance decision | Independently explain a failed import, alternatives, and escalation boundary |
| Coordinate vendor handoff windows | Conflicting dates leave an unconfirmed delivery | Omar prepares the schedule and contacts list; vendor owner Mei retains commitment authority | Resolve a competing-window case with documented constraints and accepted owners |
| Route locale exceptions | Unowned exceptions may reach the wrong approver | Rosa receives unresolved exceptions and assigns the decision owner | Recognize when routine handling ends and a higher-authority decision is needed |
| Maintain operational knowledge | Contacts and decision rationale stay with Lina | Lina's existing notes are indexed for the agreed backup audience | Another reader can find the current runbook, owner, and latest decision without Lina's prompting |
The table does not designate Farah or Omar as the full substitute for Lina. It distributes bounded preparation work while keeping technical acceptance, vendor commitments, and exceptions with named authorities. No actual vendor contact, import, or production action occurred.
The emergency contact sequence is filled in: the team contacts Rosa when Lina's role is unexpectedly unavailable; Rosa confirms which coverage period applies and notifies the named owners through the approved workplace process. If Farah is also unavailable, Rosa asks the technical owner to handle the evidence review or defer the handoff. Omar's coordination work does not expand into technical approval by default.
The capacity agreement is equally specific. Farah's manager reserves two hours per week for development and postpones an optional reporting cleanup. Omar receives two hours by reducing a nonessential status-presentation assignment. Lina reserves one hour for knowledge transfer, with Rosa taking one routine coordination meeting off her calendar. These are fictional accepted planning assumptions, not evidence that real calendars were changed.
The team is not claiming five-day full-role coverage. Its completed gap statement says: “Evidence assembly and scheduling preparation have proposed backups; final technical acceptance and vendor authority remain dependent on the named owners. An overlapping absence of those owners remains a risk requiring Rosa's decision.” That is more useful than an unsupported “successor ready” label.
Separate demonstrated ability, interest, and available capacity
OPM's current succession-planning page emphasizes assessing key positions, talent risks, readiness, and development needs. Its context is agency support. For this fictional team, those ideas become task-specific questions rather than a numerical ranking of employees' worth.
Farah's recorded evidence is a reviewed import-check example where she identified an invalid language code and correctly escalated an acceptance question. She wants deeper technical ownership but has not expressed interest in vendor negotiation. Omar's evidence is a completed schedule-conflict exercise and a clear ownership handoff; his independent technical diagnosis is unobserved. He is interested in broader coordination work, subject to the two-hour capacity limit.
“Unobserved” is different from “cannot do it.” Record the work sample, date or exercise version, evaluator, and what help was required. Avoid filling gaps with confidence, visibility in meetings, willingness to work evenings, or similarity to the current incumbent. The employer should apply its own fair development and selection processes; this example makes no universal legal or policy claim.
Do not assume a technical expert wants the whole coordinating role. Ask about the actual responsibilities, including the less visible work, and allow an employee to decline a development activity without inventing a negative performance conclusion. Interest and capacity can change, so both need review rather than a permanent label.
Case two: a completed development agreement and mixed review

The second asset extends the same fictional plan through a simulated four-week checkpoint. It is a written scenario, not a report of training or workplace testing performed for this article. The development agreement has an eight-week horizon, with the first checkpoint at week four and a final scope review at week eight.
| Participant and gap | Bounded development work | Support and capacity | Evidence required at checkpoint |
|---|---|---|---|
| Farah: independent diagnosis and decision boundary | Prepare an import-failure analysis using synthetic records; lead one reviewed explanation | Technical owner reviews; two hours weekly, optional cleanup deferred | Correctly separate observed failure, possible cause, and acceptance decision; escalate unresolved authority |
| Omar: technical-context depth | Build a vendor-window decision packet with a technical dependency section | Lina explains current dependencies; two hours weekly, presentation work reduced | Name the missing technical input and avoid promising a handoff date before its owner confirms |
| Lina: usable knowledge transfer | Index current runbook, contacts, and example decisions | One hour weekly; Rosa covers routine meeting | Second reader locates the authoritative note and identifies an outdated instruction |
| Rosa: coverage and opportunity oversight | Confirm decision owners and review learning access for other interested staff | Manager owns scope and workload decisions | Open gaps, capacity changes, and next development opportunities recorded |
At the simulated checkpoint, Farah correctly identifies the invalid-code symptom but needs a prompt to separate a proposed mapping change from the owner's acceptance decision. The reviewer records partial progress: evidence interpretation demonstrated with support, independent boundary judgment not yet demonstrated. Farah is not reclassified as ready for the full role.
Omar's packet correctly names a technical sign-off dependency and leaves the vendor date uncommitted. However, his second exercise is incomplete because an urgent assignment consumed the reserved time. Rosa records a capacity failure in the plan, not a lack-of-interest finding about Omar. The next two-hour block replaces another optional presentation task, subject to the same fictional manager agreement.
The second reader finds Lina's runbook but discovers that one contact note points to an outdated team alias. Lina corrects the index in the scenario; a subsequent reader can identify the current owner from the corrected note. The fictional second-reader check passes for the corrected contact note only. It does not prove the entire emergency procedure or every dependency has been exercised.
Rosa's filled checkpoint decision is: “Continue both development paths. Farah needs another unprompted boundary case; Omar needs protected time for the incomplete exercise. Knowledge lookup improved after one correction. Current emergency authority remains unchanged. No full-role readiness or appointment decision has been made.” At week eight, the plan still needs an independent boundary case from Farah and the completed technical-dependency exercise from Omar; neither result is supplied here.
Explain the appointment boundary in ordinary language
OPM's leadership-development guidance discusses preparing interested employees before supervisory transitions and using individual development planning to clarify aspirations. Those federal arrangements do not define another employer's promotion rules. Development evidence can inform a later decision while the future role, headcount, requirements, and authorized selection process remain separate.
Rosa's fictional discussion with both employees uses this wording:
This plan funds practice in responsibilities the team needs. It does not reserve Lina's position or promise a promotion. The current role remains occupied. If an opportunity arises, the organization will confirm its scope and use the applicable selection process. We will review your learning evidence and interests without treating this development assignment as an appointment.
The message also states what is promised in the scenario: the agreed practice scope, support, reserved time, and checkpoint discussion. Those are concrete management commitments the plan can review. “Nothing is guaranteed” should not become an excuse to leave an employee doing an additional job indefinitely without workload decisions or feedback.
If an actual temporary assignment needs different pay, title, reporting, access, or employment terms, route those matters through the authorized company process before relying on the plan. A backup contact list or manager's informal assurance does not settle them. Keep the current role holder's authority clear until a separate approved change occurs.
Maintain a living plan with honest unresolved risks
Review the role profile when responsibilities, dependencies, available people, or organizational priorities change. Recheck the profile when a vendor or technical acceptance requirement changes, because the previous coverage evidence may no longer apply. An assessment's date and scope matter as much as its label.
For this example, the finished review pack contains the responsibility table, five-day coverage boundaries, accepted capacity substitutions, two development agreements, synthetic exercise evidence, and the week-four decision. Restricted individual notes stay with the appropriate manager; the team-facing document lists coverage contacts and escalation responsibilities. No real confidential candidate data is present.
Measure the work directly: which responsibilities have an authorized backup, which require supervision, which evidence is incomplete, and which dependencies remain uncovered. Record the demonstrated responsibility and required support; workshop attendance alone does not establish readiness to carry the role. Equally, a limited exercise should not be turned into a broad judgment about an employee's future potential.
The next review asks whether Farah completed an unprompted boundary case, whether Omar received the promised time, and whether the knowledge index remains usable. Until then, the emergency plan and future appointment remain separate. Save those open questions with their owners; return to LandOffer for related people-management guides after documenting the support and authority the team actually agreed.


