Capability Handoff Checklist¶
Transfer checklist — instantiates Dependency-Capture Exit Design
A signed-off transfer checklist that proves the receiving team can actually perform each captured task before the handoff is allowed to complete.
A role becomes a trap when one person is the only one who can do the work, and the surest way out is to make someone else demonstrably able to do it. Capability Handoff Checklist is the itemized, sign-off-gated instrument that turns "we trained them" into "they can be observed doing it unaided." Its defining move is that competence is proven by performance, not asserted by a document or a training log: each captured task is listed, and the item is only checked when a named successor performs it independently, watched by someone other than the outgoing incumbent. When every item is closed, the checklist itself is the authority to complete the handoff and wind the incumbent down to a bounded, temporary support role. It transfers capability into people; it is not the place where that knowledge gets written down for anyone at all — that is a different sibling's job.
Example¶
At a regional hospital, one dialysis nurse — call her the senior operator — is the only person cleared to set up, prime, and troubleshoot the machines on the renal ward. When she is on leave, treatments are rescheduled; when she talks about retiring, managers quietly panic. Rather than beg her to stay, the ward builds a Capability Handoff Checklist. It enumerates the tasks that actually live only in her hands: priming a new circuit, responding to a venous-pressure alarm mid-session, swapping a clotted dialyzer without losing the blood volume, and the end-of-day disinfection cycle.
Each line names a specific successor and a supervising observer who is not the senior operator — a charge nurse or the unit educator. An item is checked only after the successor performs it start-to-finish on a live or simulated session, unaided, twice. The alarm-response line stays open for weeks because the first two nurses freeze the first time; that open box is the point. When the last item closes for at least two nurses per shift, the checklist authorizes the handoff: the senior operator moves to a defined, time-boxed "call me only for X" support boundary, and the ward is no longer captive to a single person.
How it works¶
- Enumerate the captured tasks, not the job title. The checklist decomposes the role into the concrete, tacit-heavy operations that genuinely bottleneck on one person, ignoring the routine parts anyone already covers.
- Assign named successors and an independent observer. Every task maps to specific people who must own it afterward, and the person signing off is deliberately not the incumbent, so "they've got it" cannot be self-graded by the one with an interest in staying needed.
- Check by unaided performance. An item closes only on demonstrated independent execution — ideally repeated, and under the failure conditions that matter — never on attendance or a nodded-through walkthrough.
- Gate the handoff on completion, then bound the residue. Full closure is the trigger to complete the transfer; the incumbent is retained only within an explicit, shrinking support window so the fallback does not silently become permanent dependence again.
Tuning parameters¶
- Coverage depth (n-deep) — how many successors must clear each task. Requiring two or three per shift removes single-person risk but costs more training time; one is faster but rebuilds a bottleneck.
- Demonstration bar — talk-through vs. supervised live execution vs. unaided-under-stress. Raising it makes the sign-off mean more and slows closure; lowering it lets hollow check-marks through.
- Observer independence — how far the sign-off authority sits from the incumbent. Full independence resists capture; convenience (letting the incumbent grade) reintroduces exactly the incentive you are fighting.
- Residual window — how long and how narrow the incumbent's post-handoff support is. Tight windows force real independence; generous ones keep the dependency alive under a new label.
When it helps, and when it misleads¶
The checklist's strength is that it makes capability observable and gate-able: it converts a diffuse fear ("what if she leaves?") into a finite list whose completion is a defensible green light. It also resists the incumbent's most natural defense — the claim that the work is too subtle to transfer — by demanding demonstration rather than accepting assertion.
Its classic failure is the hollow tick: items marked complete after a demonstration too gentle to count, so the paperwork says "transferred" while the ward still calls the senior operator at the first real alarm. This is the training analog of see one, do one, teach one[n1] taken as a slogan rather than a standard — the "do one" done once, in easy conditions, and waved through. The guard is to keep the sign-off authority independent of the incumbent and to include the failure-mode tasks explicitly, since those are precisely the ones a captured expert has an interest in leaving unchecked.
How it implements the components¶
capability_and_knowledge_transfer_plan— the checklist is the operational transfer plan for hands-on competence: task list, successors, and the demonstration bar each must clear.handoff_and_sunset_trigger— full closure of the list is the concrete trigger that authorizes completing the handoff and standing the incumbent down.residual_support_boundary— it defines the bounded, shrinking window in which the outgoing incumbent may still be called, so the fallback cannot quietly become permanent.
It does not externalize that knowledge into open, portable artifacts anyone could pick up (substitute_or_second_source_path, dependency_pathway_map) — that's Open Documentation Package; the checklist transfers competence into named people, not documents.
Related¶
- Instantiates: Dependency-Capture Exit Design — supplies the demonstrated-capability precondition the exit depends on.
- Consumes: Open Documentation Package — successors train against its runbooks; the checklist verifies they can act on them.
- Sibling mechanisms: Dependency-Reduction Scorecard · Exit-Readiness Review · Fixed-Term or Sunset Mandate · Independent Needs Assessment · Open Documentation Package · Outcome-Based Contract · Post-Exit Dependency Audit · Rotation or Term Limit · Second-Source Review
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: A signed-off transfer checklist that proves the receiving team can actually perform each captured task before the handoff is allowed to complete, making its operative form a bounded evaluation of existing evidence or work that produces a finding or disposition.
Independent corroboration: The frozen evidence defines Capability Handoff Checklist as 'A signed-off transfer checklist that proves the receiving team can actually perform each captured task before the handoff is allowed to complete', so its operative form is Assessment, Review & Assurance.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Knowledge-transfer and operations practice supplies a signed handoff gate that closes only when the receiving team demonstrates each transferred task.
Related originating lineages:
- Education & Pedagogy — Competency-based assessment contributes observed performance rather than attendance or exposure as the evidence of readiness.
- Medicine & Healthcare — Clinical apprenticeship supplies supervised demonstration and the see-one, do-one, teach-one lineage that the checklist strengthens.
Review resolution: Organizational management is the agreed primary lineage because the checklist governs succession and transfer out of person-dependence. Education contributes demonstrated competence rather than attendance, and healthcare contributes observed sign-off for safety-critical tasks; their combination with a bounded residual-support rule is an Encyclopedia synthesis.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] See one, do one, teach one — the traditional surgical-apprenticeship aphorism that a trainee watches a procedure, performs it, then teaches it. It captures why demonstration matters but is widely criticized when "do one" is treated as sufficient rather than as the first of many supervised repetitions; the checklist's repeated, independent-observer bar is the corrective. ↩