The most expensive five seconds in dispatch

Double-booking happens in the moment a dispatcher drags one more job onto an already-full tech, certain there's room, and there isn't. Nobody notices until the tech is standing in a driveway across town from where the next customer is waiting. By then you've blown a promised window, you're fielding an angry call, and you're scrambling to cover a job that should never have been booked.

It almost never feels like a mistake when it happens. The board looked open. The tech "usually" finishes that kind of work fast. The conflict only becomes obvious once it's too late to fix cheaply.

Why it keeps happening

  • The schedule lives in too many places. A job on the calendar, a callback promised over the phone, a "quick favor" texted to a tech directly. None of them can see the others, so none of them can warn you.
  • Time isn't actually blocked. A tech is at a dentist appointment until 11, or in a training block, but the board shows that time as bookable. So you book it.
  • Jobs have no real duration. If a job is a dimensionless point on the calendar instead of a start-and-end span, two jobs can occupy the same hour and the schedule looks fine.
  • Same-day emergencies get jammed in. The emergency has to go somewhere, so it lands on whoever's name is closest to the cursor — on top of work that's already there.

The fix is structural, not disciplinary

You can't train your way out of double-booking by telling dispatchers to "be more careful." The schedule has to make the conflict impossible to miss. Three things have to be true:

  1. One board, one source of truth. Every job, every tech, every commitment on a single live view. The Dispatch Efficiency Playbook makes the case in full: phone calls and sticky notes are where conflicts hide.
  2. Every job has a start and an end. When you schedule a job with a real time span instead of a vague "morning," the board can actually reason about whether a second job overlaps the first.
  3. Non-job time is blocked too. Breaks, training, PTO, a long lunch — block them on the board the same way you'd block a job. If the time isn't available, the system should refuse to pretend it is.

In Hosting Field, scheduling a job with start and end times and blocking out breaks, training, and PTO on the dispatch board is exactly how this works — and the board warns you before you double-book a tech. The warning fires at the moment of the mistake, when it costs nothing to fix, instead of at 9 a.m. in a customer's driveway.

Build slack in on purpose

A board packed to the minute breaks the instant one job runs long — and a job running long is what creates most double-bookings in the first place. Leave 15–20% of each tech's day unbooked. That buffer absorbs the overrun without cascading into the next appointment. The same discipline that protects your routes from collapsing (see reducing windshield time) protects your schedule from conflicts.

What clean scheduling buys you

Every prevented double-booking is a window you kept, a callback you didn't have to make, and a customer who never had a reason to leave a one-star review. It also protects your first-time fix rate — a tech who arrives late and rushed is a tech who misses things. The cheapest conflict is the one the board catches before anyone gets in a truck.