Field Photo Documentation Standards for Service Technicians
A photo can settle a scope question, explain a recommendation, or make a return visit faster. It can also become an unusable camera roll of dark, duplicate images. The difference is a field-photo standard: a small set of images taken at defined points in the job, named by their purpose, and reviewed before the technician leaves.
Start with the decisions the photos need to support. A technician, dispatcher, estimator, manager, and customer do not need every image for the same reason. Define the minimum views that show the reported condition, the affected location, the completed work, and any remaining exception. Keep the standard short enough to use during a busy day.
Use a before, context, and after sequence. The before photo documents the specific condition. The context photo shows where that condition sits in the property or equipment. The after photo shows the final result. For a condensate repair, that could mean the damaged line, a wider equipment-area view, and the repaired connection. A close-up alone often cannot prove location or scope.
Make required views service-specific. A plumbing leak investigation and a panel upgrade do not need the same checklist. Give each common job type a compact set of required angles, then let the technician add evidence for unusual conditions. Avoid a universal rule such as take lots of photos. It produces volume without answering what the next person needs to know.
Capture usable evidence, not just activity. Check focus, lighting, orientation, and whether the image includes the relevant component. Do not photograph personal documents, access codes, or occupants unless your policy and necessary permissions support it. If a safety concern or concealed condition needs a photo, record a concise note that explains what the viewer is seeing rather than relying on a filename alone.
Tie photos to the right job record. In Joby, keep job-specific files and notes with the lead and appointment context so the office can locate them alongside the customer conversation and related estimate. This is a recordkeeping workflow, not a claim that every image is automatically classified or that a photo alone authorizes additional work. The team still decides what should be shared and what requires approval.
Separate evidence from customer-facing communication. A technician may need ten detailed photos to document a failed component, while a customer may need two clear images and a plain-language explanation. Select the appropriate set through your established communication process. Before sending, make sure the image supports the claim being made and does not expose another customer's property or sensitive information.
Add the photo check to the closeout routine. Before changing the job to the next internal stage, ask: Do we have the required before and after views? Is the exception documented? Does the estimate or work summary match the images? A dispatcher can return a missing-evidence request while the technician is still nearby instead of discovering it during an invoice dispute days later.
Use photos to improve estimate handoffs. When an onsite technician identifies work for a sales or estimating follow-up, provide one overview, one condition detail, relevant measurements where appropriate, and a factual note about what was observed. Do not make the image package substitute for a scoped estimate or customer approval. It simply gives the next owner a clearer starting point.
Review a small sample each week. Pick recent completed jobs from different service types and score whether a new team member could understand the condition, location, completed work, and exception without calling the technician. If the missing piece is usually context, change the checklist. If the images are often dark, adjust the field coaching and equipment guidance.
The goal is not more photos. It is reliable visual evidence at the points where your team makes decisions. A simple standard, attached to the right Joby record and checked before closeout, turns routine field images into a usable part of the service history.
