I get where you’re coming from, but I’ve seen app logs go missing or get “updated” after the fact. Screenshots might feel like overkill, but when you’re dealing with split-second coverage changes, that little image can be the difference between a paid claim and a nightmare. I’d rather have too much than not enough, honestly.
Screenshots might feel like overkill, but when you’re dealing with split-second coverage changes, that little image can be the difference between a paid claim and a nightmare.
Honestly, I get the logic, but stopping to screenshot every status change? That’s just not practical when you’re hustling. I rely on the trip receipts and in-app history—they’ve always backed me up. If they start losing logs, that’s their problem, not mine.
Yeah, screenshots seem like a lot when you’re in the middle of a busy shift. I’ve always just trusted the app records too—if something goes sideways, that’s on them, right? But I did have a buddy who had to fight tooth and nail over a claim because the logs “didn’t show” he was on a ride. Makes you wonder if it’s worth the hassle just in case... but man, who’s got time for that every trip?
Honestly, I get where you’re coming from. It feels like overkill to screenshot every ride, but after seeing a couple folks get burned by “missing” logs, I started doing it for the big fares or weird trips. Not every single time, just when it feels sketchy. It’s a pain, but losing out on a claim is worse.
It feels like overkill to screenshot every ride, but after seeing a couple folks get burned by “missing” logs, I started doing it for the big fares or weird trips.
I totally get that. Had a client once who only screenshotted the “big” rides, then got in a fender bender on what he called a “routine” trip. No screenshot, and the app glitched—he spent weeks trying to prove he was even on the clock. It’s a hassle, but those screenshots can be gold when things go sideways. Sometimes it really does come down to having that one extra piece of proof.