Emergency Parts Run vs Reschedule: Decision Tree

Why this matters

A tech is on site, the job is half done, and the part needed to finish is not on the truck. Now there is a choice: send someone on an emergency run to get the part and finish today, or pack up and come back another day. Make the wrong call and you either burn a tech's afternoon chasing a cheap part across town, or you leave a customer down overnight when a quick run would have saved them. The right answer depends on a few clear factors. Work through them in order.

Start here: is the customer down hard?

The first question is severity, because it overrides almost everything else.

• If the customer is in a true emergency (no heat in a cold snap, no water, a safety hazard, a business that cannot operate), lean hard toward finishing today. A reschedule on a hard-down customer risks the relationship and may not even be acceptable. The part run is usually justified almost regardless of cost.
• If the customer is inconvenienced but functional, you have room to weigh the run against a return trip more coolly. Keep going down the tree.

If it is not a hard-down: is the part reachable today?

A run only makes sense if it actually finishes the job.

• If the part is in stock at a nearby supplier and you can get it and return within a reasonable window, the run is on the table.
• If the part is across town, out of stock locally, or backordered, the run is off the table. You are rescheduling no matter what, so stop the tech from chasing a part they cannot get and book the return cleanly.

If reachable: does the math favor the run?

Now weigh the true cost of each path. The part's price is rarely the deciding factor. The labor and opportunity cost is.

• If the run is quick and the job is nearly done, finishing today usually wins. A short round trip that closes the ticket beats a full return visit with its own travel, setup, and scheduling cost.
• If the run is long and the remaining work is short, the math often flips. Burning hours of a tech's day for a few minutes of finish work is expensive, and that same time could serve another customer.
• If finishing today displaces a more valuable or more urgent job, reschedule. A tech locked on a parts run is not available for the next call.

If the numbers are close: weigh these tiebreakers

When the run and the reschedule cost roughly the same, let the softer factors decide:

• Customer relationship. A loyal repeat customer or a frustrated one who has already waited tilts toward finishing today.
• Second-trip friction. Some jobs are painful to return to (hard access, gated property, a customer who is rarely home). Avoiding a second mobilization has real value.
• Tech utilization. A slow day makes the run cheap because the tech had no better use of the time. A packed day makes it expensive.
• Diagnostic certainty. If you are sure the part fixes it, the run is safe. If there is a chance the part is wrong and you will be back anyway, do not compound the trip.

If you reschedule: do it right

Choosing the reschedule is not the failure. Handling it badly is.

• Order the part immediately so it is in hand before the return visit, not chased again on the day.
• Book a firm return slot while you are still on site and the customer is in front of you.
• Leave the customer informed, including why the part was not on the truck and exactly when you will be back.

The bottom line

Hard-down customers get the run unless the part is unreachable. Functional customers get the run only when the part is close and the labor math favors finishing. When it is close, relationship and second-trip friction break the tie. The cheap part is almost never the reason to drive across town. The customer's situation and the tech's time are.

References

• See related: The Supplier Backorder Customer Communication
• See related: The Defective Part Out of the Box: Decision Tree
• See related: Sub vs Self-Perform This Job: Decision Tree
• Trade-standard practice for field dispatch and service scheduling