Recovering lost productivity (disruption) under NEC
How disruption is priced as part of a compensation event, the output records that prove it, and why you must put it in your first quotation.
On this page
Your gangs are working, the programme hasn't slipped, but the work is taking more hours than it should because the Client or Project Manager has made it harder to do. That is disruption, and it is recoverable if you handle it correctly.
The short answer
Disruption has no separate claim under NEC. It is priced inside the compensation event that caused it, because the assessment covers the whole effect of that event on Defined Cost (the allowable cost items in the contract's schedule), including extra labour hours, plant time and supervision. It must go into the quotation, because an implemented event is not reopened later. Start measuring output on the day it begins.
What to do, step by step
- Warn and notify. The eight weeks in clause 61.3 start when you become aware of the event, not when you have worked out the productivity loss.
- Begin measuring immediately. Record output per shift on the affected work, and on a comparable unaffected area if one exists.
- Write down the cause that day. A diary note that a gang stood idle for three hours because access was blocked is worth far more than a reconstruction a year later.
- Try to reduce it, and record what you tried. The assessment assumes a competent and prompt response (clause 63.9).
- Price it in the quotation. Once implemented, an event stands (clause 66.3 in NEC4, 65.2 in NEC3) and the assessment is your only right to money for it (clause 63.6). Do not submit a quotation that leaves disruption out and expect to return to it.
- If you cannot forecast it fairly, ask the Project Manager to state an assumption (clause 61.6), which is corrected later if wrong.
What to record
- Output per gang per day, split by area as well as by trade
- Stoppage and delay logs with times, causes and who was told
- Dated photographs of the areas affected
- Your records and your subcontractors' records in the same format
- Other causes of reduced output at the same time, such as weather or a new crew. Mention them yourself, because the other side will
What not to do
- Do not pile many small disruptions into one lump at the end. NEC assesses event by event, and a bundle makes cause hard to show.
- Do not compare against your tender output if the gang never achieved it. Compare with what was actually achieved elsewhere.
- Do not stay silent while it happens. A failure to warn can reduce the assessment under clause 61.5.
- Do not confuse it with prolongation. Disruption can cost money with no delay to Completion at all.
When to get help
A commercial manager should be involved from day one. If a large productivity account is being disputed, or the other side argues that your own inefficiency is to blame, get specialist advice on the method before you submit. Under Options C and D, Defined Cost is paid either way, so disruption matters for the target.
Example
A pipework package inside a pumping station on Option A. The Client's electrical crews occupy half the floor from week 6. Figures are invented.
| Measure | Value |
|---|---|
| Joints per day in the clear area, weeks 3 to 5 | 12 |
| Forecast joints per day in the shared area | 8 |
| Joints remaining in the shared area | 96 |
| Days needed at 12 per day | 8 |
| Days needed at 8 per day | 12 |
| Extra gang days at an illustrative £2,000 | 4 days, £8,000 |
The comparison is against real output elsewhere, which is why measuring early matters.
Related guides
- Prolongation under NEC
- Quotations for compensation events
- Keeping records under NEC
- Compensation event mistakes
This guide is general information, not legal advice. Check it against your contract.
