Fatigue Check Protocol¶
Checklist — instantiates Decision Load Management
A checklist or pause protocol that responds to signs of degraded decision quality.
A Fatigue Check Protocol is a standing rule that watches for the moment judgment starts to fray and, when it fires, forces a response — a pause, a handoff, a reschedule, or a second review — before more decisions are made on a depleted tank. Its defining move is quality-triggered intervention: it monitors observable signals that decisions are degrading (rework climbing, reviews going shallow, standards drifting, the queue aging) and converts those signals into a concrete stop-or-protect action. It is not about routing decisions or scheduling them in advance; it operates within a decision-making session, in real time, to keep depletion from silently corroding the calls being made. Its whole premise is that decision quality is a finite resource that runs down over a long unbroken sequence, and that the fix is structural — a triggered pause — not an exhortation to try harder.
Example¶
A radiology group noticed that reading accuracy on a long unbroken worklist drifted as a shift wore on — the same ambiguous nodule flagged carefully at 9am might get a quicker, thinner read at hour six, when the radiologist had already worked through two hundred studies. Blaming individuals had done nothing. So they install a Fatigue Check Protocol. It defines the signals to watch: reads-per-hour climbing while dictation length shrinks, an uptick in "quick normal" verdicts, self-reported strain. When two signals cross a threshold, the protocol triggers a short checklist — take a mandated ten-minute break, and route the next batch of high-complexity studies to a fresh second reader.
The trigger is structural, not disciplinary: it responds to the context (a long depleting run), not to a person's character. The illustrative effect is that the thinnest reads — the ones most likely to miss something — get caught by a pause or a second set of eyes instead of being trusted at face value. This is the decision fatigue[n1] concept turned into an operating safeguard rather than a warning.
How it works¶
The protocol has a sensing half and an acting half. The sensing half specifies the fatigue and quality signals to watch — rework rate, review depth, standard consistency, queue age, self-reported capacity — and the threshold at which they count as "quality is degrading now." The acting half specifies the response the moment the threshold trips: a mandated break, a handoff to a fresh decider, a reschedule of the remaining hard items, or a second review of recent calls. The two are pre-committed together so the response does not itself require a fatigued judgment call — that is the point of making it a checklist. Because it treats the decider's fresh judgment as a depletable budget, its interventions all buy the same thing: they stop consequential decisions from being spent past the point where quality holds.
Tuning parameters¶
- Signal sensitivity — how readily the protocol reads degradation into the metrics. High sensitivity catches fatigue early but interrupts often, some of it needlessly; low sensitivity avoids nuisance stops but lets real depletion run.
- Trigger threshold — how many signals, how far over the line, before the response fires. A single-signal trigger is twitchy; a multi-signal trigger is robust but slower to react.
- Response intensity — whether the triggered action is a short pause, a full handoff, or a re-review of prior calls, trading disruption against protection.
- Monitoring stance — how the signals are gathered (self-report vs. observed metrics) and, critically, whether the data is used structurally or punitively.
- Recovery criterion — what counts as "fit to resume," from a fixed break length to a re-checked signal, balancing throughput against genuine recovery.
When it helps, and when it misleads¶
The protocol earns its place in high-volume, high-consequence decision work where quality visibly decays across a long session — clinical reading, adjudication, sustained review — and where a missed late-session call is costly. Making the pause automatic and signal-triggered catches degradation that the fatigued person is, almost by definition, worst placed to notice in themselves.
Its most corrosive failure is fatigue-signal surveillance: when the monitoring becomes punitive — a stick to measure and blame individuals rather than a structural safeguard — people hide the very signals the protocol needs, and it dies. It can also misfire as nuisance interruptions if sensitivity is set too high, training people to override it, or it can lull a team into treating the checklist as sufficient when the real fix is reducing load upstream. The archetype is explicit that fatigue is a property of context and workflow, not a character flaw. The guarding discipline follows from that: keep the signals structural and non-punitive, tune sensitivity so triggers stay credible, and treat a firing protocol as evidence the workload needs redesign — not that a person needs correcting.
How it implements the components¶
fatigue_signal— it names the observable indicators of degrading judgment and the threshold at which they count as a fatigue signal.decision_quality_monitor— it continuously reads decision-quality proxies (rework, review depth, consistency) during a session to detect degradation as it happens.decision_energy_budget— its interventions enforce a budget on fresh judgment, stopping or protecting decisions once the depletable attention supply runs low.
It does not preselect or delegate the decisions themselves (default_or_delegation_rule) — that is Default Option Design — and it does not group decisions into planned windows (batching_rule); scheduling by energy is the Decision Calendar.
Related¶
- Instantiates: Decision Load Management — the protocol realizes the "detect degraded judgment and pause or protect" safeguard.
- Consumes: Decision Calendar — where a calendar schedules high-stakes work for high-energy windows, the protocol catches the depletion the schedule failed to prevent.
- Sibling mechanisms: Decision Calendar · Low-Stakes Decision Automation · Decision Batching Workflow
Editorial Notes¶
Form Classification¶
Form family: Control, Automation & Runtime
Rationale: Fatigue Check Protocol operates as a live operational control that automatically routes, enforces, adapts, or responds during execution because it a checklist or pause protocol that responds to signs of degraded decision quality.
Independent corroboration: The frozen evidence defines Fatigue Check Protocol as 'A checklist or pause protocol that responds to signs of degraded decision quality', so its operative form is Control, Automation & Runtime.
Nearest alternative: Protocol, Workflow & Routine — Threshold sensing and an immediate break, handoff, or reschedule close a live quality-control loop; the checklist supplies its response sequence.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Psychology
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: The trigger rests on psychological research on fatigue and degraded judgment, operationalized here as a human-factors safeguard.
Related originating lineages:
- Aviation & Aeronautics — Aviation human-factors practice materially developed duty, fatigue, and go/no-go safeguards.
- Medicine & Healthcare — Clinical shift work and patient-safety practice materially shaped fatigue screening and mandatory pause protocols.
- Organizational & Management Science — Work-design and occupational practice supplied structural workload, handoff, and recovery controls.
Review resolution: Both reviewers agree that psychology is primary. I retain medicine_healthcare, aviation_aeronautics, organizational_management only as formative origin lineage(s), without treating every later application as an origin. cross_disciplinary_synthesis is appropriate because the exact artifact combines contributions from multiple professional lineages. Reach is multi_domain as a separate applicability judgment: it does not widen or narrow the recorded provenance. Encyclopedia synthesis is true because the exact generalized artifact is an encyclopedia-authored combination or refinement. The secondary differences are reconciled with no unresolved primary-provenance ambiguity.
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] Decision fatigue — the observation that making a long, unbroken sequence of choices tends to degrade their quality, often traced to the broader (and debated) research program on ego depletion. Whatever the mechanism's exact size, the practical lesson holds: a structural pause protects late-in-sequence decisions better than willpower does. ↩