The best field service dispatching practices are the ones that prevent repair work: most of a dispatcher's day goes to fixing promises made earlier, so the biggest wins come from making better promises, not faster fixes.
Watch a dispatcher for a morning and count what they actually do. Some of it is assignment: this call goes to that tech. Much more of it is repair. The 10:00 is going to be late, so call the customer. The 11:30 is on the wrong side of town, so swap it. The install crew found a rotted subfloor, so the afternoon is gone. Each of those is a problem that was created hours or days before, usually at the moment the job was booked.
That is the mechanism behind every practice below. Dispatching is where bad promises get discovered. Fewer bad promises means less dispatching, and the dispatching that is left is the kind that only a person can do well.
Count your repair work first
Before changing anything, measure how much of the day is repair. For one week, have your dispatcher tally every schedule change and tag it with a cause: drive was longer than planned, job ran long, customer not home, parts, emergency inserted, booked to the wrong skill.
Repair share = Changes caused by the original booking ÷ All changes
Your numbers will differ. What matters is that you can see which causes come from the booking and which come from the field. The practices below target the first group.
The ten practices
1. Check the drive before the slot is offered
Most late arrivals start as a slot that looked open on a calendar and was never reachable. Whoever books the job, phone or web, should see the drive from the previous job at that hour before offering the time. This one practice removes more repair work than the other nine combined. We explain why routing afterward cannot fix it in route optimization vs feasible scheduling.
2. Measure the drive from where the truck will be
Drive from the shop is the wrong number for any job after the first. At 1:00 p.m. the truck is at its 11:30 job. Every estimate that starts from the shop is optimistic for trucks working away from it and pessimistic for trucks near it, so it is wrong in both directions.
3. Put skills in the booking, not in the dispatcher's head
If only three techs can do a heat pump install, the booking step should only offer their time. When skills live in a dispatcher's memory, every new hire at the phone books the wrong person and dispatch repairs it.
4. Size durations from what actually happened
A job type estimated at 60 minutes that averages 85 will push every day it touches. Pull actual time on site by job type every month and update the estimate. For how to build the first estimate, see job duration estimate.
5. Plan the first and last drive
The drive from home or the shop to the first job, and from the last job back, is part of the paid day. A first job booked at the far edge of the territory spends the best hour of the morning on the highway. Our guide to planning a dispatch day around drive time shows how to count it.
6. Decide your emergency policy before the emergency
Either hold capacity for same-day calls or agree in advance which kinds of booked work get moved. Deciding on the phone, under pressure, is how a full board turns into a wrecked one. The two approaches are set out in emergency call scheduling.
7. Get the late signal from the field early
The tech knows a job will run long well before the office does. If the only signal is the tech failing to show up at the next job, you learn about the problem when it is already a late arrival. Ask for a check-in halfway through each job, not at the end.
8. Tell the customer before the window starts
A customer told at noon that their 2:00 is now 3:30 has time to adjust. A customer who works it out at 2:20 calls the office, and now dispatch is answering phones instead of dispatching. Set a rule: anyone who will be more than a set number of minutes late gets a text before their window opens.
9. Keep one board
Subcontractors on a spreadsheet, installs on a whiteboard, service calls in the software. Every separate calendar is a place where two promises can overlap without anyone noticing until a truck arrives. One board, everyone on it.
10. Review yesterday every morning for ten minutes
Look at three things: which jobs were late and why, which bookings had to be moved, and which trucks crossed their own path. That last one, backtracking, is the clearest sign that the booking step created the drive. Ten minutes a day on causes beats an hour a day on symptoms.
What a dispatcher's day looks like after
The goal is not to replace the dispatcher. It is to change what they spend the day on. With booking checking the drive and the skill, and the field reporting early, the dispatcher's work moves toward the decisions only a person makes well: which customer can be moved, which tech can handle a hard customer, what to tell a commercial account whose job slipped. We wrote about where that line sits in Dispatcher or software?
CrewLink, in early access, is built around practices 1, 2, 7 and 8: it offers only times a qualified tech can reach from the previous job, its tech app asks for a mid-job check-in and re-flows the rest of the day when a job runs long, and affected customers are texted. Its dispatch board puts the drive next to each job instead of hiding it inside the block. The other six practices are habits, and they work with any tool.
What to take away
- Most dispatching is repair work caused by the original booking. Count it for a week before changing anything.
- The biggest single practice is checking the drive, from where the truck will be, before a slot is offered.
- Put skills and realistic durations into the booking step, plan the first and last drive, and agree an emergency policy in advance.
- Get the late signal from the field halfway through a job, tell customers before their window starts, and keep everything on one board.
Common questions
What are the most important field service dispatching best practices?
Check the drive before a slot is offered, measured from the previous job rather than the shop. Book by skill. Use durations taken from real jobs. Agree an emergency policy before you need it. Those four prevent most of the changes a dispatcher would otherwise make later.
What should be on a dispatcher checklist?
Each morning: review yesterday's late jobs and moves, confirm first drives, check who is out and which skills are short. During the day: watch for mid-job check-ins, text customers who will be late before their window starts, and log every change with a cause.
How do you measure whether dispatching is improving?
Track the number of schedule changes per day and the share caused by the original booking. Track on-time arrival and how many customers learned they would be late before their window started. Fewer changes with the same job count means the booking step is improving.
Does dispatch software replace a dispatcher?
Not for companies of 5 to 50 trucks in most cases. Software can stop bad bookings and surface late jobs early. A person is still better at deciding which customer can be moved and how to tell them.