You’re reimbursing technicians for mileage based on their handwritten logs. Or you’re trusting them to remember the route at the end of the week. Or you’re using a GPS tracker that dumps raw coordinates into a CSV, and someone has to piece together which trip was which job.

None of these methods tell you if the route was efficient. None of them prove billable travel to the customer who questions the invoice. And none of them catch the pattern where your most experienced tech is driving 40 minutes out of his way because he doesn’t know the shortcut through the industrial park.

For trades businesses running three trucks or thirty, drive time is a line item that compounds. A plumber averaging six stops a day and burning an extra 20 minutes per trip is losing two billable hours. Multiply that across a crew, across a month, and you’re looking at $3,000 to $8,000 in labor that could’ve been on the tools. Add fuel, wear on the truck, and the reimbursement errors that always seem to round up, and the number climbs past $50,000 annually for a mid-sized operation.

The manual fix is a second job. You can ask techs to log every departure and arrival. You can cross-reference odometer photos with job tickets. You can build a spreadsheet that tries to map addresses to mileage. Or you can accept that 15% of your drive time data is wrong and move on.

The AI fix is a single agent that watches GPS, matches trips to jobs, logs the route, flags the outliers, and hands you a report that’s audit-ready. No app for the tech to open. No end-of-day data entry. No disputes over whether the 47-mile round trip was actually necessary.

Why Drive Time Tracking Falls Apart

Most trades businesses start tracking mileage when they realize they’re reimbursing more than they’re billing. A tech submits 320 miles for the week. You look at the job list and count five local calls. The math doesn’t work, but you don’t have time to argue, so you pay it and make a note to “figure this out later.”

Later never comes, because tracking drive time manually requires the tech to do something extra at every stop. Open an app. Snap a photo of the odometer. Write down the time. If the day is busy and the phone is ringing and the next job is 20 minutes away, that step gets skipped. By Friday, the log is half-empty and the tech is filling in the blanks from memory.

Even when the data is complete, it’s not useful. You have a list of miles driven, but you don’t know if the route was optimal. You don’t know if the tech stopped for lunch and logged it as job travel. You don’t know if he drove to the supply house on the way home and counted the whole trip. And you definitely can’t use that data to justify a travel charge to a customer who’s already questioning the invoice.

The bigger problem is routing inefficiency that you can’t see. A tech who’s been with you for five years has his own mental map of the territory. He knows the roads, but he doesn’t know that the new bypass saves 12 minutes to the north side. He doesn’t know that two of his morning calls are three blocks apart, but he’s driving between them in the order they were dispatched. You’re losing time, fuel, and billable hours, and the only way you’d catch it is to ride along for a week and take notes.

Dispatch overhead makes it worse. If you’re the one routing the jobs, you’re doing it with a paper map or a mental model of where everyone is. You don’t have live locations. You don’t have historical drive times between common pairs of addresses. You’re guessing, and every guess costs 10 or 15 minutes that could’ve gone to the next call.

This is where the AI audit for trades businesses starts. We pull three months of job data, overlay GPS if you have it, and show you exactly where the time is going.

What an AI Agent Sees That You Can’t

An agent built to track drive time doesn’t need the tech to do anything. It watches the GPS feed from the phone or the vehicle tracker you already have. It knows the job schedule from your dispatch system. When the truck starts moving after a job is marked complete, the agent logs the departure, tracks the route, and matches the arrival to the next job on the list.

If the route is direct, the agent files it. If the route includes a detour, the agent flags it and checks whether the detour was to a supply house, a job site that’s not on the schedule, or a personal stop. It doesn’t guess. It compares the coordinates to known locations in your system: your shop, your suppliers, your customer addresses.

At the end of the day, the agent has a complete log. Every trip. Every mile. Every minute. It calculates the reimbursement based on IRS rates, compares it to what the tech submitted, and highlights any variance over 5%. It also calculates billable travel for each job, using the actual route and the rate you’ve set for travel charges.

The agent doesn’t stop at logging. It analyzes patterns. If a tech is consistently taking longer routes between two common job types, the agent surfaces that. If a crew is making three trips to the supply house in a single day, the agent suggests consolidating the run. If a job that should be 15 minutes away is consistently taking 30, the agent flags it for review, because either the address is wrong or there’s a routing issue you don’t know about.

This is the difference between tracking and intelligence. Tracking tells you what happened. Intelligence tells you what to fix.

One HVAC contractor we work with was reimbursing techs for an average of 380 miles per week per truck. After the agent started logging routes, the average dropped to 310 miles. The difference wasn’t fraud. It was rounding errors, forgotten stops, and routes that included personal errands the tech didn’t think to subtract. The company saved $1,400 per truck per month in reimbursement alone, before counting the fuel and time savings from better routing.

