Delay Analysis, Change, Claims, and Forensic Scheduling

Introduction

Construction projects rarely proceed exactly as originally planned. Design information may be issued late, ground conditions may differ from those assumed, owners may change requirements, resources may become unavailable, or unusually severe weather may affect productivity. The planning professional must distinguish the event itself from its effect on time, cost, productivity, and contractual entitlement.

Delay analysis is therefore more than comparing two dates. It requires a reliable programme, contemporaneous evidence, a clear cause-and-effect relationship, and an understanding of contractual risk allocation. This chapter examines delay, disruption, acceleration, float, concurrency, change, claims, and the principal prospective and retrospective methods used in professional practice.

Learning Objectives

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

1. Distinguish delay, disruption, acceleration, critical delay, and concurrent delay.
2. Explain float ownership and the significance of the critical path.
3. Identify the records required for reliable delay and claims analysis.
4. Assess the schedule effects of changes and delay events.
5. Compare prospective and retrospective delay-analysis methods.
6. Explain the professional, contractual, ethical, and technological implications of forensic scheduling.

1. Fundamental Concepts

1.1 Delay

Delay is the postponement of an activity, milestone, or project completion date relative to an approved or contractually relevant baseline. An activity can be delayed without delaying project completion if it has available float. Conversely, a relatively short delay to a critical activity may delay completion significantly.

Delay may be classified by responsibility and entitlement:

• Excusable delay: A delay for which the contract permits relief, commonly an extension of time. It may be compensable or non-compensable.
• Compensable delay: Usually a delay caused by the owner or another risk allocated to the owner, entitling the contractor to time and, subject to the contract, money.
• Non-compensable excusable delay: An excusable event, such as some forms of exceptionally adverse weather, that may justify time relief but not additional payment.
• Inexcusable delay: Delay for which the contractor bears responsibility and normally receives no time relief; damages may arise under the contract.
• Critical delay: Delay that affects the contractual completion date or another contractually significant milestone.

The classification depends on the contract, governing law, facts, and evidence. A label alone does not establish entitlement.

1.2 Disruption

Disruption is a reduction in the efficiency or productivity of planned work. It may occur even when the completion date is unchanged. Examples include out-of-sequence work, repeated remobilisation, overcrowded work areas, excessive inspection requirements, design revisions, trade interference, and fragmented access.

Delay concerns when work finishes; disruption concerns how efficiently it is performed. A project may suffer both. For example, a late structural design may delay steel erection and also cause multiple work stoppages that reduce labour productivity.

1.3 Acceleration

Acceleration is an instruction, agreement, or imposed condition requiring work to finish earlier than the contractor’s planned or contractually required completion date, or requiring recovery of delay. Acceleration may be:

• Directed acceleration: expressly instructed by the owner.
• Constructive acceleration: arises when the contractor is entitled to additional time, but the owner refuses or fails to grant it and nevertheless insists on the original date.
• Voluntary acceleration: undertaken by the contractor without an established owner obligation, often to protect a commercial objective.

Acceleration measures may include overtime, additional shifts, extra crews, prefabrication, resequencing, additional plant, or premium procurement. The cost and effectiveness of each measure should be documented rather than assumed.

1.4 Change

A change is a modification to the scope, quality, sequence, quantities, method, or timing of the contracted work. Changes may be initiated by an owner instruction, design development, regulatory requirement, differing site condition, or a contractor proposal.

A change can produce:

• direct additional or reduced work;
• delay to the changed activity;
• disruption to unaffected work;
• resequencing and loss of productivity;
• procurement or approval effects; and
• acceleration pressure.

A change is not automatically a claim. A claim arises when a party asserts a contractual or legal entitlement that is not resolved through ordinary project administration.

2. Critical Path, Float, and Concurrency

2.1 Critical path

The critical path is the sequence of logically connected activities that controls the earliest possible completion date under the analysed programme. In a simple activity network, total float may be expressed as:

where TF is total float, ES is early start, EF is early finish, LS is late start, and LF is late finish. All values use the same time unit, such as days. The relationship assumes a logically consistent network and a forward and backward pass using the same calendar and durations.

Activities with zero or near-zero float are often critical, but the practical critical path may change as actual progress, logic, calendars, and constraints change. A schedule should therefore be analysed dynamically rather than treated as a permanent prediction.

2.2 Float ownership

Float is the time available before an activity delays a successor or project milestone. Contracts may address float expressly. Common interpretations include:

