Time has a daily rate.

Here is the arithmetic everybody reaches for. Preliminaries on this job are $85,200. The programme runs twelve months. That is $7,100 a month, or about $233 a day. Forty-one days of delay, therefore, comes to roughly $9,563.

It is clean, it is checkable, and it is the wrong answer.

Not wildly wrong, and not dishonest. But it is an average standing in for a measurement, and the difference between those two is what this week is about — because it is also the difference between a number that survives scrutiny and one that gets negotiated.

Nobody ever spent the average

THE AVERAGE IS A LINE NOBODY SPENT $85,200 across twelve months, and not one of those months looked like the average $7,100 average mobilise full site · crane, cabins, supervision wind down A delay in month three and a delay in month eleven cost completely different amounts.
Illustrative shape, not measured values. The point is that the flat line is the one number the site never spent.

Preliminaries are not a flat monthly charge. They are a curve. In the first month there is a compound, a small team and not much else. By the middle of the job there is a crane on hire, a full complement of site staff, three cabins, security, and a set of temporary works. By month eleven the crane has gone and half the staff are on the next project.

So a delay in month three and a delay in month eleven cost completely different amounts, and the flat line is the one figure the site never actually spent in any month of the job.

The $7,100 is a useful planning number and a good sanity check. It is not, on its own, a claim.

The rule most claims get backwards

WHICH PERIOD DO YOU PRICE? the answer is not the one most claims use THE TAIL OF THE JOB the weeks added at the end crane gone, cabins reduced, half the staff demobilised easy to identify, and wrong THE PERIOD THE DELAY FELL IN the months the event actually held the works up priced from what the site was genuinely costing then This is why the windowed analysis mattered. Dated days can be priced. A lump of forty-one undated days can only be multiplied by an average.
The guidance keeps returning to the same phrase: at the time. It applies to the money as much as to the analysis.

Now the rule, and it is the single most useful thing in this week.

The costs of a delay are assessed by reference to what was going on at the time the delay event occurred — not by reference to the extra weeks tacked onto the end of the job.

That is the opposite of how most prolongation claims are built. The instinctive approach is to identify the period between the original completion date and the actual one, price what the site cost during those weeks, and claim it. It is easy to identify and easy to evidence.

It is also, on most jobs, the cheapest period of the whole project. The crane is off hire, the cabins are coming down, and the site team is three people finishing snagging. Pricing your delay at the tail-end rate is frequently claiming considerably less than you are entitled to.

It can run the other way too. A delay that fell during a quiet spell, priced at a busy tail-end rate, overstates the claim and hands the other side an easy correction.

Either way, the guidance keeps returning to the same two words: at the time. Week 12 argued that a windowed analysis is worth more because it produces dated days. This is the week that pays off. Dated days can be priced against what the site was actually costing in those months. A lump of forty-one undated days can only be multiplied by an average.

What you spent, not what you priced

A second correction, and it catches experienced people.

Prolongation is recovered on cost actually incurred — time genuinely taken up, expense genuinely suffered. What the tender allowed for preliminaries is close to irrelevant to that calculation.

The reason is not moral, it is practical: bids are unbalanced. Preliminaries get loaded or thinned for commercial reasons that have nothing to do with what the site will cost, and a tender allowance is a bidding decision rather than a measurement.

Which cuts both ways and is worth being clear-eyed about. If you loaded your preliminaries at tender, the allowance flatters you and you will not be paid on it. If you thinned them to win the job, the allowance understates your actual spend — and you can recover the actual spend, because that is what the rule measures.

Which parts of the preliminaries run with the clock

WHAT IS AND IS NOT IN THE CLAIM only the part of the preliminaries that runs with the clock TIME-RELATED · IN site staff and supervision accommodation and welfare plant standing on hire security, insurances, utilities NOT TIME-RELATED · OUT mobilisation and setting up demobilisation and clearing anything priced per unit of work one-off items, however large Claiming the whole preliminaries figure per week is the error a reviewer looks for first.
A longer job does not need a second setting-up. Splitting the preliminaries properly is most of the work.

The third correction is the one a reviewer tests first, because it is the quickest to find.

