Delay Analysis, Claims and Forensic Scheduling

Introduction and Context

Project delay is not simply the difference between a planned completion date and an actual completion date. It is a question of causation, entitlement, responsibility, criticality, measurement and evidence. A project may finish late without the contractor being responsible for all late events; conversely, a project may finish on time while suffering compensable disruption, acceleration or loss of productivity. Delay analysis therefore combines network scheduling, contract interpretation, project controls, engineering records and forensic reasoning.

In professional practice, delay analysis supports extensions of time (EOT), prolongation costs, disruption claims, acceleration claims, liquidated damages assessments, negotiation, adjudication, arbitration and litigation. The analyst must establish what the accepted baseline was, what actually occurred, how events affected the critical path, whether competing events operated concurrently, and which party assumed the relevant risk.

Learning Objectives

By the end of this chapter, the reader should be able to:

1. Distinguish delay, disruption, acceleration and prolongation.
2. Classify delay according to cause, responsibility, compensability and criticality.
3. Apply as-planned versus as-built, impacted as-planned, time-slice/window and time-impact methods.
4. Assess critical path changes, float, concurrency and mitigation.
5. Preserve and evaluate schedule evidence for claims and dispute resolution.
6. Formulate technically defensible conclusions while recognising contractual and methodological limitations.

1. Core Concepts and Terminology

Delay is the extended time required to complete an activity, work package or project relative to an appropriate reference plan. Disruption is reduced productivity or altered execution efficiency, even where completion is not delayed. Examples include repeated remobilisation, overcrowding, out-of-sequence work, excessive change and restricted access. Prolongation is the additional time-related cost of maintaining resources and project overheads beyond the period reasonably contemplated by the contract. Acceleration is an instruction or circumstance requiring completion earlier than the otherwise achievable or contractually adjusted date.

A delay event is not automatically a critical delay. A critical delay affects the date of a contractual milestone or completion. A non-critical delay consumes available float but does not change completion. If an activity has total float TF = 5 days and an event delays it by three days, the event is normally non-critical, subject to changes elsewhere in the network. Float is not necessarily owned by either party; its treatment depends on the contract, governing law and factual context.

A useful distinction is:

Delay Categories

• Excusable delay: A delay for which the contract grants relief, commonly an EOT; it may be compensable or non-compensable.
• Compensable delay: A delay caused by the employer or a risk allocated to the employer, normally supporting time and cost relief.
• Non-compensable excusable delay: An allocated neutral event, such as specified exceptional weather, supporting time but not necessarily cost.
• Non-excusable delay: Contractor-responsible delay, usually supporting neither EOT nor additional payment.
• Concurrent delay: Two or more relevant delay events overlap in time and affect the same completion or controlling path, with responsibility potentially divided between parties.
• Disruption: Loss of planned productivity, measured against a reliable productivity expectation.

The labels are not universal legal conclusions. The contract and applicable law govern entitlement. A technically credible schedule analysis cannot replace contractual interpretation.

2. The Baseline and the Evidence Architecture

Delay analysis begins with the correct reference plan. The baseline should be the accepted programme, including activity IDs, durations, calendars, relationships, constraints, milestones, coding, resource assumptions and the data date. A schedule prepared after the event may be useful, but it should not silently replace the contemporaneous accepted plan.

Important evidence includes:

• contract documents, amendments and notices;
• accepted baseline and revised programmes;
• periodic updates with native scheduling files;
• progress photographs, daily reports and site diaries;
• requests for information, submittal and approval logs;
• instructions, variation registers and change quotations;
• correspondence concerning access, design, procurement and inspection;
• labour, plant, delivery and productivity records;
• meeting minutes, look-ahead schedules and recovery plans;
• as-built quantities, installation records and commissioning data; and
• metadata showing file creation, revision and approval history.

Native schedule files are particularly important because PDF prints may omit calendars, logic, constraints, lag, actual dates and calculation settings. Each update should be preserved in read-only form, hashed where appropriate, and accompanied by an audit record. The analyst should record the software version, data date, status method, calendars, out-of-sequence progress settings and any manual edits.

A sound evidence process follows four principles: contemporaneity, completeness, traceability and independence. Records should be collected routinely rather than only after a dispute arises. Unsupported recollection may explain a record but should not substitute for it.

3. Network Logic and Criticality in Delay Analysis

The critical path is the longest path through a logically connected network, generally determining the earliest project completion under the stated calendars and constraints. For an activity, total float may be expressed as:

