Build Your Own Miles-per-$1,000 Benchmark to Catch Mileage Log Gaps

There is no single official "miles per $1,000 of fares" number, because it depends heavily on your market, the platform, and how much of your driving is online-waiting time versus paid trips. What is useful is building your OWN benchmark from a few real weeks of data, and using it to sanity-check whether your mileage log looks complete.

Source: your own weekly mileage and earnings data, cross-checked against why your gig platform mileage number isn't enough and the recordkeeping standard in IRS Publication 463.

Why a generic industry number would not actually help you

A driver working dense urban Uber or Lyft rideshare with short, frequent trips has a completely different miles-per-dollar ratio than a DoorDash or Amazon Flex driver running long-haul delivery routes in a rural area. Publishing one number as if it applied broadly would be exactly the kind of unverified figure worth being skeptical of on a tax page, and the IRS still expects a real mileage log either way, not an industry average. The useful version of this benchmark is personal, built from your own weeks of driving.

How to build your own benchmark

1. Pick 3 to 4 representative weeks, a mix of busy and slow shifts
2. For each week, record total gross fares and total miles driven, including online-waiting and dead miles, not just paid-trip miles
3. Divide total miles by (gross fares divided by 1,000) to get your personal miles-per-$1,000 figure for each week
4. Average the weeks to get your own working benchmark

A worked example of the calculation

A driver grosses $1,850 in fares over a week and logs 640 total miles for that same week, including online-waiting and dead mileage. Their miles-per-$1,000 figure for that week is 640 divided by 1.85, or about 346 miles per $1,000 of fares. Repeating this across a few weeks and averaging smooths out any single unusually busy or slow week.

How to actually use the benchmark once you have it

Once you have your own typical ratio, check any future week against it. A week where your logged mileage comes in far below your usual ratio, for the same or similar gross fares, is worth a second look, it may mean your tracking had a gap that week, a dead battery, an app that stopped auto-detecting, rather than an unusually efficient shift.

What can throw the benchmark off, and that is fine

• A week with unusually long airport runs will show fewer miles per dollar than a week of short local trips
• A slow week with lots of online-waiting time will show more miles per dollar than a busy surge week
• Switching between rideshare and delivery within the same week changes the ratio, since delivery and rideshare fare structures differ

Why this is a sanity check, not a substitute for actual tracking

This benchmark exists to help you notice when a week's logged mileage looks off relative to your own normal pattern, prompting you to investigate a possible tracking gap. It is not a substitute for a real, trip-by-trip mileage log, and it should never be used to estimate or pad an actual deduction figure without the underlying trips to support it.

Should I use this benchmark to fill in a week I forgot to track?

No, use it only to flag that something looks off and prompt you to reconstruct that week from other evidence, the same defensible-reconstruction approach covered elsewhere, not to substitute an estimated number directly onto your return.

Does this benchmark work the same for delivery drivers as rideshare drivers?

Build a separate benchmark for each type of work you do, since delivery and rideshare have different typical trip lengths and fare structures, and mixing them into one ratio makes the sanity check less useful.

How often to update your benchmark

A benchmark built once at the start of the year can drift out of date as your market changes, a new competitor enters, surge patterns shift, or you move to a new area. Rebuilding it every few months from a fresh set of representative weeks keeps the comparison meaningful, rather than flagging every week as unusual against a ratio that no longer reflects current conditions.

Is it worth sharing benchmark numbers with other drivers in the same market?

Comparing notes with other drivers in your specific market and platform can be a useful sanity check on your own number, but treat any shared figure as a rough reference point, not a standard to match, since individual routes and habits still vary.

What quest bonuses and streak pay do to the ratio

A platform bonus paid for completing a set number of trips or hitting a weekly streak counts toward your gross fares for that week even though it isn't tied to any single trip's distance. A week that included a large bonus will show a lower miles-per-$1,000 figure than a week without one, purely because the denominator grew without any extra driving behind it. Pull bonus income out of the calculation, or note which weeks included one, so a bonus-heavy week doesn't get flagged as a false mileage gap.

The real fix underneath any benchmark is a mileage log that never has a gap to catch. Try TruMile →

Related guides