You don’t realize mileage tracking is a problem until someone asks you to prove it.
Last year, I got a reimbursement review email from a client: “Please provide your mileage log for Q2–Q3, including origin/destination and business purpose.” I had… a total miles number I’d scribbled in a notes app and a bunch of “I definitely drove there” confidence. Two days later, they rejected part of the reimbursement because my log didn’t tie to anything. Real money gone. And the worst part was the realization: this is where I messed up – there was nothing contemporaneous to point to.
This post is about what to do if you forgot to track mileage after the fact – in a way that holds up better for an auditor, an employer, or a picky finance department.
The email that makes your stomach drop (and why “I’ll estimate it” backfires)
When you’re missing months of mileage, the reflex is to “recreate” a year with clean totals.
That’s where people accidentally dig the hole deeper.
A mileage log isn’t just a number. It’s a story with receipts: date, where you went, why it was business, and how you got the miles. If you hand over a spreadsheet full of round numbers and perfectly repeated trips, it can look manufactured even if you really did the driving.
Blunt truth: if you forgot to track, you’re not fixing that by becoming a spreadsheet artist.
Step 1: Stop guessing and define the time window you can actually support
Start by drawing a hard box around what you can defend.
- What months do you have any supporting material for? (Invoices, dispatch logs, calendars, client emails)
- Did you change vehicles mid-year?
- Are you mixing gig work with a W-2 job that reimburses differently?
Pick a window you can support without inventing. If you can support April–December well and January–March is a blur, that’s not a moral failure – it’s a risk decision.
If you’re reconstructing for taxes, remember the general standard: the IRS wants adequate records created near the time of the travel. Rebuilt logs can still be used, but they’re stronger when they’re clearly grounded in other records and not just “my best guess.”
Step 2: Rebuild trips from “anchors” (calendar, invoices, dispatch logs, messages)
Think in anchors, not miles.
Anchors are items that prove you were supposed to be somewhere for work:
- Gig platform daily/weekly summaries (even if the mileage is wrong, the dates and jobs help)
- Client invoices, work orders, service tickets
- Appointment calendar entries
- Dispatch texts, email threads, DM confirmations
- Photos you took on-site (timestamps)
Now rebuild in this order:
1) List the business days you actually worked.
2) For each day, list the stops you can prove (Job A, Job B, supplier run).
3) Only after you have stopped, calculate the miles.
This sounds slow because it is. But it prevents the classic trap of starting with a total and trying to reverse-engineer a “log” to justify it.
Download MyCarTracks and start tracking your mileage now
Step 3: Consistently add mileage (and pick one method you can explain)
Once you have stops, you need a consistent mileage method you can explain without sweating.
Common options people use when rebuilding:
- Mapping tool mileage between addresses (consistent routing assumptions)
- Known route mileage for repeat runs (e.g., “warehouse to Site A is 18.2 miles”) and only adjusting when there’s evidence it changed
- Odometer deltas if you have start/end readings for some periods (oil change receipts, inspection records, photos)
What matters most is not that your miles are “maximized.” It’s that you can say:
- “Here’s how I calculated miles.”
- “Here’s what I used as source records.”
- “Here’s why these trips were business.”
GPS miles vs odometer vs platform miles (quick reality check)
People get hung up because numbers don’t match.
- The odometer counts the distance the car traveled.
- GPS/app may smooth routes, drop short trips, lose signal, or merge segments.
- Platform-reported miles often ignore repositioning, deadhead miles, or off-app errands that were still business-related.
Mismatch isn’t automatically “wrong.” But inconsistency without explanation looks bad.
Step 4: Create a credibility package: what to attach, what to write, what to keep
If this is for an audit response or reimbursement review, don’t just send the log alone.
Keep (and where appropriate, provide) a simple “credibility package”:
- The reconstructed log (date, start/end location, business purpose, miles)
- Supporting documents folder by month (PDFs/screenshots)
- A short written note describing your method and what’s missing
Example of the tone that helps (not legal advice):
“This log was reconstructed from calendar entries, invoices, and dispatch records. Mileage was calculated using consistent point-to-point mapping between documented stops. Where specific addresses were unavailable, trips were excluded rather than estimated.”
That last line matters.
The common mistake: trying to match platform miles instead of proving business purpose
A lot of gig workers chase the platform mileage number like it’s the “answer key.”
It usually isn’t.
If you’re ever questioned, the fight is rarely about whether you drove exactly 21.7 vs 22.4 miles.
It’s about whether the trips were business and whether your recordkeeping is believable.
Platform miles can be a reference, but building your log to “match” them can accidentally delete legitimate miles (like driving to the first pickup, supply runs, or repositioning between busy zones) or create weird gaps you can’t explain.
The earned insight: partial, boring records beat perfect-looking reconstructions
This is the uncomfortable thing I learned the hard way:
A reconstructed log that admits uncertainty is often safer than a perfect one.
Beginner advice says, “make it complete.” In real life, “complete” after the fact can look like you made it up.
Auditors and reviewers have seen the too-perfect spreadsheet: identical miles every Tuesday, neat weekly totals, no variance, no missing days. Real driving is messy. Traffic exists. Detours happen. If your reconstructed year looks like a metronome, it can raise eyebrows.
So if you truly can’t support a chunk, exclude it or mark it clearly as unsupported and don’t claim it. Yes, that can mean losing some deduction.
But losing a portion you can’t prove is usually cheaper than having the whole thing questioned.
How to prevent this next year without making your life a tracking project
After getting burned, my rule became: capture trips close to real time, even if categorization happens later. The failure mode isn’t “wrong math” – it’s missing days.
I keep a simple habit:
- End of day: quick check that trips exist (not perfect labeling)
- End of week: fix categories and add any missing business purpose notes
After I had a reimbursement rejection, I switched my personal workflow to automatic tracking (I use MyCarTracks) mainly because it reduced the “blank weeks” problem. Not because it made the report prettier, but because it gave me something consistent to fall back on.
Whatever system you use, optimize for one thing: not relying on memory when someone asks for proof months later.