where ES and EF are early start and early finish, and LS and LF are late start and late finish. The units are time units, such as days. This relationship assumes a consistently calculated precedence network and compatible activity calendars. In schedules with multiple calendars, the numerical relationships must be interpreted using the scheduling software’s calendar logic.

A delay analysis must test whether the affected activity was critical at the time of the event, not merely whether it appears on the baseline critical path. Criticality can migrate because of progress, resequencing, changes, mitigation, resource decisions and other delays. A baseline critical path is therefore evidence of intended control, not conclusive proof of actual causation.

The analyst should distinguish:

• Driving logic: relationships that determine when an activity can start or finish.
• Near-critical path: a path with little available float and significant sensitivity.
• Negative float: an indication that imposed dates or constraints cannot be met by the calculated programme; it is not itself proof of delay responsibility.
• Float consumption: reduction in available time without necessarily delaying completion.
• Critical path drag: the extent to which an activity or relationship contributes to the completion duration, subject to the network structure.

4. Principal Delay-Analysis Methods

No single method is universally superior. The appropriate method depends on the quality of the baseline, the reliability of updates, the maturity of records, the complexity of changes and the purpose of the analysis.

4.1 As-Planned Versus As-Built

This method compares the intended programme with actual start, finish and completion dates. It is useful as an initial diagnostic and where contemporaneous programme data are weak. It can identify broad slippage but generally cannot isolate individual causes reliably. It is especially vulnerable to hindsight, because it may compare a static plan with an outcome produced by many interacting events.

4.2 Impacted As-Planned

The analyst inserts delay activities representing employer-risk events into the baseline network and recalculates completion. The difference between the unimpacted and impacted completion dates is the modelled delay:

where ΔT is the modelled time effect and both completion dates use the same calendar and milestone definition. The method assumes that the baseline is reliable, the inserted events are accurately modelled and the original logic remains a reasonable representation of causation. It is prospective in structure but often retrospective in use, and it may ignore actual progress and intervening changes.

4.3 Time-Impact Analysis

A time-impact analysis inserts a discrete delay fragnet into the latest accepted update immediately before the event, then recalculates the programme. A fragnet is a small network representing the event, its duration, logic, mitigation and affected work. The analysis measures the incremental change in completion or milestone date.

This method is often appropriate for contemporaneous EOT assessment because it uses the status of the project immediately before the event. It should not insert an event into an update that already includes its consequences, or double counting will result. The analyst must also explain assumptions about remaining durations, actual progress and logic.

4.4 Window or Time-Slice Analysis

The project is divided into periods, such as monthly update intervals. For each window, the analyst compares the planned and actual status, identifies the controlling path, records relevant events and explains changes in completion forecasts. This method is powerful for complex projects because it recognises that criticality changes over time.

A window analysis should not merely compare two bars on a chart. It should reconcile the statused network, actual records, changes in logic and the factual chronology. The selected window length should reflect the project’s reporting cycle and event density. Very long windows obscure causation; very short windows may magnify data noise.

4.5 Collapsed As-Built

The analyst begins with the as-built network and removes or shortens selected delay events to estimate a counterfactual completion date. This can be useful when actual execution is well documented but the baseline is unreliable. It is sensitive to hindsight and to the analyst’s assumptions about what would have happened absent the event.

4.6 Choosing the Method

A robust investigation may use more than one method as a sensitivity test. Different methods should not be mixed selectively to obtain a preferred answer. Differences should be explained rather than concealed.

5. Concurrency, Responsibility and Mitigation

Concurrency is one of the most contested subjects in delay claims. Temporal overlap alone is insufficient. The events must be relevant to the same completion or controlling path, and each must have a causal capacity to produce the delay under examination. A contractor delay occurring in the same calendar period as an employer delay may not be concurrent if it affects a different non-critical path.

The analyst should ask:

1. What is the precise period of overlap?
2. What activities and milestones did each event affect?
3. Was each event independently capable of delaying completion?
4. Did one event merely follow from, or magnify, the other?
5. Did mitigation change the overlap or critical path?
6. What does the contract and applicable law state about concurrency?

A practical responsibility matrix may classify each event as employer-responsible, contractor-responsible, neutral, shared or unresolved. The classification should be linked to evidence rather than asserted from the identity of the party reporting it.

