The emergency tax nobody budgets for
Every field service operation gets the call: a flooded basement, a dead furnace in January, a walk-in cooler down at a restaurant on a Saturday. Emergency work is the highest-margin, highest-loyalty revenue you have — a customer in a crisis remembers who showed up. But it's also the single fastest way to detonate a day that was planned to the minute. One emergency jammed onto a full board cascades into three blown windows, two angry callbacks, and a tech working until 8 p.m.
The instinct is to treat each emergency as a one-off scramble. That's the mistake. Emergencies aren't rare exceptions — they're a predictable volume you can plan capacity around, even if you can't predict the specific call.
Reserve capacity before you need it
The teams that handle emergencies calmly don't have more techs — they hold the right slack. Three structural moves:
- Leave the board 15–20% open. A schedule packed to 100% has no room to absorb anything. The same buffer that protects you from a job running long is what lets you take the emergency without bumping scheduled work.
- Run a rotating "flex" tech. On any given day, designate one tech whose board is deliberately light — first in line for same-day work. Rotate the role so nobody's pay suffers and everybody stays sharp on emergency work.
- Pre-decide the escalation tiers. What counts as a true emergency (safety, property damage, total loss of service) versus an "urgent" that can wait until tomorrow morning? If dispatch has to litigate that in the moment, you've already lost time.
The on-call rotation that doesn't burn people out
After-hours and weekend coverage is where good techs quit. A fair on-call system is non-negotiable:
- Rotate predictably. A published rotation weeks out beats "whoever picks up." People can plan their lives around a known schedule.
- Pay for the burden, not just the call. On-call standby pay plus a premium call-out rate respects that being tethered to a phone is itself a cost.
- Cap the load. Nobody should pull on-call two weeks running. Burnout here cascades into turnover you can't afford.
Make the board absorb the shock
When the emergency lands, the schedule has to re-flow fast — and the dispatcher has to see the damage before committing. The right tech is usually the closest one with the right skills and the most slack, not whoever's name is under the cursor. Skill-aware, location-aware assignment keeps you from sending an emergency to someone who then has to drive across town, blowing the next window in the process.
In Hosting Field, the dispatch board shows every tech's day as a live, per-technician view with an unassigned queue, so a same-day call drops into the board where you can see exactly whose schedule it dents — and the board warns you before you double-book the tech you're tempted to overload. Status discipline (enroute, on-site, complete) means you know in real time who's actually free, not who should be free.
Protect the customers you didn't cancel on
The hidden cost of an emergency is the customer whose window you quietly blew to make room. The fix is the same discipline that earns five-star reviews everywhere else: proactive communication. The moment a scheduled job has to move, the customer hears it from you — "we had an emergency and need to shift you to 2 p.m., does that work?" — before they're standing by the window wondering where the truck is. A bumped customer who got a heads-up forgives you. One who got silence leaves a one-star review.
What to measure
- Same-day absorption rate — emergencies handled without bumping scheduled work. The closer to 100%, the better your capacity planning.
- Emergency response time — booking-to-arrival for true emergencies. This is what customers feel most acutely, and it's one of the KPIs that actually matter.
- Schedule disruption — how many scheduled jobs got moved per emergency. Rising disruption means your buffer is too thin.
Emergencies will never stop coming. The goal isn't to predict them — it's to build a day that can swallow them whole and keep every other promise you made.