Preauthorized Playbook¶
Pre-authorization playbook — instantiates Decision-Tempo Decoupling
Pre-approves a set of bounded responses to predictable pressure events, each with its limits and its intent, so fast action never has to wait on the slowest approval path.
The Preauthorized Playbook is a standing document of bounded responses already approved for predictable pressure events — each play spelling out what may be done, its hard limits, and the intent it serves — so that when the event hits, a front-line actor can act at once rather than dragging the whole organization through its slowest approval path. Its distinguishing move is that authorization is granted ahead of time and in writing: the playbook does not decide which stimulus deserves a play or when the trigger trips; it pre-loads the content and the permission of the response. And because each play carries its intent, a local actor facing an off-script variant can act in the spirit of the play rather than freezing for central clarification — which is how initiative survives being delegated.
Example¶
When a major storm hits, an electric utility's control center is swamped: hundreds of outage reports, downed-line calls, and crew requests arrive faster than any central desk can adjudicate. Waiting for headquarters to sign off on each action is the tempo trap — it keeps the lights off longer. So the utility maintains a Preauthorized Playbook. For downed conductor reported in a residential area, the play authorizes the first responding crew to de-energize the circuit and set a safety perimeter immediately — up to a defined voltage class, without waiting for a switching order — because the intent (public safety first) is fixed and the action is bounded and reversible. For substation near its load limit, a play pre-approves shedding a named non-critical feeder.
Each play states its limits (what you may not do: no work on transmission-class lines without a switching order) and its intent, so a crew facing an unlisted variant can act in the spirit of the play instead of stalling. The playbook is why a lineman 40 miles from the control center can do the safe, right thing in the first ten minutes rather than the ninetieth.
How it works¶
- Pre-decide the response, not the trigger. For each predictable pressure event, write the bounded action that is approved before the event, so sign-off is off the critical path.
- Bound every play. Explicit limits — scope, cost, reversibility, what is off-limits — are what make pre-authorization safe. An unbounded play is not a play; it is abdication.
- Attach intent to each play. State what the play is protecting, so a local actor can extend it to a novel variant without waiting and can tell when a situation has outrun the play entirely.
- Keep it a library, not a decision engine. The playbook supplies ready responses; a rule, an operator, or a delegated cell chooses and fires them.
Tuning parameters¶
- Envelope width — how much each play permits. Wider envelopes enable faster, more autonomous action but raise the cost of a play misapplied; narrower envelopes are safer but send more events back up the slow path.
- Intent specificity — how tightly each play's purpose is written. Rich intent lets locals adapt to novel variants but invites interpretation drift; rigid intent is predictable but brittle when reality does not match the named event.
- Reversibility floor — the minimum reversibility an action needs to be preauthorized at all. Raise it and only safe, undoable actions are pre-cleared; lower it and you pre-clear heavier commitments, faster but riskier.
- Coverage versus curation — how many events get plays. Broad coverage handles more of the storm without escalation but bloats the book past what anyone can recall under load; tight curation stays memorable but leaves gaps.
When it helps, and when it misleads¶
Its strength is that it takes central approval off the critical path for exactly the events where fast action is safe, and — because each play carries intent — it preserves initiative under delegation instead of trading control for speed. It is the difference between a distributed team that acts coherently and one that either freezes or freelances.
Its characteristic failure is drift: a play written for one situation gets invoked a little out of spec, again and again, without immediate harm, until the exception is the norm and the envelope has quietly expanded past what anyone approved. This is normalization of deviance, and it is how a safety playbook becomes the cause of the incident.[n1] The classic misuse is reaching for a play because it is available rather than appropriate — fighting the current event with the last event's script. The discipline is structural: every play carries an explicit "does not apply when…," invocations are logged and reviewed, and a play that keeps getting stretched is a signal to rewrite it, not to keep bending it.
How it implements the components¶
The Preauthorized Playbook realizes the pre-loaded action side of the archetype — the content and permission of fast response:
preauthorized_action_envelope— the playbook is the envelope: the set of bounded, pre-approved actions with their limits.initiative_preservation_intent— each play carries the intent it serves, which is what lets a local actor keep the initiative — acting in spirit, adapting within bounds — instead of stalling for clarification.
It does not decide which stimulus routes to a "preauthorized action" in the first place (Response-Obligation Matrix) or fire the play when a condition trips (Trigger-Based Response Rule); and where the plays need a standing human owner holding delegated authority, that role is the Mission Command or Delegated Authority Cell, not the document itself.
Related¶
- Instantiates: Decision-Tempo Decoupling — the playbook is the pre-loaded response library that makes safe fast action possible without central sign-off.
- Consumes: Tempo Pressure Map identifies the predictable pressure events worth a play; its plays fill the "preauthorized action" branch of the Response-Obligation Matrix.
- Sibling mechanisms: Mission Command or Delegated Authority Cell · Trigger-Based Response Rule · Response-Obligation Matrix · Tempo Pressure Map · Deliberate Response-Delay Window · Rate Limit and Cooldown Rule · Asynchronous Decision Queue · Independent Signal Verification Lane · Decision-Cycle Wargame · Tempo-Trap Red-Team Review · Cadence Reset Retrospective
Editorial Notes¶
Form Classification¶
Form family: Rule, Policy & Commitment
Rationale: The mechanism grants standing bounded permission for named responses, with explicit limits, intent, and off-limits conditions before pressure arrives.
Nearest alternative: Representation, Specification & Plan — The plays are written down, but preauthorization and constraints are the load-bearing form.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Military & Strategic Studies
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Bounded responses approved before predictable pressure events arise from military contingency planning.
Related originating lineages:
- Disaster Management & Risk Reduction — Disaster management contributes emergency activation and escalation limits.
- Organizational & Management Science — Organizational management contributes delegated authority and decision-tempo design.
- Security Studies & Intelligence Analysis — Security incident playbooks materially adapted the approach to fast-evolving threat events.
Review resolution: Both blind reviewers agree that military strategic studies is the primary origin. Reconciliation resolves alternate origin disagreement, origin mode disagreement, encyclopedia synthesis disagreement. Formative alternate lineages are retained as disaster_management, organizational_management, security_intelligence; later breadth of use is recorded separately as domain_reach=multi_domain, while origin_mode=cross_disciplinary_synthesis describes the relationship among origin lineages.
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 playbook is inert on its own — a library of permissions, not an actor. Its safety lives entirely in the bounding limits and in the review of how plays are actually invoked; an unbounded or unreviewed playbook is indistinguishable from "everyone do whatever seems fast." This is why the two dials that matter most, envelope width and reversibility floor, are safety settings before they are speed settings.
[n1] Normalization of deviance — Diane Vaughan's term for the process by which an out-of-spec practice, used repeatedly without immediate harm, gradually becomes accepted as normal until it fails badly. Preauthorized plays are especially prone to it because their whole value is fast, unsupervised use; logging invocations and periodically re-reviewing the envelope is the standard guard. ↩