Jump to Section
It's there. But is it evidence? A Legal & Governance Q&A on construction records that hold up under scrutiny
Finding a file isn't the same as being able to stand behind it. This series answers real questions from construction Legal, Risk, and Governance leaders about the gap between "we have the record" and "we can prove it in front of someone whose job is to doubt us."
1. Opposing counsel wants the full change-order history on a disputed project. Do we produce it, or do we produce a version we hope holds up?
Reality check:
Discovery doesn't ask whether a record exists. It asks whether you can produce the correct version, show it hasn't been altered since it was filed, and explain the chain of custody in front of someone paid to find the hole in your answer. Most firms only learn which version they actually have, when a claim forces the question.
The workaround:
Legal asks IT or the project team to manually reconstruct the history from emails, shared drives, and whoever's memory is sharpest, cross-referencing dates and hoping nothing's missing. It can produce a version. It rarely produces one anyone's confident enough to put a signature behind.
2. We're under a litigation hold. Can we prove nothing's been altered since the hold went into effect?
Reality check:
A litigation hold is an instruction. It isn't proof. If a record's integrity is challenged, "we told everyone not to touch it" isn't an answer a court accepts; someone still has to demonstrate the file itself hasn't changed.
The workaround:
Most firms rely on hold notices, access restrictions, and occasionally asking IT to check who touched a folder after the fact. It shows intent to comply. It doesn't show the file is unchanged, because nothing was actually verifying that at the time.
3. A regulator asks for Golden Thread / Gateway 3 records on a completed building. Whose job was it to keep those defensible, and can they prove it?
Reality check:
Regulatory audits assume a continuous, traceable record from design through completion. In practice, that record was usually somebody's part-time responsibility across several handovers, and no single person can currently prove the whole thread is intact.
The workaround:
The usual response is a pre-audit scramble, someone is tasked with pulling together whatever documentation can be found and building an index before the deadline. It produces a folder. It doesn't produce confidence that nothing's missing, because no one's checked against the original requirement, only against what's easy to find.
4. We're six months post-acquisition. If the subcontractor's project records don't hold up under a warranty claim, whose liability is that now?
Reality check:
Indemnity clauses in the purchase agreement assume the underlying records support a claim if one arises. If the acquired company's project history is incomplete, inconsistent, or unverifiable, the paperwork promising protection doesn't change what you can actually produce when a warranty claim lands on your desk.
The workaround:
Risk and legal teams lean on the contract language itself, treating a strong indemnity clause as if it were the record. It allocates blame if things go wrong. It doesn't give you anything to actually produce when a claim requires evidence, not an argument about whose fault it is.
4. We deleted a record to meet a GDPR/PECR erasure obligation. If a regulator or claimant later askes why it's gone, can we prove the deletion was legitimate?
Reality check:
Retention policy says when a record can be disposed of. Data protection law sometimes says it must be, sooner. Most firms can point to the decision that was made when those collided, but far fewer can produce proof of exactly what was deleted, when, under what authority, and that the deletion itself followed policy. That gap only becomes visible once a regulator or opposing counsel asks why a record that should exist, doesn't.
The workaround:
The usual trail is an email thread or a line added to a retention spreadsheet, reconstructed after the fact, if anyone ever asks. It shows someone made a judgment call. It doesn't produce a disposal records with the same evidentiary weight as everything you kept.
Closing the gap between "kept" and "defensible"
Five different questions, one recurring gap: each of these firms had a record. None of them had a record they could stand behind the moment someone with authority started asking hard questions.
That gap has a name, even if it doesn't always get one internally. It's the difference between storage and digital preservation - between a file that still technically opens and a record whose authenticity, chain of custody, and completeness can actually be demonstrated. Intelligent archiving is what closes it: not a passive place records get put after a project ends, but an active layer that keeps them organized, verifiable, and retrievable for as long as they might be asked for.
Applied across the scenarios above, that looks like:
- Chain of custody, on demand: verified version history and integrity checks on project records, so what gets produced in discovery or under a hold is the version you can defend, not the version that happened to survive.
- Continuous compliance readiness: the Golden Thread / Gateway 3 record stays organized and retrievable from handover onward, so producing it for a regulator is an export, not a reconstruction project.
- M&A risk transferred to real evidence: acquired project records are consolidated into a single, verifiable archive, so an indemnity clause is backed by something you can actually produce, not just contract language.
- Disposal that's provable too: records disposed of under GDPR/PECR obligations are logged with the same audit rigor as retained records, so a question about what's missing gets answered with a defensible disposal record, not a reconstructed explanation.
In every case, the difference isn't whether the record exists. It's whether someone can prove it, on demand, to someone whose job is to doubt them. That's what a genuine preservation and archiving strategy is for, and it's the standard Preservica builds to meet.
We'll go further into the details of evidence and legal hold in a future post. In the meantime, if you'd like to discuss your own requirements, please do get in touch.
