You're on scene. Worth adding: three cars tangled on the interstate. Still, two people walking wounded. One trapped, unconscious. The radio crackles — "Dispatch, we've got an MCI.
But do you? Really?
Here's the thing: not every ugly scene with multiple patients is a multiple-casualty incident. And the difference isn't just semantics. It changes how you triage, what resources you call, how you manage the scene, and whether your documentation holds up later.
Let's break down what actually counts — and what doesn't The details matter here..
What Is a Multiple-Casualty Incident
An MCI isn't defined by a specific number. Worth adding: that's the first misconception to clear up. You'll hear "three or more patients" tossed around in some protocols, others say "five," some jurisdictions don't put a number on it at all.
The real definition is functional: an incident where the number and severity of casualties exceed the immediately available resources.
Read that again. Exceed the immediately available resources.
That means a two-car crash with four critical patients in a rural area with one ambulance and a 20-minute mutual aid response? That's an MCI. Day to day, same four patients in a metro system with three ALS units on scene in four minutes? Might just be a busy call.
The resource gap is the trigger
It's not about patient count. That said, it's about the gap between what you have and what you need. That gap forces you to change how you operate — triage instead of treat-first, delayed transport decisions, unified command, casualty collection points, all of it Turns out it matters..
If you can handle every patient with standard procedures and available crews, it's not an MCI. It's just a multi-patient call.
Levels of MCI declaration
Most systems use tiers. Something like:
- Level 1 — Local resources stretched but manageable. Maybe 3–5 critical patients. Mutual aid requested.
- Level 2 — Regional assets needed. 6–15 patients. Hospital notification protocols activate.
- Level 3 — Mass casualty. 15+ patients. State/federal assets, disaster plans, alternate care sites.
But the thresholds vary. A lot. What's a Level 2 in Wyoming might be a Tuesday in Los Angeles.
Why It Matters / Why People Care
Misclassifying an incident has real consequences. Both directions.
Under-declaring
You treat it like a routine multi-patient call. Transport decisions made patient-by-patient. No casualty collection point. No triage officer. The sickest wait while you package the walking wounded first because "they're ready to go.
Hospitals get surprised. Resources arrive late. Command falls apart because nobody established it early It's one of those things that adds up..
People die who might not have Most people skip this — try not to..
Over-declaring
You pull the MCI card for a three-car fender-bender with two minor injuries and one complaint of neck pain. Now you've activated mutual aid, tied up hospital beds, burned through your MCI cache, and exhausted crews who now question the next declaration.
Cry wolf enough times and the system stops responding with urgency.
The documentation trap
Here's what nobody talks about in class: if you declare an MCI, your documentation standards change. Triage tags. Think about it: patient tracking forms. Resource logs. Time-stamped decision records. If you don't declare but should have, your PCRs better reflect why — or you're explaining it in a deposition.
How It Works (or How to Decide)
So how do you make the call in real time? You don't have a checklist taped to your dash. You need a mental framework.
The 30-second size-up
First arriving unit. Windshield assessment. You're asking three questions:
- How many patients look critical? Not total patients — critical. Red tags. Airway, breathing, perfusion threats.
- What do I have right now? Crews, ambulances, ALS, BLS, extrication, air assets. Not what's coming. What's here.
- Can I manage the critical patients with what I have right now?
If the answer to #3 is no — or even "probably not" — you declare.
The resource math
Let's say you roll up on a van rollover. Eight occupants. Two unconscious, two difficulty breathing, four walking wounded.
You have: one ALS engine, one BLS ambulance, one ALS ambulance (you). Three crews. Two transport units.
Critical patients: four. Transport capacity: two. ALS providers: three (you, your partner, engine medic) The details matter here..
You cannot manage four critical patients with three ALS providers and two ambulances. Not simultaneously. Not without leaving someone unattended Practical, not theoretical..
Declare the MCI.
When the numbers lie
A school bus crash. Practically speaking, thirty kids. Twenty-nine green tags, one red That's the part that actually makes a difference..
By patient count, this screams MCI. One critical. Triage, treat, transport. By acuity? On top of that, if you've got three ALS units and four ambulances, you can handle this without MCI protocols. Standard ops.
But — and this matters — you still need some MCI structure. Here's the thing — patient tracking. Reunification. Practically speaking, parent notification. Hospital distribution so one ER doesn't get 29 pediatric patients.
So you might declare a limited MCI or MCI-standby — activate the tracking and coordination pieces without full triage-over-treatment protocols.
The "walking wounded" trap
This catches everyone. Think about it: you see 15 people standing around, talking, holding towels to minor cuts. Looks like a green-tag festival. Easy.
But three of them have occult pneumothoraces. Two have cervical spine injuries they don't feel yet because of adrenaline. One has an expanding abdominal bleed Nothing fancy..
Triage everyone. In practice, every single person. The MCI declaration forces that discipline. Without it, you skip the quiet ones It's one of those things that adds up..
Common Mistakes / What Most People Get Wrong
"We need X patients to declare"
No. Also, i've seen 12-patient MCIs that weren't declared because the system absorbed them. Plus, you need a resource gap. I've seen 3-patient MCIs that should've been Simple, but easy to overlook..
The number is a proxy. The gap is the reality.
"MCI means triage tags on everyone"
Triage tags are a tool. In real terms, not the definition. The tag doesn't make it an MCI. In practice, you can run MCI protocols with tape and Sharpies if that's what you have. The operational shift does Still holds up..
"Once declared, we can't un-declare"
False. Think about it: you can downgrade. You should downgrade if resources arrive and the gap closes. But — and this is critical — you don't undo the tracking. In practice, patient accountability continues. Because of that, documentation standards stay elevated. You just shift back toward standard treatment priorities.
"The IC declares the MCI"
Technically yes. In real terms, practically? Also, the first medic on scene usually makes the call by what they request. The IC formalizes it three minutes later. Consider this: "Dispatch, start the MCI page" is the declaration. Don't wait for a chief officer to arrive to pull the trigger The details matter here..
"All MCIs are disasters"
An MCI is an operational condition. Which means a disaster is a jurisdictional/legal declaration. Different things.
…different objectives. An MCI is triggered when the incident’s demands exceed the routine capabilities of the responding agencies; it is a tactical label that tells crews to shift from individual‑patient care to a coordinated, system‑wide approach. A disaster, by contrast, is a formal proclamation by a governmental authority that unlocks additional legal powers, funding streams, and sometimes liability protections. Recognizing that distinction helps responders avoid two common pitfalls: over‑relying on the disaster label to justify resource requests that could be met through mutual‑aid agreements, and under‑utilizing MCI protocols when a jurisdictional disaster declaration has not yet been made.
Practical steps after the MCI call
-
Establish a clear command structure – Even if the Incident Commander (IC) is still en route, the first arriving unit should announce “MCI in effect” and assign a Triage Officer, a Treatment Officer, and a Transport Officer. These roles can be filled by the most experienced providers on scene, regardless of rank.
-
Activate patient‑tracking immediately – Use whatever system is available: electronic patient‑track boards, paper tags, or a simple spreadsheet on a rugged tablet. The goal is to capture name (or identifier), age, triage category, vital signs, interventions rendered, and destination. This continuity survives any later downgrade of the incident.
-
Standardize triage but stay flexible – Begin with a rapid global assessment (RGA) to identify obvious life‑threats, then apply a validated algorithm (START, JumpSTART, or SALT) to the remainder. If resources are extremely limited, consider a “reverse triage” approach: treat the most salvageable patients first while maintaining surveillance for deteriorating conditions But it adds up..
-
Coordinate hospital distribution early – Contact the regional medical communications center (or its equivalent) as soon as the first patient is categorized. Provide a running tally of red, yellow, and green patients so receiving facilities can activate surge plans, open additional bays, or divert ambulances as needed.
-
Plan for reunification and family support – Designate a liaison (often a law‑enforcement or social‑services officer) to gather contact information, establish a reunification point, and begin notifying guardians. Even in a limited MCI, the psychological impact on families can be substantial; addressing it early reduces confusion and potential litigation Small thing, real impact..
-
Document, document, document – Capture timestamps for each major decision: MCI declaration, triage completion, transport initiation, and any resource requests. These records are essential for after‑action reviews, quality‑improvement initiatives, and, if needed, legal defensibility No workaround needed..
-
Monitor for de‑escalation – As additional units arrive or patient conditions stabilize, reassess the resource gap. If the imbalance resolves, the IC may downgrade the incident to “MCI‑standby” or revert to standard operations. That said, retain the tracking system and elevated documentation standards until all patients are definitively disposed of (treated, transferred, or released).
Training and preparation
The most effective MCI response hinges on pre‑incident preparation. Regular drills that simulate varying patient volumes and acuities — especially those that challenge the assumption that “more patients = automatic MCI” — build the mental flexibility needed to recognize a true resource gap. Still, incorporate scenario‑based learning that forces providers to triage every individual, practice improvised tagging, and rehearse communication with hospital coordinators. After each exercise, conduct a hot wash that focuses not only on speed but also on the completeness of patient accountability and the clarity of the MCI‑vs‑disaster distinction.
Conclusion
Declaring an MCI is less about hitting a specific patient count and more about recognizing that the existing response system is stretched beyond its routine capacity. Worth adding: remember that the MCI label is a tool for coordination, not a permanent state; it can be scaled up or down as resources fluctuate, while the core principles of patient tracking, clear communication, and standardized documentation remain constant. By focusing on the operational gap — rather than a numeric threshold — responders can initiate the right mix of triage, treatment, transport, and support measures at the precise moment they are needed. Mastering this nuanced approach ensures that every patient, whether critically injured or seemingly minor, receives the appropriate level of care and that the system remains resilient, accountable, and ready for the next challenge.
This is the bit that actually matters in practice.
