A practical seven-point checklist for construction photo evidence that holds up in lender draws, insurance claims, OSHA reviews, and subcontractor disputes. What every photo needs, what most miss, and how to fix it.

A construction photo is not just a picture. It is a financial instrument. It releases lender draws. It settles change orders. It defends against subcontractor claims. It satisfies OSHA inspections. It backs up insurance loss reports. The difference between a photo that does these things and one that does not is a few seconds of setup at capture time.

Here is the seven-point checklist that turns a shoebox of jobsite photos into a defensible record.

1. Date and time, visibly stamped

Every photo needs the date and time rendered into the visible pixels. EXIF metadata is not enough. Cloud platforms strip EXIF. PDF exports lose it. Screenshots erase it. Once the date is missing, the photo proves nothing about when work was done.

Visible stamps survive everything: Procore, PlanGrid, Dropbox, email attachments, PDF job packets, screenshots a paralegal takes during discovery. If you can see the date on the image, the date is part of the proof.

The cheapest fix: take photos with a stamp camera app on your iPhone. The TimeStamp Camera iOS app renders the date and time as part of every shot, with no extra step.

For photos already taken without a stamp, the browser stamp tool reads EXIF date from the file and renders it as visible text. Drop a folder, get back a ZIP of stamped JPEGs.

2. GPS coordinates and site address

Date alone is half the answer. The other half is location. A photo of foundation prep on the wrong lot, a punch-list item attributed to the wrong unit, or a damage photo with no street address is the kind of detail a defense attorney builds an argument around.

Render the GPS coordinates and the site address into the visible image. Coordinates are precise. The address is human-readable. Both together remove every ambiguity about where the photo was taken.

The same tools handle this. The iOS app captures GPS at the shutter and reverse-geocodes to a street address (works offline; address fills in once back on signal). The web tool reads the GPS from EXIF or accepts manual entry.

For photos without GPS (screenshots, scanned blueprints, photos from cameras with location off), enter the coordinates manually. Get them from Google Maps: right-click the spot, pick What's here, copy the lat/lng.

3. Project or job tag in the stamp

A photo with a date and a GPS coordinate but no context still requires explanation later. "What project is this?" "Which unit?" "Whose claim?"

Add a free-text label to the stamp: project name, lot number, change order ID, claim ID, technician name. Whatever string makes the photo self-describing without a separate spreadsheet.

Stamp camera apps treat this as a "job note" or "label" field. Set it once at the start of the shift, every photo for that shift carries the same label, you swap it when you move to the next site. The label becomes part of the visible image.

Three benefits compound:

Filter and search. Anyone who has the photo file can find others from the same job by reading the label.
No cross-contamination. Photos from two jobs taken the same day cannot get confused.
Subcontractor accountability. Tag photos with the subcontractor's name. When a warranty issue surfaces three years later, the responsible party is on the photo.

4. Atomic time, not device clock

This one is technical but it matters in disputes. Phone and camera clocks drift. Timezone settings get accidentally changed. A device in airplane mode for a few days can come back with the clock off by minutes. In rare cases, a tampered device can have its clock set arbitrarily.

A photo whose timestamp came from a device clock can be plausibly disputed. A photo whose timestamp came from a network-synchronized atomic clock at the moment of capture is much harder to dispute, because the time was set by an external source the photographer did not control.

The TimeStamp Camera iOS app pulls atomic time from network time servers at every shutter press. The visible stamp is then the actual real-world time, not the device's guess at the time. For court, audit, and insurance use, this is the difference between "it could have been faked" and "it would have required cooperation from the NTP infrastructure."

5. Originals alongside stamped versions

Stamped photos are for sharing. Original files are for chain-of-custody. Always keep both.

A typical workflow:

Original JPEG/HEIC saved to originals/2026-05-14/site-A/
Stamped JPEG saved to stamped/2026-05-14/site-A/
Both backed up to cloud the same day

The stamped photo is what you upload to Procore, attach to a draw request, send to the insurance adjuster, or print into a punch-list packet. The original is what you keep in case anyone questions whether the visible stamp matches the underlying EXIF data. They almost never look. When they do, you want both files in the same place.

