# GPS Photo Evidence: A Contractor's Guide

> How to use GPS-stamped photos as field evidence: what makes a record defensible, what to keep, and the workflow that wastes the least time.

*Published: 2026-04-04* · *4 min read*

Canonical URL: https://timestampcamera.net/photo-guides/gps-photo-evidence-a-contractors-guide


**Quick answer:** Photos beat memory and beat invoices in contractor disputes. To make a field photo hold up, capture with a GPS camera app that burns the date, time, GPS coordinates, and project tag visibly onto the pixels (so the evidence survives social uploads that strip EXIF), preserve the original file untouched, keep a daily backup in two destinations, and never edit or rename a file you might need to reference in a claim. The full playbook below.

If you're a contractor, an adjuster, or anyone whose work product ends up
in a dispute, photos are your cheapest and most powerful evidence. They're
also the most commonly misused: wrong dates, no location, the file
modified after the fact, or stripped of metadata on upload.

This is a short, practical guide to making field photos hold up.

## What "defensible" actually means

You don't need a court-quality forensic chain to win an argument with an
owner, a sub, or an insurance carrier. You need three things:

1. **A timestamp that wasn't drawn from a phone clock you control.** Atomic
   (network-synced) time at capture eliminates "your clock was wrong" as a
   defense.
2. **A location that anyone can verify.** Coordinates plus an
   address, visible on the image, not just hidden in EXIF that gets
   stripped on upload.
3. **An original file you didn't touch.** Stamp a copy. Keep the original.
   If anyone asks, you produce both.

Most disputes end at step 2: the other party sees a photo with date, time,
and address baked in, and the conversation moves on. The third only
matters in formal proceedings.

## A workflow that holds up

For a small crew, this is the minimum:

- **Capture with a GPS camera app.** The
  [iOS app](https://apps.apple.com/us/app/timestamp-camera-gps-photo/id6760574630)
  on this site writes the stamp into the pixels at the moment of capture.
  Atomic time, not device time. GPS even when offline.
- **Use a per-photo job note.** Project name, unit, room, defect type:
  whatever turns "a photo" into "a record." On TimeStamp Camera, this is
  the *Job note* field.
- **Don't edit the originals.** If you need to crop, rotate, or annotate,
  do it on a copy. Originals stay untouched.
- **Back up daily.** Cloud storage with versioning. Dropbox, Google Drive,
  iCloud: any with version history. If a photo's metadata is ever
  questioned, you can show the original, untouched copy.

For a larger operation that needs to prove anything formally, add:

- **A second clock.** Take one photo per visit of a network-time source
  (e.g. a quick screenshot of `time.is`) along with the field photos. Cheap
  cross-reference.
- **Per-trip exports.** End-of-day, batch-process the day's photos through
  the [web tool](/#web-tool): same stamp settings, all photos consistently
  labeled. Useful for owner packages and lender draws.
- **A retention policy.** Decide how long you keep originals (one project
  cycle? seven years?) and stick to it.

## Common mistakes

**Relying on EXIF GPS.** Most platforms strip EXIF on upload. The photo on
the carrier's portal may have no GPS at all even though your original did.
Always render a visible stamp.

**Cropping out the stamp.** Don't crop the timestamp out of a photo before
sending it. If you must crop, crop a copy and keep the original.

**Using the same coordinate for the whole day.** Some apps cache GPS to
save battery. Take a fresh GPS read per photo, especially when moving
around the site. The TimeStamp Camera iOS app re-acquires per-shot.

**Storing originals on a single device.** If the phone is lost, replaced,
or wiped before backup, the evidence is gone. Cloud sync the camera roll.

**Trying to "fix" a date later.** EXIF date editing tools exist, but
editing the date on a photo *after* a dispute starts is the worst possible
move. Don't. If a photo's date is wrong, write a memo explaining why; the
honest answer is much stronger evidence than a clean-looking edit.

## Adjuster perspective

If you ever talk to a property adjuster about photo evidence, the common
sentiment is: *the date and address on the image, plus an unmodified
original, ends 90% of conversations.* Photos with conflicting timestamps,
missing locations, or evidence of editing extend the conversation,
sometimes for weeks.

This is the same reason carriers themselves are starting to require
GPS-stamped photos for catastrophe deployments: it cuts settlement time and
fraud risk in roughly equal measure.

## The 30-second checklist

Before you put a phone down at the end of a workday:

- [ ] Every photo from today is in the cloud (originals, not just edits).
- [ ] Every photo carries date, time, and a visible GPS stamp.
- [ ] Per-photo notes (unit, defect, claim ID) are on the photos that need
      them.
- [ ] No photo has been cropped or edited from the original.
- [ ] If any photo's date or location looks wrong, you've written a one-line
      note explaining why.

That's the entire system. The tools you use are less important than the
discipline, but the right tools make the discipline cheaper.

---

Related reading:

- [How to add GPS coordinates to a photo (iPhone, Android, Web)](/photo-guides/how-to-add-gps-coordinates-to-a-photo)
- [How to read EXIF metadata](/photo-guides/how-to-read-exif-metadata)
- [Best GPS camera apps in 2026](/photo-guides/best-gps-camera-apps-2026)
