System status management (SSM) is one of the most useful tools an EMS system has, and one of the easiest to get wrong. The main pitfalls are coverage holes left behind after each dispatch, crews worn down by constant moves, plans built on call counts instead of real workload, uneven coverage across neighborhoods, and a rollout that the workforce never accepted. Each one can be prevented. This article shows where they come from and what municipal leaders and EMS managers can do about them.
TL;DR
- SSM decides where your remaining ambulances will be when the next call arrives. Every system has either good system-status management or poor system-status management, even if no one calls it that.
- The recurring failures are coverage holes after dispatch, excessive posting moves, planning on call volume instead of unit-hour demand, and weak buy-in from crews and dispatchers.
- Results depend on system design, managerial competence and workforce commitment, not on the software or the posting plan alone.
- Audit coverage by neighborhood and income level, and measure quality of care alongside time.
- An outside performance gap analysis can show a municipality where its plan is helping and where it is quietly failing.
Table of Contents
- What system status management actually does
- Pitfall 1: The coverage hole nobody plans for
- Pitfall 2: Planning on call counts instead of unit-hours
- Pitfall 3: Crews who spend the shift moving or waiting
- Pitfall 4: Dispatch without reliable location and status data
- Pitfall 5: Chasing response time at the expense of safety
- Pitfall 6: Coverage that looks fine on average and fails some neighborhoods
- Pitfall 7: Ignoring hospital offload and diversion
- Pitfall 8: Rolling it out without the workforce
- A quick self-check for your own system
- Fixed posts versus dynamic deployment: both have a place
- How municipal leaders should review a plan
- Our perspective
- Getting help with your plan
- FAQ
- Sources
What system status management actually does
In a fixed-post model, ambulances sit at stations and return there after each call. SSM works differently. It manages EMS resources before and between calls so that units are positioned for the next response, moving them according to anticipated and real-time demand.
Jack Stout put the central point plainly in a 1983 JEMS article: SSM determines where the remaining ambulances will be when the next call comes in. It follows that every EMS system has either system-status management or system-status mismanagement. A municipality that has never adopted a formal plan is still making posting decisions. They are just being made by habit.
That is why the pitfalls matter. The question is rarely whether to manage status. It is whether you do it with data, discipline and safeguards.
If you want the fundamentals first, our overview of system status management and EMS response covers the model in more depth.
Pitfall 1: The coverage hole nobody plans for
Every time an ambulance is dispatched, the area it was covering is left thinner. The Cornell operations-research review explains that spreading ambulances across a city shortens travel distance but creates a coverage hole whenever a unit is sent out. Real-time relocation is the way systems close those holes.
The mistake is sending the closest available unit every time without asking what the dispatch does to the rest of the map. The same authors argue that relocation decisions should account for the hole each dispatch creates, rather than simply selecting the nearest ambulance.
A 2025 simulation of Manhattan shows what is at stake. A dispatch policy that penalized assignments reducing coverage in high-demand areas produced a mean high-priority response under six minutes in 90% of episodes, versus 75% with nearest-unit dispatch. The authors describe this as a proof of concept, not a forecast for any particular city. It is a good illustration of the principle, though: the dispatch decision and the coverage plan are the same decision.
What to do: Define a minimum coverage standard for each zone. Review how often a single dispatch drops a high-demand zone below that standard, and set rules for who moves, and when, to restore it.
Pitfall 2: Planning on call counts instead of unit-hours
Many plans start with how many calls arrive each hour. That is a reasonable start and a poor finish. EMS1’s 2019 guidance on matching supply to demand recommends measuring consumed unit-hours rather than call counts. Call duration, hospital status, emergency department wall time, training, meals and breaks all change how much capacity the system actually uses.
Two systems with identical call volume can need very different staffing. If one has long hospital turnaround times, its ambulances are unavailable for longer, and a plan drawn from call counts will undercount the demand.
The historical record supports the underlying approach. A 2004 review of the origins of SSM reports that past demand patterns predict future demand, that demand varies by hour and weekday, and that response times fall when ambulance supply is matched to calls. The pattern is reliable. The measurement has to be honest.
What to do: Build your demand curve from unit-hours consumed, by hour and day of week, and refresh it on a regular schedule. Include hospital offload time as its own line, not a footnote.
Pitfall 3: Crews who spend the shift moving or waiting
The same Cornell review lists crews spending much of a shift driving between locations or waiting in undesirable places among the recognized pitfalls of SSM. Anyone who has worked a street post at 3 a.m. in a convenience store lot knows how this feels.
Excessive moves wear on people in several ways: fuel and vehicle wear, fatigue, limited access to restrooms and meals, and a sense that the plan was designed for a map instead of for the people who work it.
Stout’s 1989 JEMS article is direct about the stakes. Used skillfully, SSM can improve wages, working conditions and patient response. Used by unskilled managers or dispatchers, it can cause substantial harm. The same article says a skilled plan balances high-volume and low-volume coverage, off-peak reliability, employee health and safety, skills maintenance, job satisfaction, economic efficiency and financial stability. Overemphasizing any one of those creates unacceptable tradeoffs.
What to do: Set a ceiling on moves per unit per shift, and track it. Designate posts with real amenities. Ask crews which posts they would change and why, then act on the answers you can.
Pitfall 4: Dispatch without reliable location and status data
A posting plan is only as good as the information behind it. Effective SSM requires dispatchers to know each ambulance’s location and status, supported by GPS units and crew status updates. If a unit shows as available when it is still clearing a hospital, the plan is working from fiction.
This is also a staffing problem for the communications center. Dispatchers carrying out dynamic posting need clear authority, written decision rules and training, not a verbal tradition handed down from the last shift supervisor. Our guide to the role of dispatch in EMS explains how the communications center fits into response performance.
What to do: Audit your status data against reality for a sample of calls. Check how long status changes lag behind actual events, and fix the lag before tuning the plan.
Pitfall 5: Chasing response time at the expense of safety
Time targets are easy to measure, which makes them tempting to chase. But faster is not always better. The 2022 joint statement from major U.S. EMS organizations says lights-and-siren operations create significant risk to EMS personnel, patients and the public and should be limited to situations where the time saved is expected to be clinically important.
The same statement recommends acuity-based dispatch categories, physician oversight and formal quality assurance. It also calls for monitoring lights-and-siren use, appropriateness, protocol compliance and outcomes, and for reviewing crashes and near misses. It advises that service agreements be guided by quality-care metrics rather than time metrics.
That last point matters for any municipality writing a contract. If the only number in the agreement is a response-time compliance rate, you may reward the behavior that creates risk. Pair time standards with clinical and safety measures. For the evidence on why speed still matters for the right calls, see why faster EMS response times improve outcomes, and for practical steps, our playbook for reducing EMS response times.
What to do: Tier your response standards by acuity. Report safety indicators next to time indicators in every performance review.
Pitfall 6: Coverage that looks fine on average and fails some neighborhoods
Citywide averages can hide real disparities. A San Francisco analysis found that ZIP codes in the $25,000 to $50,000 income bracket had the lowest probabilities of meeting average response-related measures, including an 11.5% chance of being within the city’s average one-mile emergency-room distance. That study is about one city and is not a national estimate. Its lesson travels well, however: if you only report averages, you will not see who is being left behind.
Dynamic deployment concentrates ambulances where demand is predicted to be highest. That is efficient, and it can also quietly thin coverage in areas with lower historical call volume, which are sometimes the areas with the least access to other care.
What to do: Map response performance by neighborhood, and where you can, by income and demographic data. Set a floor for every zone, not only a citywide average, and report on it publicly.
Pitfall 7: Ignoring hospital offload and diversion
SSM manages ambulances, but the hospital controls how quickly they come back. The NAEMSP’s 2011 resource document says prolonged ambulance offload and diversion reduce available EMS capacity. It recommends surveillance, communication of resource availability, benchmarks and regular review as system-status tools and quality-improvement measures.
In practice, a system with perfect posting and a 90-minute offload delay is a system with fewer ambulances than it thinks. The fix sits partly outside the EMS agency, which is why it needs a seat at the table with hospital leaders and municipal officials.
What to do: Track offload time by receiving facility, share it monthly with hospital partners, and build it into your capacity model.
Pitfall 8: Rolling it out without the workforce
Stout’s work and later reviews both point to the same thing. The 2004 review concludes that dynamic deployment and peak-load staffing can improve response times but may reduce quality, and that results depend on system design, managerial competence and workforce commitment. The Cornell authors likewise note resistance to poorly implemented SSM.
Resistance is usually a signal. Crews push back when moves feel arbitrary, when no one explains the data, or when schedule changes arrive without discussion. Peak-load staffing changes shift lengths and start times, which affects family life and second jobs. Leaders who skip the conversation pay for it later in turnover and grievances.
Our article on peak demand staffing tactics for EMS leaders goes through how pilots can build trust before a full rollout.
What to do: Pilot in one zone or one shift pattern. Share the data, publish what you learn, and adjust before expanding.
A quick self-check for your own system
| Question | A healthy answer | A warning sign |
|---|---|---|
| How do you measure demand? | Unit-hours by hour and weekday, including offload time | Call counts only |
| What happens after a dispatch? | Written rules restore coverage in affected zones | The nearest unit goes, and coverage sorts itself out |
| How many moves per shift? | Tracked, with a ceiling | No one knows |
| How is performance reported? | By zone, acuity and clinical outcome | One citywide average |
| How accurate is unit status? | Audited against real events | Assumed |
| Who owns the plan? | A trained manager with documented authority | Informal practice |
Fixed posts versus dynamic deployment: both have a place
It would be a mistake to treat SSM as universally better. Fixed-post deployment is simple, predictable and easy for crews and the public to understand. For small or low-volume systems, or where stations serve other functions, it can be the right fit. Dynamic deployment offers more flexibility and efficiency for systems with strong demand variation and good data. The right model depends on call volume, geography, staffing and governance. Our guide to EMS deployment models for municipalities walks through how to match the model to the community.
How municipal leaders should review a plan
The Federal Interagency Committee on EMS identified safety for patients and practitioners as a primary mission requirement in its 2019 strategic-plan white paper. It adds that system performance is affected by workforce demographics, technology and data use, standards, policies, threats and resources. That list works well as a review framework for a deployment plan:
- Workforce: Can your staffing and schedules sustain the plan over years, not weeks?
- Technology and data: Is location and status data accurate, and are analysts able to use it?
- Standards and policies: Are the posting rules, response categories and safety policies written down?
- Threats: What happens during a surge, a major incident or a hospital diversion?
- Resources: Is the funding stable, and does the plan hold up if a vehicle or crew is out of service?
Ask for contingency arrangements as part of the review, not as an afterthought. A plan that works only when everything is running normally is not a plan for emergencies. For wider context, see our guide to municipal EMS best practices.
Our perspective
We have spent more than 32 years working alongside EMS agencies and municipalities, and one pattern comes up again and again. Leaders ask us to speed up response, and what they really need is a clearer view of how their system behaves across a full week.
SSM is not a trick for squeezing more out of a fixed number of ambulances. At its best it is a discipline: know your demand, protect your coverage, take care of your people, and measure what matters to patients. When any one of those is dropped, the plan drifts. We would rather see a community adopt a modest, well-governed plan than an ambitious one that crews and dispatchers do not trust.
Our advice is to treat the plan as a living document. Review it with crews, test it against real call data, and be willing to say when a post or a rule is not working. That is how you earn the confidence that makes any deployment model succeed.
— Mike
Getting help with your plan
If you are unsure whether your deployment plan is helping or hurting, we can help. Our System Status Management, Peak-Load Staffing Modeling & Scheduling and Response Time Improvement Analysis services start with your data and your people, and we stay with you from issue identification through deployment. You can see the full list of engagements on our main services page, or reach us at thepscgroup.net to start a conversation. If you are building or rebuilding a system, our resource on designing smarter EMS systems is a good place to begin.
FAQ
What is the biggest risk of system status management?
The biggest risk is poor execution, not the concept itself. Stout warned that SSM can cause substantial harm in the hands of unskilled managers or dispatchers. Coverage holes, excessive moves and weak workforce buy-in are the most common ways that shows up.
Does SSM always improve EMS response times?
No. Research reports that dynamic deployment can improve response times, but results depend on system design, managerial competence and workforce commitment. It may also reduce quality if the plan is built around time alone. Measure clinical and safety outcomes next to response time.
How do we know if our plan is leaving neighborhoods behind?
Map response performance by zone instead of relying on a citywide average, and compare it with demographic data such as income. A San Francisco study found meaningful differences by ZIP code income bracket. Set a minimum standard for every zone and report it regularly.
Should a small system use fixed posts instead?
Often, yes. Fixed posts are simple and predictable, and they suit low-volume systems or places where stations serve other roles. Dynamic deployment tends to pay off where demand varies sharply by hour and day, and where location and status data are reliable.
When should we bring in an outside consultant?
Consider it when you are designing a new system, when response performance is slipping without a clear reason, or when a plan has stalled because of workforce resistance. An independent performance gap analysis can show where coverage, staffing and data are out of step.
Sources
- System Status Management: The Fact Is, It’s Everywhere (JEMS, 1989)
- System Status Management: The Strategy of Ambulance Placement (JEMS, 1983)
- EMS system status management: Match supply to demand (EMS1, 2019)
- The origins of system status management (PubMed, 2004)
- Operations Research Tools for Addressing Current Challenges in Emergency Medical Services (Cornell, 2009)
- Dynamic penalty-based dispatching (Frontiers, 2025)
- San Francisco emergency response and socioeconomic analysis (arXiv, 2021)
- Joint Statement on Lights and Siren Vehicle Operations (NAEMSP, 2022)
- FICEMS Strategic Plan White Paper (2019)
- Ambulance Diversion and Emergency Department Offload Delay (NAEMSP, 2011)
