You just dropped a rider off in a neighborhood with nothing going on. No pings, no nearby demand. You drive fifteen minutes back toward where the action actually is, and only then does your next offer show up. Those fifteen minutes, and the miles that went with them, never appeared on any platform's numbers. That's deadheading, and the miles it costs you are dead miles: real wear, real gas, real time, with no payout attached to them at all.
Why platforms don't show you this cost
Uber and Lyft's own numbers are built around the trip you're paid for: the pickup and the ride itself. What happens after drop-off, and what happens before you accept your next offer, isn't part of that picture. That's not a hidden conspiracy, it's just outside the scope of what a single ride's payout is describing. But it's very much inside the scope of what driving for a living actually costs you, which is exactly the gap DriveLens's scoring is built to close: not just what a ride pays, but the drive to get to it, covered in how DriveLens scores a ride offer.
Why some zones are dead-mile traps
A dropoff zone can look fine on paper, decent rider density, reasonable fares nearby, and still be a bad place to end a trip if it consistently leaves you without a quick next pickup. This is usually a pattern specific to a zone and time of day, not something you'd guess without actually driving it repeatedly and noticing where you keep ending up stuck. It's exactly what dropoff intelligence in a heatmap is meant to surface: not just where rides start, but where they leave you and how long you sit or drive before the next one, covered in understanding your DriveLens heatmap.
Minimizing dead miles without guessing
A few things actually help here. First, tracking your own dropoff outcomes over time rather than relying on memory, since a handful of bad experiences in a zone can feel more common than they actually are (or the reverse: a real pattern can feel like bad luck until you look at the data). Second, being willing to end a shift or reposition deliberately rather than chasing the first ping regardless of where it leaves you. Third, weighing a ride's dropoff location as part of the decision to accept it in the first place, not just its payout and pickup distance.
None of this makes dead miles disappear entirely; some amount of driving without a paying rider is unavoidable in this work. But treating it as a real, trackable cost instead of an invisible one is the difference between a shift that pays what it looks like it should and one that quietly doesn't.