Chapter 04
Risk and claims from the owner side
How the captured record helps an owner manage risk, defend claims, and govern change, including the discipline of expecting evidence on both sides and the contract-stage moves that make later disputes shorter and cheaper.
01
Orient: the owner's risk register
An owner's risk register usually focuses on cost overrun, schedule slip, safety, regulatory exposure, and reputation. Each is real, and each has an evidence shape. Cost: payment evidence, quantity verification, and variation substantiation. Schedule: programme-confidence checks and milestone evidence. Safety: closeout rates, near-miss patterns, and incident readiness. Regulatory: audit-ready records for inspections, stage filings, and any statutory regime that touches the asset. Reputation: a project that is on top of its evidence tends to behave better in public-facing moments because there are fewer surprises and fewer awkward questions. The register becomes operational when each line has an evidence ask attached and a custodian named. A register that names risks but not the artefacts that would let the owner read them is a list of worries. A register that names artefacts and custodians is a tool. The difference is the difference between a meeting that ends with the same risks repeated and a meeting that ends with a position on each, with the artefact that supports the position. The owner´s job is not to chase the risks; it is to make the register a working document that produces decisions rather than meetings. A register that is reviewed monthly with the standing pack, and that is updated against captured-base evidence rather than against verbal assurance, will move with reality. A register that is reviewed only when something has gone wrong has already failed at the only thing a register is for, which is to make the move before the wrong thing happens.
02
Owner-frame: claims as governance, not theatre
When a claim arrives, the owner has the same need as the contractor: a defensible record of the period in question. Most owners do not maintain their own captured base; they rely on the contractor´s. The discipline is to specify retention, custody, and access rights at contract stage so the owner can interrogate the record without negotiation when the claim arrives. A claim defended on time-aligned evidence is a different conversation from one defended on recollection: shorter, less personal, and more likely to settle without external counsel. The captured base does not eliminate claims, and it should not. Genuine claims arise from genuine events. The captured base shortens the period between the event and the resolution, and it tends to filter the unsubstantiated claims out of the system before they consume legal budget. An owner who handles their first major claim with a clean captured base in hand tends to find the experience changes how they specify every contract that follows: the retention term lengthens, the custody arrangement is named explicitly, the access rights are written rather than implied. The asymmetry that used to favour the side with better lawyers shifts toward the side with the better record. That shift is the quiet commercial benefit of running the discipline at portfolio scale, and it is one of the few benefits that gets cheaper rather than more expensive the more contracts the owner runs against the same template.
03
Workflow: the change that becomes a claim
Most disputed claims start as changes that were not properly closed at the time. A direction is given verbally at the gate. An RFI is answered with a sketch on a phone. A weather event is logged but not tied to the affected work fronts. A subcontractor is asked to accelerate one Friday afternoon and nobody writes it down. Months later, those moments arrive as a claim, and the project tries to reconstruct them from chat threads, calendar entries, and the recollection of people who have since moved to other jobs. The reconstruction is expensive, and it is often inconclusive, which is the worst outcome because it forces the dispute to be resolved on relative leverage rather than on what actually happened. The owner-side discipline is to insist that change is closed in the moment. The captured base, the notice register, and the variation log carry the record forward, not the memory of the people who happened to be in the room. The standing pack should include a short section on changes raised, changes closed, and changes outstanding for the period, so that nothing accumulates silently. The discipline is unglamorous and it is the move that distinguishes claims that resolve in months from claims that resolve in years. The owner who insists on it pays a small administrative cost on every change and saves the disproportionate cost of the late-arriving claim that, by the time it lands, has lost the context that would have closed it cheaply at the time.
04
Governance: counterclaims and fairness
The captured record cuts both ways. It supports legitimate claims and it undermines unsubstantiated ones. The honest owner recognises that the same record that protects them from a weak claim may also protect the contractor from an unfair counterclaim. The owner who treats the record as a fair tool, rather than a partisan one, tends to find that contractors propose more transparently and disputes resolve more quickly. The reverse posture — using the record only when it suits the owner, and resisting access when it does not — destroys the trust the record was supposed to create and is read by every contractor on the framework within a quarter. Reputation in the contractor market is durable; it persists across projects and across personnel changes on the owner side. An owner with a reputation for reading the record fairly attracts better proposals, gets more transparent pricing, and finds that disputes settle earlier because the contractor expects to be heard. An owner with the opposite reputation pays a premium on every contract and inherits the disputes that the premium implies. The fairness is not a value statement; it is a commercial position. The captured base only earns its keep on the owner side when both sides expect to be read by it, and the only way both sides come to expect that is if the owner reads it the same way every time.
05
Failure modes
Three failure modes recur, and all three are cured at signing rather than at the point of dispute. Retention that ends at practical completion, leaving the warranty period and the latent-defect period without the record. Custody that sits with the contractor by default, so the owner cannot interrogate the base after a contractor leaves the framework or is replaced on a future phase. Access rights that are described in the contract but never tested until a dispute arrives, at which point the access turns out to be theoretical because the credentials are with someone who has left, the export format is incompatible with the legal team´s tooling, or the chain of custody was never recorded in a way that would survive cross-examination. All three failure modes are administrative, and all three are cheap to fix when the agreement is being drafted. None of them is cured at the point of dispute, when the leverage is gone and the only remaining lever is the cost of fighting it out. The owner who has fought one major claim without the right contractual scaffolding tends not to repeat the mistake. The owner who reads this and acts before the first major claim saves themselves the lesson. The legal team that updates the standard development agreement once, and then sees it survive contractor pushback on the next three contracts, will not need to be persuaded a fourth time.
Practice
01. Take your standard development agreement. Mark every clause that touches retention, custody, access, or evidence rights for the captured base. Identify two amendments you would make for the next agreement, and what they would protect against.
Look for: Common amendments: extending retention through the warranty and latent-defect periods, naming a custodian and successor-custodian, granting the owner read access on a named portal, and specifying export rights in a court-admissible format with a chain-of-custody log. Each amendment should be matched to a real risk: late-emerging defects, contractor exit from the framework, dispute escalation to formal proceedings. The exercise tends to expose that the standard agreement has been edited around the point but never updated to reflect what evidence the owner now expects to have.
02. Pick the most recent claim or potential claim on your portfolio. Write the single page you would put in front of counsel that summarises the captured-base evidence, its custody chain, and any gaps. What is missing, and what would you do differently next time?
Look for: A clean page lists the period in question, the work fronts affected, the artefacts that exist (with timestamps and source), the gaps (with a reason), and the custody chain. The exercise tends to surface that the gaps are predictable: weekends, areas not on a capture plan, or the days around a personnel change. Those gaps are addressable in the next capture plan, which is the point: the lesson from the current claim is the specification for the next contract.
Checkpoint
For your most exposed contract, what evidence do you currently have access to as the owner, on what retention terms, and through which named custodian?
Recommended reading