A technician who spends an extra hour driving is not just losing an hour. That hour pushes the next arrival window, creates overtime, delays a quote follow-up, and leaves a finished job sitting uninvoiced at the end of the day. Route planning for service technicians is how a service business protects its capacity while keeping the office, the field, and the customer on the same plan.
For a three-truck plumbing company, a growing HVAC shop, or a roll-off operator juggling deliveries, swaps, and pickups, the goal is not the prettiest line on a map. The goal is to complete the right work, in the right order, with enough room for the work that will not go as planned.
Route planning is an operating decision, not a map feature
A map can calculate the fastest path between stops. Dispatch has to make harder decisions. Which customer has a committed arrival window? Does the technician have the right certification, equipment, or truck inventory? Is this a recurring pool visit that can move, or a no-cooling call that needs priority? Does a dumpster swap need a specific truck, disposal capacity, or a driver who knows the site?
Those details decide whether a route is workable. If the office plans only around distance, technicians inherit the gaps. They call in for missing information, arrive without the materials, or find the next appointment booked across town with no buffer for traffic or a repair that ran long.
A useful route starts with a reliable job record. The address, contact details, job type, promised window, assigned crew, required equipment, notes, and access instructions should all be attached to the work before it becomes a stop. When those records live in separate spreadsheets, text threads, and scheduling apps, dispatch has to reconstruct the truth every morning.
Build routes from commitments first
The most dependable sequence is to place fixed commitments first, then fit flexible work around them. A scheduled commercial maintenance visit, a customer with a narrow arrival window, a time-sensitive restoration job, or a disposal site cutoff should shape the day before lower-priority stops do.
Separate fixed appointments from flexible capacity
Not every job deserves the same place on the calendar. A booked installation with a customer waiting at home is fixed. A recurring landscaping visit may be flexible within a service day or week. A quoted job that has not been approved is not route work at all, no matter how likely it feels.
That distinction prevents a common error: building a full route from work that is not actually ready. An accepted quote should create a job, and the job should be scheduled before it is dispatched. It sounds basic, but it keeps unapproved work, incomplete customer details, and vague verbal commitments from turning into field activity.
Match work to the crew before optimizing geography
The closest technician is not always the right technician. A drain-clearing call may need a particular machine. An electrical repair may need a licensed technician. A roll-off delivery may need a specific truck size, or a driver with experience at a tight site.
Assign the job to a qualified person and the right vehicle first. Then sequence that crew's stops to cut unnecessary travel. This is where smaller service businesses gain the most control. They do not need a complex optimization model to stop two crews from passing each other on the highway. They need the schedule, skills, equipment, and locations visible in one place.
Leave capacity for real life
A route with no buffer is not efficient. It is fragile. Traffic, customer delays, parts runs, gate codes, weather, disposal lines, and jobs that uncover more work than expected will all happen.
The right buffer depends on the business. A pest control route of short, repeatable visits can be planned tighter than a restoration or plumbing route where scope changes are common. Start from actual job durations, not the durations you hope for. If a two-hour repair routinely takes two and a half hours with travel, documentation, and customer communication, schedule it that way.
Give technicians a clear field view
A route only works if the technician can run it without calling the office for every detail. Field teams need the work assigned to them, the stop sequence, customer and site information, service notes, relevant photos, and a simple way to mark progress.
They do not need company-wide revenue, invoice balances, payroll information, or every customer record in the system. Good route planning includes permissions. Technicians see what they need to do the work well, and office-only financial information stays protected.
That separation also improves accountability. When a technician marks a stop complete, the office can see that the field work is done. If the job requires a signature, photos, a meter reading, a disposal ticket, or additional notes, those requirements should be clear before the technician closes it out. A status of "done" is not enough when billing, warranty work, or a customer dispute comes later.
Treat route changes as controlled changes
Routes change during the day. The problem is not that changes happen. The problem is when they happen silently.
A technician may get a customer request on site and agree to add work. A customer may call asking for a different time. An emergency may need to displace routine maintenance. Those changes can be right, but they need an owner in the office or the dispatch flow. Otherwise the route shifts without anyone checking customer commitments, labor capacity, pricing, or the effect on the next stop.
A practical rule is simple: technicians report the request and document what they see; authorized office staff approve changes that affect the schedule, the scope, or the price. That keeps responsiveness without turning the field schedule into a set of private side agreements.
For urgent work, dispatch should see the trade-off clearly. If moving a crew to an emergency call means two existing customers will be late, someone should decide that and communicate it. Customers forgive a proactive update far more readily than a missed window with no explanation.
Connect route completion to invoicing
A completed route is not a completed business process. The work still has to be reviewed, billed, and paid. Finished, unbilled work is the quietest way a service business loses money.
This is where disconnected scheduling tools create an expensive gap. The technician finishes the job in one system, the office later re-enters it into accounting or invoicing software, and the exceptions get buried. Maybe the technician added a part. Maybe the job was marked complete without a required signature. Maybe a recurring visit happened but never turned into an invoice.
The better workflow is Lead, Quote, Job, Route, Invoice, Paid. Each stage creates the next record and makes the exceptions visible. A job completed in the field should move to an invoice-ready state, not vanish into a completed column nobody reviews until month-end.
Everglow is built around that connected workflow. The Route view lays out each crew's next seven days stop by stop, with the driver, the time, the address, and anything still unassigned; the day can be put on a map, and the day's customers notified from the same screen. Plan the day fills unassigned jobs by skill, time window and drive time, and shows the plan before anything moves. When a stop is complete, the job moves toward invoicing and payment status reflects what actually happened. You can open a live demo company and see a week of routes, no account needed.
Measure the failures, not just the miles
Drive time matters, but it is not the only route metric that affects margin. A business can cut mileage and still lose money through late arrivals, low first-time fix rates, repeat trips, unbilled work, or crews waiting at a site because the access instructions were missing.
Review routes weekly for the exceptions that cost the most: jobs that regularly run past their planned duration, repeat dispatches to the same customer, stops that often miss their arrival window, route changes made after crews leave, and completed jobs waiting too long for invoices. Measure route performance against actual labor, travel, materials, and billing outcomes, not against the schedule as it looked at 7 a.m.
Do not overcorrect from one bad day. A single traffic incident does not prove a route is flawed. A pattern of late second appointments, frequent technician overtime, or invoices delayed after certain job types does. The point of the review is to adjust the planning assumptions before the same problem becomes normal.
Start with the next dispatch day
Better route planning does not require rebuilding the whole operation overnight. Start with tomorrow. Confirm which jobs are truly scheduled, identify the fixed customer commitments, match each job to the right crew and vehicle, sequence the stops by geography and priority, and reserve time for the uncertainty your business actually sees.
Then make one rule non-negotiable: a completed stop must create a visible next action, whether that is invoice review, customer follow-up, approval for additional work, or payment collection. A route is only profitable when the work done in the field reliably reaches the office process that turns it into revenue.