The Three Pieces of Drive Time AI

The first piece is passive GPS logging. The agent needs to see where the truck is without requiring the tech to check in. Most modern dispatch systems have a mobile app with location services. If you don’t, a $30 plug-in tracker in the OBD port does the job. The agent pulls the feed every 60 seconds and stores the route.

The second piece is job matching. The agent compares the GPS timeline to the job schedule. If a job is marked complete at 10:47 and the truck starts moving at 10:52, the agent knows that’s the start of the travel window to the next stop. If the next job is marked started at 11:18, the agent knows the travel time was 26 minutes. It calculates the distance, checks the route against the fastest option, and logs any variance.

The third piece is exception handling. Not every trip is job-to-job. Techs go to the supply house. They stop for fuel. They swing by the shop to grab a part. The agent learns these locations from your system and from repeated patterns. If a truck stops at the same address three times in a week and that address isn’t a customer, the agent asks you once if it’s a supplier or a personal stop. After that, it handles it automatically.

The agent also handles edge cases. If a tech forgets to mark a job complete and drives to the next stop, the GPS log shows two jobs back-to-back with no travel time recorded in the dispatch system. The agent reconciles the data, logs the trip, and flags the incomplete job record so your admin can close it.

If a truck sits in one place for 90 minutes between jobs, the agent checks if that location is a customer address, a supply house, or neither. If it’s neither, the agent flags it as non-billable time and excludes it from the travel calculation. You get a clean log without having to interview the tech about what happened on Tuesday at 2:00 PM.

How This Connects to Dispatch and Payroll

Drive time data is only useful if it flows into the systems you already use. An agent that tracks routes but dumps the results into a separate report is just another tool you have to check. The agent we build for trades businesses writes directly to your dispatch system, your accounting platform, and your payroll file.

When a job is complete, the agent updates the job record with actual travel time and distance. If you bill customers for travel, the line item is added automatically, with the route and mileage attached as backup. If the customer questions it, you have GPS proof that the trip was 18.3 miles and took 34 minutes, not the 12 miles they think it should’ve been.

For payroll, the agent exports a mileage report that matches the pay period. Each tech gets a line for every trip, with the date, the job number, the route, and the reimbursement amount. Your bookkeeper imports it, and the reimbursement is processed without a single manual entry. If a tech disputes the number, you pull up the map and show them the route the agent logged.

For dispatch, the agent builds a routing database. Over time, it learns the typical drive time between every pair of locations you service. When you’re scheduling a new job, the agent suggests the optimal tech based on current location and historical travel time to that address. It also flags jobs that are outliers, like a service call that’s 40 minutes from your usual territory, so you can decide whether to charge a travel fee or decline the work.

This is where Omni for trades businesses becomes the operating system, not just a tracking tool. The agent isn’t just logging miles. It’s feeding dispatch decisions, pricing decisions, and routing decisions in real time.

The Real Cost of Inaccurate Drive Time Data

Mileage reimbursement errors are visible. You’re paying $0.67 per mile, and if the log is inflated by 15%, you’re writing checks for trips that didn’t happen. For a business running six trucks and averaging 1,200 miles per truck per month, a 15% error is 1,080 miles. That’s $723 per month, or $8,676 per year, going out the door for nothing.

Unbilled travel is harder to see but often larger. If you’re not tracking drive time accurately, you’re not billing it accurately. A service call that includes 30 minutes of travel and 90 minutes on-site should have a travel charge. If your invoice only shows the labor, you’re leaving $40 to $80 on the table per job. Multiply that across 20 jobs per week, and you’re missing $40,000 to $80,000 annually in recoverable costs.

Routing inefficiency is the silent killer. A tech who drives an extra 10 minutes per trip because he doesn’t know the fastest route is losing an hour per day. That’s five billable hours per week, or 250 hours per year. At a $95 loaded labor rate, that’s $23,750 per tech. If you’re running four trucks, the number is close to $100,000.

None of these costs show up as a line item. They’re buried in fuel, labor, and the gap between revenue per truck and what you know it should be. The only way to surface them is to track every trip, compare it to the optimal route, and measure the delta. That’s not a job for a human. It’s a job for an agent that never stops watching.

One electrical contractor told us his breakthrough moment was seeing the agent’s report on supply house trips. His crews were making an average of 2.3 trips per day to the same supplier. Each trip was 12 minutes round-trip. The agent calculated that consolidating to one trip per day would save 47 hours per month across the team. That’s $4,465 in labor, plus the fuel and the wear on the trucks. The fix was simple: stock the most common parts on each truck and make one planned run in the morning. The agent surfaced the problem. The owner made the call.

