What makes a dispatch board hold up on a bad morning?
Recovery speed, not density. A board survives a bad morning when reassigning a job takes seconds and automatically notifies the new crew, the old crew, and the customer; when job durations come from what that job type actually took last time rather than a two-hour default; when each route keeps one deliberate afternoon gap for same-day work; and when every move available by drag is also available from a keyboard dialog. Most teams optimize schedule building and leave recovery to whoever is loudest, which is why a fifteen-minute disruption costs three hours.
The schedule you built on Friday afternoon is a theory. Monday tests it. A tech calls out, the first job hides a problem nobody quoted, and a commercial customer moves an appointment that three other stops were routed around. What happens in the next twenty minutes decides whether the day is recoverable or whether the dispatcher spends it on the phone.
Three failures, in the order they happen
- Someone is missing, so a full route needs a new owner before eight
- A job runs long, so everything behind it is now wrong and nobody downstream knows
- A customer moves, so a route that made geographic sense no longer does
Notice that none of these are scheduling problems. They are recovery problems. Most teams optimize the building of the schedule and leave recovery to whoever is loudest, which is why a fifteen minute disruption costs three hours.
What a recoverable board needs
Reassignment measured in seconds
Moving a job to another crew has to take seconds, and it has to notify the new crew, the old crew, and the customer automatically. If reassignment means a text and a hope, the dispatcher will batch the changes and the field will run on stale information for an hour.
Durations that came from reality
If every job is scheduled at two hours because two hours is the default, the board is fiction by ten in the morning. Durations should come from what the same job type actually took the last several times, which means the system has to be recording it. This is the quiet reason time tracking matters to a dispatcher who never looks at payroll.
Visible slack
A board packed to a hundred percent has nowhere to put an emergency, so the emergency goes on top of a crew that is already behind. Leave one deliberate gap per route in the afternoon. Teams that hold that gap absorb same-day work without overtime, and teams that fill it pay for it in evening hours.
Keyboard access, not just drag and drop
Dispatchers move fast and some use a screen reader. A board where the only way to move a job is a mouse drag is slower for the first group and unusable for the second. Every move available by drag should be available in a dialog.
The morning routine that prevents most of it
- Confirm attendance before crews leave, not after the first missed stop
- Look at the two longest jobs on the board and ask what happens if either doubles
- Check that each route is geographically tight, then leave the afternoon gap alone
- Send the customer notifications for the day early, so a slip is a reschedule and not a complaint
"We stopped grading the schedule on how full it looked and started grading it on how fast we could change it. Same trucks, two more jobs a day."
A good board is not the one with no white space. It is the one where a bad morning costs twenty minutes instead of a day.
Common questions
- How much slack should a dispatch board have?
- Roughly one deliberate gap per route in the afternoon. A board packed to a hundred percent has nowhere to put an emergency, so the emergency lands on a crew that is already behind. Teams that protect the gap absorb same-day work without overtime; teams that fill it pay for it in evening hours.
- Where should job durations come from?
- From history. If every job is scheduled at two hours because two hours is the default, the board is fiction by ten in the morning. Durations should be based on what the same job type actually took the last several times, which is the quiet reason time tracking matters to a dispatcher who never looks at payroll.
- Does a dispatch board need to work without drag and drop?
- Yes. Dispatchers move fast and some use a screen reader, so a board where the only way to move a job is a mouse drag is slower for the first group and unusable for the second. Every move available by drag should also be available in a dialog you can reach from the keyboard.
- What morning routine prevents most bad days?
- Confirm attendance before crews leave rather than after the first missed stop, look at the two longest jobs and ask what happens if either doubles, check that each route is geographically tight, and send the day's customer notifications early so a slip becomes a reschedule instead of a complaint.