What should a dispatch board show?

Every job for the day assigned to a tech, a status per job (unassigned, scheduled, en route, on site, or done), a separate queue for emergency or same-day calls, and which techs are available right now.

How should jobs be scheduled to cut drive time?

Group jobs by area instead of by the order calls came in. A tech who crosses town between two jobs loses time and fuel a second job in the same neighborhood would not have cost, and that shorter drive time frees up room for one more call before the day ends.

How should a shop handle an emergency call?

Pick one policy in advance: hold an open slot each day, pull the nearest available tech off a lower-priority job, or bring in overtime when the queue backs up. Any of the three works, as long as the dispatcher isn't deciding a new policy on every call.

How do techs and the office stay in sync without constant phone calls?

A tech who updates status (en route, on site, done) from a phone keeps the board current without a call, so the office sees the same picture the tech does instead of having to phone in and ask.

What happens when a bumped customer isn't told about the delay?

They usually call in to ask where the tech is, which costs the office more time and goodwill than a two-minute call telling them about the delay before they notice it.

How to run a dispatch board for a small shop

Say your dispatcher books two jobs on opposite sides of town, back to back, because that's the order the calls came in. Your tech spends 40 minutes driving between them instead of the 10 it would have taken to reach a job in the same neighborhood. That's lost fuel, and it's the afternoon slot you needed when a same-day call comes in at 2pm and there's nowhere left to put it.

A dispatch board is the shared, live view of every tech, every job, and every day. Running one well means keeping it accurate in real time, not just filling it out each morning. For a shop with two to ten techs, that means the board reflects what's happening on the road right now, not what the schedule said at 7am.

This guide covers what belongs on the board, how to build the day's schedule, and a daily routine for keeping it accurate. Dispatch is one of the core jobs any field service software for a small shop needs to handle well.

What belongs on the board

Four things need a place on any dispatch board, no matter how you build it.

Every job for the day, assigned to a tech, in the order it's scheduled.
A status per job: unassigned, scheduled, en route, on site, or done.
An emergency or same-day queue, separate from the day's planned jobs, so a same-day call doesn't get lost in tomorrow's schedule.
Tech availability: who's out, who's on a longer job than planned, and who's free next.

A board missing any of these turns into a static list your dispatcher has to call around to check, instead of a live picture of the day.

Building the day's schedule

Group jobs by area before assigning them, not just by the order calls came in. A tech who bounces across town between two jobs loses time a second job in the same neighborhood wouldn't have cost. That lost time shows up twice: in fuel and in the afternoon slot it takes off the board, since a shorter drive between calls leaves room for one more job before the day ends.

Leave room in the schedule for at least one same-day call before the board fills up. Book every tech back to back all day and you have nowhere to put an emergency without bumping someone else's appointment, and that bump is the call your office ends up apologizing for.

Handling emergency calls

Decide the policy before the call comes in, not while it's on the line. You generally pick one of three approaches: hold an open slot each day for same-day work, pull the nearest available tech off a lower-priority job and reschedule that one, or bring in overtime when the queue backs up. Any of the three works. What doesn't work is a dispatcher improvising a different answer on every emergency call, since that's how one customer gets bumped by mistake and another waits far longer than they should.

Whichever policy you use, tell the bumped customer before they notice the tech is late. A call that says the appointment moved to a later window, and why, costs your office two minutes. A customer who has to call in and ask where the tech is costs a lot more goodwill than that.

Keeping techs and the office in sync

Every minute a tech spends calling in a status update is a minute your dispatcher spends confirming something the board should already show. A tech who taps en route, on site, and done from a phone keeps the board current without a call, and your office sees the same picture the tech does instead of relying on a phone call to find out where things stand.

Job history matters here too. A tech walking into a repeat call with notes and photos from the last visit doesn't have to ask the customer to explain the problem again, and doesn't have to call the office to piece together what happened last time.

A daily dispatch routine

Start the day by clearing yesterday's unfinished or rescheduled jobs before adding new ones.
Group the day's jobs by area, not by when the call came in.
Leave at least one slot open for a same-day or emergency call.
Check tech status through the day instead of waiting for a call to update the board.
Close out the board at day's end: confirm every job is marked done, rescheduled, or moved to tomorrow, so nothing quietly falls off.

SpanCrew's dispatch board shows every job, every tech, and every day in one view, with jobs draggable between techs and status visible as en route, on site, or done, for $99 a month flat with no per-tech pricing, currently in early access.