Governance RACI With Backups¶
Governance tool — instantiates Functional Vacancy Backfill
A responsibility chart that pre-names, for every decision a role owns, both its primary holder and a standing backup — so the map of who-may-act already exists before anyone goes absent.
A RACI chart records, for each decision, who is Responsible, Accountable, Consulted, and Informed. Governance RACI With Backups adds the one column that matters for this archetype: for every Accountable seat it also names a standing backup and the pre-agreed condition under which that backup's decision rights become live. Its defining trait is that it is the only mechanism here that exists before the vacancy — a map drawn in calm weather. It does not sense an absence, grant interim authority, or resolve a stalled call; it pre-answers the question the other mechanisms would otherwise have to improvise under pressure: when this named person is absent, who already holds the right to act, and over exactly which decisions?
Example¶
A regional water authority runs a multi-year pipe-replacement program. One Program Sponsor holds sign-off on scope changes above a threshold, on release of contingency funds, and on pausing work for safety. For two years nothing goes wrong — until the sponsor is hospitalized during a wet-season emergency and a ≈$2M contingency release sits unsigned for nine days, because "only the sponsor can approve that."
The lesson lands, and the authority builds a Governance RACI With Backups. Each decision the sponsor owns becomes its own row — scope-change approval, contingency release, safety pause — and each row carries an Accountable primary (the sponsor), a named backup (a different one per row: safety → operations lead; funds → finance lead), and the trigger that makes the backup's rights live: "primary unreachable > 48h on a time-critical safety or funds decision." When the next absence comes, the deputy doesn't ask permission; the chart already says the rights are theirs, for those rows, under that condition. The same nine-day stall now clears in two — not because anyone was braver, but because the authority-to-act was mapped and escrowed in advance.
How it works¶
- Inventory the decisions, not the person. Break the role into the discrete decisions it actually owns — one row each — rather than one line for "the sponsor's job."
- Name a primary and a backup per row. Backups can differ by decision, matching the substitute to the competence each call needs.
- Escrow each backup's rights against a condition. The backup's authority stays dormant until a stated trigger fires; the chart records the condition, not just the name.
- Keep it short and current. Few rows, reviewed on the org's own cadence, so it reads in a minute and never names people who have moved on.
Tuning parameters¶
- Row granularity — one line for the whole role versus a row per decision type. Finer rows route the right backup to the right call but cost upkeep.
- Backup depth — a single alternate versus a ranked chain (first, second). Deeper chains survive double-absence but dilute clarity about who acts.
- Escrow-condition strictness — how hard the trigger is to meet (time-only versus time-plus-materiality). Loose triggers activate fast but invite capture; strict ones protect the seat but can be too slow.
- Coupling to the trigger — whether the condition is self-declared or read from an external signal (a health check, a timeout rule). Tighter coupling reduces argument about whether the backup may act.
When it helps, and when it misleads¶
Its strength is that it removes the "who's even allowed to decide?" hesitation before it can cost days, and it turns key-person risk from a surprise into a visible map[1]. It is the substrate every other backfill mechanism reads from.
Its failure mode is staleness: a RACI is only as live as its last update, and a backups column naming people who have since moved is worse than none — it still reads as authoritative. It also says nothing about whether the primary is truly absent (a detection question) or whether the incumbent should be re-engaged first. The classic misuse is the chart drawn once for an audit and never refreshed, or padded with so many rows that no one can find the live one. The discipline is to review it whenever the org itself changes and to keep it short enough that a stale row is obvious.
How it implements the components¶
decision_function_inventory— its rows are the inventory: the role split into the discrete decisions it owns.deputy_or_successor_pool— the backups column names the standing pool of substitutes, per decision.escrowed_decision_rights— each backup's rights are held dormant against a stated condition; the chart is where they are escrowed.
It does not sense the vacancy or grade the sponsor (role_function_health_signal, nominal_occupancy_assessment → Sponsor Health Check) or grant the live interim authority when one fires (backfill_authority_envelope, legitimacy_notice_and_record → Interim Authority Letter). It supplies the map those mechanisms act on.
Related¶
- Instantiates: Functional Vacancy Backfill — supplies the standing who-may-act map the whole backfill depends on.
- Sibling mechanisms: Interim Authority Letter · Sponsor Health Check · Deputy Sponsor Charter · Functional Vacancy Declaration · Decision Timeout Rule · Auto-Escalation Workflow · Decision Stall Register · Acting Sponsor Rotation · Two-Key Escalation Panel · Sponsor Re-Engagement Notice · Post-Backfill Authority Review
Editorial Notes¶
Form Classification¶
Form family: Organization, Role & Governance
Rationale: The mechanism maintains an authority arrangement that assigns each decision to a primary role and a standing backup before absence occurs.
Nearest alternative: Representation, Specification & Plan — A chart displays the assignments, but their operative value is the enduring role and authority coverage they establish.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: RACI responsibility matrices and succession planning are established organization-design practices.
Related originating lineages:
- Disaster Management & Risk Reduction — Continuity planning and designated alternates materially add the backup role.
Review resolution: Both reviewers agree that organizational_management is primary: RACI responsibility matrices and succession planning are established organization-design practices. I retain disaster_management only as formative lineage, not as a list of later applications. I resolve origin_mode as cross_disciplinary_synthesis because the artifact joins distinct disciplinary contributions. I resolve domain_reach as multi_domain because it transfers across several fields but is not a domain-free primitive. Encyclopedia synthesis is true because the exact generalized packaging is an encyclopedia-authored combination or refinement.
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¶
The backups column names who covers each decision at a glance; it does not empower them in depth. That fuller chartering of a standing deputy — mandate, onboarding, review — is the job of a Deputy Sponsor Charter. Read the RACI as the breadth-first index and the charter as the depth on any one seat.
References¶
[1] Swanson, M., Bowen, P., Phillips, A., Gallup, D., & Lynes, D. Contingency Planning Guide for Federal Information Systems. NIST Special Publication 800-34 Revision 1 (2010). Maps contingency roles, key personnel, contact information, and alternates so dependencies are explicit. registry ↩