Handover Briefing and Transition File¶
Transition protocol — instantiates Authority Rotation and Term Limitation
Packages the open decisions, obligations, and tacit context of a departing authority into a transferable record and live briefing, so the role turns over without the institution restarting.
Rotation solves entrenchment but creates a new risk: the successor inherits the office and none of what the office knew. Handover Briefing and Transition File is the mechanism that carries a role's working memory across the gap — the open decisions, live obligations, deadlines, unwritten rationales, delicate relationships, and dormant risks that never appear in any org chart. The one idea that defines it is that it targets continuity, not tenure: it does nothing to bound how long anyone serves and everything to ensure the next holder starts informed rather than from zero. It has two inseparable halves — a transition file (the standing, structured artifact) and a briefing (the live, often overlapping conversation that transfers the tacit knowledge no document captures).
Example¶
A university's academic department is rotating its chair. The outgoing chair assembles a transition file: the tenure cases in flight, each with its timeline, dossier status, and the confidential reasoning of the committee so far; the budget's soft commitments that exist only as promises to the dean; a harassment grievance mid-process; the facilities contract that renews in March; the faculty member whose retirement is quietly expected. Then comes the briefing — two weeks of overlapping onboarding in which the incoming chair, and the associate chair who will carry day-to-day continuity into the new term, sit with the outgoing chair to hear what the file cannot say: which alliances are fragile, which "routine" approval is actually contentious, why a past decision was made the way it was. The result is that the new chair walks into the first tenure meeting knowing the stakes, rather than discovering them mid-vote.
How it works¶
What distinguishes this mechanism from generic documentation is that it captures reasoning and relationships, not just records, and it uses a living carrier:
- Structured file. Open items are organized by type — decisions pending, obligations owed, deadlines, risks, stakeholder commitments — each with its current state and rationale, not just its existence.
- Live briefing. The tacit layer — who to trust, what a silence means, why a rule is bent — is transferred in conversation, ideally with the incoming and outgoing holders overlapping for a bounded window.
- Deputy as continuity thread. A deputy or apprentice who spans both terms holds the operational memory so the whole institution does not hinge on one overlap conversation.
Tuning parameters¶
- File depth — exhaustive dossier versus a tight brief on live items only. Deeper preserves more but risks a data-dump nobody reads.
- Overlap duration — how long the outgoing and incoming holders serve in parallel. Longer transfers more tacit knowledge but shades toward the predecessor lingering past their exit.
- Custody — whether the file lives in an independent institutional archive or on the departing holder's own storage. Independent custody is what keeps the record from walking out the door.
- Confidentiality handling — how sensitive rationales (personnel, legal) are passed without breaching the people they concern.
- Deputy involvement — how much of the continuity load rides on a spanning deputy versus the direct handover.
When it helps, and when it misleads¶
Its strength is that it is the direct antidote to transition discontinuity[n1] — the failure in which a capable successor stalls for months simply because the context left with their predecessor. Done well, it makes turnover cheap enough that an institution can rotate freely without fearing each handover.
Its failure mode is that a file is only as honest as its author. A departing holder can curate it to flatter their tenure, omit the inconvenient, or — worse for the archetype — write it thin on purpose to remain indispensable, so that the successor keeps having to call. An over-long overlap has the mirror problem: the "briefing" becomes a channel through which the predecessor keeps deciding. The disciplines that guard against this are to store the file in an archive the institution controls rather than the person, to time-box the overlap firmly, and to have a third party (or the deputy) confirm the file is complete before the outgoing holder's authority actually ends.
How it implements the components¶
handover_and_continuity_packet— it is the packet: the structured, custody-controlled record of open decisions, obligations, rationales, risks, and stakeholder commitments.deputy_or_apprentice_pipeline— the overlapping briefing runs through a deputy or apprentice who spans both terms and carries operational memory into the next one.
It does not check whether the transfer actually took (entrenchment_signal_monitor — Entrenchment Audit) or set how long anyone serves (term_length_and_renewal_rule — Fixed Term-Limit Clause); it supplies the continuity those other mechanisms assume.
Related¶
- Instantiates: Authority Rotation and Term Limitation — the handover is the archetype's guard against turnover destroying institutional memory.
- Sibling mechanisms: Entrenchment Audit · Fixed Term-Limit Clause · No-Consecutive-Terms Rule · Rotating Chair Schedule · Sortition or Lottery Rotation · Staggered Board-Term Calendar · Sunseted Delegation Order · Cooling-Off Period
Editorial Notes¶
Form Classification¶
Form family: Protocol, Workflow & Routine
Rationale: Handover Briefing and Transition File operates as a repeatable ordered procedure or handoff sequence that coordinates action because it packages the open decisions, obligations, and tacit context of a departing authority into a transferable record and live briefing, so the role turns over without the institution restarting.
Independent corroboration: The frozen evidence defines Handover Briefing and Transition File as 'Packages the open decisions, obligations, and tacit context of a departing authority into a transferable record and live briefing, so the role turns over without the institution restarting', so its operative form is Protocol, Workflow & Routine.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Single lineage
Present-day reach: Multi-domain
Rationale: Succession planning and knowledge management developed transition files plus live handover briefings.
Related originating lineages:
- Public Administration & Policy — Governmental changes of office independently institutionalized formal transition books and briefings.
Review resolution: Both reviewers agree that organizational_management is primary: Succession planning and knowledge management developed transition files plus live handover briefings. I retain public_administration_policy only as formative lineage, not as a list of later applications. I resolve origin_mode as single_lineage because the mechanism is best explained as one continuous professional lineage. I resolve domain_reach as multi_domain because it transfers across several fields but is not a domain-free primitive. Encyclopedia synthesis is false because the exact generalized packaging is already established enough that encyclopedia-specific synthesis is not required.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] Institutional memory — the accumulated, largely tacit knowledge held by an organization's roleholders — is what a transition puts at risk; the transition file and briefing are the standard instruments for moving it off a departing individual and into the office. ↩