A picture ends the argument
Two months after a job, a customer calls: the work was never done right, the tech damaged something, the invoice was for parts they never got. Without evidence, it's your tech's word against the customer's memory — and the customer is the one writing the review. With a timestamped before-and-after photo attached to the job, the conversation is over in thirty seconds. Photo evidence is the cheapest insurance policy in field service, and most operations leave it sitting on techs' camera rolls where it does nobody any good.
Job photos do three jobs at once: they defend you in disputes, they sell the next piece of work, and they prove the job happened the way you billed it. The difference between a photo that helps and a photo that's lost is structure — photos attached to the right job, not scattered across a phone.
Defense: the dispute that never happens
- Pre-existing damage. A photo taken on arrival, before anyone touched anything, means the dent that was already there can't be pinned on your tech.
- Proof of work performed. The new part installed, the cleared blockage, the corrected wiring — photographed in place — backs up every line on the invoice.
- Site conditions. A photo of the hazard, the access problem, or the customer's setup explains why a job took longer than quoted, before anyone calls it padding.
Sales: the photo that books the next job
The most underused photo in field service is the one the tech takes of the problem they didn't fix today. The corroded panel next to the one they replaced. The water stain that hints at a leak. A tech can describe it, but a photo handed to the customer — "this is what I saw, here's what it'll become" — sells the follow-up work far better than a sentence in a report. Visual evidence converts because it's undeniable.
Proof: making the photo count
A photo only helps if you can find it and trust it. That requires discipline most camera-roll workflows can't deliver:
- Attach it to the job, not the phone. A photo tied to the specific job record is retrievable in seconds two years later. A photo in a tech's gallery is gone.
- Capture context. When the photo lands, when it was taken, and which job it belongs to all need to travel with it.
- Make it secure. Customer property and site photos are sensitive. They should live behind access controls, not in a public link anyone can guess.
Hosting Field handles photo evidence on the job: techs attach photos to the job from the field, and those photos are stored privately and served through signed URLs — never raw, guessable bucket links — so a job's documentation is both findable and protected. Combined with the on-site notes and mobile work order detail, the job record becomes a complete, defensible account of what happened.
Build the habit into the workflow
Techs won't photograph jobs because you told them to once. They'll do it when it's frictionless and expected:
- Make it a step, not a chore. Arrival photo, work-in-progress photo, completion photo — three taps built into how a job moves.
- Tie it to completion. A job isn't done until it's documented. When photos are part of marking a job complete, coverage takes care of itself.
- Show techs the payoff. When a photo kills a chargeback or books a follow-up, tell the team. Behavior follows visible wins.
What to measure
- Photo coverage rate — share of jobs with at least a before and after. Low coverage is a dispute waiting to happen.
- Dispute resolution time — how fast a billing or quality complaint closes. Good photos collapse it.
- Follow-up conversion from documented issues — work booked off problems a tech photographed but didn't fix that day.
The job is finished when the truck leaves. The record of the job is what protects your money and earns the next one — and a structured photo is the smallest effort with the biggest return in all of field service.