Logging Mileage on Late-Night Surge Shifts Without Losing Miles to Sleep

Late-night and overnight surge shifts pay well, and they are also exactly when manual mileage logging falls apart, because the driver most likely to skip an entry, forget to note a business purpose, or fall asleep before writing anything down is a driver five hours into a bar-close shift.

Source: IRS Publication 463, on the contemporaneous record standard, applied to real driving conditions.

Why fatigue is a mileage-tracking problem, not just a driving one

A contemporaneous log depends on entries being made close to the time of each drive. A driver working a 10 p.m. to 4 a.m. surge shift, taking back-to-back fares through the overnight hours, is the least likely person to reliably tap "start trip" and "end trip" by hand for every single ride, or to write a clear business-purpose note at 3 a.m. between drop-offs. The gaps that show up in overnight logs are rarely intentional, they're just what happens when a manual system meets real exhaustion.

Where the miles actually disappear on a surge shift

• A driver forgets to restart tracking after a longer break between fares
• Repositioning toward the next surge zone gets skipped because it "wasn't a real trip"
• An entry gets logged the next afternoon from memory, after the specific route is already fuzzy
• A dead phone battery mid-shift, common on a multi-hour overnight run, kills tracking for the rest of the night

Why automatic tracking matters more here than on a normal daytime shift

Auto-detected, GPS-based tracking removes the dependency on the driver remembering to do anything at all, which matters most exactly when a driver's attention and memory are at their weakest. The record gets built by the drive itself, not by a tired person's discipline at 2 a.m.

A worked example of what a bad night costs

A driver working four overnight surge shifts a month loses an estimated 15 percent of true mileage to forgotten entries and a mid-shift dead battery, on roughly 480 miles a month of overnight driving. That is about 72 missed miles a month, worth around $54.72 at the 76-cent second-half 2026 rate, or close to $660 over a year of overnight shifts logged manually and imperfectly.

Practical steps that actually help on a manual system

• Keep a phone charger in the car specifically for overnight shifts, not just a general backup
• Log the trip's business purpose the moment you finish a fare, not at the end of the whole shift
• If a gap happens, note it as a gap immediately rather than guessing the mileage days later

Does a mid-shift nap between fares affect anything for mileage purposes?

No, mileage only accrues while driving. A parked break generates no mileage either way and does not need to be logged as a gap.

Should overnight mileage be tracked any differently than daytime mileage for tax purposes?

No, the same rules and the same 2026 rate split apply regardless of the hour the miles were driven. The only difference is how much harder it is to keep the record accurate manually overnight.

What a reviewer sees in an overnight log full of gaps

A log with several unexplained multi-hour gaps on the same recurring overnight shifts, week after week, reads differently than a handful of isolated gaps scattered across the year. The pattern itself, always missing the same late window, suggests a systemic tracking failure rather than occasional forgetfulness, and it is worth fixing the underlying cause rather than treating each gap as a one-off exception to explain later.

If my phone dies mid-shift, is there anything I can do after the fact to reconstruct that stretch?

Yes, use the same reconstruction approach that applies to any gap: platform trip history for that window, a rough sense of the route and distance, and a clear note that the entry was rebuilt rather than logged live. A documented reconstruction is far stronger than leaving the gap unexplained.

Why surge-shift drivers have the most to lose from bad tracking

Surge pay makes late-night and overnight shifts financially attractive precisely because the driving is often heavier during those windows, more trips, more repositioning, more total mileage packed into a shorter shift. That means the dollar value of a missed mile is effectively the same as any other mile, but the volume of miles at risk of being missed is higher on a surge shift than on a typical daytime shift, simply because more driving is happening in a compressed, exhausting window.

A driver who works several overnight surge shifts a month and relies on manual logging is, in effect, taking on a bigger tracking-accuracy risk exactly during the shifts that generate the most mileage to track. Fixing the tracking method for those specific shifts, even while keeping manual habits elsewhere, addresses where the actual exposure concentrates.

Auto-tracking works the same at 3 a.m. as it does at noon. Try TruMile →

Related guides