Why reconstructed and paper logs fall apart under scrutiny
Most field service businesses do not lose a mileage deduction because they drove too little. They lose it because they cannot prove the miles they drove. The truck went 22,000 business miles last year — the owner knows it, the technicians know it, and the fuel receipts hint at it. But when someone asks for the record that backs the number, what surfaces is a spreadsheet built the week before the filing deadline, populated from memory and a glance at the calendar.
That kind of after-the-fact reconstruction is exactly the record most likely to be challenged. The problem is not honesty; it is timing. A log assembled months later cannot show that any individual trip actually happened on the day claimed, to the place claimed, for the reason claimed. It is an estimate wearing the costume of a record. The same weakness applies to the glovebox notepad with a few scrawled odometer readings and no destinations — it captures a number without the context that makes the number believable.
The phrase people reach for is "audit-proof mileage log." It is a useful goal, but worth being precise about: there is no official certification that stamps a log as audit-proof, and no record can guarantee an outcome. What you can do is keep the kind of records the IRS expects — complete, trip-by-trip, and recorded at the time — so that if a question ever comes, your documentation does the talking. That is the realistic version of audit-proof, and it is entirely achievable.
The IRS "contemporaneous" requirement, in plain English
The word that does the heavy lifting here is contemporaneous. It simply means recorded at or near the time the trip happened — while the details are still fresh and accurate — rather than reconstructed later. IRS Publication 463, which covers travel and car expense recordkeeping, describes timely-kept records as carrying more weight than a written statement prepared afterward from memory. The logic is intuitive: a note written the day you drove is more credible than one written eleven months later.
This is general guidance, not a verbatim rulebook, and the specifics of your situation are a conversation for a CPA or tax professional. But the principle is stable and it is the single most important thing to understand: a record's credibility is tied to when it was created, not just what it says. Two logs can contain identical numbers, and the one written contemporaneously is the stronger record.
For a field service business, that reframes the whole task. The goal is not to produce a beautiful mileage report at tax time. The goal is to capture each trip as it happens during the year, so that the year-end report is just a sum of records that already existed. If the capture is contemporaneous, the report is trustworthy. If the capture happens only at the end, no amount of formatting fixes the timing problem.
A mileage log is not a math problem you solve in April. It is a habit you keep all year — or a system that keeps it for you.
The four things every trip record must show
Strip away the formatting and the IRS generally wants the same four facts for each business trip. Miss any one and the record gets weaker; capture all four and you have something defensible.
1. The date. When the trip happened. A real date that maps to a real workday is the anchor for everything else. "Sometime in March" is not a date.
2. The destination. Where you went. A customer site, a supplier, a second job — the place that gives the trip a reason to exist. A destination ties the miles to a verifiable location rather than a guess.
3. The business purpose. Why the trip was for work. "Service call," "warranty visit," "parts pickup for the Henderson job." This is the fact a bare GPS point cannot supply on its own, and it is often the one that is missing from generic mileage logs. The purpose is what distinguishes a deductible business mile from a personal errand.
4. The miles driven. How far. The actual business miles for the trip — and many drivers also track the vehicle's total annual mileage so business use can be expressed as a percentage of the whole. The miles are what the standard rate ultimately prices.
Notice that two of these four — date and miles — are mechanical and easy to capture automatically. The other two — destination and purpose — require knowing something about why the vehicle moved. That distinction is the whole game, and it is where a mileage tool built into your field service software pulls ahead of a standalone tracker.
How real-time GPS capture meets the standard
Recording trips by hand satisfies the standard in theory and fails it in practice, because humans forget. The trip you meant to write down at 4pm is gone by 5pm, and the one you reconstruct in April is exactly the weak record we started with. The reliable way to keep a contemporaneous log is to let the work capture it automatically as it happens.
This is where GPS-based capture earns its place. A trip recorded on the device as it is driven is contemporaneous by definition — it exists the moment the wheels turn, not the moment someone remembers. That immediately covers the date and the miles, two of the four required facts, with no human effort and no memory involved.
The harder two facts — destination and purpose — are where FSM Navigator's mileage tracking is built differently from a standalone app. Because the mileage record lives inside the same system that runs your jobs, each business trip is captured against the actual service visit it belongs to. When a technician marks a job en route and then arrived, the drive between those two points becomes a logged trip tied to that job — so the destination and the business purpose come straight from the work itself, not from someone's memory three weeks later. The record knows it drove to the Henderson address because there was a job at the Henderson address.
The result is a year-long stack of trip records, each one carrying the date, the destination, the purpose, and the miles, each one recorded as it happened, and each one traceable back to a real event in your system. At year end there is nothing to reconstruct — the IRS-ready records already exist, and they help you stay audit-ready rather than scrambling. To turn those logged miles into a dollar figure you apply the 2026 standard rate; the IRS set the 2026 business mileage rate at 72.5 cents per mile, and our 2026 mileage rate guide walks through the math for HVAC, plumbing, and electrical shops.
One honest note on what these records are and are not: they are documentation of business driving, not a reimbursement payout. A company can use them to reimburse technicians or to support a deduction, but the log itself is a record. And while the system produces the kind of records the IRS expects, the decision about what to claim and how is one to make with a CPA or tax professional who knows your books.
A short checklist for a defensible log
Before you trust your current setup, run it against this. A defensible mileage log captures each business trip at the time it happens; shows the date, destination, business purpose, and miles for every trip; ties each trip to something verifiable, such as a job or a customer visit, rather than to memory; keeps the records intact and exportable for the years you may need them; and stays consistent all year instead of appearing in a single April session. If any of those are missing today, the fix is not a better spreadsheet — it is a system that captures the trips for you as the work happens.
The good news for field service businesses is that you are already generating the hard part. Every dispatch is a destination. Every job is a purpose. The miles are just the distance between them. Capture that automatically and the audit-proof goal stops being a year-end chore and becomes a byproduct of running the day.