Avoidable truck rolls: 3 dispatch mistakes to fix

• Collect equipment details, symptoms, access information, and earlier visit notes.
• Check expected completion time and travel before assigning the next appointment.
• Confirm parts will reach the tech before the repair appointment.
• Review return visits by recorded cause, including necessary visits and unknown causes.

A truck roll is expensive even when it goes well. A tech loads the van, drives across town, spends the morning on site, and drives back. When the job isn't finished, the whole trip happens again. The customer waits another day, the fuel and hours are spent twice, and the next job on the board slides out of place.

The decisions that cause them tend to repeat across shops, which is good news, because the same fixes work in most shops too.

It helps to know how common the problem is. The Workiz blog cites industry reports showing that service businesses can lose up to 20% of potential revenue because of poor scheduling and tracking. The same article puts unnecessary travel at 14% of all service visits. It also describes a gap between teams: lower-performing teams have 24% avoidable dispatch rates, while top performers reduce this to just 3% by adopting digital solutions for service dispatching.

Those are figures from a vendor's blog, so treat them as a rough guide, not a benchmark for your own shop. Even so, the direction is clear. Repeat trips are common enough that changes to how jobs are dispatched can show results quickly.

This post covers three dispatch mistakes that create avoidable truck rolls, what each one looks like on the board, and what to change. Start with the one you see most often.

The truck is only the most visible cost. When a job needs a second visit, you pay for the labor on both trips, the fuel for both, and the time the tech could have spent on a paying job. You also pay in customer trust. A customer who has to be home twice, or who hears "we'll come back," starts to wonder whether the shop has the job under control. That customer may be less willing to book the next job, and more likely to leave a review that mentions the wait.

There is a scheduling cost too. A repeat visit rarely fits neatly into the day. It pushes out a job that was already booked, which pushes out another, and the dispatcher spends the afternoon on phone calls instead of planning. Mistakes that look small on one ticket add up across a week, and across a month they become the reason the board never looks right.

The point is not to blame the tech who had to drive back. Repeat visits can result from process problems. The information was missing, the location was unknown, or the parts were not checked. Those are fixable from the office, and that is where this post focuses.

A repeat trip can start with a ticket that says "not working" or "making a noise." The dispatcher reads it, sees an open slot, and assigns it. The tech reads the same line on the way out, arrives, and finds something different: an older model that takes a different part, a second problem that began after the customer's last call, or equipment in a spot the ticket never mentioned. Nobody can finish a job they don't understand.

Illustrative example: a missing access detail

Here is an example, invented for illustration. A customer reports a leak from a water heater. The ticket has the address and a phone number, and nothing else. The tech drives out with the parts for the most common model. On site, the unit is a different brand, the leak is from a fitting rather than the tank, and the shutoff valve sits behind a locked panel the customer forgot to mention. The tech can diagnose the problem but can't fix it. The customer is told to wait for another visit, and the office has to book one. With an illustrative drive of 10 minutes each way, the return visit adds 20 minutes of travel before repair time.

What the ticket needs

A dispatch-ready ticket answers a short set of questions before anyone drives anywhere:

• What is the make and model, and is there a serial number or a photo of the label?
• What is the symptom in the customer's own words, and when did it start?
• What has already been tried, by the customer or by an earlier tech?
• Were there earlier visits to this address, and do their notes mention the same equipment?
• How does the tech get in? Gate codes, pets, a key holder, or a customer who is only home in the afternoon all change the plan.

None of these questions is hard. Ask them on the phone and record the answers on the ticket. The mistake is letting the ticket go out before the answers are in the record.

Use a dispatch handoff checklist to organize the record.

If the answers are missing, set the job to a "needs information" status and call the customer back. A short call takes a few minutes. A second trip to find out a model number costs the tech's time, the fuel, and the customer's patience, all for a fact that could have been collected on the first call.

Make sure the tech sees the full record before leaving. A repeat visit can happen if the tech glances at a one-line summary on a phone and misses the photos or the notes from the last visit. Send the full ticket to the tech's device, and ask them to confirm they've read the notes before they start the drive. That takes far less time than one extra trip.

Watch for the ticket that gets copied forward. When a customer calls back about the same issue, the new ticket often inherits the old wording but not the old findings. Link the new job to the previous one so the tech can see what was already checked and what was ruled out. A returning problem with a history needs that history on the screen.

Improving intake is a practical place to start. When dispatchers write down what the tech should expect to find, and what the customer has already tried, the job goes out with a picture of the problem. The tech arrives ready to fix it instead of ready to diagnose and leave.

Many dispatchers assign work from memory. The tech who finished nearby a few hours ago is probably still close by, the one who called in sick is definitely not available, and the one who said they'd be done by noon is probably still on a job across town. Memory is wrong often enough to cost trips. A tech sent to a job that is ten minutes away from the one they're finishing can arrive late, and a late arrival often pushes the next job back.

Travel time is also less predictable than it looks on a map. The Workiz article notes that good routing can help you avoid traffic snarls that might turn a 20-minute drive into an hour. That gap matters most when a job depends on a set arrival window. A customer who was promised a morning visit and gets a late afternoon arrival may not be home for the follow-up either.

Live location and job status help in two ways. First, they let you choose the closest available tech based on what is actually happening, not what you remember. Second, they let you give the customer an honest arrival time, which cuts down on missed visits caused by a customer who left or a tech who arrived to an empty driveway. The same article gives one example of how this can work: the system auto-updates job statuses if a tech is within 100 yards of the site. You don't need that exact feature to get the benefit. You do need the habit of checking where people are before you assign the next job.

