How to run a dispatch board without chaos

What the board is for

A dispatch board, whether a whiteboard, a spreadsheet or the scheduling screen in your field service software, has one job: show everyone, at a glance, where every technician is, what they are doing, what is next and where the gaps are. Chaos starts when the board is out of date and people go back to calling and texting each other to find out what is happening.

The role behind the board is a real profession. There were 202,810 non-emergency dispatchers employed in the US in May 2025^[1], and building equipment contractors, the industry group for HVAC, plumbing and electrical firms, employed 14,490 of them^[2]. In many smaller home service companies, the board is run part-time by a CSR, office manager or owner, which makes simple, consistent rules even more important.

Lay the board out the same way every day

• One row per technician or crew, in the same order every day.
• Columns for time, in half-hour or hour blocks, from the first start to the last expected finish.
• Each job shows the customer name or ticket number, job type, arrival window and status.
• A separate unassigned lane for jobs that are booked but not yet placed, and one for callbacks and parts holds.
• A notes area for the day: weather, a tech out sick, a parts delivery, a surge declared.

Whatever tool you use, the layout should let someone walking past understand the day in ten seconds. If it takes longer, the board has too much on it.

A color code everyone reads the same way

The most common board problem is color drift: someone adds orange for “waiting on parts,” someone else uses orange for “customer called,” and within a month nobody trusts the colors. Keep the code short, print it next to the board or pin it in the software, and change it only at a team meeting.

Plan capacity in blocks

Filling every slot with booked work feels efficient until the first emergency of the day arrives and there is nowhere to put it. Instead, divide each tech's day into blocks before booking: emergency or same-day blocks, maintenance blocks, install blocks and a buffer.

1. Set the blocks each morning from expected demand. In a heat wave, most of the day may be same-day blocks; on a mild spring day, maintenance can take most of it.
2. Hold same-day blocks until a set release time, such as 11 a.m., then open them to booked work.
3. Put installs on the first slot of the day so they do not collide with afternoon repairs.
4. Leave a buffer after every few jobs for overruns and drive time, based on your actual history.
5. Keep at least one tech's afternoon flexible on high-demand days, so there is somewhere for the reshuffle to land.

Technician time is expensive and getting more so. Average hourly earnings of production and nonsupervisory employees at US specialty trade contractors reached $39.05 in September 2026, up 4.7% on a year earlier^[3]. Idle gaps and needless drive time on the board are paid hours that produce nothing.

Adding techs is not easy either. US construction job openings were 289,000 in September 2026, up from 194,000 a year earlier^[4]. For most companies, a better board is the cheapest capacity they can find.

The 10-minute morning huddle

1. 01

   Start on time, standing up

   Same time every day, before the first trucks leave or by phone at a fixed time. Ten minutes, no more.

2. 02

   Walk the board row by row

   Each tech confirms the first job, parts on the truck and any concerns about the day.

3. 03

   Flag risks

   Long jobs, difficult customers, parts not yet arrived, weather and anyone running short of hours.

4. 04

   Set the blocks

   The dispatcher confirms the same-day blocks and the release time for the day.

5. 05

   Name the flex tech

   One tech is designated to take the first reshuffle if an emergency comes in.

The huddle is not a training session or a place to solve yesterday's complaint. Anything that takes longer than a minute moves to a separate conversation after the trucks have left.

Mid-day reshuffle rules

By late morning, the board rarely matches the plan. Jobs overran, an emergency came in, a customer cancelled. Reshuffles cause chaos when they are made on instinct and communicated by scattered calls. Write the rules down.

• Safety and priority jobs go to the nearest qualified tech, using the flex tech first.
• A job at risk of missing its window by more than 30 minutes gets a decision: move it to another tech, or call the customer with a new time.
• Never move a job without telling both techs and the customer.
• Move maintenance before repairs, and repairs before installs, when something has to give.
• Change the board first, then send the message, so the board stays the source of truth.

Example: a Tuesday that went wrong at 10 a.m.

Example. A seven-tech company starts Tuesday with a full board. At 10:05 a.m., Tech 3's install hits an unexpected electrical problem and will run four hours over. At 10:20, a no-cool call comes in from a flagged customer with an infant. The dispatcher follows the rules: the flex tech, Tech 6, takes the no-cool call. Tech 6's two afternoon maintenance visits move to Tech 2, who had a held same-day block. Tech 3's afternoon repair is offered to the customer for first call tomorrow, and the customer agrees. All changes go on the board first, then by text to each tech and by call to each customer. By 10:40 the board is accurate again.

Whiteboard, spreadsheet or software?

Small shops often start with a whiteboard, and it works while the dispatcher and techs are in the same building every morning. It breaks once techs go straight from home to the first job, or when someone other than the dispatcher needs to see the board. Spreadsheets are a step up but get messy with real-time status updates.

Field service software with a live board, tech status updates from a phone app and customer notifications is the usual destination once you have several trucks. Whatever you use, the rules in this article matter more than the tool: a fixed layout, a short color code, capacity blocks, a huddle and written reshuffle rules. A messy process moved into expensive software is still messy.

Close the day properly

• Mark every job on the board with its final status, including incomplete jobs and parts holds.
• Move incomplete work and callbacks into tomorrow's board or the unassigned lane, with a note.
• Check parts for tomorrow's first jobs and tell techs what to pick up.
• Hand open issues to the on-call tech or answering side in writing.
• Build tomorrow's capacity blocks from the forecast and booked work.

Measure the board

• On-time arrival rate against the window and against the on-the-way estimate.
• Jobs completed per tech per day, by job type.
• Drive time as a share of the day.
• Held blocks used versus released.
• Reshuffles per day and how many reached customers before the window ended.

Review these weekly. For the windows you promise customers, see arrival windows compared, and for the person who runs the board, see the dispatcher job description.