Role Rotation or Deputy Schedule¶

Continuity protocol — instantiates Role Expectation Architecture

A standing schedule of who holds a role now, who covers when they're out, and who takes over next — so the position survives any single person leaving the seat.

A Role Rotation or Deputy Schedule is the continuity plan for a role: a named roster fixing who occupies the seat, who deputizes during absence, and how the seat legitimately passes to the next holder. Its defining idea is making the role outlive any individual by pre-appointing coverage and succession before either is needed. Where a handoff checklist governs the content of a single transfer, this schedule governs the standing arrangement — who is up, who is backup, and who is next — treating turnover as a planned cycle rather than an emergency.

Example¶

A university department fills its chair on a fixed three-year rotation, with an associate chair serving as standing deputy. The schedule is public: current chair, associate (covers sabbaticals, recusals, and the chair's day-to-day absences), and the incoming chair named a full year ahead so they can shadow. Eligibility is written in — only tenured faculty who have served on the executive committee may enter the rotation — so the pool is pre-vetted rather than scrambled for. When the sitting chair takes medical leave mid-term, there is no vacuum: the associate steps up under an already-legitimate mandate, and because succession was scheduled, the department is not hostage to one person's calendar. The rotation also caps burnout — nobody is chair indefinitely — and defuses the single-point-of-failure risk of one irreplaceable holder.^[1]

How it works¶

The schedule pre-commits people to a seat over time. It has three moving parts — a primary who holds the role now, a deputy who covers gaps under a standing mandate, and a successor line naming who is next, ideally early enough to shadow — plus written eligibility for entering the rotation at all. Its distinctive property is that legitimacy is arranged in advance: because the mandate to cover or to succeed is already conferred, coverage and succession trigger automatically when the moment comes, instead of by a scramble for authority nobody clearly holds.

Tuning parameters¶

Rotation period — how long a term runs; short terms spread load and reduce capture but cost continuity and depth, while long terms build mastery but raise burnout and single-point-of-failure risk.
Deputy depth — one named backup versus a full bench; a deeper bench survives multiple simultaneous absences but dilutes how much each deputy actually practises the role.
Overlap / shadowing window — how long incoming and outgoing holders overlap; more overlap transfers tacit knowledge but costs double-staffing.
Eligibility width — how large the qualified pool is; widening it eases coverage but risks lowering the competence bar for who may hold the seat.
Mandatory versus voluntary rotation — forced turnover prevents entrenchment and capture but can eject a genuinely irreplaceable holder before a successor is ready.

When it helps, and when it misleads¶

Its strength is converting turnover from a crisis into a scheduled event and killing single-points-of-failure before they bite; it doubles as a quiet burnout guard, since no one holds a draining seat forever. Its failure modes: rotating too fast churns out accumulated expertise and institutional memory faster than each holder can rebuild it, and a schedule can be a paper plan — a named deputy who has never actually performed the role is coverage in name only. Its classic misuse is rotating to look resilient, a name in every backup slot, while never testing whether that backup can truly step in. The risk it exists to defeat is the bus factor — the number of people who would have to vanish before the role can no longer be performed^[1] — and a schedule only lowers it if the coverage is real. The discipline: make deputies actually exercise the role, name successors early enough to shadow, and pair the roster with a genuine transfer of knowledge rather than a transfer of title.

How it implements the components¶

The schedule fills the continuity slice — coverage, succession, and who may hold the seat — not what the role does while it is held:

handoff_substitution_and_succession_path — it is the standing path: primary to deputy on absence, outgoing to successor on exit.
appointment_legitimacy_and_exit_rule — it fixes in advance how the seat is legitimately entered, covered, and vacated, so a stand-in acts under a real mandate rather than an improvised one.
eligibility_and_competence_conditions — it names who may enter the rotation, keeping the coverage pool pre-qualified instead of assembled in a panic.

It does not define the role's duties or authority (expected_behavior_bundle, authority_and_permission_scope) — those are the Role Card and the RACI or Decision Participation Matrix; it does not script the item-by-item content of a given transfer — that is the Handoff Checklist; and it does not bring the incoming holder up to competence — that is the Onboarding and Role Shadowing Runbook.

Instantiates: Role Expectation Architecture — it is the continuity layer that lets a designed role persist across the people who hold it.
Consumes: Handoff Checklist — each scheduled change-over runs the checklist to move the role's live state cleanly.
Sibling mechanisms: Role Card or Participation Card · Role Review Retrospective · Handoff Checklist · Onboarding and Role Shadowing Runbook · RACI or Decision Participation Matrix · Swimlane or Service Blueprint · Role Charter · Position Description or Office Mandate · Delegation Letter or Authority Envelope · Conflict-of-Interest Disclosure · Role Compatibility Check

Notes¶

The schedule answers who and when, never what or how well. A rotation paired with neither a handoff of the role's live state nor onboarding for the incoming holder is a calendar with no substance — the seat changes hands on time and the work still falls through. Treat the roster as one leg of a tripod with the Handoff Checklist and the Onboarding and Role Shadowing Runbook.

References¶

[1] The "bus factor" (or truck factor) is the number of team members who would have to be lost before a role or body of knowledge becomes unrecoverable; a bus factor of one is the canonical single-point-of-failure. A deputy-and-succession schedule is a direct way to raise it — but only when the named backups have genuinely exercised the role. ↩