Route Density vs Strict Appointment Times: Decision Tree

Why this matters

Every dispatcher eventually fights the same tension: booking jobs in the order customers asked for them versus booking jobs in the order that keeps the truck moving efficiently. Chase pure geography and you break specific promises. Chase pure promise-keeping and you burn hours of the day in traffic between far-flung stops, which shows up as fewer jobs done, more overtime, and a tired tech who arrives at the last call in a worse mood than the first. Neither extreme wins by itself. The skill is knowing which one to bend on, call by call.

Start here: how firm is the time actually

Not every appointment window carries the same weight. Sort the job in front of you before deciding anything else.

• A hard commitment (a customer took time off work, a commercial account needs a specific window for access, a callback promise was already made for a time) should not move for density. The promise is the point.
• A soft window ("morning is fine," "whenever works," a first-time customer with no stated preference) has real room to shift for route efficiency without anyone noticing or minding.

If you cannot tell which one you are looking at, ask. A thirty-second call to confirm flexibility beats guessing wrong in either direction.

If the appointment is a hard commitment, protect it and route around it

1. Lock the time first, then build the rest of the day's stops around that fixed point like a scaffold.
2. Accept the less-efficient route on either side of it. A slightly longer drive to make a promised window costs less than a broken promise costs in trust and reputation.
3. Do not silently downgrade a hard commitment to a soft one just because the board would look tighter without it. If the day's density is genuinely broken by protecting the promise, that is information about the day's booking, not license to break the promise.

If the appointment is a soft window, optimize for the cluster

1. Group it with the nearest job on the board that shares a similar window, rather than leaving it in whatever order it was booked.
2. Prefer filling in a gap between two firm stops over adding a new far-side trip. A soft-window job slotted into an existing drive path costs almost nothing; the same job added as a new destination costs a full round trip.
3. Tell the customer the tightened window as soon as it is set, not as a surprise call-ahead an hour before. "We can get you in the late morning, does that still work?" keeps the soft window soft instead of quietly becoming a promise you never confirmed.

If density and promises are in direct conflict on the same day

This is the real test. Two customers both want a similar time, but only one fits the route without a long crosstown drive.

• The customer who was explicit and firm about the time wins the slot. Route density is a tool for filling the schedule efficiently, not a reason to bump a kept promise.
• The customer with the soft window gets offered the next-best slot, ideally one that still fits the route, with a clear reason if asked: "We had a fixed appointment on that side of town, this time still works well with your job."
• If neither customer will bend and the route truly cannot support both, the honest answer is that the day is overbooked for the area it is trying to cover, not that one customer is being unreasonable. Flag it rather than force a bad fit.

If a booked-tight route starts falling apart mid-morning

A traffic snarl, a job running long, or a wrong address estimate can turn a well-planned dense route into a mess by 10 a.m.

1. Re-check which of today's remaining stops are hard commitments before touching anything. Those are non-negotiable anchors.
2. Re-sequence the soft-window stops around the anchors, not the other way around.
3. Call ahead on anything sliding, even the soft ones. A soft window with no promised time still deserves a heads-up when the actual arrival moves by more than a few minutes.

The recap

1. Classify every appointment as hard commitment or soft window before you build the route.
2. Route hard commitments as fixed anchors and accept the drive-time cost around them.
3. Cluster soft windows around the anchors and around each other for density.
4. When the two conflict, the firmer promise wins the slot, and the softer one gets the next-best option with a reason.
5. When a route breaks mid-day, re-anchor to the hard commitments first, then re-sequence everything else.

References

• See related: The Scheduling Buffer: Why You Need Slack
• See related: Communicating ETA Changes Without Annoying the Customer
• Trade-standard practice for field-service route sequencing and dispatch