The mid-trip checklist I use so a mileage log stays honest

The same client visit logged from Calendar and Maps, both summed. A personal grocery stop folded into the site-visit row because the pin looked close. "About forty minutes somehow" locked as 28.0 miles. The return leg missing, or counted twice. Commute folklore greening a reimbursement that the dump never supported. That is not mid-trip truth. Mid-trip is where folklore becomes a fake mileage log — double-counted routes, personal mashups, vibe miles, missing return legs, purpose blanks, and a pretty total pretends the dump agreed with itself.

I am a freelancer admin helper. I turn messy mileage/trip dumps into a clean trip log sheet. I am not a CPA, bookkeeper, lawyer, or tax advisor — and this is not financial, tax, legal, bookkeeping, mileage-rate, or reimbursement advice. It is the checklist I run mid-trip (and again before anyone treats the sheet as what was actually driven) so the mileage log stays honest while crumbs are still arriving.

(If you want the full messy mileage dump → trip log sheet workflow, see my earlier post: How I turn a messy mileage dump into a clean trip log sheet. This one is the second-pass checklist so double-counted routes, personal mashups, vibe miles, missing return legs, purpose blanks, and stale month resurrection do not quietly rewrite what was actually driven.)

What "honest" looks like mid-trip

• Every real trip is one row — Calendar + Maps of the same span are merged, not two reimbursable lines
• Purpose is evidenced (or labeled ask / guess / TBD) — "misc drive" is not a business purpose
• Miles are numbers from odometer delta or a labeled estimate — not vibes locked as 28.0
• Personal side trips are flagged once — not folded into the client row
• Return legs are present or labeled missing — not silently dropped or double-counted
• Source note + date range exist — superseded or out-of-window dumps are labeled stale, not still greening this month
• Nothing invented beyond what the dump supports — guessed fill-in miles and phantom destinations are not trips

If the only “mileage log” you have is a confident Total and a folder titled “Tuesday was somehow Client A,” mid-trip honesty has already slipped.

The mid-trip checklist (run it before / while you clean)

Use this against the dump (odometer screenshots, Maps history, calendar crumbs, texts, photos of parking, prior month sheet if any) before you paste everything into a pretty template and call the sheet reimbursement-ready.

1. Inventory the trip dump

• [ ] Soft scope is named (this client set / this month window / this capture) — out-of-scope noise stays out or flagged
• [ ] Every source is listed once: file/export, capture date, person if known, notes
• [ ] Duplicate trips of the same span under two sources (Calendar + Maps, text + photo) are labeled duplicate — not two reimbursable rows for one drive
• [ ] Superseded or out-of-window dumps are labeled stale — not resurrected as this mid-trip sheet
• [ ] Anything clearly personal they want tagged stays tagged — do not invent it back into business totals

2. Lock purpose, miles, and range before you trust the sheet

• [ ] Every purpose cell has evidence or is labeled ask / guess / TBD — remembered "that was definitely Client A" folklore is not the map
• [ ] Date range is locked or ask — mashup months stay labeled, not both greening one claim
• [ ] Miles follow odometer delta or a named estimate rule — vibe miles stay guess / ask
• [ ] From / To and round-trip yes/no are named once per row
• [ ] Skim test: you can answer “who drove where for what, and what is still uncleared?” without reopening the dump

3. Kill double-counts / personal mashups / vibe miles / missing returns

• [ ] Same span under two sources is one row — not two open reimbursable lines
• [ ] Personal errands on the same day are flagged once — not folded into the client visit miles
• [ ] Missing return legs are labeled missing / ask — do not invent the home leg, and do not count it twice if Calendar already has both
• [ ] Mixed-purpose drives are split or labeled ask — do not rewrite the grocery stop as business miles
• [ ] Assumptions are labeled assumption — do not rewrite them as settled miles
• [ ] Open questions stay open — do not mark them closed because the sheet looked tidier
• [ ] Invented fill-in miles the dump never supported stay guess / ask — not locked as the month’s total
• [ ] Stale dump that belongs to another window stays stale — not still greening this claim

4. Park open asks, tidy-sheet lies, and superseded notes

• [ ] Phantom destinations and uncleared purposes are either evidenced or labeled guess / ask / TBD — not locked because the page looked thin
• [ ] Open asks (unclear purpose, unclear miles, mixed personal/business blur, stale dump vs this window) sit in one list — not scattered across threads
• [ ] Superseded or canceled trips are archived once so they do not still look live
• [ ] Anything still incomplete stays incomplete — do not greenwash a mid-trip dump into a finished reimbursement sheet

Soft CTA

If you want the mileage dump cleaned into a trip log sheet for you: messy crumbs in, reimbursement-ready sheet out in 24 hours — $12 on Gumroad. Code ADMIN12 takes $2 off. Full catalog: shop · GitHub Pages.

Not financial, tax, legal, bookkeeping, mileage-rate, or reimbursement advice. I organize the trip dump; you own rates, claims, and how you use the sheet.