Mitigation is a continuing project-management obligation in many contractual settings, subject to the contract and law. It may include resequencing, alternative procurement, additional shifts, parallel work, design release prioritisation or temporary works. Mitigation must be realistic: it may create acceleration cost, safety risks, rework, congestion or disruption. An analyst should compare the proposed mitigation with contemporaneous resource availability and site constraints, not assume unlimited capacity.

6. Disruption and Productivity Analysis

A delay analysis addresses time; a disruption analysis addresses efficiency. Typical indicators include labour hours per unit, installed quantities, crew composition, overtime, waiting time, rework, stacking of trades and out-of-sequence work.

A simple productivity measure is:

where P is productivity in units per labour-hour, Q is installed quantity and H is labour-hours. The measure is meaningful only if quantity definitions, work scope, crew composition, measurement boundaries and conditions are comparable.

Methods include measured mile analysis, earned-value comparisons, planned-versus-actual productivity, industry studies and labour-hour variance analysis. The measured mile compares a relatively unaffected period or area with an affected period or area. Its validity depends on similarity of work, conditions, crews, materials, access and measurement rules. Industry factors may be useful for benchmarking but are weaker than project-specific records.

The analyst should avoid treating all labour-hour overruns as disruption. Overruns may result from design development, changed quantities, contractor inefficiency, learning effects, poor estimating or inaccurate records. Causation requires a link between the alleged event and the measured loss.

7. Extensions of Time and Claims Structure

A well-structured EOT claim normally establishes:

1. the contractual completion obligation;
2. the notice and particulars requirements;
3. the event and contractual risk allocation;
4. the affected activities and relevant logic;
5. the critical-path effect;
6. mitigation and concurrent events;
7. the requested days and revised completion date; and
8. supporting records and expert methodology.

Time entitlement and money entitlement should be analysed separately, even when they arise from the same event. An event may justify an EOT but not compensation, or cost may be recoverable for disruption without moving completion. Prolongation costs should be tied to the demonstrated extended period and should avoid double recovery through variations, preliminaries, disruption and acceleration claims.

A claim chronology should state dates precisely. “Late design” is not enough: the claim should identify the required release date, actual release date, affected work, available alternatives, resulting logic and measurable consequence. Causal narratives should distinguish fact, inference and opinion.

8. Forensic Scheduling Workflow

A defensible workflow is iterative:

1. Define the question. Is the issue EOT, liquidated damages, disruption, acceleration or valuation?
2. Establish the contractual framework. Identify milestones, notices, float provisions, concurrency rules and record obligations.
3. Collect and preserve evidence. Secure native schedules, records, communications and metadata.
4. Validate schedules. Check duplicate IDs, open ends, excessive constraints, invalid actuals, out-of-sequence progress, calendars and unexplained edits.
5. Create the chronology. Reconcile instructions, physical progress, access, design and procurement dates.
6. Map events to the network. Identify affected activities and logic rather than relying on general descriptions.
7. Select and justify the method. Explain why the chosen method fits the evidence and question.
8. Analyse windows and criticality. Identify controlling paths before and after each event.
9. Test responsibility and concurrency. Consider mitigation and alternative causes.
10. Perform sensitivity analysis. Vary reasonable assumptions and report the effect.
11. Reconcile with records. Ensure calculated dates correspond to observable project events.
12. Report transparently. State assumptions, limitations, source documents, calculations and conclusions.

Software can recalculate networks rapidly, but it cannot determine whether a relationship represents actual causation. Manual overrides, logic changes and undocumented baseline edits may materially affect results. The analyst must retain an untouched source file and a documented working copy.

9. Illustrative Case: Riverside Medical Centre

The following is a fictional illustrative case.

Background

A contractor was to complete a medical centre on 30 September. The accepted baseline showed façade completion driving internal commissioning. Monthly updates were issued. The contract provided an EOT for employer-caused design delay, subject to notice, and treated contractor-caused delay as non-compensable.

Problem

The engineer issued revised façade details 18 days after the planned design-release date. During the same period, the contractor was late in procuring specialist curtain-wall brackets by 12 days. The employer alleged that the contractor’s procurement delay caused the completion slippage. The contractor sought 18 days’ EOT and prolongation costs.

Analysis

The analyst preserved the baseline and updates, checked actual progress and examined the submittal register, design transmittals, purchase orders, delivery records and site photographs. A window analysis showed that, immediately before the design event, façade installation was on the controlling path with four days of float. The revised design delayed fabrication by 14 working days because two of the 18 calendar days overlapped a planned non-working period. The procurement delay affected the same bracket package for 12 working days, beginning six days after the revised design was received.

