Decision Timeout Rule¶
Decision rule — instantiates Functional Vacancy Backfill
A bright-line deadline that deems a decision stalled once it sits unresolved past a preset clock, converting open-ended waiting into an automatic, pre-agreed trigger for backfill.
The hardest part of backfilling an absent authority is knowing when you are allowed to — too early and you have usurped a merely-busy sponsor, too late and the harm is done. Decision Timeout Rule settles that in advance with a bright line: a decision of a defined type, once properly submitted and left unresolved past a preset clock, is deemed stalled — and that deeming is the trigger the rest of the backfill machinery waits on. Its defining move is pre-commitment: the threshold is agreed while everyone is calm and no particular decision is on the table, so when the clock later expires, backfill fires on a rule set in advance rather than on someone's nerve in the moment. It decides the when, and only the when — it names no substitute and routes nothing.
Example¶
A company's purchases above a threshold need the category owner's approval. When that owner is travelling, disengaged, or overloaded, requisitions can sit for weeks and projects miss their windows. Finance adopts a Decision Timeout Rule: any compliant requisition under ~$50k that the category owner neither approves nor rejects within ten business days is automatically deemed timed-out and becomes eligible for backfill approval by a named deputy. The rule is deliberately fenced — the clock starts only once the requisition is complete (so nothing can be "timed out" by starving it of information), it pauses if the owner asks a documented question, and the requester, who benefits from the bypass, cannot themselves start or force the clock. When a $30k requisition for lab reagents hits day eleven untouched, the rule does its one job: it declares the decision stalled and the deputy channel opens. Nobody had to argue that ten days was "long enough" — that was settled months earlier.
How it works¶
- Define the clock per decision type. A safety sign-off and a travel approval should not share a timeout; the rule is a small table, not a single number.
- Define when the clock starts. Almost all the rule's integrity lives here: it starts on a complete, properly-routed submission and pauses on a genuine, logged query, so completeness cannot be gamed into a false stall.
- Deem, don't decide. On expiry the rule changes the decision's status to stalled-and-eligible; it does not itself approve anything. The approval belongs to whatever backfill channel the status unlocks.
- Fence against weaponization. The party who would gain from the bypass cannot trigger the clock, and repeated near-timeouts flag the sponsor for a health check rather than silently normalizing.
Tuning parameters¶
- Clock length — short deadlines protect throughput but risk overriding a sponsor who is merely deliberating; long ones respect deliberation but let harm accrue. Set per decision type by cost of delay.
- Start/stop definition — what counts as a complete submission and what legitimately pauses the clock. This dial, more than the length, decides whether the rule can be gamed.
- Scope of covered decisions — which decision types are timeout-eligible at all. Widening scope closes more gaps but moves the rule toward eroding the role.
- Consequence on expiry — whether a timeout opens backfill automatically or merely permits it pending a declaration. Automatic is faster; permissive keeps a human in the loop.
- Reset behavior — whether a single sponsor action resets the clock fully or only for that decision, which governs how easily an absent sponsor can keep resetting to stay just inside the line.
When it helps, and when it misleads¶
Its strength is removing the hardest judgment from the heat of the moment: by pre-agreeing the deadline, it converts a fraught "is it time to go around them?" into a checkable fact. The pattern has a real cousin in administrative law's deemed approval — statutes that treat an agency's silence past a statutory period as a decision, precisely so an official cannot stall indefinitely by doing nothing.[n1]
Its failure modes are those of any bright line. A clock set too short manufactures stalls out of ordinary deliberation and trains sponsors to rubber-stamp to beat the timer; set too long, it launders real neglect as "still within policy." And it is weaponizable: a requester who wants the sponsor bypassed can try to run out the clock, which is why the start/stop fencing is not optional decoration but the rule's spine. The discipline that keeps it honest is to tune the clock to each decision's genuine cost of delay, guard the clock-start against gaming, and treat chronic timeouts as a signal about the role, not a routine to be normalized.
How it implements the components¶
Decision Timeout Rule fills only the trigger-definition slice:
decision_stall_threshold— the rule is the threshold, made explicit and pre-committed: the clock, its per-type lengths, and the deeming that fires backfill.abuse_and_bypass_guardrail— the start/stop fencing and the "beneficiary cannot start the clock" rule are what stop the threshold from being weaponized into a bypass tool.
It does not gather the evidence that a role is failing (role_function_health_signal, the Decision Stall Register), issue the status change (legitimacy_notice_and_record, the Functional Vacancy Declaration), or name and route to the substitute who acts once the clock expires (interim_decision_resolver, Acting Sponsor Rotation and Auto-Escalation Workflow).
Related¶
- Instantiates: Functional Vacancy Backfill — the rule supplies the pre-agreed trigger the rest of the backfill sequence waits on.
- Sibling mechanisms: Decision Stall Register · Functional Vacancy Declaration · Auto-Escalation Workflow · Acting Sponsor Rotation · Deputy Sponsor Charter · Sponsor Health Check · Sponsor Re-Engagement Notice · Interim Authority Letter · Governance RACI With Backups · Two-Key Escalation Panel · Post-Backfill Authority Review
Editorial Notes¶
Form Classification¶
Form family: Rule, Policy & Commitment
Rationale: Decision Timeout Rule operates as a standing rule, threshold, contractual commitment, or policy constraint governing future conduct because it a bright-line deadline that deems a decision stalled once it sits unresolved past a preset clock, converting open-ended waiting into an automatic, pre-agreed trigger for backfill.
Independent corroboration: The frozen evidence defines Decision Timeout Rule as 'A bright-line deadline that deems a decision stalled once it sits unresolved past a preset clock, converting open-ended waiting into an automatic, pre-agreed trigger for backfill', so its operative form is Rule, Policy & Commitment.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Law & Governance
Origin pattern: Single lineage
Present-day reach: Multi-domain
Rationale: Administrative law cohered deemed-approval and tacit-consent rules under which official inaction beyond a statutory deadline produces a predeclared legal status.
Related originating lineages:
- Organizational & Management Science — Escalation and continuity governance generalized timeout triggers to stalled organizational decisions.
- Public Administration & Policy — Service standards and permit administration supplied fixed decision clocks designed to prevent indefinite blockage.
Review resolution: Administrative law cohered deemed-approval and tacit-consent rules under which official inaction beyond a statutory deadline produces a predeclared legal status.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
The rule's power and its danger are the same thing: it can override a present, thinking sponsor purely on a clock. That is why the mature version times out into eligibility for backfill, not backfill itself — the expiry says "a substitute channel may now open," and a separate declaration or resolver still has to act. Keeping the deadline and the decision-to-act in different hands is what stops a timer from becoming a coup.
[n1] Deemed approval (or tacit consent) is a real device in administrative law: a statute provides that if an authority fails to decide an application within a set period, approval is automatically treated as granted. It exists for the same reason as this rule — to deny an official the power to block indefinitely through inaction. ↩