“That crack was already there”
At handover, everyone has their own photos. None carries a date a third party can verify, and the date written in the file changes in one click.
Construction · Companies and tradespeople
The snag is dated, located, tied to the device. The dispute stops at the photo.
Progress, snags, handover, statutory notices. Every photo is sealed inside the app at the moment it is taken, offline if need be, and verifiable by the client with no account.
3 free proofs every month for a sole trader. For a company, a pilot with the dashboard and the API.
The problem as it is lived
At the end of a project, putting the work right costs weeks, and the argument is about “when” and “in what state”. A gallery photo says neither.
“The fit-out was not finished on that date”
Progress statements, late penalties, payment calls. The progress photo is worth its date, and its date is worth nothing without proof.
“The notice was not up”
Permit board, safety notices, collective protections. The inspection comes, and you have to show it was there, that day, in that place.
What the proof establishes here
The same three checks as on any Evidiq proof, read in the terms of a building site.
What it establishes
- The latest date at which the photo existed, anchored outside our servers.
- The area recorded at the shutter, to within a few kilometres on the public page: the right site, not the right room.
- The device and the app, through the attestation requested on submission.
- That the file has not changed since it was sealed.
What it does not establish
- That the work is compliant. The photo shows a state; it does not judge an execution or a standard.
- What the proof is worth in your dispute. That judgement belongs to whoever receives it: client, expert, judge.
A sealed photo complements a handover report or a formal statement, it does not replace them. It brings what they often lack: a date and an origin a third party re-checks with public tools. Understand a proof.
How it works
Here it is the field app, not the link: you, or your site manager, do the capturing.
Live, inside the app, never from the gallery.
The viewfinder guides you: level, UTC time, position lock. In a basement or a dead zone, the proof is built on the device and leaves as soon as the network returns.
The photo, its date, its area and the device are bound together.
Nothing moves after that. You choose whether the link also gives the original file.
One link, attached to the report or the handover minutes.
The client, the architect or the expert opens the verification page with no account. The link is revoked from “My links”.
A company with several crews runs everything from the dashboard: proofs, export, webhooks into your tracking software. The console.
A real proof, as your client will see it
The demonstration proof, the same as on the home page. The whole card is a link to the real verification page.
What gets asked on a site
What about no network on site?
The capture happens anyway, in a basement or a dead zone. The proof is built on the device, waits for a connection, then goes on its own: depending on the device, it may need the app reopened. An interrupted capture never creates two proofs nor two charges.
Can I prove the state before the works?
Yes, and it is the most useful case: a series of photos sealed before the first intervention establishes the latest date and the area of every shot. On the day someone argues about a crack that “was already there”, the verification page says so, with the date, without anyone having to take a word for it.
Does the client need an account to verify?
No. The verification link opens in any browser, with no account and nothing to install. The page names what was verified, check by check, and says what could not be. You choose whether the link also gives the original file.
The other industries: insurance, property inventories, delivery.
Your next snag, dated.
A tradesperson installs the app, with three free proofs every month. A company scopes a pilot with the dashboard and the API.
Hosted in FranceOffline, resumes with no duplicateVerifiable with no accountWhat proves it