Before-and-after photos help prove condition, scope and completion. But folders named by date, photos buried in text messages and uploads that fail without warning create a second documentation job at the end of the day.
The five parts of defensible job photos
1. A required shot list
A restoration job and an HVAC service call do not need the same evidence. A reusable job pack tells the technician which wide, detail, serial-number and completion photos are still missing.
2. Capture context
The record should connect the original file to the job, step, author, device time and optional location. Later annotations should not overwrite the original.
3. A visible upload receipt
The crew needs to know whether each photo is saved locally, queued, uploaded or rejected. A thumbnail alone does not prove the server has the file.
4. Approval beside the evidence
When scope changes, the customer should see the relevant photos and explanation before approving. The decision then stays attached to those facts.
5. A portable job pack
The office, customer, insurer or bookkeeper may need different exports. FieldProof plans a structured timeline and a human-readable PDF rather than a locked gallery.
Designed for evidence, not surveillance
Job documentation should capture the work required by the job. It should not become continuous worker tracking. Pilot teams will help define sensible defaults for location, retention, redaction and customer consent.