DoorDash "Active Time" vs. Miles Driven: Why They're Not the Same Number

DoorDash's "active time" measures the time from when you accept an order to when you complete it, not how long you were online and available during a Dash overall (that whole-Dash period is a separate metric, "Dash time"). Neither one measures how many miles you actually drove. A high Dash-time or active-time number can come with very little mileage, and a modest one can come with a lot of driving, depending on how spread out the deliveries were.

Source: IRS Publication 463, on business mileage as the relevant figure for the standard mileage deduction, distinct from time-based platform metrics.

What active time is actually measuring

Active time is the total time between accepting each order and completing it, added up across every order in a Dash. It does not include the time spent waiting for an order to be assigned in the first place. That waiting time plus the active periods together make up "Dash time," the broader metric for how long you were online during the whole Dash. Both are scheduling and pay-eligibility metrics, and neither one has anything to do with distance.

Why the two numbers can move in opposite directions

A slow zone can produce a long Dash-time number with almost no driving, sitting parked most of that time waiting for an order to be assigned in the first place. A busy zone can produce a short Dash time with heavy mileage, back-to-back deliveries with real distance between the restaurant and each drop-off, plus dead mileage between orders. Active time itself, the portion actually spent working an accepted order, doesn't track distance in a fixed way either: a delivery with a long drive and a delivery with a short drive can take about the same active time depending on traffic and prep delays. None of these time-based numbers predicts mileage.

Why this matters for taxes specifically

Neither active time nor Dash time has a role in your mileage deduction. Only actual miles driven for business purposes count, whether that driving happened during a single long Dash or across several short ones. A Dasher who assumes a big active-time or Dash-time number for the week automatically means a big mileage number is making an assumption the data does not support.

A worked example

On a slow Tuesday afternoon, a Dasher logs 3 hours of Dash time but completes only 4 orders, driving a combined 14 miles total, most of that Dash time spent waiting for an order to be assigned. On a busy Friday dinner rush, the same Dasher logs 2.5 hours of Dash time, completes 11 orders, and drives 38 miles, most of that time actually spent working accepted orders back-to-back. The Friday shift has less Dash time and nearly three times the mileage. Mileage tracking has to run off actual driving, independent of either shift's active-time or Dash-time total.

What to actually track instead of active time

• Every mile driven while in an active Dash, order-assigned or not
• Dead miles between drop-offs and the next order, covered separately in dead miles between drops
• The date and total miles per Dash session, not the active-time duration

Does DoorDash's own tax summary use active time to calculate mileage?

No, DoorDash's tax summary reports delivery-leg mileage from assigned orders, not active time. Active time is a separate metric shown elsewhere in the app for scheduling and pay purposes.

Should I stop tracking active time altogether since it doesn't matter for taxes?

Active time and Dash time are both still useful for deciding when and where to Dash for better pay, just keep them separate from your mileage log, which needs to be built from actual driving distance regardless of either duration.

Why this confusion is common among newer Dashers

The Dash-time and active-time numbers are what DoorDash surfaces most prominently in the app during a Dash, so one of them is the natural number a newer Dasher reaches for when estimating their own mileage at tax time, especially since the two terms themselves are easy to mix up. The confusion is understandable, not a sign of doing anything wrong, but it's worth correcting early, since a full year of assuming either one predicts mileage means a full year of guessing rather than tracking.

Does the same distinction apply to Uber's or Lyft's version of active/online time?

Yes, the same logic holds across platforms. Whatever a platform calls its online or active-time metric, it measures availability or scheduling, not distance, and none of them substitute for an actual mileage log.

Why this matters more for Dashers working multiple zones

A Dasher who moves between different delivery zones over the course of a shift, chasing better order density or higher pay in a different area, will see active time and mileage diverge even more sharply than a Dasher who stays in one zone all shift. Repositioning between zones adds real mileage without necessarily adding much active time, since travel between zones while no order is accepted falls under Dash time rather than active time, regardless of how far it covers.

For a Dasher working this way regularly, mileage tracking has to capture the zone-to-zone repositioning drives specifically, not just the delivery legs within any single zone, since those inter-zone drives can represent a meaningful share of total business mileage for the shift.

Why this same mismatch shows up on other delivery platforms too

Instacart's shopping-and-delivery time, Amazon Flex's block duration, and similar time-based metrics on other delivery platforms all carry the same disconnect from actual mileage that DoorDash's active time does. A Dasher who also works other delivery apps should apply the same reasoning across all of them: whatever time-based number a platform surfaces prominently, treat it as a scheduling and pay metric only, and keep mileage tracking entirely separate and independent of it.

Track the miles, not the clock. Auto-tracking captures every mile of a Dash regardless of how busy it was. Try TruMile →

Related guides