A Photo Isn't Evidence Until It Can Prove Where and When It Was Taken

A photo without a time, location, and record link isn't evidence

Field programs generate photos constantly: site conditions, sample locations, well completions, boring logs, hazard observations. The problem surfaces later, in a regulatory submission, a chain of custody dispute, or a client asking whether a sample really came from where the report says.

Documentation breaks down around the photo, not the photo itself

EXIF gives you a lat/long and a timestamp. It doesn't tell you which sample the photo belongs to. So the link gets rebuilt by hand, from memory, weeks after the crew left the site.

QNOPY captures photo as part of the record, not an attachment to it

Capture runs inside the same offline-first workflow as sampling and inspection. Every photo gets GPS and a timestamp automatically, tied to a specific sample, boring, or observation rather than a folder. Photos taken with no signal sync and attach to the right entry once the device reconnects. AI Event Summary then pulls from that structure to draft the report narrative.

No extra app, no manual tagging, nothing for the technician to do differently.

What that buys you:

• Chain of custody dispute: "was this collected here, at this time" gets answered on the spot.

• Phase I ESA: the report assembles faster because visual and finding were paired at capture.

• EHS inspection: no ambiguity months later about which finding a hazard photo supports.

  
  

A photo that can't prove where and when it was taken becomes someone's problem to solve manually, usually at the worst possible time.

See what a structured photo record looks like: Request a QNOPY demo