The before-you-share checklist I use so a mileage log still matches what was driven

A mileage trip-log sheet can look claim-ready while its story is already wrong: a phantom trip row is added for a tidy month; soft “about forty minutes somehow” is upgraded to a hard 28.0; Calendar and Maps of the same span are double-counted into one green total; a Slack “sounds about right” rewrites the week; a superseded prior-month dump still ships as this period; or a personal grocery stop is quietly folded into the client visit without a label.

Before-you-share is different from a mid-trip cleanup. This is the pass I run when the sheet is about to leave my hands and someone else may treat every mile as what was actually driven.

I am Brittany Bonds, a freelancer admin helper. I turn messy mileage and trip dumps into clean trip-log sheets. I am not a CPA, bookkeeper, lawyer, or tax advisor, and this is not legal, financial, tax, bookkeeping, mileage-rate, or reimbursement advice. It is an administrative proof-checking routine, not a recommendation about what anyone should claim, deduct, or reimburse.

This complements How I turn a messy mileage dump into a clean trip log sheet and The mid-trip checklist I use so a mileage log stays honest. Those live posts cover the first-pass workflow and the mid-trip honesty cleanup. This third pass is the pre-share evidence check — not a rewrite of either.

What “honest enough to share” looks like

• Every trip row and mile total maps to an odometer note, Maps/calendar crumb, photo, or a labeled ask — nothing invented for a tidy claim preview.
• Soft estimates stay soft; hard decimals only appear when a source supports them.
• Same-span duplicates (Calendar + Maps, text + photo) stay merged or labeled duplicate — they are not two reimbursable lines.
• Slack guesses and “I think that was Tuesday…” stay labeled guess / ask — not client- or employer-confirmed.
• Superseded or out-of-window dumps are labeled stale or removed from the share view.
• Personal side trips stay flagged once — not silently rewritten as business miles.
• An emoji reaction or vague “sounds about right” is not treated as a locked month total unless the sheet states what was confirmed.

If the only share instruction is “send the clean mileage log,” pre-share honesty has already slipped.

The before-you-send checklist

Use this against the near-final sheet and live evidence: the original trip dump (odometer screenshots, Maps history, calendar crumbs, texts, parking photos), prior period sheet if any, and the mid-trip scratch trail. The goal is not to make every cell complete. The goal is to make uncertainty visible before the sheet becomes someone else’s claim source of truth.

1. Freeze trip rows to what was driven

• [ ] Every trip row maps to a source crumb, screenshot, export, or a labeled ask — no orphan row gets a confident “this is the month” look.
• [ ] Invented destinations, template filler, and “bonus” trips that never appeared in the dump stay out or labeled proposed / ask — polish is not permission.
• [ ] Duplicate entries under two phrasings (Calendar + Maps of the same span) are merged or marked duplicate — one drive is not two claim slots because it looked tidy twice.
• [ ] From / To naming stays close to the source; a polished synonym may not be the same route or client site.
• [ ] Skim test: a reader can point from each row back to a source, or see that it still needs confirmation.

An invented trip row is not automatically useless. It is a proposal. The misleading part is leaving it dressed as what was already driven for the period.

2. Keep miles and purpose strength-honest

• [ ] Soft notes (“about forty minutes,” “half day on the road”) stay soft — they are not upgraded to hard decimals for neatness.
• [ ] Hard mile totals keep an odometer delta, named estimate rule, date, or confirmer when available — silence is not consent.
• [ ] Purpose stays evidenced or labeled ask / guess / TBD — “misc drive” is not a business purpose just because the sheet looked thin.
• [ ] Round-trip yes/no and return legs match the latest source; a missing return stays missing / ask — do not invent the home leg for a prettier total.
• [ ] Business vs personal stays labeled when the dump distinguished them — folding one into the other without a note is a rewrite.
• [ ] Skim test: a reader can tell which lines are locked, which are soft, and which still need confirmation.

This is a consistency check, not mileage-rate or reimbursement advice. I am recording what the dump disclosed, not deciding what anyone must claim.

3. Retire stale dumps before they travel

• [ ] Walked-back, canceled, or out-of-window trips are labeled stale or removed from the share view — they do not still green a month total.
• [ ] When odometer, Maps, and calendar disagree, keep the conflict visible as recheck — do not pick the easier miles because they fit the template.
• [ ] Capture or last-checked date exists for material totals — “I cleaned this last week” is not a freshness rule.
• [ ] Raw scratch, rejected options, and unresolved conflicts stay in the evidence trail but out of the clean share view.
• [ ] Skim test: a reader can tell whether each line describes the current dump, an older period, or something still needing confirmation.

A stale trip line is historical context. The misleading part is leaving it dressed as this period’s share-ready miles.

4. Challenge the Slack “sounds about right”

• [ ] Replace “they said sounds about right” with the exact trips, miles, or date range that were confirmed, parked, or never named on the sheet.
• [ ] An emoji reaction, “lgtm,” or vague thumbs-up is labeled by what it covered — it does not silently rewrite trip totals.
• [ ] If Slack approved a different version than the sheet you are about to send, stop and reconcile — do not ship the prettier draft under the older reaction.
• [ ] Make the share ask specific — confirm this trip, this overlap, this personal flag, this period — instead of asking for another vague thumbs-up.
• [ ] Leave a visible needs confirmation marker where sharing would otherwise create a false record of agreement.
• [ ] Final skim: I can answer “what source supports this line, what still needs confirmation, and what did Slack actually cover?” for every share-ready row.

If a row fails one of these checks, I would rather send a visible needs confirmation label than make the mileage log look complete by guessing.

Soft CTA

If you have a messy mileage or trip dump and want it organized into a clean trip-log sheet, mileagesheet on Gumroad is $12. Code ADMIN12 takes $2 off. Browse the full shop or the catalog mirror on GitHub Pages.

Not a CPA. Not legal, financial, tax, bookkeeping, mileage-rate, or reimbursement advice — just an admin checklist for keeping a shared mileage log tied to what was actually driven.