Taper and Handoff Plan¶
Workflow — instantiates Donor-Coupled Capacity Governance
Coordinates staged reduction, localization, substitution, or formalization of support with contingency buffers.
A Taper and Handoff Plan is the sequenced operating workflow that actually executes a change in support — the ordered set of steps, gates, and buffers by which a subsidy is reduced, localized, substituted, or converted into a formal standing arrangement without dropping the recipient. Its defining property is that it is a staged path, not a switch: support comes down (or hands over) in increments, each increment gated on a readiness milestone, each with a contingency buffer standing by in case the increment goes wrong. Where an agreement writes down what must be earned and a quota bounds how much is given, this plan choreographs the sequence of moves over time — which slice hands over first, what has to be true before the next slice moves, and what catches the recipient if a step falls short. It is the difference between a transition and a cliff.
Example¶
A large firm has run a subsidized internal build-and-deploy platform that every product team uses for free; the platform team absorbs the cost centrally. Leadership decides to sunset the central subsidy and move teams onto a self-funded, chargeback model — but flipping it off would strand dozens of teams whose pipelines depend on it. The platform group writes a Taper and Handoff Plan.
The plan lays out a staged transition: cohort by cohort, not all at once. Cohort 1 (three low-risk teams) migrates first; only when they run a full release cycle on the new self-funded tooling — a capacity milestone — does Cohort 2 begin. Each cohort's central support is tapered in three steps (full → advisory-only → off), with a rebound buffer held at every step: the old pipeline stays warm and reversible for two weeks after each cohort's cutover, so a failed migration rolls back instead of taking down a production deploy. The plan also names the localization path — teams that can't self-fund get the tooling open-sourced internally so they can run it themselves — and the formalization path for teams that opt to keep central support under a paid SLA. The subsidy still ends, but as a governed sequence with a floor under each step, not a date on which the lights go out.
How it works¶
The distinguishing work is sequencing and reversibility, not the terms or the diagnosis:
- Decompose the change into increments. Break the taper or handoff into slices small enough that any one going wrong is survivable, and order them by risk and readiness.
- Gate each increment on a milestone. No slice moves until the prior slice's readiness evidence is in — the plan advances on proof, so a stall in readiness stalls the taper.
- Hold a buffer at every step. Keep a rollback path or standby support live for a defined window after each increment, so a failed step rebounds into the buffer rather than into harm.
- Route each recipient to a transition mode. Reduce, localize, substitute, or formalize — the plan assigns each recipient the exit that fits it, rather than forcing one path on all.
Tuning parameters¶
- Increment size — how much support moves per step. Small steps are safe and slow and administratively heavy; large steps are fast and expose more at once.
- Gate strictness — how much readiness evidence a step demands before the next begins. Strict gates prevent premature cutover but can stall the whole sequence on one lagging cohort.
- Buffer duration — how long the rollback path or standby support stays live after each step. Longer buffers are safer but keep the subsidy partly running and delay the savings.
- Parallelism — how many increments run at once. Parallel cohorts finish sooner but strain the support team and correlate failures.
When it helps, and when it misleads¶
Its strength is that it makes a support change reversible and paced — the two properties that separate a handoff from an abandonment. It is the archetype's operating answer to its worst failure mode, "abandonment disguised as capacity building," because a genuine taper carries a buffer and a rollback while a disguised abandonment does not.
Its failure mode is the plan that exists on paper but is executed as a cliff anyway: buffers get cut for cost, gates get waived under schedule pressure, and the staged plan collapses into a hard cutover under a friendlier name. It also tends to be over-optimistic about how fast recipients build the capacity each gate assumes, so the sequence stalls or is forced through. The gradual, reversible ideal has a well-known software analogue in the strangler-fig pattern — replacing a system piece by piece while the old one keeps running until each new piece is proven[n1] — and its lesson is that the old support must stay alive until the new capacity is real. The classic misuse is pocketing the savings by killing the buffer early. The guarding discipline is to make buffer removal itself a gated step requiring evidence, not a default that happens on schedule.
How it implements the components¶
transition_or_formalization_path— it is the executed path: the sequenced reduce/localize/substitute/formalize route each recipient follows.local_capacity_milestone— each increment is gated on a readiness milestone, so the taper advances only as capacity proves out.withdrawal_rebound_buffer— it holds a live rollback or standby buffer at every step, so a failed increment rebounds into the buffer rather than into harm.
It does not measure the recipient's endogenous floor or stage the alternate catch — recipient_capacity_baseline and fallback_support_source belong to Withdrawal Rebound Drill; this plan schedules the taper, the drill rehearses surviving it.
Related¶
- Instantiates: Donor-Coupled Capacity Governance — supplies the staged, buffered path that turns a support change into a governed transition.
- Consumes: Capacity Milestone Agreement — its milestone gates are the readiness conditions each taper increment waits on.
- Sibling mechanisms: Withdrawal Rebound Drill · Capacity Milestone Agreement · Support Load Quota · Cross-Boundary Support Agreement
Editorial Notes¶
Form Classification¶
Form family: Representation, Specification & Plan
Rationale: Taper And Handoff Plan is defined in the frozen evidence as: Coordinates staged reduction, localization, substitution, or formalization of support with contingency buffers. Its operative deployed or enacted form is therefore Representation, Specification & Plan.
Nearest alternative: Protocol, Workflow & Routine — Protocol, Workflow & Routine can support this mechanism, but the evidence centers the concrete operation described above rather than the alternative family's defining operation.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Universal
Rationale: Taper and handoff plan derives most directly from organizational management's coordination, workflow, and capability tradition; its defining operation is to coordinates staged reduction, localization, substitution, or formalization of support with contingency buffers.
Related originating lineages:
- Education & Pedagogy — Education's instruction, assessment, and scaffolded-learning tradition provides a formative adjacent lineage for the same taper and handoff plan operation.
- Medicine & Healthcare — Clinical medicine, public health, and recovery practice supplies a parallel or contributing lineage for the mechanism's defining operation: coordinates staged reduction, localization, substitution, or formalization of support with contingency buffers.
- Public Administration & Policy — Public administration, policy implementation, and program oversight supplies a parallel or contributing lineage for the mechanism's defining operation: coordinates staged reduction, localization, substitution, or formalization of support with contingency buffers.
- Systems Thinking & Cybernetics — Systems thinking, feedback control, and cybernetics supplies a parallel or contributing lineage for the mechanism's defining operation: coordinates staged reduction, localization, substitution, or formalization of support with contingency buffers.
Review resolution: Both blind reviewers independently select organizational_management as the primary historical origin for the concrete operation—Coordinates staged reduction, localization, substitution, or formalization of support with contingency buffers. The queued differences concern reported ambiguity, alternate origin disagreement, origin mode disagreement, not the primary lineage. I retain every alternate that either reviewer explains, without a numeric cap, and choose origin_mode=cross_disciplinary_synthesis because the reviewers' combined evidence identifies material construction from multiple disciplines. domain_reach=universal records later portability rather than multiplying historical origins; confidence=medium is the conservative shared evidentiary level, and encyclopedia_synthesis=true preserves either reviewer's affirmative synthesis finding.
Attribution caveat: Tapering and handoff have healthcare, development-policy, and organizational lineages.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; medium confidence.
Notes¶
[n1] Strangler fig pattern — Martin Fowler's term for incrementally replacing a legacy system by growing the new one around it and retiring the old piece by piece, keeping the old running until each replacement is proven. The same "keep the old support alive until the new capacity holds" logic governs a good taper. ↩