• Total float is project float: either party may use it, provided the contractual completion date is protected.
• Contractor-owned float: the contractor may use it for its own planning purposes, subject to contractual limitations.
• First-come, first-served: the party whose event first consumes float may effectively obtain its benefit.
• Shared or silent contractual treatment: ownership is unresolved and may require interpretation under the contract and applicable law.

The prudent scheduler should not assume that float belongs automatically to the contractor or owner. The contract, accepted programme, amendments, and governing legal principles must be reviewed.

2.3 Concurrent delay

Concurrent delay exists when two or more independent delay events overlap in time and both affect a critical completion date, with at least one event attributable to each party. Mere simultaneous occurrence is insufficient. The events must be causally connected to critical delay during the same relevant period.

Important questions include:

1. Did each event actually affect a critical path?
2. Did the effects overlap, or did one event finish before the other became critical?
3. Can the effects be separated by reliable evidence?
4. Does the contract define the consequences of concurrency?
5. Does governing law apply a “true concurrency” or “dominant cause” approach?

Concurrent delay can affect entitlement to time, compensation, or damages differently. Students should avoid universal conclusions because legal outcomes vary by jurisdiction and contract wording.

3. Evidence and Contemporaneous Records

A defensible analysis begins with records created during the work, not with a narrative prepared after a dispute has developed. Important records include:

• approved baseline and update programmes;
• schedule narratives and change logs;
• daily reports, labour and plant records;
• drawings, specifications, requests for information, and responses;
• submittal, procurement, and approval registers;
• site instructions, variation orders, and meeting minutes;
• photographs, surveys, delivery tickets, and inspection records;
• weather and site-condition records;
• correspondence concerning notice, access, productivity, and mitigation;
• payment records, timesheets, and cost ledgers; and
• records of mitigation, acceleration, and rejected alternatives.

Records should identify dates, responsible parties, affected locations, activities, resources, and observed consequences. A daily report stating “work delayed” is weak evidence unless it explains what prevented work, when the prevention occurred, and which activities were affected.

Notice provisions are particularly important. A contract may require notice within a specified period, followed by particulars and continuing updates. Failure to comply may restrict entitlement, although the outcome depends on the contract and applicable law. Project teams should maintain a notice register linking each event to relevant correspondence, programme updates, cost records, and decisions.

4. Schedule Impact Assessment

A schedule impact assessment links an event to a measurable change in planned performance. A sound analysis normally follows these steps:

1. Define the event: identify its cause, start date, end date, location, and responsible party.
2. Confirm the contractual test: determine notice, causation, time-bar, mitigation, and valuation requirements.
3. Select the appropriate programme: use the accepted baseline or a reliable contemporaneous update.
4. Establish the affected logic: identify predecessor, successor, resource, calendar, and constraint relationships.
5. Insert or model the event: represent the event and its logical consequences without rewriting unrelated work.
6. Measure the result: compare completion, milestones, float, and affected activities before and after the event.
7. Test alternatives: consider mitigation, resequencing, concurrency, and changes in the critical path.
8. Document assumptions and conclusions: explain data gaps, methods, and confidence limits.

A simplistic comparison between the original completion date and actual completion date does not prove causation. Actual late completion may result from contractor delay, owner delay, neutral events, changes, or a combination.

Worked example: critical and non-critical delay

Suppose a baseline contains the following path:

The planned completion is day 50. If an owner instruction delays activity B by 5 days, and no mitigation is possible, the controlling path becomes 55 days and completion moves to day 55. The event produces 5 days of critical delay.

Now suppose an independent activity E has 8 days of total float. A 5-day delay to E moves its finish within its available float and does not change project completion. It is an activity delay, but not a critical project delay. If a later event consumes 4 days of E’s remaining float, the combined effects may become critical. This illustrates why delay analysis must consider the programme status at the time of each event.

5. Prospective and Retrospective Methods

5.1 Prospective methods

Prospective analysis evaluates the likely effect of a known or anticipated event using the programme status existing when the event occurred or was instructed. It supports timely extension-of-time decisions and project administration.

#### Time impact analysis

A time impact analysis inserts a carefully modelled “fragnet”—a small network representing the event—into the latest accepted update before the event. The analyst then recalculates the schedule and observes the effect on completion and float. The method is strongest when:

• updates are regularly prepared and accepted;
• logic and progress status are reliable;
• the fragnet represents the actual event; and
• the analysis is performed close to the event date.

It becomes weaker when the update is inaccurate, logic has been manipulated, or the event is modelled after the fact using information unavailable at the time.

