Technician scheduling and dispatch

Take four technicians with six stops each, a normal day. One job runs ninety minutes over. Three jobs behind it now have to move.

Each move is two conversations: the customer who was promised an afternoon window, and the technician whose next address just changed. At four minutes a conversation that is roughly twenty four minutes of office time for one bad job, and the day is not over. Three disruptions in a week, which is a quiet week, is over an hour of somebody doing nothing but rearranging and explaining.

The hour is the part you can see. The expensive part is the customer nobody got to in time, who is now a voicemail at five past four and a one star review on Saturday. That call did not get missed because anyone was careless. It got missed because the only copy of the plan was in one person's head while they were on the phone about something else.

A schedule that only knows times and addresses cannot answer the question that actually matters, which is what should move.

It needs to know where each person is right now and how long it takes to get anywhere else, because a twenty minute gap in a dense suburb is a different thing from a twenty minute gap with a forty minute drive at the end of it. It needs to know who is licensed or certified for what, so the apprentice does not inherit the gas line. It needs to know what is on each truck, because the fastest reschedule in the world is useless if the part is in the other van.

And it needs to know which jobs can slide and which cannot. A tenant who took a morning off work, a permit inspection with a fixed window, an elderly customer who will not open the door after dark: those are not the ones to move, and a dispatcher who has to remember which is which will eventually move the wrong one.

On a whiteboard, moving a job is: rub it out, write it somewhere else, text the technician, call the customer, remember to change the paperwork, and hope nobody was mid-drive to the old address.

It should be one drag. The technician sees the new order on their phone, the customer gets the new window without anyone dialing, and the job record keeps a note that it moved and why. That last part sounds like bookkeeping until the customer asks why nobody came on Tuesday, and the honest answer is sitting right there instead of being reconstructed from memory.

The record underneath all of this is the work order, which is what carries the promise and the history from the booking through to the invoice. Scheduling moves it around; the record itself is a separate piece and it is worth getting right first.

The whiteboard, the shared calendar that three people edit and nobody trusts, and the group text that carries the real plan. Usually also a paper route sheet that gets printed at seven and is wrong by nine.

It does not replace the dispatcher. Somebody who knows the customers, the crew, and the city is worth more than any board. What changes is that their judgment gets applied to a full picture rather than to whatever they can hold in their head at the time.

One or two people running a fixed route where nothing moves. If the day rarely changes shape, a calendar is enough and this will feel like ceremony.

A business whose scheduling problem is actually a capacity problem. If you are booked six weeks out and losing customers to the wait, better dispatch will not manufacture hours. Pricing or hiring is the honest answer there, and the free audit will usually say so rather than sell you a board.