Only the time-related part of the preliminaries belongs in a prolongation claim. Site staff, accommodation, welfare, standing plant, security, insurances and utilities all run with the clock: keep the site open another six weeks and they cost another six weeks.

Mobilisation does not. Neither does demobilisation, nor anything priced against a quantity of work rather than a duration. A longer job does not require a second setting-up.

Splitting the preliminaries into the part that runs with time and the part that does not is genuinely most of the work in a prolongation claim, and a claim that skips it — taking the whole $85,200, dividing by the programme, and multiplying by the delay — has made an error the other side does not even need an expert to find.

The overlap that gets found

One more thing to check before the claim goes out, because it is the first place a reviewer looks after the time-related split.

Site staff appear in a prolongation claim as a time-related cost. They also appear, frequently, in a disruption claim as supervision absorbed by managing change. Both entries can be perfectly honest and describe the same people in the same weeks, and together they charge for them twice.

The same trap catches standing plant claimed as prolongation and again as part of a variation, and site accommodation recovered under an extension and again inside an agreed change. Week 22 named double counting as the hazard of building a claim event by event; this is where it actually shows up.

Run one reconciliation before submitting: every time-related cost, listed once, with the single claim head it belongs to. Finding the overlap yourself costs an afternoon. Having it found for you costs the credibility of everything around it.

And still no profit on it

Week 3 established this and it belongs here too. Under the ground conditions clause the entitlement is to Cost, and Cost is defined to exclude profit.

So a fully successful prolongation claim restores what you spent keeping the site open and adds nothing. You financed the extra weeks, carried them on your own working capital — the $130,404 Cost & Cash Week 17 measured — and got the money back with no return on it.

That is the correct outcome under the clause and it is worth stating plainly, because a great many people are surprised by it at exactly the wrong moment.

The version nobody uses

There is a neat solution to all of the above and it is almost never adopted.

Agree a daily rate for delay at the outset, the same way the contract already fixes a daily rate for liquidated damages. Both parties know what a day is worth, the entire argument above disappears, and the assessment becomes arithmetic.

The reasons it is rare are not technical. Neither side wants to name the number early, and both prefer the optionality of arguing later. But on a job where the parties genuinely intend to settle things as they arise, it is available, and it removes more disputes than almost any other single clause.

Practical insight

Take your current job and build the curve rather than the average. Twelve rows, one per month, and in each one the time-related preliminaries actually incurred.

You will need to strip out mobilisation, demobilisation and anything quantity-driven, which is the exercise. Most cost systems will not do it for you, because preliminaries are usually coded as one lump.

What you end up with is a monthly rate table, and it does two things. It tells you what a week of delay is genuinely worth in any given month, which is a management number as much as a claims one. And when a delay does arrive, the claim is a lookup rather than an argument.

Do it once and maintain it monthly. It takes an hour to build and about ten minutes a month, and it converts the weakest part of most claims into the strongest.

Key takeaways

✔ An average monthly preliminaries figure is a planning number, not a claim; no month of the job costs the average.

✔ Prolongation is assessed on what the site was costing at the time the delay occurred, not during the extra weeks at the end.

✔ The tail of a job is usually its cheapest period, so pricing delay there often understates the entitlement.

✔ Recovery is on cost actually incurred; tender allowances are bidding decisions and carry little weight.

✔ Only time-related preliminaries qualify — mobilisation, demobilisation and quantity-driven items do not.

✔ Under a Cost entitlement there is no profit on any of it, so full recovery leaves you level rather than ahead.

✔ Site staff and standing plant are easily claimed twice, under prolongation and again under disruption or a variation; reconcile before submitting.

✔ A pre-agreed daily rate for delay removes the whole argument and is almost never put in the contract.

What's coming next

Site costs are only half of what a longer job consumes. The other half is happening in an office the delay never touched: the estimator, the accounts team, the directors' time, the borrowing that funded the overrun. Next week is head office overhead and finance — the formulae that exist to calculate it, why each of them is contested, and what a tribunal is really being asked to accept.

Enjoyed this lesson?

Join with Google to get each new lesson the moment it's published — and help me see which topics matter most to you. No spam, one email a week, unsubscribe anytime.