What the Audit Looks Like

When you book a 60-min Omni Audit, we don’t start with a demo. We start with your data. You send us three months of job records, GPS logs if you have them, and mileage reimbursement reports. We load it into the same agent stack we’d build for you, and we run the analysis.

The first output is a drive time audit. We show you total miles driven, total miles reimbursed, and total miles billed to customers. We flag every trip where the route was more than 10% longer than the fastest option. We calculate how much time and money you’re losing to inefficient routing, and we show you the top five patterns that are costing you the most.

The second output is a routing map. We plot every job you ran in the last 90 days, color-coded by tech. We overlay the routes the agent logged, and we highlight clusters where jobs are close together but being handled by different techs or on different days. This is where you see the dispatch opportunities you’re missing.

The third output is an agent spec. We describe exactly which agents we’d build, what data they’d pull, where they’d write the results, and what decisions they’d automate. For drive time tracking, that’s usually three agents: one for passive GPS logging, one for route optimization, and one for billing reconciliation. We also spec the integrations to your dispatch system, your accounting platform, and your payroll process.

You walk out of the audit with a dollar number, a timeline, and a decision. Most trades businesses see ROI in the first 90 days, because the leakage we find is large enough that even partial fixes pay for the build.

If you’re not ready for the full audit, we’ve built a worksheet that helps you quantify the drive time problem on your own. The After-Hours Call Recovery Plan for Trades includes a mileage tracking template and a routing analysis checklist you can use with your current data. It won’t give you the agent-level intelligence, but it’ll show you where to look.

The Agents You Build Once

The 24/7 Dispatch Voice Agent is the front door. It answers every call, qualifies the job, checks your crew’s availability, and books the slot. It also logs the customer’s address and calculates estimated travel time from the closest available tech. If the job is urgent, the agent routes it to the top of the queue. If it’s scheduled, the agent places it in the optimal slot based on routing efficiency. It also triages basic service issues over the phone, so your trucks only roll when there is genuine hands-on work to do.

The Estimate Follow-Up Agent is the closer. Every estimate you send gets tracked. The agent follows up on day two with a polite check-in. On day five, it offers to answer questions or adjust the scope. On day fourteen, it makes a final offer with a small incentive to close. This agent doesn’t track drive time, but it’s part of the same stack, and it converts 15% to 25% of stale estimates into booked work.

The Review and Reactivation Agent is the retention engine. After every completed job, it asks the customer for a review. If the review is positive, it posts to Google and your website. If the review is negative, it alerts you before it goes public. The agent also tracks service intervals and reactivates customers when they’re due for maintenance. For HVAC and plumbing businesses, this agent alone generates 10% to 15% of annual revenue from repeat work that would’ve been forgotten.

These agents don’t replace your team. They handle the repetitive work that doesn’t require judgment, so your team can focus on the calls that do. The drive time agent is part of this system. It runs in the background, logging routes, flagging inefficiencies, and feeding data to dispatch and billing. You don’t interact with it daily. You just see the results in your reports and your bank account.

Why This Matters Now

Fuel is expensive. Labor is expensive. Trucks are expensive. The margin on a service call is thin enough that 20 minutes of wasted drive time can turn a profitable job into a breakeven. If you’re running a trades business at scale, you can’t afford to guess at routing, trust handwritten logs, or skip the travel charge because you don’t have the data to back it up.

The businesses that win in this market are the ones that know their numbers. They know the cost per mile. They know the average drive time between common job pairs. They know which techs are efficient and which ones are burning time. They use that data to price accurately, dispatch intelligently, and bill confidently.

AI makes that possible without adding headcount. The agent tracks every trip, learns every route, and surfaces every inefficiency. It doesn’t take a day off. It doesn’t forget to log a stop. It doesn’t round up the mileage because it’s easier than doing the math.

If you’re still using spreadsheets and odometer photos, you’re leaving money on the table. If you’re reimbursing mileage without verifying the route, you’re paying for trips that didn’t happen. If you’re not billing travel because you can’t prove it, you’re giving away $40,000 to $80,000 per year.

The fix is a 60-minute conversation. Book my Omni Audit and we’ll show you exactly where your drive time is going, what it’s costing you, and what an agent would do about it. No deck. No generic advice. Just your data, your numbers, and a plan you can execute.

For more on how AI agents integrate across dispatch, follow-up, and reactivation, visit our insights library or explore the full Omni platform. If you’re ready to see what this looks like for your business, the audit is the fastest way in.