What is a disruption claim?
Disruption concerns reduced productivity. It can occur with or without delay to completion, so the evidence and analysis need to address the particular effect claimed.
Practical commentary. Check the contract form, edition, amendments and applicable law for your project.
Identify entitlement before valuation
Reduced productivity alone does not establish a right to compensation. Identify the contractual or legal basis, the responsible event and the resulting loss. Separate other causes, including the Contractor’s own performance.
Choose a method that fits the records
A measured-mile analysis compares productivity on comparable affected and unaffected work. It requires a credible comparison and suitable records; it is not mandatory or always possible. The SCL Protocol discusses other methods and their limitations.
Make the evidence usable
For an internal review, assemble activity references, quantities completed, resource hours, dates, changed working conditions and contemporaneous explanations. Ask whether each record uses consistent units and covers the same work boundaries.
Keep assumptions visible in the review pack. A team member should be able to trace a selected quantity or resource entry back to its source without reconstructing the entire project history.
Connect the analysis to NEC4
On NEC4 ECC work, use the applicable compensation event assessment rules. A retrospective productivity study does not replace the dividing date, Defined Cost or programme provisions.
Sources and further reading
- SCL Delay and Disruption Protocol, second edition
- NEC: Accepted programmes
- GMH blog: the programme baseline (practical commentary; check the applicable edition and amendments).
.webp)
