The Storm or Emergency Demand Spike Decision Tree

Why this matters

A storm, a heat wave, a cold snap, or a regional outage can flood your phone with more work than you can ever do in the days you have. Handle the spike well and you earn loyal customers, strong reviews, and a reputation that outlasts the event. Handle it badly and you burn out your crew, botch jobs in a rush, and leave a trail of customers you promised and never reached. This is a triage problem. The answer is rarely "do everything." It is "do the right things in the right order and tell everyone the truth."

Start here: is the spike short or sustained?

Before you change anything, judge how long the surge will last. The whole response depends on it.

• If it is a short spike (a one-day storm, a brief outage), the move is to push hard with the crew you have, defer non-urgent work, and ride it out without restructuring.
• If it is sustained (a multi-week heat wave, a regional disaster), you cannot sprint the whole way. Pace the crew, bring in temporary help if you can, and plan for a marathon.

Misjudging this is the classic error. Sprinting a marathon breaks your people; pacing a sprint loses the window.

Step 1: triage every incoming call by severity

Not all "emergencies" are equal. Sort calls the moment they come in so the truly urgent rise to the top.

• True emergency: a safety hazard, active damage, or a vulnerable household (no heat in a deep freeze, no cooling for someone medically fragile, water actively flooding). These jump the line.
• Urgent but stable: the customer is uncomfortable or inconvenienced but safe. These get scheduled fast, but after true emergencies.
• Routine that can wait: anything that is not made worse by a short delay. These get deferred without guilt.

Give whoever answers the phone a one-page severity guide so the sort happens consistently, not by gut feel under pressure.

Step 2: decide who you serve first within a tier

Once calls are tiered, order within each tier on purpose, not first-come-first-served alone.

• If a job protects against further damage, prioritize it. Stopping active damage prevents a bigger job later.
• If existing customers and agreement-holders are calling, weigh serving them first. They are your base, and the spike is when loyalty is won or lost.
• If two jobs are equal, let geography break the tie. Cluster nearby calls to cut drive time and squeeze more stops into the day.

Step 3: protect capacity by deferring honestly

The single biggest failure in a spike is over-promising. A customer told "we'll be there today" who never sees a truck is angrier than one told the truth up front.

• If you genuinely cannot reach someone soon, say so plainly and give an honest window.
• If a job can safely wait, book it for after the surge and tell the customer why.
• If you are full, stop taking new same-day commitments rather than stacking promises you cannot keep.

A realistic "we can get to you in a few days" beats a hopeful "today" that becomes a broken promise.

Step 4: extend capacity without breaking the crew

If the spike is sustained, look for ways to do more work without simply demanding more hours from exhausted techs.

• If you can add temporary help, bring in a trusted subcontractor or an on-call hand for the overflow.
• If parts are the bottleneck, stock the few high-failure items the event drives before you run out.
• If the crew is the bottleneck, extend hours deliberately and in shifts, with mandatory rest, rather than running everyone flat out until they make mistakes.

Pushing tired people into long days produces sloppy work and callbacks that cost you the time you tried to save.

Step 5: hold quality even under pressure

Speed is the temptation; a botched rush job is the real cost. Keep the non-negotiables non-negotiable.

• Keep the safety steps. Skipping a lockout or a leak test to save minutes is how a fast day becomes a liability.
• Document what you did, even briefly. A spike generates follow-up calls, and a thin record makes them harder.
• Watch for the rushed re-call: a job redone in two days erases the time you saved by rushing it once.

Step 6: communicate proactively, not reactively

During a spike, silence reads as abandonment. Get ahead of it.

• Post your status (taking emergencies, booking a few days out) wherever customers look.
• Confirm and update booked customers so they are not waiting in the dark.
• After the event, follow up with anyone you deferred. The surge ends; those relationships do not have to.

References

• Trade-standard practice: emergency-call triage and severity-based dispatch.
• OSHA: worker fatigue and extended-shift safety guidance during high-demand periods.
• See related: Peak-Season Burnout Risk; The Seasonal Staffing Ramp-and-Cut Decision Tree.
• SBA (U.S. Small Business Administration): disaster and business-continuity planning resources.