Two Jobs Overlap: Which to Prioritize Decision Tree
Why this matters
A tech is on one job, a second one is waiting, and there are not enough hours or hands to do both on time. Maybe the first job grew, maybe a same-day emergency landed, maybe two appointments collided in the schedule. Whoever decides which job wins is rationing the company's scarcest resource - labor hours - and the choice ripples into customer trust, contract obligations, and revenue. Deciding by gut ("the loudest customer") produces inconsistent, unfair outcomes. A simple priority ladder makes the call defensible and repeatable.
The governing principle: rank by consequence of delay, then by obligation, then by recoverability - not by who called most recently or yelled loudest.
The situation
Overlaps usually take one of these shapes:
- An active emergency lands while a tech is mid-job on routine work.
- Two scheduled jobs collide because the first ran long.
- A high-value or contract-obligated job competes with a smaller walk-in.
- A job at risk of an SLA or warranty deadline competes with a flexible one.
The right answer depends on what is actually at stake at each site, which the dispatcher must read quickly rather than defaulting to first-come-first-served.
What is at stake
Customer harm: A job where delay means flooding, no heat in a freeze, or a safety hazard outranks a job where delay means inconvenience. Harm-if-delayed is the top sort key.
Obligations: Contract SLAs, membership guarantees, and warranty-callback deadlines are promises with teeth. Missing them can cost the contract or trigger penalties. Honor commitments before chasing one-off upside.
Recoverability: A job that can be rescheduled cheaply (flexible customer, no harm from waiting) should yield to one that cannot. Reschedulability is a feature - use it.
Fairness and trust: Customers tolerate a delay far better when they hear it early with a real reason. The cost of a delay is mostly in the silence, not the wait.
The decision tree
Sort the competing jobs through these gates in order:
Does either job involve an active safety hazard or escalating property damage (gas, active flood, no heat in dangerous cold, electrical hazard)? -> That job WINS. Safety and damage-in-progress outrank everything. Stabilize or dispatch to it first.
With safety equal, is either job under a hard obligation - a contracted SLA, a membership response guarantee, or a warranty callback within its window? -> The obligated job WINS over a non-obligated one. You promised it; keep the promise or you risk the relationship and possible penalty.
With obligation equal, can one job be rescheduled with little harm and a cooperative customer, while the other cannot? -> Serve the NON-reschedulable job; move the flexible one. Call the flexible customer early, explain, and offer the next concrete slot.
Still tied (both flexible, no safety, no obligation)? -> Prefer the job already in progress (finishing it avoids a second mobilization and a half-done site) or the one whose delay creates the larger downstream pileup. Avoid leaving a job partially complete unless making-safe and returning is genuinely cleaner.
Can you split the difference - send a second tech, pull from another route, or stabilize one and return? -> Do that before forcing a winner-loser outcome. Reinforcement beats triage when it is available.
What to document
- Both jobs, their symptoms, and the priority classification you assigned (safety / obligation / flexibility).
- The decision and the reason, so a manager can see the call was principled.
- The notification to the deferred customer: time called, what you told them, and the new commitment you made.
- Any SLA or warranty deadline that drove the decision.
The note that matters most is proof you told the bumped customer early and gave them a real new time.
Communicating the delay
The deferred customer's experience is decided in the first phone call, not in the wait. Call before the missed window, not after. Lead with the reason ("an emergency came in"), give a specific new time (not "sometime later"), and offer something if the inconvenience is real. A customer who is bumped well often becomes more loyal than one whose job went perfectly, because they saw how you handle pressure. A customer who finds out by watching the window pass in silence remembers it for years.
When to add capacity instead of choosing
Forcing a winner is a last resort. Before you do, check whether a second tech, a nearby route, or a subcontractor can cover one job. The cost of pulling in help is almost always less than the cost of a lost contract or a damaged relationship from a botched overlap. Choose between jobs only when you genuinely cannot cover both.
Avoiding the overlap in the first place
Most overlaps are scheduling failures, not bad luck. The two most common causes are jobs that routinely run longer than their booked slot and same-day add-ons stacked without buffer. A dispatcher who tracks actual job durations against booked durations can size slots realistically instead of optimistically, which removes the daily collision. Building a small float into the route - one deliberately empty slot per tech per day - absorbs the emergency that would otherwise force a triage decision. The float looks like lost capacity on paper, but it is cheaper than the cascade of late arrivals, bumped customers, and overtime that an over-packed schedule produces. Prioritization is the firefight; honest slot sizing and a daily buffer are how you stop starting fires.
References
- Contractual SLA and service-guarantee terms (your membership and maintenance-agreement language) - the source of hard obligations.
- ConsensusDocs service-agreement conventions on response-time commitments.
- State contractor-licensing standards of practice on honoring scheduled commitments and timely communication (varies by state).
- OSHA general duty principles (29 U.S.C. 654) - life-safety and damage-in-progress as the top priority sort key.