Recovering the cost of extra time on site under NEC
NEC has no separate prolongation claim. See how time-related cost goes into the compensation event, what to include and what to leave out.
On this page
The job is running longer than planned because of something the Client or the Project Manager did, and your site team, cabins and cranes are costing money every extra week. You are looking for the prolongation claim. There isn't one.
The short answer
NEC has no stand-alone extension of time claim and no separate loss and expense account. The extra time and the cost of staying longer are both dealt with inside the compensation event that caused the delay: the Completion Date moves, and the Prices go up by the time-related Defined Cost (forecast or actual) plus the Fee. If you have no notified compensation event, you have nothing to attach prolongation to.
What to do, step by step
- Notify the event on time. You have eight weeks from becoming aware it has happened (clause 61.3). Miss that and the Prices and dates generally stay put.
- Model the delay. Show how far the event pushes planned Completion, compared with the Accepted Programme current on the dividing date (clause 63.5 in NEC4, 63.3 in NEC3). No visible delay means no prolongation.
- List what stays on site longer because of this event: management, welfare, power, standing plant, and so on.
- Price it as Defined Cost. Use the schedule of cost components for your main Option, not your tender preliminaries, unless rates have been agreed with the Project Manager under clause 63.2.
- Add the Fee and put it all in one quotation. The assessment of the event is your only entitlement for it (clause 63.6 in NEC4, 63.4 in NEC3).
- Reflect the same movement in the programme you submit with the quotation.
What to record
- The Accepted Programme current when the event was notified, and your revised version
- Weekly cost of each time-related item, with invoices and hire agreements
- Evidence that standing gangs or plant could not reasonably be moved elsewhere
- Notes of any overlapping events, so the same week of site staff is not claimed twice
What not to do
- Do not claim head office overheads or profit separately. They sit inside the Fee (clause 52.1).
- Do not add finance charges unless they fall within the cost schedule.
- Do not include cost caused by your own slow progress.
- Do not rely on a generous tender allowance for preliminaries. The measure is the effect on Defined Cost.
- Do not hold the claim back for an end-of-job account. The contract does not have one, and each event is dealt with when assessed.
When to get help
Several events overlapping is where this gets difficult. If the combined delay is greater or smaller than the sum of the parts, get a planner to model the programme event by event. Take commercial or legal advice if the Project Manager disputes causation or says you were already late.
Example
A substation fence and gate contract on Option A. The Client's transformer compound is handed over four weeks later than the date on the Accepted Programme, and the programme shows planned Completion moving by four weeks. Figures are invented.
| Item | Per week | Four weeks |
|---|---|---|
| Site manager and engineer | £6,000 | £24,000 |
| Welfare, power and security | £1,200 | £4,800 |
| Mobile crane, standing | £2,800 | £11,200 |
| Subtotal | £40,000 | |
| Fee at an illustrative 10% | £4,000 | |
| Change to the Prices | £44,000 |
The Project Manager may say the crane could have been used elsewhere. Have the answer ready.
Under the target-cost Options (C and D) the Defined Cost is paid anyway, so the event matters because it moves the target and the date.
Related guides
- Delay analysis basics
- Float and time risk allowance explained
- Terminal float
- Programme and compensation events
This guide is general information, not legal advice. Check it against your contract.