The time-impact test inserted the design fragnet into the update immediately before the design release. Completion moved by 10 working days after available float and planned recovery were considered. A second test added the procurement delay. Because procurement delay overlapped the design-driven fabrication restriction for eight working days and had only four independent working days of effect, the combined completion movement was 14 working days rather than 26.

The analysis did not treat the overlap as automatically concurrent. The contractor’s procurement delay was independently capable of affecting the controlling path for four working days. The engineer’s delay was employer-responsible for the period in which fabrication could not proceed. Contract interpretation was required to determine whether the overlap barred cost recovery, reduced it, or required apportionment.

Outcome

On the stated assumptions, the contractor had a technically supportable basis for an EOT of 14 working days, subject to notice compliance and the contract’s concurrency provision. The cost conclusion required a separate assessment of responsibility during the overlapping period. The claim was revised to show the precise affected activities, overlap, mitigation and evidence rather than claiming the full 18 days.

Learning Points

The case illustrates that: baseline float matters; calendar conversion matters; concurrency requires causal analysis; an event’s duration is not identical to its completion impact; and time entitlement should not be inferred directly from cost entitlement.

10. Limitations, Ethics and Governance

Forensic scheduling is partly quantitative and partly interpretive. Common limitations include incomplete updates, unreliable actual dates, retrospective logic, inadequate progress measurement, missing notices, inconsistent calendars and poor document control. An analyst should not manufacture precision from uncertain evidence. Ranges, qualifications and sensitivity results may be more honest than a single unsupported number.

Experts owe duties of independence, competence and candour. They should disclose adverse evidence, distinguish advocacy from analysis and avoid changing methodology merely to support a party’s preferred result. Confidential information must be handled according to legal and professional obligations. Automated extraction and AI tools can assist with document classification, chronology construction and anomaly detection, but outputs require human verification. An AI-generated date or inferred causal link is not evidence unless traced to an authentic source.

Contemporary practice increasingly uses integrated 4D models, cloud-based update histories, digital photographs with geolocation, automated schedule-quality checks and structured common data environments. These tools improve traceability but also create governance risks: access permissions, version conflicts, data alteration and overconfidence in dashboards. A visually persuasive 4D animation does not prove that the represented sequence occurred.

Best-Practice Checklist

• Use the accepted baseline and every relevant update.
• Preserve native files, PDFs, correspondence and metadata.
• Define completion and milestone dates consistently.
• Analyse actual criticality in each relevant period.
• Map every alleged event to specific activities and logic.
• Separate time, cost, disruption and acceleration analyses.
• Test concurrency rather than assuming it from date overlap.
• Explain mitigation and counterfactual assumptions.
• Validate quantities, calendars, actual dates and constraints.
• Use sensitivity analysis where evidence is uncertain.
• Report adverse facts and methodological limitations.
• Ensure conclusions are contractually informed but technically reproducible.

Chapter Summary

Delay analysis determines how events affected time, criticality and responsibility; it is not a simple comparison of planned and actual completion. The analyst must establish a reliable baseline, preserve contemporaneous evidence and understand changing network logic. As-planned versus as-built provides an overview, whereas impacted as-planned, time-impact and window analyses offer progressively stronger causal insight when supported by appropriate records. Concurrency requires overlapping, independently causative effects on the same controlling path. Disruption concerns productivity rather than completion alone, and time entitlement must be distinguished from cost entitlement. A defensible forensic schedule is transparent about assumptions, mitigation, evidence quality, contractual rules and uncertainty. Technology can improve analysis and preservation, but professional judgment and independent verification remain essential.

Key Terms

Delay: Additional time required relative to an appropriate reference plan.

Disruption: Reduced productivity or changed execution efficiency.

Prolongation: Time-related cost arising from extended project duration.

Acceleration: Measures or requirements intended to achieve earlier completion.

Critical path: Longest controlling path through the network.

Total float: Time an activity can move without delaying the relevant completion date.

Excusable delay: Delay for which the contract grants time relief.

Compensable delay: Delay that may support recovery of time-related cost.

Concurrent delay: Overlapping independently causative delay events affecting the same controlling outcome.

Baseline programme: Accepted reference schedule against which performance is assessed.

As-built schedule: Reconstruction of actual execution and dates.

Fragnet: Small network representing a delay event and its logic.

Time-impact analysis: Insertion of a fragnet into a contemporaneous update.

