The Job Photo and Documentation SOP

Purpose

Define the standard photos and notes captured on every job. A standard operating procedure (SOP) is the written, repeatable process everyone follows the same way, so a job's record does not depend on which tech remembered to take pictures. Job photos are the cheapest insurance a shop carries. They settle a "you broke that" dispute, they justify the work to a customer who was not on site, they support a warranty or insurance claim, and they let the office spot an incomplete job before the customer does. A tech who documents consistently protects the shop; a tech who documents when he feels like it leaves gaps exactly where a dispute will land.

Scope

Applies to every service and installation job:

  • Repair, maintenance, and installation visits
  • Warranty and callback visits
  • Any job where a pre-existing condition could later be blamed on the shop

Excludes purely administrative visits with no physical work. When in doubt, document.

Roles and responsibilities

Role Responsibility
Technician Captures the required photos and notes, attaches them to the job
Office / QA Verifies documentation is complete before the job is closed
Manager Spot-audits records, coaches gaps in the field

Procedure

Step 1: Shoot the "before" set on arrival

Before touching anything, capture the starting condition:

  • A wide shot showing the work area and its surroundings
  • A close shot of the specific problem or the unit being worked on
  • Any pre-existing damage near the work area (a scuffed floor, a cracked tile, a dinged wall)

The pre-existing-damage shot is the one that saves the shop. If the customer later claims the tech caused it, the timestamped arrival photo settles it.

Step 2: Capture concealed conditions during the work

Photograph anything that will be hidden when the job is done:

  • Conditions behind a wall, under a unit, or inside an access panel
  • A part that was failed or damaged before replacement
  • The reason for any scope change or added work

Once the panel is back on, the only proof the condition existed is the photo. This is where a change order gets justified and where a warranty claim gets its evidence.

Step 3: Record identifying data

Capture the details the office and future techs will need:

  • Model and serial numbers of equipment worked on
  • Meter, gauge, or measurement readings taken
  • Settings or configurations changed

A legible photo of a nameplate beats a hand-copied number that turns out transposed.

Step 4: Shoot the "after" set at completion

Document the finished work from the same angles as the before set. The matched before-and-after pair is what makes the work visible to a customer who never saw the problem and never saw the repair. Include a shot showing the area cleaned up.

Step 5: Write the job notes

Photos show what; notes explain why. In plain language, record what was found, what was done, what was recommended but declined, and anything the next visit should know. Notes written on site are accurate; notes reconstructed that night are guesses.

Step 6: Attach everything to the job record before leaving

Photos and notes go on the correct job record while still on site, not into a phone's camera roll to be sorted later. A photo that never gets attached does not exist when a dispute arrives six weeks on. Confirm the upload before driving away.

Step 7: Office verifies at closeout

Before a job is marked complete, the office confirms the required documentation is present: before set, after set, identifying data, and notes. A job missing its documentation goes back to the tech, not into the closed pile.

Records and retention

Keep job photos and notes for the life of any warranty on the work and long enough to cover a dispute or claim window. They are part of the permanent job record, not disposable.

Common documentation failures

  • No pre-existing-damage shot. The shop eats a repair it did not cause.
  • No concealed-condition photo. A change order or warranty claim has no proof.
  • Photos stuck on the tech's phone. Unattached, they are useless when needed.
  • Notes written from memory hours later. Details are wrong exactly when accuracy matters.

References

  • Trade-standard practice for job documentation and dispute prevention
  • Insurance and warranty claim documentation requirements
  • See related: The Quality Check Before Closeout SOP
  • See related: Customer Property Damage Protocol