Photo documentation that protects you in a dispute

What makes a photo count as evidence

A photo by itself proves something existed. A photo that holds up in a dispute proves when, where, and on what job it existed — and that it has not been altered. Three properties separate a useful evidence photo from a snapshot anyone could wave away.

• A trustworthy timestamp. The single most contested fact in a construction dispute is when. A photo dated to the day removes the argument before it starts. A photo with no reliable date is just a picture.
• Location and job context. Metadata that ties the photo to the jobsite and the specific job answers "is this even the right project?" — a question opposing parties raise constantly.
• An unbroken, attributable record. Evidence is stronger when it is clear who took it, that it has not been edited, and that it sits in a system rather than a personal phone where photos can be deleted, re-saved, or re-dated.

Timestamps and metadata: the technical backbone

Every digital photo carries embedded metadata (EXIF) — the date, time, and often the GPS coordinates the device recorded at capture. This is the backbone of photo evidence, and it is also fragile: forwarding a photo through a text thread, screenshotting it, or downloading and re-saving it can strip or reset that metadata, leaving you with an image that has no provable date.

That fragility is why "I have it on my phone" is weaker than it sounds. By the time a photo has been texted to the office, saved, and emailed to a lawyer, its original capture data may be gone. The strongest position is photos captured into a system that records the timestamp at the moment of capture and preserves it independently of the device — so even if the original phone is lost or the EXIF is stripped in transit, the record of when the photo was taken survives.

Chain of evidence: keep the record intact

Lawyers talk about "chain of custody" — being able to show that evidence is what it claims to be and has not been tampered with from capture to courtroom. Contractors do not need a forensic process, but the principle applies: the more your photos look like an unbroken, contemporaneous record, the more weight they carry.

• Capture contemporaneously. A photo taken the day the work happened is far stronger than one produced months later. A continuous record across the job reads as honest; a handful of photos appearing only after a dispute starts reads as manufactured.
• Keep the originals. Do not rely on a screenshot or a forwarded copy. The original, with its capture data, is the evidence; everything downstream is a degraded copy.
• Centralize and lock down. Photos sitting in one system the company controls — rather than scattered across personal phones — are harder to dispute as cherry-picked or altered, because the full set is intact and attributable.
• Pair photos with written logs. A photo plus a same-day daily log entry describing the work corroborate each other and form a much stronger record than either alone.

Change orders: the dispute you can prevent

The most common and most preventable dispute is the change order — extra or different work the contractor did but cannot get paid for because there is no proof it was authorized or necessary. Photos turn a "he said / she said" into a documented fact.

The pattern that protects you: when a condition arises that requires a change — rotted subfloor revealed at demo, a code issue, a client request — photograph it immediately, before you do anything about it. That dated photo of the discovered condition, paired with a written change order, shows exactly why the extra work was needed and when it was found. Without it, you are arguing that an invisible, already-fixed problem justified a charge. With it, the photo makes the case for you.

• Photograph the unexpected condition the moment it is discovered, before remediation.
• Capture enough context (wide and tight) to make the problem obvious to someone who was never on site.
• Tie the photo to a written change order describing the work, the reason, and the cost.
• Keep the dated photo with the job so it surfaces immediately if payment is later questioned.

Beyond disputes: warranty, insurance, and inspections

The same documented record that wins a dispute also defends you in three other situations. For warranty callbacks, photos of how something was actually built rebut claims of defective work — or confirm a problem is outside your scope. For insurance, dated photos of conditions and damage support claims and counter claims that damage was pre-existing or caused by someone else. For inspections, photos of covered work (rough-in plumbing, framing, wiring) prove compliance after the wall is closed. Document once, well, and the same record serves all of these.

Step by step

1. 1

   Document pre-existing conditions before you start

   Photograph the site before any work — dated and tied to the job — so you can prove what you did and did not cause.

2. 2

   Capture conditions the moment they arise

   When something unexpected appears (rot, a code issue, damage), photograph it immediately, before remediation, wide and tight.

3. 3

   Pair photos with written records

   Tie each significant photo to a same-day daily log entry or a written change order so they corroborate each other.

4. 4

   Preserve originals with their metadata

   Capture into a system that records and preserves the timestamp at capture — do not rely on forwarded or screenshotted copies that lose their date.

5. 5

   Centralize into one controlled record

   Keep the full photo set in one workspace the company controls, attributable and intact, rather than scattered across personal phones.