A close-out photograph proves nothing.
It could be from any job, any day, any phone — which is exactly why someone has to look at every one of them. So we moved the proof to the moment of capture, where it costs nothing, and the package arrives already verifiable.
Before the shutter
The phone checks he is on the line segment the engineer assigned — before he takes the photograph, not after the package is rejected.
GPS accuracy is subtracted before anything is called off-segment. Accusing a technician because the fix was poor is how a tool loses a crew.
At the shutter
Focus, exposure and legibility are judged on the device in about forty milliseconds. No network, no cloud call, no cost per photo.
At 150,000 photos a month a cloud call per photo is a budget line. Arithmetic on the phone is free, and it works at the bottom of a vault.
The stamp
Every photograph is bound at capture to where, when, which device and which requirement — then hash-chained to the one before it.
This is the one property that cannot be added later. A photograph taken without it is unverifiable forever — which is precisely why today's close-out photos have to be inspected by a person.
Off the phone
He presses done and puts the phone in his pocket. The upload continues while the app is closed, killed, or the phone reboots.
A foreground request dies in the vault and nobody finds out until the package is late. This is a background transfer the system owns.
The desk
The chain is re-verified here, server side — the phone's own word for it is worth nothing — and a package only reaches a person when something actually needs one.
Verified means nothing was changed after capture. It is deliberately not a judgement that the work passes — conflating those is how a tool starts quietly approving things nobody approved.
open the review desk →The same evidence, years later
Nothing new is captured for any of this. Claims, presence and safety all read the records close-out already created.
A claim arrives two years after the work. The records place a subcontractor seven metres from the reported point, working outside their locate ticket, with a bore six inches under spec.
run those engines →The paperwork, separately
AT&T's own documents: construction drawings against contracts and invoices, the wireless document set against itself, and CD PDFs into GIS.
Also $8,262 Ansco never invoiced on the same job. An over-billing is caught by the customer. An under-billing is only ever caught by the contractor, and only if someone looks.
run the document engines →The rule sets behind this are our best reading of AT&T’s requirements, not their published spec, and the app says so on screen. Ansco’s own rejection history is what calibrates where the line falls — it refines the judgement, it does not create it.