The one screen the whole day runs through
In most field-service operations there's a single point where the entire day is decided, and it's a person looking at a board. Every job that reaches a tech ready to work, every job that slips to tomorrow, every truck that drives clear across town when a closer one was free — all of it passes through the dispatcher moving work around on one screen. When the board is good, the day flows: techs stay busy, jobs land on the right people, and the unexpected gets absorbed without drama. When the board is bad — a whiteboard, a spreadsheet, a dispatcher's memory — the day starts coming apart by mid-morning and the office spends the afternoon firefighting.
The dispatch board is the operational heart of the business, and it's worth being precise about what a good one actually is. It is not a prettier calendar. A calendar tells you what's scheduled; a board tells you what's happening — who's free right now, who just finished early, which job has been sitting unassigned for an hour, which tech is closest to the emergency that just came in. The difference between a schedule and a board is the difference between a plan written last night and a living picture of the day as it actually unfolds. Running the board well is the highest-leverage job in the operation, and most of it comes down to keeping that picture true.
What a real board shows you at a glance
A dispatch board earns its place by answering the questions a dispatcher asks a hundred times a day without making them dig for the answer. The moment those answers require a phone call or a guess, the board has failed. A board worth running shows, at a glance:
- Who's actually available. Not who's scheduled — who is genuinely free to take the next thing, accounting for the job they're on, their skills, and their PTO or arrival commitments. "Availability" the board can't see accurately is how you double-book someone.
- What has no home yet. The unassigned jobs sitting in the queue, sorted so the urgent and the SLA-bound rise to the top. A board that hides the unassigned pile is a board that lets jobs quietly fall through, which is the single most expensive dispatch failure there is.
- Where everyone is. A tech's location relative to the next job is the difference between a smart assignment and an hour of pointless windshield time. The board should let you send the near truck, not just the next name on the list.
- What's running late. The job that should have wrapped an hour ago and hasn't, so you can find out why before it silently eats the two appointments stacked behind it.
Every one of these is a question the dispatcher would otherwise answer by calling someone or guessing. The board's whole job is to answer them instantly and truthfully, so the dispatcher spends their attention on decisions instead of on gathering the facts to make them.
Running the board through a real day
A board is only as good as how it's run, and running it well is a rhythm, not a one-time setup. The good dispatcher works the board in a steady loop all day:
- Start from the plan, then defend it. The morning board is the schedule you built the night before — a day the techs can actually finish. The dispatcher's job isn't to rebuild it; it's to protect it against the day's surprises, absorbing what they can without blowing up a plan that was sound.
- Triage the incoming against the board. A new call gets its true urgency read on the intake and then placed against the live picture: slot the routine job where it fits, and slide the emergency to the nearest capable tech even if it means bumping something less urgent. This is the core move of dispatching, and a good board makes it a ten-second decision instead of a five-minute scramble.
- Reassign the moment reality shifts. A tech calls in sick, a job runs long, a customer cancels — the board has to reflect it immediately so the freed capacity and the orphaned jobs are both visible and can be re-matched. A board that lags reality by an hour is worse than no board, because it lies to you confidently.
In Hosting Field the board is exactly this live picture — jobs carry their status through the seven-state FSM, so "in progress," "on site," and "done" are real states the board reflects rather than a dispatcher's mental note, and an unassigned emergency is visible against every tech's actual availability so the reassignment is a decision made with the facts in front of you. The system keeps the picture true; the dispatcher makes the calls. That's the right division of labor — the board should never auto-assign a job out from under a dispatcher who can see context the software can't, it should make the right assignment obvious and one action away.
The dispatcher is not a router — protect their judgment
It's tempting, once the board is good, to imagine the dispatcher away entirely — let an algorithm assign everything by distance and skill. Resist that instinct, because the best dispatchers are making judgment calls the board can't see. They know this customer is a headache who needs your most patient tech. They know that "quick" job is never quick at that address. They know the new hire shouldn't get the difficult account yet. A board that fights those instincts — that auto-assigns and makes the human override it — burns the dispatcher's most valuable contribution.
The right relationship is the one that runs through this whole operation: the board surfaces the facts, ranks the options, makes the obvious assignment a single action, and then gets out of the way so the dispatcher can apply the context that isn't in the data. Speed and accuracy from the software; judgment from the human. That's what lets a good dispatcher run forty jobs across a dozen techs and have the day hold together — the board does the remembering and the math so they can do the thinking.
What to watch
- Unassigned dwell time. How long a job sits on the board before it gets a tech. This is the vital sign of a well-run board; when it climbs, jobs are starting to fall through the cracks and your SLA compliance is about to slip with it.
- Reassignment rate. How often a job gets moved after it's assigned. A little is healthy — the day changes. A lot means the morning plan was fantasy, and you should look upstream at how the schedule is built rather than blaming the board.
- Idle-versus-driving split. How much of the fleet's day is productive work versus windshield time the board could have prevented with a smarter assignment. A board that consistently sends the far truck is leaking hours you can win back.
The dispatch board is where the business actually runs — not the schedule you planned, but the day as it happens, one assignment at a time. A board worth running keeps a true live picture of who's free, who's near, and what still has no home, so the dispatcher spends their day making judgment calls instead of gathering facts. Build the board to surface the truth and make the right move obvious, then trust the human to apply the context the software will never have. Do that, and the day holds together instead of coming apart by ten.