#### Impacted as-planned analysis

This method adds delay activities to the original baseline and observes the theoretical effect. It is relatively simple but may ignore actual progress, changed logic, resequencing, and critical-path changes. It is most suitable for preliminary assessment where reliable updates are unavailable, not as an automatic substitute for a contemporaneous analysis.

5.2 Retrospective methods

Retrospective analysis examines what actually occurred, using updates, records, as-built information, and contemporaneous communications.

#### As-planned versus as-built

The baseline is compared with actual start and finish dates. The method identifies deviations but does not, by itself, establish causation. It is useful as an overview and for identifying periods requiring deeper analysis.

#### Windows analysis

The project is divided into time windows, often monthly or by significant events. For each window, the analyst reviews the current critical path, progress, delays, changes, and completion forecast. Windows analysis can capture shifting critical paths and interaction among events.

#### As-built critical path analysis

This method reconstructs the critical path using actual dates and logic. It may be valuable where reliable as-built information exists, but reconstruction involves judgement. Actual sequence does not always prove that the sequence was logically controlling at the time.

#### Collapsed as-built or “but-for” analysis

The analyst removes selected delay events from the as-built programme and recalculates a hypothetical completion date. The difference is presented as the effect of those events. This method can illustrate causation, but it is sensitive to assumptions, retrospective logic changes, and the difficulty of removing one event from a history containing interdependent effects.

No method is universally superior. Selection should reflect the contract, available records, project complexity, dispute requirements, and the question being answered.

6. Claims and Forensic Scheduling

A claim should be structured as a reasoned chain:

Entitlement → Event → Causation → Effect → Quantum → Mitigation.

• Entitlement: What contract clause or legal principle provides relief?
• Event: What occurred, and when?
• Causation: How did it affect the work?
• Effect: What time, productivity, or cost consequence followed?
• Quantum: How is the amount calculated and supported?
• Mitigation: What reasonable steps were taken to avoid or reduce the effect?

Forensic scheduling is the disciplined examination of programme records and project facts for dispute resolution, negotiation, adjudication, arbitration, or litigation. The forensic scheduler should remain independent, distinguish fact from opinion, disclose assumptions, preserve original files, and avoid advocacy disguised as analysis.

Schedule quality also matters. A forensic conclusion is only as reliable as the schedule’s calendars, logic, constraints, actual dates, and status information. Excessive mandatory constraints, unexplained out-of-sequence progress, negative float, open ends, and unreasonably long activities may signal weak planning or deliberate manipulation.

7. Change, Disruption, and Productivity Analysis

The time effect of a change should be separated from its productivity effect where possible. A revised quantity may extend duration through additional work, while a design revision may also create idle labour, remobilisation, or work-area interference.

Common disruption approaches include:

• Measured mile: compares productivity during an unaffected period with productivity during an affected period performing comparable work.
• Earned-versus-actual labour analysis: compares labour hours used with hours associated with measured or earned quantities.
• Industry or published productivity factors: may provide context but are weaker than project-specific records.
• Project-planned productivity comparison: compares actual performance with the contractor’s planned production rate, subject to proving that the plan was realistic.

The measured-mile approach is conceptually expressed as:

The rates must use consistent units, such as labour-hours per cubic metre, and the affected and unaffected work should be sufficiently comparable. The formula is not valid if the periods differ materially in crew composition, work complexity, access, weather, or scope without adjustment.

8. Illustrative Case: Late Design and Concurrent Contractor Delay

The following is a fictional illustrative case.

Background

A university laboratory project has a contract completion date of 30 June. The accepted update at the start of March shows mechanical installation on the critical path. The owner issues revised laboratory-service drawings on 10 March, and the contractor cannot complete affected installation for 12 calendar days.

At the same time, the contractor has a documented procurement problem: specialist valves ordered late are unavailable for 8 of those 12 days. The contract contains an extension-of-time clause for owner changes and requires mitigation. It does not clearly define concurrency.

Analysis

The analyst first verifies that mechanical installation was critical in the 1 March update. The drawing revision is modelled as a fragnet in that update. The procurement delay is separately modelled using contemporaneous purchase orders, delivery records, and site reports.

The evidence shows that the owner’s drawing delay prevented installation for days 1–12. The valve shortage independently prevented installation for days 1–8, but only in one work zone; other zones could have proceeded. The analysis therefore avoids assuming that the two events have identical effects. It examines location, available work fronts, logic, and actual crew movement.

Approach and outcome

