Triage & Prioritization Protocol¶

Prioritization protocol — instantiates Acute Stabilization Command

Orders an incident's competing demands by urgency, impact, and tractability so scarce responders work the highest-yield problems first — and lower-priority harm is consciously allowed to wait.

When an incident throws up more demands than there are hands, the instinct — work whatever shouts loudest, or whatever arrived first — spends the scarce resource on the wrong things. Triage & Prioritization Protocol replaces that with a repeatable sort: every open demand is placed in a priority band by how urgent it is, how much it threatens the floor, and how tractable it is right now, and responders work strictly top-down. Its defining move — the one that separates it from ordinary planning — is that it explicitly licenses deferral: some real harm is knowingly left to wait so that finite effort goes where it protects the most. It is not a judgment of the incident's overall severity (that grade is already set); it is the moment-to-moment allocation of scarce attention within it.

Example¶

An emergency department is hit by a sudden surge that far exceeds the staff on shift. Rather than treat in arrival order, the team applies a triage protocol: each new arrival is rapidly sorted into a band by acuity, so that those for whom prompt care is both urgent and effective are seen first, those who are stable are held, and minor needs consciously wait. The aim is not to treat everyone at once — impossible — but to hold a floor: no one who can be saved is left unattended past the point it matters, while the scarce clinicians spend their minutes where those minutes change outcomes. As conditions shift, patients are re-sorted; a "wait" is a snapshot, not a sentence.^[1] The same protocol shape governs a flooded operations desk sorting incoming failures, or a repair crew choosing which break to fix first.

How it works¶

What distinguishes triage from a to-do list is that it is built for scarcity and motion:

Bands, not a fine ranking. Demands are bucketed (immediate / deferred / minor, or similar) fast; the protocol trades precision for speed because the sort must keep up with the inflow.
A sort key that decouples urgency from importance. Something can be important but not yet actionable, or minor but instantly fixable; the key weighs urgency × threat-to-floor × tractability, not loudness.
An explicit deferral category. The protocol makes "not now" a named, recorded decision rather than a thing that quietly falls off.
Re-triage on a beat. The ordering is re-run as the situation changes, because a priority set once goes stale fast.

Tuning parameters¶

Band definitions — how many priority classes and where their cut-lines sit; coarse bands sort fast but lump unlike cases together.
Sort-key weighting — how much urgency, floor-threat, and tractability each count; mis-weighting sends effort to the loud over the load-bearing.
Re-triage interval — how often the ordering is refreshed; too rare and it ossifies, too often and re-sorting eats the response.
Floor level — how much must be protected before attention moves on; a high floor is safer but consumes more of the scarce resource per item.
Triage authority — who owns the sort, held separate from the people executing it so the sorter isn't captured by the task in front of them.

When it helps, and when it misleads¶

Its strength shows only under genuine scarcity: it stops first-come-first-served waste, concentrates finite effort where it most protects the floor, and turns "we chose not to do X" into an explicit, revisitable decision instead of an accident.

It misleads when applied where there is no real scarcity — then triage is just overhead and everything should simply be done. A miscalibrated sort key confidently prioritizes the wrong things; anchoring on the first triage without re-triage leaves the response fighting a situation that has already moved. And deferral carries real ethical weight that a tidy protocol can make feel routine. The classic misuse is invoking "triage" as cover to permanently drop work that was merely inconvenient rather than genuinely lower-priority. The discipline that guards against it is mandatory re-triage on a cadence, an explicit floor, and keeping the deferral list visible so nothing is silently abandoned.

How it implements the components¶

Triage & Prioritization Protocol fills the allocate-under-scarcity components — what a prioritizer produces:

stabilization_objective — the protocol operationalizes "stable enough" as its sort key: every demand is ranked by how much it moves the incident toward the objective.
safety_and_service_floor — triage exists to hold this floor with scarce means; it is the line the top-priority work is chosen to keep from breaching while lower-priority harm waits.

It does not classify the incident's overall severity or trip the regime — that is Severity Matrix Activation — and it does not choose the specific reversible fixes applied to the top-priority items, which fall to Reversible Service Degradation and Containment or Rollback Action.

Instantiates: Acute Stabilization Command — Triage & Prioritization Protocol is how the regime spends its scarce effort while the acute phase runs.
Sibling mechanisms: Severity Matrix Activation · Reversible Service Degradation · Common Operating Picture Board · Containment or Rollback Action · Deactivation Checklist · Incident Action Log · Incident Command System · Incident Response Runbook · On-Call Rotation Activation · Post-Incident Review (Hotwash) · Root-Cause Analysis Handoff · Status Update Cadence · War Room / Incident Channel

Notes¶

A triage decision is a snapshot, not a verdict. Its whole legitimacy rests on being revisited: the case deferred now may be the priority in ten minutes. A protocol that sorts once and never re-triages is not triage — it is a one-time queue that happens to have discarded things, and it will keep starving cases whose situation has changed.

References¶

[1] Field triage systems such as START (Simple Triage And Rapid Treatment) formalize exactly this pattern — a fast, repeatable sort into a few priority bands, revisited as conditions change — so that limited responders are directed to where intervention is both urgent and effective. ↩