The Surge Playbook: Prioritizing Jobs When Everyone Calls on the Same Day

Certain events send every affected homeowner reaching for the phone on the same day — a storm that damages a dozen roofs on the same street, a heat wave that breaks a dozen aging AC units at once, a cold snap that finds every weak furnace in town. On a normal day you can serve customers roughly in the order they called. On a surge day, that approach means someone with an actual emergency waits behind someone with a minor issue, purely because of when they happened to call.

Why first-come-first-served breaks down here

The order calls come in has no relationship to the order jobs should actually be handled in. A homeowner with an active leak through the ceiling and a homeowner who noticed a few missing shingles are both calling about storm damage, but they are not the same priority, and treating them identically because they called within ten minutes of each other is a bad use of a scarce resource.

This is also the moment reputational damage is most likely, both ways — the customer with the real emergency who waited behind lower-priority calls will remember it, and so will everyone they tell. Getting priority order right on a surge day matters more than getting it right on a normal one.

Deciding when to bring in outside help

Part of the surge playbook is knowing, ahead of time rather than in the moment, at what point demand exceeds what your own crews can reasonably handle safely and well. Some businesses have a standing relationship with a subcontractor or a neighboring crew specifically for these days; others decide in advance how far out they’re willing to push the schedule before they start turning away lower-priority work rather than doing it badly.

Whichever approach fits your business, it’s a decision worth making calmly in advance rather than improvising for the first time in the middle of the busiest day of the year, when the pressure to say yes to everything is highest and the judgment to say no where it matters is hardest to access.

Building the triage into the intake

A short set of questions, asked the same way every time — is there active water or safety risk, is anyone unable to stay in the home or use essential systems, how long has the issue been happening — turns a chaotic call queue into a sorted one. This can be built into a script for a person answering phones or into an automated intake flow, as long as the questions are consistent.

Whoever or whatever captures the intake should flag true emergencies immediately and separately from the general queue, so the person managing the day’s schedule can see the priority list rather than a flat chronological one.

What still needs a person managing the day

Turning the triage answers into an actual schedule — who gets seen first, how many crews get reassigned from planned work to storm response, what gets honestly told to customers further down the list — is a real-time judgment call for whoever’s running operations that day, not something to hand off to a fixed rule.

And the communication to everyone not seen today matters as much as the triage itself. An honest, specific update — where they are in the queue, roughly when to expect a crew — keeps a delayed customer patient in a way that silence never does, surge day or not.

Debrief after the surge passes

Once the immediate rush is over, a short debrief — what worked, where the triage broke down, which promises turned out to be unrealistic — while it’s still fresh is worth far more than trying to reconstruct lessons months later at the start of the next season.

Surge days are infrequent but predictable in most trades — the same kind of storm, the same kind of heat wave, tends to recur. Treating each one as a chance to improve the playbook, rather than just surviving it, is what makes the next surge day go more smoothly than the last.