System Status Management vs Station-Based EMS: What Posting Actually Does to Your Day

Two medics finish the same 12-hour shift on paper. One spent it at a station with a kitchen, a recliner, and a bed she never got to use but knew was there. The other spent it in the truck — three post moves before lunch, a gas station bathroom, and a nap that never happened because the tablet kept reassigning her.

Same hours. Same job title. Two different days.

The difference usually isn't the schedule. It's the deployment model — where your unit sits when it isn't on a call. And it's the part of a job that almost never makes it into the posting, because nobody thinks to describe it.

The two models, plainly

Station-based deployment is the older shape and the one most people picture. Your unit has a home. You start there, you clear back to it, and between calls you're in a building — with a bathroom, a kitchen, somewhere to sit that isn't a captain's chair. Historically, ambulances ran out of fixed bases, most commonly fire stations, positioned according to political boundaries rather than where calls actually happen. In rural areas and volunteer services, it remains the only model that makes sense.

System status management (SSM) flips the question. Instead of asking "where does this unit live," it asks "where is the next call most likely to come from, at this hour, on this day of the week?" — then puts the truck there. Those locations are called posts, and moving between them is posting.

SSM was introduced to EMS more than four decades ago by economist Jack Stout, who wrote the concept up for JEMS in the early 1980s and is widely credited as the father of high-performance EMS. The idea is genuinely elegant: demand for ambulances isn't random. It clusters by hour and by day in patterns you can see in years of call data. If you know Tuesday at 17:00 pulls calls from the east side, don't leave the truck parked west and drive across town after the tones — be east already.

The classic version uses a set of pre-planned hourly deployment maps — a plan for each hour of the week — and shuffles available units to match. Newer dynamic deployment systems do it with software making near-real-time recommendations off a forecasting model, adjusting as units go available and come out of service.

Why services do it

Because it works on the metric services are judged by. When the truck starts closer to the call, response times fall — and in most contracts, response-time compliance is the number attached to the money. That's the whole business case, and it's not a cynical one: a shorter distance from wherever the unit is sitting to wherever it's going is also a shorter stretch of emergency driving, which is one of the more dangerous things any of us do.

What it actually does to your shift

Here's the part the recruiting page skips.

Downtime stops being a place. On a station system, the gap between calls has walls. On a heavily posted system, it's a parking lot. That changes small things that turn out to be large things: where you eat, how you use a bathroom, whether "rest" means lying down or means reclining a seat. None of it shows up in your hours worked.

Post moves accumulate as invisible work. Every reassignment is a drive — engine on, seatbelt on, attention on. It isn't a call, it doesn't count as a transport, and it doesn't appear on any productivity metric. But the number of post moves in a shift is one of the more reliable predictors of how crews feel about a system, and it deserves to be counted as workload even though it usually isn't.

Your fatigue gets measured by the wrong number. Most services track unit hour utilization (UHU) — transports divided by staffed unit hours. Ten trucks staffed around the clock is 240 unit hours; 120 transports across that day gives a UHU of 0.5. Agencies commonly target somewhere in the 0.30 to 0.50 range and push toward the lower end specifically to reduce crew fatigue. It's a useful number, but it counts calls, not driving. Two crews at identical UHU can have wildly different shifts if one of them spent an extra two hours moving between posts.

Shift length changes what a given UHU costs you. A busy ratio is survivable across 12 hours in a way it isn't across 24 — shorter shifts tolerate higher utilization, while 24-hour shifts with high usage and little chance to rest carry real risk. This is why services running 24s usually aim lower, and why "we're at 0.4" means something different depending on the pattern underneath it. (If you're comparing the patterns themselves, we mapped 24/48, 48/96, Kelly days, and 12-hour cars here.)

Four things people get wrong about it

Worth knowing before you turn down a job — or accept one — over the word "posting."

1. SSM doesn't automatically mean street corners. Where a post physically is comes from agency policy, not from the strategy. A post can be a hot-spot intersection, a lot a few blocks away that's safer and more comfortable, or a purpose-built station. Plenty of dynamic systems post to buildings.
2. Constant post-to-post bouncing is a symptom, not a feature. Well-run systems use movement patterns designed to reduce total unloaded miles. If crews are ping-ponging all shift, that's an implementation problem people in the industry name as one — not the inevitable price of the model.
3. It doesn't have to abandon the edges of the county. Coverage weighting can be built in to balance raw call demand against geographic coverage. Whether your service does that is a fair question to ask.
4. Dynamic deployment and classic SSM aren't the same thing. Fixed hourly plans and a live algorithm behave differently on the street. If someone tells you the system is "dynamic," it's worth asking which one they mean.

The questions worth asking before you take the job

Not to be difficult — because these are the details that decide what your Tuesday feels like, and most of them are answered readily if you ask.

• How many post moves does a typical unit make in a shift? Somebody knows this number.
• Are posts buildings, or lots? Ask specifically about the overnight posts.
• Where do crews eat, and is there a meal-break policy that actually holds?
• What's the UHU target, and what shift length is it paired with? 0.45 on 12s and 0.45 on 24s are different jobs.
• Is there a late-call policy? On a system optimized to keep units available, the last hour is exactly when a call lands.
• What happens on the overnight? Some services post hard until 22:00 and then let units sit. Some don't.

None of these have a universally right answer. A tightly posted urban system with real relief at shift end and a lot with a bathroom can be a fine place to work. A station system with a 0.6 UHU and no meal policy can be worse. What you're trying to find out is which trade you're actually making.

Where the schedule fits

One thing that doesn't change between the two models: you still need to know which days are yours. Whether you're posting all shift or sitting in quarters, the rotation underneath — 24/48, 48/96, a Kelly cycle, day cars and night cars — is what decides when you're home, and it's the part you can plan around even when the shift itself is unpredictable. (Sleep is the piece that takes the most damage on a heavily posted system; our shift-work sleep guide covers anchoring rest when downtime isn't guaranteed.)

That's what Duty Pals is for: set your rotation once — whatever pattern your service runs — and years of your real on and off days lay themselves out on a calendar you can actually see, so the parts of your life that happen off the truck can be planned around it. It doesn't know where dispatch will post you at 14:00. It does know whether the 14th is yours. Duty Pals is currently in pre-registration; you can sign up to be notified when it launches.

Deployment models, UHU targets, meal-break rules, and post policies vary enormously by service and, where applicable, by union contract. Everything here is a map of how these systems are generally built — your agency's policy and your own agreement are the authority on how yours works.