Pre-loss documentation · blockchain anchoring · construction defect · FRE 901(b)(9) · FRE 902(13)
Meta description: Nevada's Supreme Court puts the burden on insureds to prove coverage in construction defect claims. Here's what pre-loss documentation has to establish and why. (158 chars)
---
A contractor finishes a commercial renovation. Three years later, the building owner files a construction defect claim: water intrusion that allegedly began during the original build. The insurer responds with a simple question. Prove when the damage started.
The owner produces photos, inspection records, maintenance logs. Every document was created after the tenant reported a problem. Nothing predates the date the insurer is disputing. The timeline stays open.
This isn't a unique fact pattern. Claims Journal reported this week that the Nevada Supreme Court ruled the insured must prove coverage owed in construction defect litigation. Courts aren't going to resolve timing ambiguity in your favor. The burden sits with the party making the claim. Meeting it requires documentation that was built before the dispute, not assembled after it.
---
Why After-the-Fact Documentation Fails
Construction defects have long latency. A waterproofing failure doesn't produce visible damage immediately. Water infiltration, settling, mold growth. These emerge over time. By the time a claim is filed, the gap between when the defect allegedly began and when anyone documented it can be years.
Documentation assembled during that gap looks reactive. Photos taken three weeks before the claim was filed don't tell a court anything about what the condition was two years ago. Opposing counsel knows this. So do courts.
File metadata doesn't close the gap either. EXIF timestamps in photos can be changed in under a minute with free software. The date field in a Word document reflects when the file was last saved, not when the condition it describes existed. These are routinely challenged in discovery, and for good reason.
Volume doesn't help if the timing is wrong. A thousand photos with contested timestamps isn't stronger documentation than ten photos with verifiable ones.
---
What Pre-Loss Documentation Has to Prove
The shift that matters is not how much you document. It's when you establish a verifiable record.
Documentation created before a dispute, before a claim, before a problem is reported: this exists independently of any litigation motive. That independence matters. Courts ask whether the process that produced the timestamp is reliable. Not whether you have a lot of records. Whether the records can be authenticated as existing when you say they did.
FRE 901(b)(9) allows authentication of evidence produced by "a process or system that produces an accurate result." That's the evidentiary framework for blockchain-anchored timestamps. But 901(b)(9) requires a foundation: usually expert testimony or a qualified certification explaining the anchoring process. It doesn't self-authenticate.
For that, you want FRE 902(13). Under 902(13), a written certification from a qualified person establishes authenticity without live testimony. No expert on the stand. No deposition. The certification itself does the work at trial.
Know which rule you're relying on before a dispute arises. Building documentation around 902(13) compliance means generating the right certification materials at anchoring time, not trying to reconstruct them two years later in discovery.
---
How Blockchain Anchoring Works
ProofLedger computes a SHA-256 hash of any file and records that hash on two independent blockchains. Polygon confirms the anchor instantly. Bitcoin anchors run daily via batch, connecting individual file hashes to confirmed Bitcoin blocks through merkle proofs. Two chains, two independent verification paths, one workflow.
The file never leaves the device. Only the hash goes on-chain. A SHA-256 hash is a fixed-length fingerprint of the file's contents at that moment. If a single byte changes, the hash changes. Which means an anchored hash proves the file existed, unchanged, at the time it was anchored.
Each anchor produces a public verify URL. Opposing counsel can check it. An expert witness can check it. An auditor can check it. No account required. The result is either "hash found, anchored at this time on these chains" or "hash not found." There's no version of that answer that can be gamed after the fact.
Bitcoin's proof-of-work immutability is the deeper layer. Altering a Bitcoin block requires redoing the computational work of every subsequent block in the chain. That's not a practical attack. It means a hash anchored to Bitcoin stays anchored, regardless of what happens to the original file.
---
Practical Documentation Workflow for Construction Defect Exposure
The point of failure in most construction defect documentation isn't the absence of records. It's when the records were made.
Before construction begins, document the existing property condition. Site photos, deficiencies already present, condition assessments. Anchored at the time of inspection, this establishes a baseline that predates any claimed defect. If water intrusion was already present before the contractor arrived, that's a fact the baseline can establish.
During construction, anchor documentation at milestones. Structural inspections, waterproofing layers before they're covered up, punch list completion. Each anchored set creates a sequential record of what was done and when.
After any complaint or remediation, anchor immediately. The timestamp on the anchor is the evidentiary fact. Documenting a repair thoroughly and anchoring two weeks later loses the benefit. The gap is the problem.
Evidence packs organize anchored files by case, claim, or matter, with loss dates and pre/post indicators. When a claim arrives, the timeline is already structured rather than scattered across drives and email threads with contested metadata.
---
When the Insured's Burden Changes the Calculation
Construction defect litigation is slow. Discovery windows are long. Documentation that looked adequate at claim filing can look thin three years in, when opposing counsel has worked through every metadata field and every file creation date.
The Nevada ruling is a useful frame for how courts approach this. The insured must prove coverage owed. That means proving not just what the condition was, but when it existed relative to the policy period. An adjuster's inspection report that can't be placed in time is documentation without authentication. It shows something. It doesn't prove when.
An anchored inspection report, site photos anchored the day they were taken, a maintenance log anchored the day it was written: these aren't just evidence. They're verifiable facts on two independent public ledgers. The same answer comes back for both parties. That's what neutral temporal authority means in practice. The timestamp isn't a claim someone is making. It's a mathematically settled fact.
Documentation assembled after the fact is documentation assembled under litigation motive. Courts understand this distinction. Anchored records that predate any dispute don't carry that problem.
If your workflow involves construction defect exposure, the time to build the record is before anything goes wrong. Anchor before the loss, not after. Risk documentation, not claim documentation.
Start documenting your construction projects before disputes arise at proofledger.io