The notice held. Now price it.

The notice held. Now price it.

Four tracks have circled the same rock. Risk Week 5 priced it at $48,450 — seventeen of forty-two piles at $2,850 each — and said plainly that the figure was conditional, because nothing evidenced what the northern half of the site was made of. Risk Week 14 asked whose risk it was. Contract Week 13 asked whether the contract even calls it a variation. And Contract Week 1 opened on an email that was never a notice, and on a commercial manager who found out forty-one days after the event.

This track changes one fact and leaves everything else alone. The notice was served: inside the period, in the form the contract requires, to the person named in the Contract Data. Everything Contract Week 10 warned about was avoided. The right survived.

That's not the end of the argument. It is the start of a different one, and a harder one.

What the last track handed over

Three things, and the whole of this track runs on all three.

A preserved right. The notice is in, the records exist, and nobody can argue your entitlement away on a technicality.

A programme that can be re-run. Track 1 built it. Contract Week 11 made it a contractual document, with a deemed no-objection at twenty-one days on the initial submission and fourteen on a revision. An unobjected programme is the Programme, and that matters more here than it did there: every method in this track needs a plan it is allowed to call the plan.

A question. Contract Week 9 sets out the test for an extension of time and stops, deliberately, before measuring anything. Contract Week 8 builds entitlement before a claim exists. Neither one says how much.

Two questions, and only one of them is answered

Every claim has two halves, and they fail independently of each other.

The first is entitlement. Does the contract give you a right in these circumstances, and did you do what was needed to keep it alive? It is a question about documents, and you answer it by reading a clause and a file. That is the whole of the previous track.

The second is quantum. How much time, and how much money? It is not a question about documents at all. It is a question about a project that never happened.

The asymmetry is worth sitting with. An engineer who has never lost a claim on entitlement can still lose the entire value of one on quantum, and that's the more common way to lose.

The comparison nobody can observe

Here is the difficulty in one sentence. To say what the rock cost, you have to say what would have happened without it — and that job was never built.

Entitlement has a document to point at. Quantum has only a comparison, and one side of the comparison doesn't exist. Every method in this track is an attempt to construct that missing side from something: a baseline programme, a set of updates, an as-built record, a stretch of undisrupted work on the same site. The methods differ in what they borrow and what they assume, and that is precisely why two competent analysts reach two different numbers from one set of facts.

So the question that governs this track is not which method is best. It is which method your records will carry.

What a claim actually has to prove

Four links, and each is proved from somewhere different.

Cause is an event, evidenced from site records. Effect is movement in the programme, evidenced from the programme itself. Entitlement is the clause that turns that movement into a right, and Track 4 covered it. Quantum is the number, and it is evidenced from the cost ledger that Cost & Cash Week 10 built.

A claim is only as strong as its weakest link, which is why a beautifully argued clause rescues nothing when your as-built record is a set of monthly photographs.

Time and money are two claims, not one

The rock generates both, and they're assessed by different tests.

The money claim is for the work itself: the piles that had to be redrilled, priced from what was actually spent. The time claim is for the site staying open longer, and it is priced by length rather than by cause. Preliminaries on this job run at $7,100 a month — $85,200 spread across a twelve-month programme — and that clock runs whether the delay came from rock, rain or a late drawing.

They can also come apart completely. You can finish on the original completion date and still have lost a great deal of money, because you built it in a worse sequence with more people than the plan assumed. There's no extension of time in that story at all. That is disruption, and it has its own half of this track.

Forty-one days, and the shape of the problem

Contract Week 1 established that the commercial manager found out forty-one days after the event. Read as a delay rather than as a governance failure, that number shows you the shape of everything this track has to do.

Forty-one days of what? Of the rock delaying the piling, if piling was driving the completion date at the time. Of nothing at all, if the piling had float and something else was driving. Of some part of the forty-one, if the driving path changed halfway through — which, on a real job, it usually does.

Those three answers are not opinions. They are what three different analytical methods return, and each is defensible on the same facts.

Why the margin is the whole argument

Net margin on this job is $48,163, from Cost & Cash Week 22. The conditional value of the rock is $48,450. The two numbers sit within three hundred dollars of each other, and that coincidence is the reason this track exists.

A claim that recovers in full leaves the job at roughly the margin it was priced to earn. A claim that recovers half of it turns a profitable job into a break-even one. A claim that fails on quantum having succeeded on entitlement leaves you holding a proven right worth nothing.

None of that is decided by how good your engineering was. It is decided by whether the records you kept eighteen months earlier can support a method that produces a number a reviewer can't take apart.

Practical insight

Take the last claim your organisation submitted, and find the sentence where it stops arguing about entitlement and starts arguing about amount.

That sentence is usually easy to find, because the register changes. The entitlement half cites clauses and dates. The quantum half starts citing rates, hours and comparisons. Mark it.

Now read only what comes after it, and ask one question of every number: what is this being compared with, and where did that comparison come from? If the answer is a baseline programme, check that it was the accepted one. If it is a rate, check that the rate is in the contract rather than in your estimate. If you can't find the comparison at all, you've found the reason the claim was negotiated down.

Do this before you need it. On the job you are running now, the records that will decide your next quantum argument are being created this week, by people who have no idea that's what they're doing.

Key takeaways

✔ Entitlement and quantum are separate halves of a claim, and a right that survives every time bar can still be worth nothing.

✔ Entitlement is answered from documents; quantum is answered from a comparison with a project that never ran.

✔ Every delay method is a way of constructing that missing comparison, which is why competent analysts disagree on the same facts.

✔ The method is chosen by the records you kept, not by the answer you prefer.

✔ A claim proves four links — cause, effect, entitlement, quantum — and each is evidenced from a different place.

✔ Time and money are two claims: the work costs what it costs, and the delay costs $7,100 a month regardless of what caused it.

✔ The rock is worth $48,450 against a net margin of $48,163, so the quantum argument is the whole commercial outcome of the job.

What's coming next

Before any of the methods, the chain has to close. Next week is cause and effect: what it means to say that an event caused a delay, why a list of things that went wrong is not a causal argument, and why the link most claims skip is the one between the two.