A windowed analysis shows that the owner event delayed the controlling laboratory-system milestone by 6 days after mitigation and resequencing. The contractor’s valve shortage caused 3 days of critical effect in a separate zone, but its critical effect overlaps only 2 days with the owner event. The contractual consequence cannot be decided by schedule analysis alone; it depends on the concurrency clause and applicable law. The project team should record the owner-related time effect separately from contractor-caused delay and avoid claiming the entire 12-day period without proof.

Learning points

1. An event’s duration is not necessarily its critical delay.
2. Concurrency requires analysis of critical effect, not merely overlapping dates.
3. Mitigation and alternative work fronts must be tested.
4. Separate owner-caused time, contractor-caused time, and neutral effects.
5. Contract interpretation remains essential even after the schedule facts are established.

9. Professional Practice, Governance, and Technology

Schedule analysts should preserve original programme files, maintain version control, record data dates, and make changes traceable. Ethical practice requires balanced treatment of favourable and unfavourable evidence. Selectively deleting updates or presenting a chosen critical path without explaining alternatives undermines professional credibility.

Scheduling software can rapidly perform logic calculations, compare updates, and identify changes in float. However, software does not determine contractual entitlement or prove causation. Artificial intelligence may assist with document classification, correspondence searches, anomaly detection, and extraction of dates from records. Human review remains necessary because scanned documents may be incomplete, project terminology may be ambiguous, and an algorithm may confuse a forecast with an actual event. Governance should include audit trails, data security, validation, and disclosure of material assumptions.

Contemporary good practice increasingly integrates 4D models, common data environments, electronic field records, drone imagery, and mobile progress capture. These tools improve evidence only when data is consistently collected, time-stamped, georeferenced where appropriate, and linked to the schedule and work breakdown structure.

10. Best-Practice Workflow

A practical workflow for delay and claims management is:

1. Establish an approved, logic-linked baseline.
2. Update progress regularly using defined status rules.
3. Record events immediately and issue notices under the contract.
4. Link each event to affected activities, locations, resources, and documents.
5. Preserve original schedule files and revision histories.
6. Analyse criticality at the relevant data date.
7. Separate delay, disruption, change, and acceleration claims.
8. Assess concurrency and mitigation explicitly.
9. Select a method appropriate to the question and evidence.
10. Present conclusions with assumptions, limitations, and supporting records.

Challenges and Limitations

Delay analysis is limited by incomplete records, unreliable baselines, changed logic, uncertain actual dates, multiple causative events, and inconsistent definitions of completion. Float may be consumed without clear contractual rules. Retrospective analysis may be influenced by hindsight, while prospective analysis may rely on forecasts that later prove inaccurate. Productivity analysis is especially sensitive to differences in scope, crew, access, weather, and learning effects.

Accordingly, an expert opinion should express appropriate confidence rather than false precision. A conclusion such as “the evidence supports approximately six critical days, subject to the contract’s concurrency rule” is often more defensible than an unsupported claim of exactly twelve days.

Chapter Summary

Delay analysis connects contract requirements, programme logic, project records, and cause-and-effect reasoning. Delay concerns time; disruption concerns productivity; acceleration concerns achieving an earlier or maintained date through additional effort; and change modifies scope, sequence, or conditions. Critical delay affects a contractual milestone, while non-critical delay may consume float without changing completion.

Reliable analysis requires contemporaneous records, a sound baseline, regular updates, transparent logic, and explicit treatment of mitigation and concurrency. Prospective methods, particularly time impact analysis, support timely administration. Retrospective methods, including windows analysis and collapsed as-built analysis, investigate what actually occurred. No method is automatically correct; its suitability depends on the evidence and contractual question.

Claims should establish entitlement, event, causation, effect, quantum, and mitigation. Professional integrity requires preservation of records, disclosure of assumptions, and separation of factual analysis from advocacy. Digital tools and AI can improve processing and evidence management, but they cannot replace engineering judgement or contractual interpretation.

Key Terms

Acceleration: Measures intended to achieve an earlier or maintained completion date.

As-built programme: A record or reconstruction of actual project progress and sequence.

Baseline programme: The approved reference schedule against which progress and change are assessed.

Claim: An assertion of contractual or legal entitlement requiring determination or agreement.

Concurrent delay: Overlapping independent delay events, usually attributable to different parties, that affect critical completion.

Critical delay: Delay that affects a contractual completion date or milestone.

Critical path: The controlling sequence of activities determining the earliest completion date.

