Scheduling and the Dispatch Board
If you're running operations for a service business, the dispatch board is the screen you'll have open more than any other. It answers the questions that come up dozens of times a day: "Who's free at 2 PM?" "Is anyone running behind?" "Who can take this emergency call?" "What's still unassigned for tomorrow?" Done well, those questions take five seconds. Done poorly — or done by reading through a dozen calendars individually — they take five minutes each, and that adds up to half a workday.
This article covers what the dispatch board does, how to read it, the daily rhythm of using it, and the half-dozen mistakes that turn it from "ops cockpit" into "wall of confusing colored boxes."
When you'd use this
- It's morning and you need to assign or finalize today's schedule across your techs.
- A new high-priority call just came in and you're hunting for who's free.
- A customer rescheduled and you need to see who has open slots later today or this week.
- You're reviewing yesterday's coverage to spot patterns ("we ran behind on Tuesdays the last three weeks, why?").
- A tech is calling in sick and you need to redistribute their appointments fast.
- You're doing morning huddle and want one shared view to walk through with the whole team.
If you're a single-tech shop running mostly from a phone, the calendar might serve you better. The dispatch board is built for multi-tech operations where you're juggling assignments.
The mental model
The board is a grid. Time runs across the top — usually morning to evening, sometimes hour-by-hour, sometimes broken into shorter chunks. Each tech (or team) has a row. Appointments appear as colored blocks placed on the row of the tech they're assigned to, at the time they're scheduled.
Above (or below, depending on your account) the per-tech rows is an unassigned area — a holding pen for jobs that have been scheduled to a day but not yet pinned to a tech. That's the queue dispatch is working through.
Color tells you status. Different statuses (Scheduled, Confirmed, En Route, In Progress, Complete, On Hold, Cancelled, No Show) get different colors so you can see "what's going on" without reading every block. Your account's exact colors can be customized; the typical pattern is:
- Cool/blue — scheduled, not yet started.
- Green — confirmed and proceeding.
- Yellow/orange — in progress.
- Solid filled — complete.
- Red/pink — problem (no-show, cancelled, on hold).
The same color logic shows up on the calendar (see The calendar — day, week, month views) so once you've internalized your account's palette, it transfers everywhere.
Drag-and-drop does most of the work
Almost everything you do on the board is dragging:
- Drag from unassigned to a tech's row to assign that job. The assignment updates and notifications go out (often an SMS to the tech, sometimes a confirmation to the customer if the appointment is firming up).
- Drag horizontally within a tech's row to reschedule the time. The job's start/end shifts, the customer is notified per your reschedule rules, and the appointment status may auto-update.
- Drag vertically from one tech's row to another to reassign. Same as above; just a different tech receives the work.
- Drag the right edge of a block to extend the duration. Useful when you realize a job is going to take longer than first estimated.
Some accounts also allow keyboard shortcuts and right-click menus on appointments — those tend to be the secondary path. Drag is the muscle memory.
The daily rhythm
A typical dispatch day looks like this:
Morning huddle (15-30 min before techs roll). Open the board. Walk through unassigned items first: is there anything that should already be assigned? Then walk through each tech's row. Are confirmations sent? Is anyone overloaded? Is anyone empty? Adjust before techs start their day.
Mid-morning settling (10-11 AM). First couple of jobs are in progress. Watch for "running behind" indicators — appointments that should have started a half-hour ago and haven't been touched. Reach out to the tech, reach out to later customers preemptively if a slip is happening.
Lunch slot (11:30-1). Highest-volume reschedule window. Customers who didn't pick up the morning confirmation call back. New emergencies come in. The afternoon's unassigned area is your priority.
Mid-afternoon (2-4 PM). End-of-day cleanup time. Review what's been completed (techs should be marking complete from the field — see Closing and recalls). Note anything that won't get done today and decide: reschedule for tomorrow, leave for the on-call tech, escalate to a manager.
End of day. Quick sweep. Anything that should have been closed and wasn't? Any "on hold" jobs that need a follow-up call tomorrow morning? Add notes so the morning shift can pick up where you left off.
Today's view vs. forward planning
The dispatch board is built for today (and sometimes tomorrow). It's the operational live view. For looking out a week or a month, switch to the calendar — the dispatch board's visual density is exactly wrong for long horizons. See The calendar — day, week, month views for when to use which.
A common pattern: the dispatcher lives on the dispatch board for today/tomorrow; the office manager or owner lives on the calendar for next-week planning. Two views, two needs, both consuming the same underlying appointment data.
Reading status colors at a glance
The point of the colors is to avoid clicking on every block. After a few days you should be able to look at the board and instantly see:
- Tech rows that are full vs. empty — workload distribution.
- Tech rows with mostly green/in-progress chips — they're moving through their day fine.
- Tech rows with a red chip — something's wrong, click to investigate.
- Big gaps in a tech's row — reschedule opportunities or capacity for an emergency add.
- Lots of items still in the unassigned area — dispatch hasn't caught up; intervene.
When colors stop being legible — usually because the palette was customized too richly with too many statuses — that's the cue to consolidate statuses, not the cue to memorize them. See Job statuses and what each one means.
Common mistakes
- Treating the board as a planner instead of a live ops view. It's not where you plan two weeks out; the calendar is. Trying to schedule the future on the dispatch board is painful and you'll end up scrolling sideways forever.
- Letting the unassigned area grow. If a job has been scheduled to a day but no tech, the system can't notify the customer with a tech-specific confirmation, and the morning of the appointment becomes a scramble. The unassigned area should be empty or near-empty by the time techs start their day.
- Reassigning without communicating. You drag a job from Carlos to Maria. Carlos doesn't know it's gone. Maria doesn't know it's hers. The customer expects Carlos. Drag is fast, but tell the people involved.
- Using the board as the canonical place to capture notes. Job-specific notes go on the job, not in a chat about the dispatch block. The board is a visualization layer; the data lives on the job.
- Ignoring the color signal. "I never look at the colors" means you're missing the signal the system is giving you. Tune the palette to your eyes if needed (within the status configuration), but use the colors.
- Multi-tech assignments handled by duplicating. If two techs are going to the same job, assign both — don't create two copies of the job. Most accounts support multiple assignees per appointment; if yours doesn't and you're regularly running multi-tech jobs, talk to your administrator about enabling it.
- Letting yesterday's incomplete work hide overnight. If a job didn't get done, decide explicitly what happens to it: reschedule, cancel, or escalate. Hidden incomplete work piles up and surfaces as customer angry calls a week later.
Performance and zoom — practical notes
On a busy day with 30+ jobs, the board can be visually dense. Most boards support zooming the time axis (per-hour vs. per-half-hour vs. per-15-minute) and filtering to specific teams or business units. Use them. A clean, narrowed view is easier to scan than a maximally-dense one. If your board is regularly cluttered to the point of being unreadable, you're either viewing too much (filter down) or you've added too many statuses (consolidate).