Chapter 02
Ground truth and evidence quality
Learn what makes site reality usable when schedule, safety, cost, or responsibility is disputed.
01
What this lesson is about
This lesson is about the second layer of the stack and the most underrated. Ground truth is what separates a record that survives a tribunal from one that produces a frustrating afternoon for the project manager who is asked to find footage of a delivery six months ago. By the end, you should be able to describe the metadata that makes a clip useful when a payment is disputed, list the weakest links in your current evidence chain, and recognise the small operational habits that quietly destroy chain of custody. The lesson assumes you already accept that capture is necessary; it argues that capture without ground truth is the kind of data that costs more to defend than to gather. Ground truth is mostly invisible work. It is also the work that decides whether the rest of the stack returns its investment.
02
What ground truth actually is
Ground truth is time-aligned, location-aware evidence that can be trusted by site teams, commercial teams, owners, insurers, or legal reviewers without the conversation pausing to verify provenance. It needs context: where the record was taken, when in the project programme, what activity was in progress, who is affected, and how the record was preserved between capture and retrieval. The simplest test for ground truth is whether a colleague could pick the record up cold and explain what it shows without asking the original capturer. If the record only makes sense to the person who took it, the project has produced data, not evidence. Ground truth is the layer that turns one into the other, and the work happens at capture time even though the value shows up months later when something is disputed.
03
Time alignment, location, and chain of custody
Three properties carry most of the weight. Time alignment means the record can be matched against the master programme baseline, the weather log, the gate record, and the design issue. A clip stamped only with a wall-clock time in the wrong time zone is half useless. Location means the record can be tied to a level, a grid line, or a package, not merely a generic site address. Chain of custody means the record has not been edited, the file path has not been re-saved through three personal devices, and the export the lawyer eventually receives matches the original. Construction makes all three harder than office software does, because devices change hands, supervisors rotate, retention windows are inconsistent across vendors, and the people who recorded the moment may have left the business by the time the moment becomes a claim. Ground truth is the operational discipline that protects against all of those.
04
Evidence grades and the everyday test
Not every record needs the same grade. A weekly progress photo for the stakeholder pack does not need the same chain of custody as a clip used in a delay claim. The mature project grades evidence: high-grade for commercial and legal use, mid-grade for management reporting, low-grade for stakeholder communication. Each grade has its own retention rules, export format, and approval path. The everyday test is straightforward. Could this record be used in a tribunal next year, or only in next Monday’s OAC. If the answer is the second, do not let it migrate into the first by accident. Conversely, do not over-engineer the stakeholder photo. Grading prevents both failures: cheap evidence used in expensive arguments, and expensive process applied to cheap reporting.
05
Preservation, retention, and the failure modes
Incident and claim workflows are time-sensitive in a way that surprises owners every time. A footage retention window of thirty days will lose the record before a delay claim is even formally raised. A retention window of six months will lose the record before a final account dispute reaches mediation. The mature project sets retention to match the dispute lifecycle, not the storage cost. Common failure modes include: cameras failing for a week and nobody noticing because the dashboard quietly used the last good frame, a switch from one vendor to another that breaks export formats halfway through a project, and chain of custody being broken by a well-meaning manager who downloads a clip onto a personal device before sending it to legal. None of these failures look serious in the moment. All of them surface at exactly the moment the project most needs the evidence to be clean.
Practice
01. For your current project, write down the retention window in place for fixed cameras, 360 walks, and gate records. For each, name one dispute lifecycle that exceeds the window.
Look for: A strong response identifies that retention windows are typically shorter than final account or insurance claim cycles and names a specific gap to close.
02. Draft a one-paragraph evidence grading rule for your team that defines high-grade, mid-grade, and low-grade records and the retention rule for each.
Look for: A strong response distinguishes commercial-legal use from management reporting, sets explicit retention periods, and makes one named owner responsible for high-grade preservation.
Checkpoint
Which metadata would you want attached to a clip used in a delay claim?
Recommended reading