Critical Function Triage Matrix¶
Prioritization tool — instantiates Recovery Trajectory Management
A scoring grid that ranks which functions must return first by weighing criticality and dependency against how badly each was hit — turning scarce recovery capacity toward what unlocks the rest.
A Critical Function Triage Matrix is a scoring grid that decides order under scarcity. When far more is broken than can be fixed at once, the matrix ranks each function by two axes — how critical it is (does it protect life, preserve legitimacy, or unlock other functions?) and how coupled it is (what depends on it, and what must precede it?) — and resolves the ranking into a dependency-aware restoration order. Its distinctive contribution is turning a priority judgment into an explicit, defensible sequence: not just "these matter most," but "restore in this order, because each step enables the next." It exists to keep recovery from being captured by the loudest, most visible, or most recently-complained-about damage.
Example¶
A hospital is hit by ransomware that encrypts servers across the enterprise. Everything is down at once: the EHR, lab and imaging, pharmacy dispensing, scheduling, billing, the parking gates. The triage matrix ranks them. Each function is scored on criticality (patient-safety impact if it stays down) and on dependency (what it blocks and what it needs first). Life-safety-critical, foundational systems rise to the top: identity and network must come back before anything authenticates; the lab and pharmacy outrank billing because clinical care depends on them; scheduling waits behind the clinical core; parking gates go last. The scores resolve into a sequence — restore identity → clinical core → ancillary clinical → administrative → convenience — where each tier is a prerequisite for the next.
The value is not the ranking alone but the legibility of it. When an executive demands billing back first "because we're bleeding revenue," the matrix answers with the explicit criteria: billing depends on the clinical core, which is not yet safe, so billing cannot lead. The argument moves from politics to scores.
How it works¶
- Enumerate functions, not assets. The unit is a function ("dispense medications"), not a server, because recovery order is about capabilities.
- Score two axes. Rate each function on criticality (life, legitimacy, irreversibility) and on dependency (upstream prerequisites, downstream dependents), typically against recovery-time targets.
- Resolve to a sequence. Sort by score subject to the dependency graph, so a high-criticality function still waits behind its prerequisites — yielding an order in which each step prepares the next.
- Re-run as reality shifts. As functions come back or new damage surfaces, the matrix is recomputed; priority is a live ranking, not a one-time verdict.
Tuning parameters¶
- Axis weighting — how heavily criticality outranks dependency (or vice versa). Over-weighting criticality can order a vital function ahead of the prerequisites it silently needs.
- Scoring granularity — a 3-tier bucket versus a fine numeric score. Fine scores discriminate better but invite false precision and endless debate over a point.
- Dependency strictness — whether the resolver treats dependencies as hard constraints or soft preferences. Hard constraints prevent unsafe ordering but can deadlock on circular dependencies.
- Recovery-time target basis — whether scores are anchored to pre-set recovery-time objectives or to in-the-moment judgment. Pre-set targets are defensible[1] but can be stale after a novel disruption.
- Re-triage cadence — how often the ranking is recomputed against the changing state.
When it helps, and when it misleads¶
Its strength is that it makes prioritization contestable in the open: the order is a function of stated criteria, so a demand to jump the queue must argue with the scores rather than with a person. It is the mechanism that protects the dependency-critical from being displaced by the merely visible.
Its failure mode is that the ranking is only as good as its inputs — a mis-scored dependency can put a function ahead of its own prerequisite, and a matrix full of confident numbers can lend false precision to what were really guesses. The classic misuse is scoring by loudness: letting the most complained-about function inflate its criticality until the matrix simply ratifies politics. The guarding discipline is to score against the damage-and-capacity evidence rather than opinion, to keep the dependency graph honest, and to re-run the matrix as functions return so the order tracks reality.
How it implements the components¶
critical_function_priority_map— its core output: functions ranked by criticality and dependency into an explicit priority order that resists capture by visible or loud damage.restoration_sequence— the priority map resolved against the dependency graph into a concrete order in which each restored function prepares the next.
It ranks and orders but does not collect the damage data it scores on — damage_and_capacity_assessment and its hazard flags belong to Damage Assessment Survey, which the matrix consumes. Nor does it attach the order to dates and crews; resource_and_capacity_rebuild_plan is Phased Restoration Schedule's. The matrix decides the logical order; the schedule times it.
Related¶
- Instantiates: Recovery Trajectory Management — this matrix supplies the priority-ranked restoration order the rest of the recovery executes against.
- Consumes: Damage Assessment Survey supplies the graded damage and capacity the matrix scores.
- Sibling mechanisms: Phased Restoration Schedule · Service Restoration Runbook · Damage Assessment Survey · Incident Recovery Plan · Community Recovery Plan
Editorial Notes¶
Form Classification¶
Form family: Decision, Gate & Allocation
Rationale: Critical Function Triage Matrix operates as a case-specific gate, selection, routing, prioritization, or resource disposition because it a scoring grid that ranks which functions must return first by weighing criticality and dependency against how badly each was hit — turning scarce recovery capacity toward what unlocks the rest.
Independent corroboration: The frozen evidence defines Critical Function Triage Matrix as 'A scoring grid that ranks which functions must return first by weighing criticality and dependency against how badly each was hit — turning scarce recovery capacity toward what unlocks the rest', so its operative form is Decision, Gate & Allocation.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Disaster Management & Risk Reduction
Origin pattern: Single lineage
Present-day reach: Specialized
Rationale: Disaster recovery and continuity planning cohered critical-function triage by life safety, impact, recovery-time objective, and enabling dependency.
Related originating lineages:
- Operations Research — Multi-criteria and precedence optimization supplied defensible scoring and dependency-aware restoration order under scarce capacity.
- Organizational & Management Science — Business-continuity governance supplied recovery-time objectives, service ownership, and executive tradeoff rules.
Review resolution: FEMA continuity guidance and CISA continuity tools establish business-impact and essential-function prioritization as preparedness practice, with optimization and management as supporting lineages.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
References¶
[1] Swanson, M., P. Bowen, A. W. Phillips, D. Gallup, and D. Lynes. Contingency Planning Guide for Federal Information Systems. NIST SP 800-34 Rev. 1 (2010). Uses business-impact analysis to establish recovery objectives and priorities from criticality, outage impact, and tolerable downtime. registry ↩