In Atlanta, GA, Darnell W runs a 5-tech plumbing operation. He lost a chargeback he should have won, because a tech’s “proof” photo was timestamped four days before the job ever happened.
What was actually bleeding
Darnell lost a $2,200 chargeback he should have won. A tech had uploaded a photo from the camera roll — timestamped four days before the job ever happened. The bank looked at the evidence, saw a date that didn't line up, and sided with the customer. The proof wasn't proof.
What Darnell asked us to build
“Make it technically impossible to close a job without a LIVE photo taken at that address, that day — no camera roll, no workarounds.”
— Darnell W, Plumbing — Atlanta, GA
What we built
We built a forced live-camera capture — not a file picker. The job can't close until the tech takes a photo through the app, and every shot is welded to the job ID, the on-site GPS, and a server timestamp. We layered in dual digital signatures: scope agreed at the start, satisfaction confirmed at the close.
No live photo yet. The job can't close without one.
Locked. Capture a live photo to unlock.
How the tool works
Try it yourself below: the job won’t close until you take a LIVE photo through the device camera. A camera-roll upload is rejected on purpose — that’s the entire point.
- Close Job stays locked until a live photo is captured inside the app.
- Every shot is welded to the job ID, the on-site GPS, and a server timestamp.
- A camera-roll upload is hard-blocked — there’s no back door.
- What you get is a tamper-proof record, with a content hash, that holds up when a customer disputes the work.
Forced photo proof is one safeguard inside the Service OS we build. Around it sit dual signatures at scope and close, job records that survive turnover, and a paper trail that wins chargebacks instead of losing them.
What came back
Zero chargebacks since go-live. The techs stopped seeing it as friction — they treat the locked record as armor when a customer tries to rewrite history.
That’s not a projection — it’s what changed after we shipped the build.
The tool you just used isn’t a mockup — it’s the kind of thing we build inside our Service OS, one module of a system made for your trade and owned by you. If you’re carrying a version of this problem, the fastest way to see what a system would catch in your operation is to run your own numbers.
The takeaways
- Camera-roll uploads aren’t proof — a live, in-app capture welded to GPS and a server timestamp is.
- Lock the close: no live photo, no closed job.
- A tamper-proof record is armor when a customer tries to rewrite history.
Ex-Microsoft operations and fractional COO for $5M+ field service operations. He writes about the systems that let trade companies scale without the owner holding everything together by hand.
These are the things we build inside our Service OS.
Every tool in this story is one module of a custom operating system we build for trade businesses — built for your trade, owned by you. Spin up a free OpsVault account and run your own operation through it: the Live Bleed Calculator, the Journey Map, the whole Vault. No credit card, no sales call.