A delay claim is about the completion date. A disruption claim is about lost productivity, and it can succeed on a project that finished on time. The proof is not the same.
Delay and disruption are distinct claims that are routinely merged into one unprovable submission. Delay concerns the completion date and is proved with a programme. Disruption concerns the efficiency of the work and is proved with productivity evidence. A project can finish on time and still carry a substantial disruption claim, and a delay claim can succeed with no disruption at all.
Delay claim at a glance
The claim is that an event for which the other party is responsible delayed the completion date, giving rise to an extension of time and, where the contract allows, the time related cost of the longer period. It is proved by programme analysis: the critical path, the float position, and the effect of the event on the end date. The evidence is the baseline, the updates, the records of what happened and the notices.
Disruption claim at a glance
The claim is that interference made the work less efficient than it should have been, so more labour and plant hours were consumed than the work warranted. It does not depend on the completion date moving. It is proved by comparing actual productivity with the productivity that should have been achieved, which requires resource records at a level of detail most projects do not keep by accident.
What has to be proved
Delay claim: That the event caused the completion date to move, demonstrated through the critical path.
Disruption claim: That productivity was lower than it should have been, that the reduction was caused by the other party, and what the additional resource cost.
Primary evidence
Delay claim: The baseline programme, the progress updates, the notices and the records of the event.
Disruption claim: Labour and plant allocation records at activity level, output records, and a credible undisrupted comparison.
Dependence on the programme
Delay claim: Total. Without a sound programme there is no way to show an effect on completion.
Disruption claim: Limited. The programme provides context, but the claim stands on productivity rather than on the critical path.
Relationship to the completion date
Delay claim: Central. If the completion date did not move, there is no delay claim.
Disruption claim: Irrelevant. A disruption claim can succeed on a project delivered on the contractual date.
Typical method of quantification
Delay claim: Prolongation cost for the established period, built from the actual time related cost incurred.
Disruption claim: A comparison of disrupted and undisrupted productivity, with the additional hours priced at the actual cost of the resource.
Common reason for rejection
Delay claim: No demonstration of critical path effect, or a notice failure.
Disruption claim: No resource records at activity level, so the loss of productivity is asserted rather than measured.
What to do during the works to preserve it
Delay claim: Maintain the baseline and updates, give notices in time and record events as they happen.
Disruption claim: Record labour and plant by activity from day one, and identify an undisrupted period for comparison while it is still recognisable.
When delay claim wins
- Situations where the completion date actually moved and damages or prolongation cost are at stake.
- Discrete events with an identifiable start and a traceable effect on the critical path.
- Projects with a sound accepted baseline and properly maintained programme updates.
- Cases where the contract requires contemporaneous assessment and a decision is needed during the works.
When disruption claim wins
- Projects completed on or near time where the contractor absorbed the interference through extra resource.
- Repetitive work where an undisrupted period exists for comparison, such as similar floors or units.
- Situations caused by access restrictions, out of sequence working, late information or excessive change.
- Cases where the contractor kept labour allocation records at activity level throughout.
How to decide
Identify which claim you actually have before writing anything. If the completion date moved and you want time or prolongation cost, it is a delay claim and the programme is the centre of the case. If the date held but the work cost more in hours than it should have, it is a disruption claim and the resource records are the centre of the case. Where both are present, submit them separately with a clear statement of what each covers, so that neither inherits the other weaknesses.
The decisive preparation for a disruption claim happens long before the claim: allocating labour and plant to activities rather than to the project as a whole. Without that, the comparison cannot be made and the claim becomes an assertion. For the delay claim the equivalent preparation is the accepted baseline and the monthly updates in native format. Methods and guidance in this field are revised periodically, so confirm the current approach with your analyst, and take advice from a licensed legal adviser on what your contract permits before committing to either route.
Domira builds and supervises projects across Saudi Arabia, and the commercial discipline above is how its projects stay inside their budget and their programme. Send the drawings, the contract or the site and Domira will tell you where the risk actually sits.
Frequently Asked Questions
What is the difference between delay and disruption in construction?
Delay concerns the completion date: an event pushes the end date out, which gives rise to an extension of time and possibly prolongation cost. Disruption concerns efficiency: interference makes the work consume more labour and plant hours than it should have, whether or not the end date moves. They are proved with different evidence and should be claimed separately.
How is a loss of productivity claim proved?
Most often by comparing productivity in a disrupted period with productivity in a comparable undisrupted period on the same project, then pricing the additional hours at actual cost. That comparison requires labour and plant records allocated to activities rather than to the project as a whole, which is why the claim is usually decided by the quality of the records kept during the works.
Can a contractor claim disruption if the project finished on time?
Yes. Finishing on time often means the contractor spent additional resource to absorb the interference, and that additional cost is exactly what a disruption claim addresses. The entitlement still depends on the contract and on showing that the other party caused the loss of productivity, so confirm the position under your own wording with a licensed adviser.
What records should be kept to support a disruption claim?
Daily labour and plant allocation by activity and location, output or progress measurement at the same level, records of access restrictions and out of sequence instructions, the information request log with response dates, and the change register. Identify a comparable undisrupted period while the work is in progress, because reconstructing one from memory afterwards rarely persuades anybody.
Have a Property Question?
Domira can help you navigate property, financing and investment decisions in Saudi Arabia. Speak with our team for an initial consultation.
