A Regional Disaster Hits While Normal Jobs Are Still Scheduled: Decision Tree

Why this matters

A storm or regional disaster does not wait for your calendar to clear. It hits with a full week of routine jobs already booked, existing customers expecting a technician, and a phone that is now also ringing with emergency calls from people who need help today. Every already-scheduled job represents a promise you made before the world changed, and every one of those customers deserves an honest answer about whether that promise still holds. This is a rebooking and communication problem, not a triage problem alone: you already have a book of commitments to work through, on top of the new demand.

Start here: is anyone on your existing schedule now in the disaster's path or its aftermath?

Before touching the board, sort your booked customers by whether the event actually affects them.

  • Customers unaffected by the event (outside the impact area, or the event does not change their situation) generally keep their original appointment. Do not disrupt bookings that do not need to move.
  • Customers affected by the event need a fresh look, because their original reason for the appointment may now be irrelevant, urgent, or dangerous to attempt.

Step 1: re-sort affected existing appointments by new urgency, not original order

A routine maintenance visit booked two weeks ago and a customer whose situation just became genuinely urgent because of the storm are not the same priority anymore, even though the maintenance visit was on the books first.

  • If the original job is now urgent (the storm damaged the exact system you were coming to service, or created a new safety issue), treat it like any other true emergency in your triage.
  • If the original job is now irrelevant or unsafe to attempt (access is blocked, the property is unsafe, the customer has evacuated), reschedule it and say so plainly rather than showing up to a job that cannot happen.
  • If the original job is unaffected in substance but the customer's day has been upended, call ahead to confirm before assuming the appointment still works for them.

Step 2: decide what to do with routine, unaffected work when the crew is needed for emergencies

Even customers outside the disaster's path may find their routine appointment gets bumped, not because their job matters less, but because your capacity is now split with urgent regional demand.

  • If you can hold routine appointments without compromising emergency response, keep them. Do not cancel work that does not need to move.
  • If the surge is large enough that emergency response requires pulling crew off routine work, proactively reschedule the routine jobs rather than letting them collide with an emergency call on the day. Reach out before the appointment, not as a no-show.

Step 3: rebook with a real commitment, not a vague "we'll call you"

A customer bumped for a legitimate reason still needs a concrete next step, or the bump reads as a cancellation with extra steps.

  • Give an honest window for rebooking, even if it is longer than normal ("within the next week, once the surge settles").
  • Note the rebooking in your system immediately so it does not get lost once the surge takes over everyone's attention.
  • If a customer's bumped job has sat unaddressed for an uncomfortably long stretch, proactively follow up rather than waiting for them to call and ask.

Step 4: protect the customers who were flexible for you

Customers who agreed to move without complaint are your easiest relationships to keep and your easiest ones to damage by forgetting them once the surge occupies your attention. Track who was bumped and confirm every one of them gets rebooked once the acute phase passes, not just the ones who called back to ask.

Step 5: keep a written log of what moved and why

A disaster reshuffles a lot of appointments quickly, and memory is not a system under that kind of load. Log every rescheduled job with the reason and the new commitment, so nothing falls through when the surge itself is over and normal operations resume.

The recap

  1. Sort existing bookings by whether the event actually affects the customer.
  2. Re-prioritize affected appointments by new urgency, not original booking order.
  3. Only bump unaffected routine work if capacity genuinely requires it, and do it proactively.
  4. Rebook with a concrete window, never a vague promise.
  5. Track and honor every bumped customer once the surge settles.
  6. Log every change in writing so nothing is forgotten in the reshuffle.

References

  • Trade-standard practice for disaster-driven schedule triage and rebooking
  • See related: The Storm or Emergency Demand Spike Decision Tree
  • See related: A Cancellation Opens a Same-Day Gap: Decision Tree