What makes a site photo usable as evidence?
The metadata and the link — when, where, by whom, and which record it belongs to. The image alone proves very little. And that metadata dies in transit: screenshot a photo or send it through a messaging app, and it is gone.
The image is not the evidence
A photograph of some reinforcement proves that some reinforcement existed somewhere, at some time, and was photographed by somebody. That is close to worthless.
A photograph of reinforcement, timestamped, geolocated, attributed to a named engineer, and attached to cover-up inspection C-04 for level 3 zone B, proves what you need it to prove. The difference is entirely in the data around the image.
How the metadata dies
It survives capture and it dies in transit, and this is the part people do not expect. Screenshot a photo and everything is stripped. Send it through a messaging app and it is recompressed and cleaned. Forward it twice and what arrives is an image of unknown provenance.
At that point the other side’s expert asks the only question that matters — how do we know when and where this was taken? — and there is no answer, because there genuinely is not one.
So capture from inside the record
A photograph taken from within an inspection form is already timestamped, already located, already attributed, and already attached to the thing it evidences. A photograph taken in the camera app and uploaded on Thursday is a file somebody will have to vouch for from memory.
The device is rarely the problem. Phone photographs with intact metadata, stored in a system with an audit trail, are ordinary and useful evidence. The chain of custody is the problem, and it is broken by convenience.
In the guides
References
- module: /modules/photos/ — the metadata doctrine and chain of custody for site photography
Zepth is the construction project delivery platform — it runs construction, procurement and asset management on one record, and does the work: reading the drawings, reviewing the submittals, matching the invoices and flagging the risks, with a human sign-off on anything consequential.
Related questions
See Zepth on your project.
A short, tailored walkthrough on your real workflow — no generic demo.
Book a meeting