Skip to content
← Blog

Construction Photo Documentation: What Actually Holds Up

/ 5 min read

Ask any contractor who has been through a payment dispute: the job was fine until it wasn’t, and then suddenly everything depended on what you could prove. The change order the client “never approved.” The wall that was “already damaged.” The work that was “never finished.”

Photos settle these arguments - but only if they were taken the right way. A camera roll full of undated, unlocated images is barely better than nothing. Here is what actually holds up, and the tools that make it automatic.

The Three Things a Site Photo Must Prove

A useful documentation photo answers three questions at a glance:

  1. What - the subject is clear, in focus, with enough context to recognize the location within the site
  2. When - the date and time are visible in the image itself, not just buried in metadata
  3. Where - GPS coordinates or an address tie the photo to the physical site

The “visible” part is not pedantry. Photo metadata (EXIF) is editable by anyone with the Photos app, and messaging apps strip it anyway when you send the photo to a client or adjuster. A timestamp burned into the image is what people accept at face value, because it was put there at the moment of capture.

If you want the full breakdown of visible stamps vs. metadata, I wrote up how to add timestamps to iPhone photos separately.

The Habits That Matter More Than the App

Tools help, but the routine is the actual system:

Shoot before, during, and after. The before photos are the ones everyone forgets and everyone needs. Existing damage, site conditions on day one, what was behind the wall before you closed it.

Wide shot first, then details. A close-up of a pipe joint proves nothing if no one can tell which building it is in. Establish context, then zoom.

Photograph what gets covered up. Wiring, plumbing, waterproofing, rebar - anything that disappears behind drywall or concrete should be photographed minutes before it does.

Same angle for before/after pairs. Stand in the same spot. The comparison does the persuading for you.

Do it daily, not “when something happens.” By the time something happens, it is too late to photograph how things were.

Solo Contractor vs. Team: Two Different Problems

If you run crews across multiple projects, you eventually want a team platform - shared project folders, who-took-what accountability, integrations with project management. CompanyCam is the best-known name in that space. These tools are priced per user per month, which is fair for a company and overkill for one person.

If you work solo or with one helper, the problem is simpler: you need every photo you take to be stamped, organized, and ready to drop into an invoice or a text to the client. You do not need seats, logins, or a sync server. A stamp camera on your own phone covers it.

That second case is what SnapProof is built for. You shoot through the app and every photo comes out with the date, time, GPS coordinates, and street address printed on it. A map view shows where each photo was taken, which doubles as a per-site filter when you are digging for last month’s photos. There is also batch stamping for photos already in your library, using their original capture data.

It works offline, which matters on job sites more than app developers seem to think - basements, rural lots, and concrete shells are exactly where documentation happens.

What About Just Using the Camera App?

You can, and plenty of people do. The iPhone records date and location metadata on every shot. The problems show up later:

  • Metadata is invisible when the photo is viewed, printed, or attached to a report
  • Sharing through WhatsApp, Messenger, or email strips it entirely
  • Anyone can edit it after the fact, which is why it convinces nobody
  • Finding “all photos from the Hendersons’ renovation” in a 15,000-photo library is its own project

The built-in camera is fine for taking the photo. It does nothing for the proving part, and the proving part is the entire reason you are photographing a job site.

A Simple Documentation Workflow

  1. Arrive on site → 3-5 wide shots of current conditions, stamped
  2. Before starting any task that covers something up → photograph it
  3. End of day → quick walk-through set, 2 minutes
  4. Change requested? → photo of the area + a text to the client referencing it
  5. Job done → final set, same angles as your day-one photos

Thirty photos a week, all stamped and mapped, costs you maybe ten minutes. The first dispute it ends pays for the habit forever.

FAQ

Are timestamped photos accepted as evidence? Visibly stamped photos taken at capture time are routinely used in insurance claims and payment disputes. No photo is automatically “legal proof,” but a stamped photo with GPS beats an unstamped one in any practical argument.

Can I stamp photos I took last month? Yes. Batch stamping reads each photo’s original EXIF date and location and prints those. Just know that after-the-fact stamps inherit whatever the metadata says; stamping at capture is the stronger story.

Do I need a signal on site for GPS stamps? No. GPS works without cell service. The address lookup may catch up when you are back online, but coordinates are recorded at capture.

iPhone or a dedicated camera for site photos? The camera you always have wins. A phone with a stamp camera app produces better documentation than a nicer camera whose photos sit unstamped on an SD card.