Photo & Located Action-Item Evidence

What makes the evidence "located"?

When an action item is created on the platform, exact lat/long coordinates can be provided, making it easy for others to find the exact location of the item they need to complete. A description says what to fix; a coordinate says exactly where to stand to fix it.

The precision lives on the finding, not in a caption. That is what turns "somewhere along the north perimeter" into a point a crew can drive to. On a large or repetitive site - a long silt-fence run, a row of nearly identical inlets - a written location invites the wrong guess; a coordinate does not. The person dispatched to close the item is looking at a map pin, and the item they close is unmistakably the one that was written.

The photo half of the record

Photos ride with the findings they document. Each action item's verification record includes a photo reference. Storage on the platform covers documents, permits, photos, images, videos, and attachments. The image shows the condition; the located action item says where it is. Together they are the before-and-after a closeout or an audit actually asks to see.

A photo reference is not decoration on the record - it is the record's proof. It shows the state a control was in when the finding was written, and, once the fix is verified, the state it was in when the item was closed. An item that carries both is an item no one has to take on faith.

What the permit asks you to locate

Locating findings is not a nicety - it is written into the report. Major observations in the report must include the locations of where erosion and discharges of sediment or other pollutants from the site have occurred, locations of BMPs that need to be maintained, locations of BMPs that failed to operate as designed or proved inadequate for a particular location, and locations where additional BMPs are needed. Exact coordinates on the action item are how that requirement stops being approximate.

A report that says a control failed "on the east side" satisfies the letter of it and little else. A report that pins the failure to a coordinate satisfies the intent - anyone reading it later can go stand where the problem was, confirm the fix, and move on.

Where the evidence lives

Nothing useful stays useful if it is hard to find later. The platform automatically files and stores completed inspection reports in a cloud-based folder, while also allowing other individuals to access them when needed. The photos and located items file with the report they came from, so the evidence and its context never drift apart.

That is the difference between evidence and a shoebox. When a record files itself the day it is written, producing it later is a search, not an excavation - and the photo, the coordinate, and the report that ties them together all come back as one thing.

The honest version of "GPS evidence"

It is worth being precise about what carries the coordinate. The exact location rides on the action item, not embedded in the photograph - the image documents the condition, and the located item points to it. That is a stronger record than a tag buried in a file: the location becomes a field anyone can read, sort, and route a crew to, rather than metadata someone has to go digging for.

The evidence a dispute actually needs

Most site disagreements are not about whether something happened but about where, when, and whether it was fixed. A photograph answers the first, a coordinate answers the second, and a record that files itself answers the third without anyone reconstructing it. A finding that lives in a located, photographed, dated item does not turn into a phone call six months later. The inspector who asks for a control's history gets a picture and a point; the owner reconciling closeout gets a record where every finding shows its condition and its place. The evidence was built as the work happened, so producing it later is retrieval, not argument.