Here is what that habit looks like in practice:

• Check the tech's expected completion time and remaining capacity before adding another job to their day. Allow time to reach the next appointment within its arrival window.
• When a job runs long, reassign or reschedule the next one early, not when the customer calls to ask where the tech is.
• Ask techs to update status on arrival and on completion, not at the end of the day from memory. A status that is wrong at two in the afternoon is worse than no status at all.
• Watch for jobs that consistently run past their planned time. That usually means the estimate is off, the job needs a second person, or the tech has been given too much for one day.

Use a customer arrival update plan when a delay changes the arrival window.

Routing also decides how a day falls apart. A tech who takes three jobs in one part of town and then one job across the county spends the time between them driving. Group nearby jobs when you can, and leave some slack in the schedule for the jobs that always run long. A little slack costs less than a second trip.

Some dispatchers worry that tracking techs feels like micromanagement, and it can be, if the system is used to punish people. The better framing is that status updates protect the tech too. When the board shows a job running long, the next assignment can move, and nobody gets blamed for a customer who waited. Explain the purpose to the team, and let techs see the same information the office sees.

The goal is not to track people for their own sake. It is to stop sending a tech to a job that is already behind, or to send one who will arrive too late to finish in one visit. When the board shows where people are, you can make those calls before the truck is on the road.

A repair that needs a part is a two-trip job if the part isn't on the truck. The pattern is familiar. The tech diagnoses the problem, realizes they need something they don't carry, orders it, and the customer gets a return visit. The dispatcher could have prevented it by checking one or two facts before the job went out.

Here is a common case, also invented for illustration. A customer calls about a unit that won't start. The dispatcher sends a tech who carries the usual parts for that brand. On site, the tech finds the start component is failing, but the version that fits this particular model is not on the truck. The diagnosis gets written up, the customer is told to expect a call, and the return visit is booked for later, with the same customer waiting again. If the dispatcher had asked for the exact model and checked the parts list first, the tech would likely have arrived with the right part, or the first visit would have been planned as a diagnostic visit with the customer told in advance.

Parts problems are hard to see because they don't look like failures. The tech completes the diagnosis, writes "needs part" in the notes, and the job is marked as progress. On the board, it looks like the work happened. In reality, the customer has one more visit ahead, and the schedule has a gap nobody planned for.

Before dispatching any job that might need parts, ask:

• Can we name the likely part, based on the model and the symptom?
• Is that part on the truck, in the warehouse, or on order?
• If it's on order, when will it arrive, and who is confirming the date?
• Does the tech have the tools and training for the likely fix, not just the most common one?

If the part can't be confirmed, plan the first visit as a diagnostic visit and tell the customer that up front. A planned second trip is an honest part of the job. A surprise second trip is a complaint waiting to happen. The difference is made in the first conversation, not on the second visit.

Make the parts check part of the dispatch routine. Some shops keep a short list of common parts for each truck and update it whenever a return visit reveals something they should have carried. Others give the dispatcher a central parts lookup to check before assigning the job. Either way, the question is the same: does the team know what it will need before the truck leaves?

Count the returns, too. Each month, list the jobs that went back to "needs part," and note which part caused each one. If the same item keeps showing up, stock it or add it to the truck list. That turns an annoying pattern into a purchasing decision, which is a much easier fix.

Track results as well. Workiz recommends setting KPIs, such as tracking on-time arrivals with a target of 95% and monitoring parts usage efficiency. You don't have to adopt those exact figures. They come from a vendor blog, and the right target depends on your territory and job mix. The habit is worth copying, though. Pick a small set of numbers you can review every week: on-time arrivals, jobs closed on the first visit, and repeat visits by equipment type. A target gives your team something to aim for. A repeat-visit count tells you which mistake to fix next.

The three mistakes pull together into a short check that a dispatcher can run before assigning a job:

1. Is the ticket complete enough that the tech knows what to expect, and do they have the history?
2. Do we know where the tech is right now, and can they finish the current job and reach the next appointment within its arrival window?
3. Will the likely part be available to the tech before the repair appointment?
4. Has the customer been told the arrival window and, if a second visit is possible, why?

If any answer is no, fix it before the truck rolls. It takes a few minutes at the desk. These checks can reduce the risk of an avoidable trip that costs fuel, a tech's hours, and the customer's patience.

Start with the last month of completed jobs. Find every job that needed a second visit, and record the evidenced reason, allowing for other causes, necessary planned visits, and unknown causes. Some will be tickets with missing details. Some will be techs sent to jobs already running late. Some will be parts nobody checked. Check whether a cause stands out in your own records. That is where to start.

Then measure again the following month. If the numbers don't move, the cause is probably something else, and the list you wrote will show you where to look. Keep the list where dispatchers can see it, and review it alongside the schedule.

Repeat trips are a symptom. Dispatch is one area to investigate using the recorded causes. Better information on the ticket, better visibility of where people and trucks are, and a parts check before the truck leaves will do more for your schedule than asking techs to hurry. Today, pick a recorded cause, add a dispatch check that addresses it, and set a time to review the results at the end of the month.

Related guides: Check 5 guardrail and toeboard limits before dispatch · Check 8 head protection rules before dispatch today · Chemical labels: 6 items to check before dispatch.

Does every return visit mean dispatch went wrong?

No, a return visit may be necessary and planned, or its cause may be unknown. Keep those visits separate when reviewing avoidable returns.

Which mistake should we address first?

Start with the cause supported by your own return-visit records. Use the notes to choose a specific change rather than assuming every return has the same cause.