What I’m Learning
The Ride Pays. The Whole Shift Counts.
The fare on the screen is only part of the story. I want to know what a few hours of driving actually leave me with.
I don’t have unlimited hours to drive. Between four kids, school runs, sports, and the rest of life, my available work time already has plenty of competition.
When I turn on an app, I need those hours to count.
That’s why I’m paying more attention to a basic question: what did the whole shift earn?
A ride can look decent on the offer screen. But getting to the passenger takes time. Waiting takes time. After drop-off, I might need to drive somewhere else before another useful offer comes along. The passenger’s trip is only one part of my work.
If I count only the minutes somebody is in the car, I can make an ordinary shift look a lot better than it was.
The money needs the same treatment. A payout is money coming in. Fuel, maintenance, tires, and the other costs of running the car still come out. Taxes matter, too. I want to know what the work leaves me with.
The biggest fare doesn’t automatically answer that question. A smaller fare may fit the time I have available. A larger one may involve enough extra driving to make it less appealing. The offer needs context.
I’m also trying to avoid judging a strategy by one great trip or one terrible afternoon. Traffic, demand, and luck can make a single shift misleading.
My starting point is simple: count the full time, recognize the costs, and judge the work by the result.
I want a useful answer when I ask whether driving was worth the hours I gave it.
How do you measure your own shifts: total payout, earnings per hour, money after expenses, or something else?