Document by Photo vs Video vs Written on a Liability Job Decision Matrix

Why this matters

On a routine job, a couple of photos and a clean invoice are enough. On a liability job, the one where pre-existing damage, a safety hazard, a disputed condition, or a high-dollar outcome is in play, the documentation you capture is the difference between a defensible position and your word against theirs. The medium matters: a photo proves a static condition, a video proves a sequence or a function, and a written note proves what was said, agreed, or refused. Choosing the wrong medium leaves a gap exactly where a dispute will land.

Good documentation is not about volume. It is about capturing the specific fact a future dispute will turn on, in the medium that actually proves it, before you touch anything. The tech standing in front of the condition is the only person who can capture it; once the truck leaves, the evidence is gone.

The situation

A tech arrives at a job carrying elevated risk: visible pre-existing damage near the work area, a customer already unhappy, a hazardous condition, a high-value asset, or a scope where the outcome could be contested. Before and during the work, the tech and dispatcher decide what to capture and how. The aim is a record that answers the question a dispute will ask, not a generic photo dump.

What is at stake

The downside of under-documenting a liability job is direct: a damage claim you cannot rebut, a "you broke it" accusation with no before-state, a safety incident with no record that you flagged it. The downside of over-documenting is small but real: wasted time and a customer who feels surveilled. The matrix routes effort to the cases and media that pay off.

Decision factors

• What fact will the dispute turn on? A condition (static), a function (dynamic), or an agreement/refusal (verbal). This drives the medium.
• Pre-existing damage exposure. Visible prior damage near your work area means a photographed before-state is mandatory.
• Reversibility. Once you cut, drain, demo, or energize, the prior state is unrecoverable. Capture before, not after.
• Customer posture. An already-frustrated or litigious-sounding customer raises the documentation bar across the board.
• Asset value and safety stakes. High-value or safety-critical work justifies video and written sign-offs that a small job would not.
• Who needs to read it later. An insurer, an adjuster, or a court reads differently than your own crew; written context turns raw media into evidence.

The decision: options and when each wins

Photos win when the fact is a static condition: pre-existing damage, a code violation, a serial/model plate, a meter reading, a finished result. Shoot wide for context, then close for detail, and capture the same angle before and after. Timestamp and geotag if your system supports it. Photos are the workhorse and belong on nearly every liability job; the question is what else to add.

Video wins when the fact is dynamic or sequential: a function test (it ran, it leaked, it would not start), a customer walkthrough where you point out and narrate conditions, an operation that a still cannot prove (a moving part, a flow, an alarm sounding). A 30-second narrated clip of "here is the crack that was already here, you can see it predates our work" is far stronger than three silent photos. Use video when the dispute will be about behavior, not just appearance.

Written wins when the fact is verbal: a customer authorized extra scope, declined a recommended repair, acknowledged a pre-existing condition, or accepted a known risk. Photos and video cannot prove consent or refusal. A signed change order, a noted-and-acknowledged decline, or a dated note in the record carries the agreement. On the highest-stakes jobs, combine all three: photograph the condition, narrate it on video, and capture the written acknowledgment.

What to document

• A before-state of any pre-existing damage in or near the work area, photographed before work starts.
• The specific condition the job's risk centers on, in the medium that proves it.
• Any customer authorization, decline, or acknowledgment in writing, dated and ideally signed.
• Function tests as video where behavior is contestable.
• The finished state from the same angles as the before-state.
• Tech name, date, and job number attached to every file so the chain of custody is clear.
• A short written caption on each key file naming what it shows and why it was captured, so raw media reads as evidence to an adjuster or court rather than an unlabeled image.

Store the media against the job record, not a personal phone. Evidence that lives on a tech's camera roll and gets deleted at the next phone upgrade is no evidence at all when the claim arrives a year later.

References

• OSHA recordkeeping requirements, 29 CFR Part 1904 (incident and hazard documentation obligations for safety-related conditions).
• Federal Rules of Evidence 901 and 1001-1004 (authentication of photographs/recordings and the original-evidence rules that govern admissibility).
• Insurance Information Institute and property-claim adjuster guidance on contemporaneous photo/video documentation of pre-existing vs new damage.
• IICRC and trade-association best-practice guidance on before/after documentation for jobs involving water, fire, or structural damage.