The schedule lies about the part between the jobs
Open a dispatch board and you see the jobs — a two-hour install at nine, an hour of service at eleven, a diagnostic across town at one. It looks like a sensible, finishable day. What the board doesn't show, unless you make it, is the part between the jobs: the forty minutes of driving from the install to the service call, the hour of crosstown crawl to the afternoon diagnostic. Add the work up and the day fits in eight hours; add the driving and it doesn't fit in ten. The schedule looked full because it was only counting half of what the tech actually has to do.
This is the quiet way a day falls apart. Nobody scheduled a bad job; they scheduled a sequence of fine jobs that, laid out across a map, were never reachable in the time allowed. The tech runs late not because they're slow but because the plan never accounted for the road. And the cost compounds down the day: the arrival window you promised the two-o'clock customer slips, the last job gets bumped to tomorrow, and the dispatcher spends the afternoon apologizing for a failure that was baked into the schedule before the truck ever left the yard.
Why drive time is the hardest thing to feel
Work is easy to estimate because you've done it a thousand times — a furnace tune-up is an hour, you know it in your bones. Drive time is the opposite: it's invisible until you're sitting in it, it changes with traffic and time of day, and it lives in the gaps where nobody's watching a clock. So the brain does the natural thing and rounds it down to nothing. "They're both on the north side" becomes a mental zero, when the truth is twenty-five minutes of surface streets. Do that across five stops and you've silently spent two hours of the day on driving you never put on the calendar.
The other trap is sequence. The same five jobs can be a tight, sensible loop or a back-and-forth disaster depending only on the order you run them. A schedule built by dropping jobs onto the board as the calls come in — first booked, first slotted — almost never produces the efficient loop; it produces a zigzag that crosses the same part of town three times. The work is identical. The windshield time is double. And no amount of the tech driving faster fixes a route that was ordered wrong on the board.
How Hosting Field's Travel-Time Estimator works
Hosting Field puts the drive time on the calendar before the day starts. The Travel-Time Estimator takes a technician's stops for the day and gives you a per-leg breakdown — distance and estimated drive time between every consecutive pair of jobs — so the part of the day that used to be invisible becomes a number you can see and plan against. The estimate uses straight-line (haversine) distance between the stops and a configurable average speed, turning into a human-readable label like "1 h 23 min" of total driving for the run.
The second half is sequence. Hit Optimise route and the estimator reorders the stops with nearest-neighbour routing to cut the total drive — turning the zigzag the booking order produced into a tighter loop, and showing you the new total so you can see what the reorder bought you. The dispatcher who used to eyeball the map and hope now has the actual drive figure for the day and a one-tap way to shrink it.
The honest boundary, and it matters: this is a planning estimate, not live navigation. The distance is great-circle, not turn-by-turn road mileage, and the time comes from an average speed, not a live traffic feed — so it's a clear-eyed approximation for building a realistic day, not a GPS that knows about the accident on the interstate. The optimiser uses nearest-neighbour, a fast, good heuristic, not a guaranteed-perfect routing solver. What the estimator does — and does well — is replace "they're both on the north side, it'll be fine" with a real number and a sane order, so the day you build is one the tech can actually finish. It won't drive the truck or reroute around a closure; it makes sure the plan was reachable in the first place, which is the part that was breaking.
Using it to build deliverable days
- Estimate the loop before you commit the windows. Lay out the day's stops, look at the total drive, and only then promise arrival windows. A window set without knowing the drive is a guess; one set after is a plan.
- Optimise, then sanity-check the order. The nearest-neighbour reorder is almost always better than booking order, but you know things it doesn't — a customer who's only home after noon, a job that has to come before another. Take the optimised loop as a strong starting point and adjust for the real-world constraints it can't see.
- Tune the average speed to your territory. A rural fleet on highways and a city fleet on surface streets don't drive at the same pace. Set the average speed to match how your trucks actually move, and the estimates get honest enough to schedule against.
What to measure
- Jobs completed as scheduled versus bumped. The clearest sign your days are deliverable: how often the last job on the board actually gets done that day instead of rolling to tomorrow. Days built around real drive time should bump far less work.
- On-time arrival rate. When the schedule accounts for the road, the windows you promise start getting hit. A rising on-time rate after you start estimating drive time is the plan finally matching reality.
- Total daily drive time per tech. Watch this fall as you optimise routes instead of running booking order. Every hour of driving you remove is an hour back for billable work — the same hour the windshield-time math has always been about.
A full-looking board and a finishable day are not the same thing, and the difference is almost always the driving nobody counted. The miles between the jobs are real work the tech has to do, and a schedule that pretends otherwise sets the truck up to run late from the first stop. Hosting Field's Travel-Time Estimator puts that hidden time on the calendar and tightens the order with one tap, so the day you hand the tech is one they can actually finish. Stop scheduling the wish and start scheduling the drive, and the afternoon of apologies turns back into an afternoon of work.