What it means
A project finishes later than the original plan, and the delay could involve design changes, late materials, weather, rework or several events together. Delay analysis asks which events actually changed the completion path.
The Society of Construction Law Delay and Disruption Protocol provides guidance on extensions of time and delay compensation and emphasises transparent information and methods, though its guidance is not itself every contract governing rule. A baseline programme should identify activities, durations and dependencies, while actual progress records show what happened, since comparing only the first and last dates cannot explain the cause.
The critical path is the sequence that determines earliest project completion under the current schedule logic, and a delay to a noncritical task may use available float without shifting the finish. Criticality can change during the project.
A fictional build has a planned finish on day 100, and a design approval is late by ten days, but five days of available float absorb part of its effect under the validated programme. The illustrative finish impact may be five days, not automatically ten.
A schedule update should reflect actual completed work before a new delay is tested, because applying an event to an obsolete plan can give a false result, so record each analysis date and version. Check contemporaneous records such as meeting notes, site diaries, approvals, delivery logs and revised schedules, since later recollections can help but may be less reliable, and keep both favourable and unfavourable evidence.
Several delay methods exist, including prospective and retrospective approaches, and the suitable method depends on available records, contract wording and the question being answered. Concurrent events need careful examination as well, because two delays can overlap in calendar time without both independently affecting completion, and the legal treatment of true concurrency may vary by contract and jurisdiction.
A contractor may have a valid time extension without automatic payment of all extra site costs, because time entitlement and financial compensation are separate questions, and RICS discusses extension-of-time assessment and delay costs as distinct issues. Notice provisions can be material, since a contract may require prompt notice and particular supporting information, and delay analysis should not replace timely communication during the work.
Mitigation matters too, as teams may resequence work, add shifts or use alternate suppliers, and the analysis should record what was feasible and what was done without assuming every acceleration cost was reasonable. Disruption is not identical to delay, because work can become less efficient without moving the completion date and a delayed finish can occur without a measurable productivity loss.
An independent reviewer should be able to reproduce the calculation from the records and schedule versions, and hiding unfavourable changes weakens the analysis. Delay analysis explains schedule causation, not simply who to blame, so the final contractual outcome requires the actual agreement, evidence and often specialist review, while prevention is a useful by-product for management because it can reveal approval bottlenecks or unrealistic lead times.
In practice
Real-world examples.
Example
A team tests whether late design approval moved the critical path. It compares the validated programme with and without the ten-day approval delay. Five days of float absorb part of the effect, so only five days reach the finish date.
Example
An analyst separates overlapping supplier and site-access delays. A fictional supplier delivers a component late while the site is closed for another reason, so the analyst tests whether the late component would have delayed critical work independently. Counting the same ten calendar days twice would overstate the effect.
Example
A manager updates the programme with actual progress before assessing a new event. A task may have started late because an approval was missing, but labour capacity might also have been unavailable, so the manager investigates both explanations. The choice of narrative follows the records, not preference.
Formula
Calculation
There is no universal delay formula. Illustrative completion impact = the difference between a validated completion forecast with an event and the comparable forecast without it, under stated assumptions.
Worked example. A project is planned to finish on day 100. A design approval is ten days late, and the validated programme shows five days of relevant float. The finish impact is 10 - 5 = 5 days, so the forecast completion moves from day 100 to day 105. If a second, independent event on the critical path adds three more days, the forecast becomes day 108, but two events that cover the same calendar days must not be counted twice.Case study
Seen in the real world.
In this fictional case, a project planned to finish on day 100 faces a ten-day design approval delay. A validated schedule shows five days of relevant float, leaving a possible five-day finish impact. The analyst checks actual progress and other concurrent events before making a contract claim. This simple case does not decide entitlement.
The analyst then reviews the contract's notice clause and finds that the contractor wrote to the client within the required period. A separate supplier delay is tested and found to have been absorbed by float, so it is excluded from the claim. The final report states its assumptions, schedule versions and uncertainty plainly so that an independent reviewer can repeat the calculation.
Watch out
Common mistakes.
- Equating every late task with project delay.
- Counting overlapping calendar days twice.
- Treating time entitlement as automatic payment entitlement.
Questions
People also ask.
Is a ten-day event always a ten-day extension?
No. Critical path, float, other events and contract terms matter.
What records help?
Baseline and updated programmes, progress logs, notices and event evidence.
Does analysis decide fault?
It supports a causation assessment; legal responsibility depends on the contract and facts.
From the founder's library

Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%