The browser stamp tool does this automatically: the input file is unchanged on your machine, and the output is a new file. The iOS app saves both the stamped image and the original to your camera roll.

6. Two backup destinations, same day

A jobsite phone that ends a shift in a porta-pot is a story every contractor has heard. The photos that were on it are gone forever. Insurance does not refund a billable day of documentation lost to a phone.

End every workday with photos in two places. Pick whichever pair fits your workflow:

iPhone + iCloud Photos (automatic, requires storage plan)
iPhone + Dropbox / Google Drive (manual upload, app handles sync)
iPhone + AirDrop to office Mac (in-house sync at end of day)
iPhone + USB to office workstation (slow but free)

The principle is two destinations, not one. iCloud alone is not enough. Local backup alone is not enough. Two destinations means a single hardware failure or single account lockout does not erase a week of work.

For Pro accounts on the iOS app, end-of-day batch upload to a configured destination runs automatically.

7. Weekly audit of a sample

Once a week, pick five random photos from the past seven days and check:

Date and time visible: yes / no
Date and time correct: yes / no
GPS coordinates and address visible: yes / no
GPS plausible (matches the actual jobsite): yes / no
Project tag correct: yes / no

This catches drift before it becomes a problem. Stale GPS cache (the camera app reused yesterday's location). Timezone changes after travel. A junior team member forgetting to set the project tag. Misconfigured stamp position cropped out of social shares. Five photos a week, five minutes total, prevents the discovery of a month's worth of broken records.

Defensible vs non-defensible photo records

Two photos of the same jobsite, taken on the same day, can have very different weight in a dispute.

Defensible	Non-defensible
Visible date, time, GPS, address, project tag	Just the image
Atomic time, not device time	Device-clock time only
Original file preserved alongside	No original to compare against
Backed up the same day to two destinations	Only on the phone, undated
Verifiable via EXIF viewer that EXIF matches visible stamp	EXIF stripped, no second source

For lender draws, change order disputes, OSHA review, and insurance claims, the left column wins. The right column gets argued away.

Common mistakes that kill a photo record

Relying on EXIF only. Cloud uploads strip it. PDFs lose it. The first time someone asks for a printed packet, the date is gone.

Using the device clock without network sync. A phone that drifted by 12 minutes during a week of poor signal produces 200+ photos with the wrong timestamps. Every one becomes contestable.

Skipping the project tag because it is "obvious." It is obvious to you on the day of capture. It is not obvious to the paralegal three years later, or to the junior PM who took over the file six months ago.

Stamps in the corner that get cropped out by Instagram. If the stamp is at the extreme edge, social-media crops eat it. Place stamps at about 3% of the image height in from the bottom-left or bottom-right. That position survives both 4:3 and 1:1 crops.

Saving stamped versions over originals. Once the original is gone, you cannot verify that the stamp matches what the camera actually wrote. Always keep both files.

No backup until end of week. A phone lost on a Wednesday loses three days of work. Daily backup is cheap. End-of-week backup is a gamble.

When this checklist pays for itself

This level of discipline is overkill for personal photos. It is exactly right for:

Lender draw packages. Banks want photo evidence that stages of construction are complete before releasing the next tranche. Photos with date, GPS, and project tag are the proof that gets the draw approved.
Subcontractor disputes. When a sub claims work was completed and you remember it differently, the photos with verifiable timestamps end the argument fast.
Insurance claims. Adjusters love unambiguous evidence. A claim file with stamped photos closes faster than one with bare iPhone snaps.
OSHA inspections. Required postings, equipment condition, training records: every documentation requirement benefits from time-and-place-stamped photo proof.
Warranty issues years later. A roof complaint in 2030 pulls up the 2026 installation photos. If the photos have date, GPS, and the installer's name on them, you have an answer in five minutes. If they do not, you have a problem.
Defect claims and post-completion litigation. The cheap insurance against a multi-year legal headache is a defensible photo record from day one.

The cost is a stamp camera app and 30 seconds of setup. The benefit is a photo record that does its job under pressure.

Construction Site Documentation: Photo Evidence Checklist for Contractors