Disruption: Loss of planned productivity or efficiency.

Excusable delay: Delay for which the contract may grant time relief.

Float: Time available before an activity or path affects a successor or milestone.

Fragnet: A small network inserted into a programme to represent an event and its logic.

Forensic scheduling: Examination of schedule evidence for dispute resolution or expert analysis.

Impacted as-planned analysis: A method that adds event activities to the baseline programme.

Measured mile: A productivity comparison between comparable unaffected and affected work.

Mitigation: Reasonable action taken to avoid, reduce, or limit loss.

Prospective analysis: Evaluation made using information available when an event occurs or is anticipated.

Retrospective analysis: Examination of completed work and records after events have occurred.

Time impact analysis: Prospective insertion of an event fragnet into a contemporaneous schedule update.

Total float: The calculated time an activity may be delayed without delaying the relevant completion date, subject to schedule assumptions.

Review Questions

Short Answer Questions

1. Distinguish delay from disruption.
2. What is meant by critical delay?
3. Identify three records useful in a delay analysis.
4. Define a fragnet.
5. Why does float ownership matter?

Long Answer Questions

1. Explain the differences among excusable, compensable, non-compensable, and inexcusable delay.
2. Compare time impact analysis, windows analysis, and collapsed as-built analysis.
3. Explain why concurrency cannot be established merely by showing overlapping dates.
4. Describe the relationship among change, disruption, acceleration, and claims.
5. Discuss ethical and governance requirements for forensic scheduling.

Analytical / Application Questions

1. A design change delays a critical activity by 7 days, but the contractor had a 4-day procurement delay during the same period. Explain the investigations required before allocating time entitlement.
2. A non-critical activity has 10 days of float and is delayed by 6 days. A later owner change consumes the remaining 4 days. Analyse how the events may become critical.
3. A contractor claims 20% productivity loss using industry data, but project records show comparable unaffected work. Recommend an appropriate analysis method and identify the evidence required.

Multiple Choice Questions with Answers

Question 1

Which condition best describes critical delay?

A. Any activity finishes later than planned

B. Delay that affects a contractual completion date or milestone

C. Any delay caused by the contractor

D. A delay that consumes less than available float

Correct Answer: B. Delay that affects a contractual completion date or milestone

Question 2

What does disruption primarily describe?

A. A change in contract ownership

B. A reduction in work productivity or efficiency

C. A revised completion date only

D. A contractor’s failure to submit a programme

Correct Answer: B. A reduction in work productivity or efficiency

Question 3

In a time impact analysis, what is generally inserted into a contemporaneous schedule update?

A. A cost ledger

B. A fragnet representing the delay event

C. A new contract

D. A weather forecast only

Correct Answer: B. A fragnet representing the delay event

Question 4

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

A. Project completion is delayed by 5 days

B. Project completion is delayed by 13 days

C. The activity uses 5 days of float and completion need not change

D. The activity becomes automatically compensable

Correct Answer: C. The activity uses 5 days of float and completion need not change

Question 5

Which statement about concurrent delay is most accurate?

A. Any two events occurring in the same month are concurrent

B. Only contractor-caused events can be concurrent

C. The events must have overlapping effects on a critical completion path

D. Concurrency is determined solely by cost records

Correct Answer: C. The events must have overlapping effects on a critical completion path

Question 6

Which method compares productivity during affected work with comparable unaffected work?

A. Measured mile

B. Impacted as-planned

C. Collapsed as-built

D. Forward pass

Correct Answer: A. Measured mile

Question 7

Which item is part of a well-structured claim?

A. Entitlement and causation

B. A preferred software brand only

C. An unsupported estimate of inconvenience

D. A replacement baseline with no revision history

Correct Answer: A. Entitlement and causation

Question 8

What is the principal weakness of a simple as-planned versus as-built comparison?

A. It cannot show any date differences

B. It does not by itself establish causation

C. It requires no project records

D. It can only be used prospectively

Correct Answer: B. It does not by itself establish causation

Question 9

A contractor is instructed to complete by the original date even though an owner-caused event justifies additional time. This situation may constitute:

A. Constructive acceleration

B. Non-critical float

C. Measured-mile analysis

D. An as-built baseline

Correct Answer: A. Constructive acceleration

Question 10

Which practice best supports forensic schedule reliability?

A. Deleting superseded schedule files

B. Changing logic without recording the reason

C. Preserving original files and documenting assumptions

D. Using only the final completion date

Correct Answer: C. Preserving original files and documenting assumptions