How to dispatch engineers more efficiently
For three vans on a known patch, efficient dispatch is mostly about what you decide the night before.
Last updated: September 2026
Efficiency is not routing
Search for dispatch efficiency and you will be sold route optimisation. For a fleet of twenty that is the right answer. For three vans on a patch the driver already knows, the savings are somewhere else entirely.
The waste in a small operation is rarely the order of the stops. It is the second visit that a missing part caused, the hour lost because nobody could get in, the job done by the person who did not know the history, and the gap in the afternoon nobody filled because the list of waiting work was in someone’s head.
Fix those four and you will get more out of the week than any routing engine would have found.
Three habits that do most of it
- Cluster by area, not by order of arrival. A day that stays in one or two postcode districts beats a day that crosses town twice. Book new work into the day that is already going that way, unless the priority says otherwise.
- Protect a slot. Keep one or two hours a day unbooked. The emergency is coming whether or not you left room for it, and a solid week means every callout breaks a promise made to somebody else.
- Send the job, not the address. The engineer should arrive knowing the fault, the access arrangement, who to ask for and what happened last time. Most wasted visits are information failures, not driving failures.
Match the person to the job, deliberately
In a small team everyone can do most things, which is exactly why the allocation is done carelessly. Two questions are worth asking before assigning: who has been to this property before, and who is nearest at that point in the day.
The first saves the twenty minutes of rediscovery, and often the second visit. The second saves the fuel. Both are decisions, not features, and both are easier when the week is visible in one place rather than assembled each morning from messages.
Where Dispatch fits
The week calendar in Dispatch shows the whole team on a grid. Drag a job onto a day and a person, timed or all day, with a note. Double bookings warn, they do not block, so you can deliberately overlap when a trade genuinely needs to.
Jobs can also be read on a map with a radius search and filters by status and assignee, which is the quickest way to spot the three jobs sitting in the same area and put them in the same day. Directions to a job open from the record, so nobody is retyping a postcode into a phone at the kerb.
The assigned engineer sees their jobs on their phone with the fault, the site address, the priority and the history attached, and can add notes and photographs as they go. Customers can be emailed automatically when a visit is booked, moved to a different day or cancelled, which removes the round of confirmation calls from the office day.
Engineers who want their work in their own calendar app can subscribe to a private read-only feed or get an email invite per job. It carries the job number and the site postcode only, and it is off until they turn it on.
What it deliberately does not do
There is no live vehicle tracking, no automatic route optimisation and no geofencing. That is a scope decision rather than an oversight: those features suit large fleets, and for a small team they mostly add a screen someone has to watch.
There is no offline mode either, so a signal-free site is read before and updated after. And there is nothing that reassigns work automatically, because in a three-van business the right allocation usually depends on something the software does not know.
A dispatch routine worth stealing
At the end of each day, look at tomorrow: are the jobs clustered, does each one have enough information on it to be done by whoever is going, and is there a gap left for the callout.
In the morning, look at the waiting work rather than only the booked work: parts that have arrived, quotes that have been accepted, jobs that were left half finished. That is where the afternoon gap gets filled from.
If the harder problem is the jobs that never make it onto the week at all, managing multiple jobs without losing track is the page for that, and scheduling emergencies covers the day that goes sideways at ten past nine.
Questions
Dispatching efficiently: FAQ
Do I need route optimisation for a small team?
Rarely. With a few vans on a familiar patch, clustering jobs by postcode area and protecting a flexible slot each day saves more time than route software would find.
What is the most common cause of a wasted visit?
Missing information rather than a bad route: the part nobody ordered, the access nobody arranged, the history nobody passed on. Send the job, not just the address.
How do I spot jobs that are near each other?
A map view with a radius search. In Dispatch jobs appear on a clustered map with filters by status and assignee, so nearby work is obvious rather than remembered.
Can engineers see their jobs on their own phone?
Yes, in a browser with nothing to install, including the fault, the site address, the priority and the history. They can also subscribe to a read-only calendar feed carrying the job number and postcode.
Is there vehicle tracking?
No. There is no live tracking, geofencing or automatic route planning, which is a deliberate scope decision rather than a feature waiting to be built.
Keep reading
More guides for trades and service businesses
Put the week where everyone can see it
A team calendar you can drag jobs around, a map that shows what is near what, and the job detail in the engineer pocket.