Sponsor Re-Engagement Notice¶
Protocol — instantiates Functional Vacancy Backfill
A formal, on-the-record prompt to a disengaged role-holder to resume the function — a documented last chance to re-engage before any backfill is activated.
Sponsor Re-Engagement Notice is the one mechanism in this archetype aimed at avoiding backfill rather than performing it. When a role-holder has gone quiet but is not gone, it delivers a formal, timestamped prompt to resume the function — naming what is missing, setting a cadence of checkpoints by which engagement must reappear, and stating what backfill activates if it does not. Its distinguishing purpose is dual: to give a recoverable incumbent a genuine chance to come back (often the cheapest fix), and to build the documented record that makes any later backfill legitimate rather than looking like a quiet coup. It is the deliberate pause between detecting a vacancy and acting on one.
Example¶
An industry standards consortium has a working-group chair — a volunteer from a member company — who has stopped scheduling meetings and has not advanced a stalled ballot in ≈4 months, blocking a specification three other groups depend on. Quietly replacing the chair would look like a takeover and could fracture the consortium's fragile inter-company trust.
So the steering committee issues a Sponsor Re-Engagement Notice: a formal, timestamped message that names the specific unmet functions (schedule meetings, drive the ballot to resolution), sets the cadence now expected (bi-weekly progress for the next month), and states the consequence (an acting chair is appointed under the group's charter if the checkpoints are missed). It is delivered at a defined checkpoint, not sprung as an ambush. One of two things follows. Either the chair re-engages and no backfill is needed — the best outcome — or the checkpoints pass unmet and the notice becomes the on-the-record justification that turns the subsequent backfill from "faction unseating a rival" into "documented, warranted step."
How it works¶
- Name the missing function specifically. Not "you seem disengaged" but "these named decisions are unmade" — concrete and answerable.
- Set a cadence of checkpoints. Explicit dates by which engagement must be visible, so re-engagement is testable rather than vibes.
- State the consequence. What backfill activates, and under whose authority, if the checkpoints go unmet.
- Put it on the record. Timestamped and retained, so the good-faith attempt is documented for whoever later judges the backfill.
Tuning parameters¶
- Tone and formality — a collegial nudge versus a formal notice. Softer preserves the relationship; firmer strengthens the due-process record.
- Checkpoint interval and count — how many missed checkpoints before backfill fires. More cycles are fairer to the incumbent but slower to protect the function.
- Consequence specificity — vague ("we'll consider options") versus precise ("acting chair appointed"). Precise notices deter and inform, but commit the issuer.
- Delivery breadth — private to the holder versus copied to stakeholders. Wider copy speeds legitimacy but can embarrass the incumbent into digging in.
When it helps, and when it misleads¶
Its strength is that it gives a disengaged-but-recoverable holder a real path back — usually far cheaper than a backfill — while simultaneously laying the legitimacy trail that later converts a backfill from "coup" into "warranted, documented step." It is the governance analogue of a notice-and-cure period.[n1]
Its failure mode is degenerating into a stalling ritual: endless notices with no attached consequence, so the function stays unsupplied while everyone feels procedurally correct. Its mirror-image misuse is the weapon — a pre-decided ouster dressed up with pro-forma "chances" no one intends to honor. It also does nothing if the holder is genuinely unreachable rather than merely disengaged. The discipline is to attach real, pre-agreed consequences to the checkpoints and cap the number of cycles, so the notice either re-engages the incumbent or resolves into backfill, rather than circling forever.
How it implements the components¶
re_engagement_attempt_path— it is the documented path for attempting to bring the incumbent back before the seat is treated as vacant.sponsor_cadence_checkpoint— it sets and runs the checkpoints at which engagement is re-tested, giving the attempt a schedule rather than an open horizon.
It does not sense the disengagement in the first place (role_function_health_signal → Sponsor Health Check) or grant anyone interim authority when re-engagement fails (backfill_authority_envelope, interim_decision_resolver → Interim Authority Letter and Two-Key Escalation Panel). It is the deliberate step between the two.
Related¶
- Instantiates: Functional Vacancy Backfill — the re-engagement attempt that protects the incumbent's claim and legitimizes any later backfill.
- Consumes: Sponsor Health Check supplies the red signal that triggers the notice.
- Sibling mechanisms: Sponsor Health Check · Interim Authority Letter · Functional Vacancy Declaration · Decision Timeout Rule · Auto-Escalation Workflow · Decision Stall Register · Governance RACI With Backups · Deputy Sponsor Charter · Acting Sponsor Rotation · Two-Key Escalation Panel · Post-Backfill Authority Review
Editorial Notes¶
Form Classification¶
Form family: Communication, Facilitation & Learning
Rationale: Sponsor Re-Engagement Notice operates as a designed message, facilitated interaction, ritual, or learning activity that changes shared understanding because it a formal, on-the-record prompt to a disengaged role-holder to resume the function — a documented last chance to re-engage before any backfill is activated.
Independent corroboration: The frozen evidence defines Sponsor Re-Engagement Notice as 'A formal, on-the-record prompt to a disengaged role-holder to resume the function — a documented last chance to re-engage before any backfill is activated', so its operative form is Communication, Facilitation & Learning.
Nearest alternative: Record, Log & Register — Sponsor Re-Engagement Notice includes features of a persistent ledger, log, register, or case record that preserves history and traceability, but its defining operation is a designed message, facilitated interaction, ritual, or learning activity that changes shared understanding.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: A formal last-chance notice before role backfill is organizational accountability and succession procedure.
Related originating lineages:
- Accounting & Auditing — Recorded delivery supports later review.
- Law & Governance — Notice and opportunity to cure support procedural fairness.
- Rhetoric — The wording must make duty, deadline, and consequence unambiguous.
- Systems Thinking & Cybernetics — Systems thinking, feedback control, and cybernetics supplies a parallel or contributing lineage for the mechanism's defining operation: a formal, on-the-record prompt to a disengaged role-holder to resume the function — a documented last chance to re-engage before any backfill is activated.
Review resolution: The blind reviewers agree that organizational_management is the primary origin and differ only on alternate origin disagreement, origin mode disagreement. I preserve every independently explained alternate from both records rather than imposing a numeric cap. I retain cross_disciplinary_synthesis because the combined evidence shows material contributions from several lineages. The broader reach of multi_domain records portability separately from historical provenance; encyclopedia_synthesis=true preserves the affirmative synthesis judgment where either reviewer identified one.
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¶
This is the archetype's fairness step, and skipping it is what makes a later backfill look like a seizure. Where the incumbent is unreachable rather than merely disengaged, the notice still matters as a record — but it cannot substitute for actually moving to backfill, and it should not be used to delay that move indefinitely.
[n1] Notice-and-cure — a contract provision giving a party in default formal notice and a defined window to fix the problem before the counterparty may act on the breach. A re-engagement notice is the governance version: formal notice, plus a window to resume, before backfill. ↩