Window analysis: Period-by-period analysis of progress, criticality and causation.

Collapsed as-built: Counterfactual removal of selected events from actual execution.

Mitigation: Reasonable action to avoid or reduce delay consequences.

Measured mile: Comparison of productivity in affected and relatively unaffected work.

Forensic schedule: Evidence-based schedule analysis prepared to explain causation and entitlement.

Negative float: Calculated shortfall against an imposed date or constraint.

Native schedule file: Original editable file containing logic, dates, calendars and settings.

Review Questions

Short Answer Questions

1. Why is a baseline programme important in delay analysis?
2. Distinguish delay from disruption.
3. What does total float represent?
4. Why is temporal overlap insufficient to prove concurrent delay?
5. State two types of evidence that should be preserved in native or original form.

Long Answer Questions

1. Compare impacted as-planned, time-impact and window analysis methods, including their assumptions and limitations.
2. Explain how critical-path migration affects responsibility analysis.
3. Discuss the relationship between EOT entitlement and prolongation cost entitlement.
4. Explain how a measured-mile productivity analysis should be designed and tested.
5. Describe a complete forensic scheduling workflow from document preservation to expert reporting.

Analytical / Application Questions

1. An employer design release is 15 working days late, but the affected activity has 8 working days of float and a contractor procurement delay consumes 5 working days during the same period. Design a method for determining the likely EOT, identifying the additional facts required.
2. A project finishes on its contractual date but labour-hours are 22% above the estimate because of resequencing and overcrowding. Explain how you would investigate a disruption claim and distinguish it from ordinary estimating error.
3. Two delay events overlap for 10 days, but one affects commissioning and the other affects structural work that had already become non-critical. Analyse whether concurrency exists and justify your conclusion using network logic and evidence.

Multiple Choice Questions with Answers

Question 1

Which statement best describes disruption?

A. A delay that always extends contractual completion

B. Reduced productivity or altered execution efficiency

C. An employer-caused event that always permits compensation

D. The difference between baseline and as-built completion dates

Correct Answer: B. Reduced productivity or altered execution efficiency

Question 2

Which method inserts a delay fragnet into the latest accepted update before the event?

A. As-planned versus as-built

B. Collapsed as-built

C. Time-impact analysis

D. Measured mile analysis

Correct Answer: C. Time-impact analysis

Question 3

If an activity has 5 days of total float and is delayed by 3 days, what is the usual immediate effect, assuming no other changes?

A. Completion is delayed by 8 days

B. Completion is delayed by 3 days

C. Float is reduced to 2 days

D. The activity becomes irrelevant to the network

Correct Answer: C. Float is reduced to 2 days

Question 4

Which evidence is particularly important for checking scheduling logic and calculation settings?

A. A press release

B. A native schedule file

C. An unsigned recollection

D. A completed invoice only

Correct Answer: B. A native schedule file

Question 5

What additional condition is required beyond calendar overlap to establish concurrency?

A. Both events must have the same author

B. Both events must affect the same controlling outcome and be independently causative

C. Both events must last exactly the same number of days

D. Both events must be described in one letter

Correct Answer: B. Both events must affect the same controlling outcome and be independently causative

Question 6

In the productivity formula P = Q ÷ H, what does H represent?

A. Contract price

B. Installed quantity

C. Labour-hours

D. Total float

Correct Answer: C. Labour-hours

Question 7

Which method is generally most capable of recognising changing criticality across successive reporting periods?

A. Window analysis

B. Static as-planned comparison only

C. Invoice comparison

D. Baseline formatting review

Correct Answer: A. Window analysis

Question 8

A contractor-responsible delay normally is classified as which type under a typical contract?

A. Non-excusable delay

B. Compensable excusable delay

C. Neutral excusable delay

D. Employer-risk delay

Correct Answer: A. Non-excusable delay

Question 9

Why should time entitlement and money entitlement be analysed separately?

A. They can never arise from the same event

B. An event may justify time relief but not compensation, or vice versa

C. Money claims do not require evidence

D. Time claims are determined only by software

Correct Answer: B. An event may justify time relief but not compensation, or vice versa

Question 10

What is a principal risk of using as-planned versus as-built analysis alone?

A. It cannot display any dates

B. It may fail to isolate individual causes and can introduce hindsight

C. It requires no baseline

D. It measures productivity directly

Correct Answer: B. It may fail to isolate individual causes and can introduce hindsight