Three weeks after a water heater swap, the customer calls. The ceiling below the utility closet has a stain, and they say your tech caused it. The same week, a different customer disputes a card charge, saying the capacitor on their bill was never replaced. Your techs did take photos. They're on four different personal phones, mixed in with vacation pictures, and nobody can find the ones that matter. Field service photo documentation only works if the right photos exist and you can find them in 30 seconds. Here's what to shoot, how to make it hold up, and how to get techs to actually do it.
The three arguments photos settle
Almost every job dispute is one of three arguments:
- "You never did it." The part wasn't replaced, the drain wasn't cleared, the inspection didn't happen.
- "You broke it." Stains, scratched floors, cracked tile, damaged drywall.
- "You charged for work I didn't need." The repair wasn't necessary, or the problem wasn't that bad.
A good photo set answers all three before anyone asks. The first argument needs proof of the work. The second needs proof of the property's condition before you touched it. The third needs proof of the problem you found.
Why it matters when a customer disputes the charge
Card disputes follow the same pattern. Stripe's dispute guidance says that, after fraudulent disputes, other high frequency dispute reasons include claims that a product or service wasn't delivered, was defective or unsatisfactory, or wasn't as described. Its advice for those cases: provide proof of service or delivery.
Two details in that guidance matter for contractors:
- The fee applies even if you accept the dispute. Stripe notes that a dispute fee still applies if you accept it rather than fight it.
- Winning doesn't erase the dispute. Stripe says the card networks don't consider how many disputes you win or lose, only how many you receive. The best photo set is one that prevents the dispute, because the customer saw the photos on the day of the job.
The field service photo documentation shot list
Keep it short enough that techs will do it every time. Five to eight photos covers most service calls.
On every job
- Arrival: a wide shot of the work area before you touch anything. This is your answer to "you broke it."
- The problem: the failed part, leak, clog or reading. Get close enough to see it.
- The nameplate: model and serial number of the equipment you worked on.
- After: the finished work, from the same angle as the arrival shot if you can.
- Clean-up: the work area as you left it.
When they apply
- The old part, next to the new one, before the old one goes in the truck.
- Readings: gauges, meters, pressure tests and temperature splits. A photo of the reading beats a number typed into a notes field.
- Anything about to be covered. Pipe inside a wall, wiring behind a panel, a fitting under insulation. Once it's closed up, the photo is the only proof.
- Pre-existing damage. A stain, a crack or corrosion you didn't cause. Photograph it and point it out to the customer before you start.
- Deficiencies found. Anything you recommend fixing, with a clear shot of why. Our guide to managing fire inspection deficiencies covers turning those into approved work.
What that looks like by trade
The categories stay the same, but the shots that matter most change with the work. On an HVAC call, it's the data plate, failed capacitor or contactor next to its replacement, and gauge readings after the repair. On a plumbing call, it's the shut-off before you start, any existing water damage, the joint before the wall closes, and the fixture running afterward. On a fire protection inspection, it's each deficiency with its location, the tag or label on the device, and the corrected condition when you come back.
What makes a photo hold up later
A photo is only useful if it can be tied to a specific job, a specific time and a specific person. That means:
- Attached to the job, not sitting in a camera roll. Photos on a tech's personal phone leave when the tech leaves.
- Tied to the equipment, so next year's tech can find this year's photos. A nameplate shot in the job makes the unit easy to match.
- Recorded with who added it and when, by the system rather than typed by hand. Know what your system records. Many apps log when a photo was uploaded, which isn't always when it was taken, especially for photos taken without signal and uploaded later.
- Captioned when it isn't obvious. "Pre-existing stain, pointed out to homeowner at 9:10" is worth more than the photo alone, and a caption is the right place for the time if it matters.
- Shown to the customer. A photo the customer saw on the day of the job rarely gets disputed later.
A note on privacy: photograph the work, not the people or the home's contents. Avoid faces, family photos, mail and screens. If a photo has to include something personal, crop it before it's shared. Customers notice when a tech is careful about this, and it's one more reason they'll trust the photos you do take.
Getting techs to actually take them
Techs don't skip photos because they're lazy. They skip them because it's slow, the app is clumsy, or nobody ever looks at the photos.
- Make photos part of the job, not a separate app. Set the expectation that the arrival and after shots are taken before a job is closed, and check for them when you review closed jobs.
- Keep the required list short. Require three: arrival, problem and after. Recommend the rest.
- Make it work offline. Basements, attics and mechanical rooms have no signal. If photos fail there, techs stop trying.
- Use the photos. Show a good photo set in the weekly meeting. When a photo wins a dispute, tell the whole team.
- Never use photos only to catch techs out. If photos only show up when someone's in trouble, techs will stop taking them. Photos that protect techs from false claims are one of the few kinds of documentation they'll thank you for. It matters for retention too; see the operational reasons technicians leave.
Give it a month. The first time a tech's arrival photo shuts down a "you broke it" call, the rest of the team stops seeing photos as paperwork.
Photos do more than settle disputes
Good field service photo documentation pays off in other places too:
- Quotes: a photo of the corroded valve sells the repair better than a description.
- Maintenance reports: members who see what you checked are more likely to renew. See our guide to raising your service agreement renewal rate.
- Training: your best tech's photo sets show new techs what "done right" looks like.
- Warranty claims: manufacturers often want a photo of the failed part and nameplate.
Where FSM Navigator fits
In the FSM Navigator mobile app, techs take photos and attach them to the job, next to their notes. Photos stay with the job, not in a camera roll, so the office can find them the day a customer calls. Each photo is recorded with who uploaded it and the upload time.
- Offline-first. Photos taken in a basement with no signal are saved on the phone and upload when the connection comes back.
- Photos on the invoice. The office can choose which job photos go on the invoice, so the customer sees the proof with the bill.
- Photo limits. Pro includes up to 10 photos per job, and Enterprise up to 20.
- Required shots as a closing habit. Make arrival and after photos part of how every job gets closed, and spot-check the jobs that closed without them.
Set your three-photo standard on next week's jobs, and see how many arguments never start.