Delay entitlement, concurrency, notice, damages, and available remedies depend on the governing contract and jurisdiction. This guide is technical education, not legal advice.
Key takeaways
- Keep event, entitlement, schedule impact, responsibility, and damages as separate questions until the evidence supports joining them.
- A delay-analysis method must fit the timing, records, schedule quality, contract, and question being answered. No named method is automatically correct in every dispute.
- Contemporaneous schedules and records carry more weight when they are complete, regularly accepted, and preserved with an auditable revision history.
A delay claim contains several different questions
Begin with the event: what happened, when, and what work did it affect? Then test contractual entitlement: was the risk allocated to a party, was notice timely and sufficient, and were contractual procedures followed? Schedule analysis addresses causation and time impact. Cost records address damages. Responsibility, concurrency, mitigation, and legal consequence connect those questions but should not be assumed from one schedule bar.
This separation prevents a common failure: using a schedule calculation to prove a legal conclusion it cannot prove by itself. A fragnet may model five days of impact under stated assumptions. It does not establish that notice was valid, the owner caused the event, the contractor mitigated reasonably, or the claimed costs are recoverable.
Classify delay only after identifying the governing language
Practitioners commonly discuss excusable, non-excusable, compensable, and non-compensable delay. Those labels are useful organizing concepts, but the contract defines the operative categories and remedies. Weather, differing conditions, owner changes, late access, design revisions, labor events, procurement failures, and force-majeure events may receive different treatment under different forms and jurisdictions.
Build an entitlement matrix before calculating days. For each event, record the clause, required notice, actual notice, responsible risk, requested remedy, supporting records, and disputed facts. This keeps the schedule analyst’s assumptions visible and lets counsel or the decision-maker change an entitlement premise without rebuilding the technical chronology from scratch.
Time impact requires a controlling completion condition
For an extension of time, the analysis normally must connect the event to a contractual milestone or completion condition through the controlling network. An event can be serious and costly without delaying completion. It may cause local disruption, resequencing, added resources, or loss of productivity instead. Those effects deserve analysis, but they are not made into critical delay by rhetoric.
Criticality is time-sensitive. Work with float when an event begins can become controlling as float is consumed. A path that appears critical in a final as-built reconstruction may not have been forecast as critical contemporaneously. The analysis should explain the path, float, status, and available mitigation at the relevant time rather than applying one end-of-project path backward to every event.
The record is the foundation of the analysis
Preserve every baseline and update in native form, with the data date, scheduling options, calendars, narrative, transmittal, comments, responses, and acceptance status. Add daily reports, correspondence, meeting minutes, change records, RFIs, submittals, procurement records, photographs, cost records, and resource data as appropriate. A schedule provides the time model; contemporaneous records establish what actually happened and why.
Test reliability before relying on a schedule. If updates contain missing logic, retroactive actuals, unexplained constraints, or extensive after-the-fact changes, document the defects and determine whether they can be corrected, corroborated, or require a different method. An analysis that silently repairs one party’s records can become less defensible than an openly limited analysis.
Prospective and retrospective methods answer different questions
A prospective time-impact analysis inserts a modeled event into an appropriate contemporaneous update to estimate forward impact. It is useful for evaluating a change while options remain, but the result depends on the statused update, fragnet logic, durations, calendars, and assumptions used. Later actual events may differ from the model.
Retrospective methods examine what occurred after the fact. Depending on the records and assignment, an analyst may use observational or modeled techniques, segmented or windows analyses, as-planned versus as-built comparisons, collapsed as-built modeling, or other approaches described in professional guidance. Method selection should follow the question, available records, schedule reliability, timing, and governing requirements—not a preference for the method that produces the largest or smallest answer.
Concurrency and pacing require precise facts
Concurrency is not simply two late activities visible in the same month. The competing delays must satisfy the applicable contract and legal test and affect the relevant completion condition during the same period or in the manner recognized by that test. Analysts should identify each event, responsible party, controlling path, timing, float, and independent effect before applying the label.
Pacing is a deliberate decision to slow work because another controlling delay already removes the need to proceed at the original rate. It can resemble contractor delay in a schedule. The distinction depends on contemporaneous intent, notice, ability to resume, and whether the alleged pacing remained within the available time created by the other event. These are evidence questions, not labels inferred from an as-built bar chart.
Mitigation and acceleration must be modeled and recorded
A party claiming delay should show reasonable mitigation considered or performed. Added crews, shifts, resequencing, alternate procurement, temporary systems, and changed handoffs should appear in the schedule and project record with their assumptions, approvals, costs, and results. A recovery schedule that merely shortens durations without explaining the means is not evidence of executable mitigation.
Acceleration may be directed, constructively required, voluntary, or disputed depending on the facts and contract. Separate the time-extension request, response, instruction, recovery measures, resource changes, productivity effects, and cost records. The schedule can show how the plan was compressed; it cannot alone prove the legal character of the acceleration.
A disciplined evaluation workflow
Define the assignment and questions. Build the contract and entitlement matrix. Inventory and validate the schedules and records. Establish a factual chronology. Select and document the method. Reconstruct or correct data only through transparent rules. Analyze controlling paths and periods, test competing causes, quantify results, and perform sensitivity checks on disputed assumptions.
Report facts, assumptions, limitations, and opinions separately. Cite every important date and input to its source record. Explain why the selected method fits and what alternative assumptions would change. Independent replication should be possible from the retained files. A confident number without a reproducible path is advocacy, not professional analysis.
Worked example
Illustrative event: late owner equipment data
The contractor requests a 20-day extension, alleging that late owner equipment data delayed fabrication. The contemporaneous update preceding the event shows fabrication on a path with 12 workdays of total float; another contractor-controlled design path is forecast to reach the same installation milestone eight workdays later.
- Confirm the contract requirement, required information date, actual transmittal, notices, and the activities the data truly drove.
- Validate the contemporaneous update and model a supported fragnet without changing unrelated logic or durations.
- Test whether the event consumes float, overtakes the parallel design path, or affects contractual completion during the relevant window.
- Analyze the contractor-controlled path independently and apply the governing concurrency test rather than subtracting one headline duration from another.
- Separate any time entitlement from fabrication premium, standby, or acceleration costs and require their own records.
Field-ready control
Delay-claim evaluation checklist
- Define the assignment, contractual milestones, claimed events, period, and requested remedies.
- Build a clause, notice, entitlement, responsibility, and evidence matrix.
- Inventory and validate every baseline, update, narrative, review record, and scheduling option.
- Build a source-cited chronology from contemporaneous project records.
- Select and justify a method suited to the question, timing, data, and governing requirements.
- Analyze path, float, causation, concurrency, pacing, mitigation, and acceleration as separate issues.
- Test disputed assumptions and disclose sensitivity and limitations.
- Separate time entitlement from cost entitlement and preserve a reproducible analysis package.
Common questions
Is a time-impact analysis always the required method?
No. It is commonly used prospectively and may be required by contract, but method selection depends on the assignment, timing, records, schedule quality, contract, and forum. Retrospective disputes may call for a different or supplemented approach.
Does every owner-caused event support an extension of time?
No. The event must satisfy the governing entitlement requirements and affect the relevant contractual completion condition under the applicable analysis. It may instead cause local disruption or cost without delaying completion.
Can the schedule prove responsibility by itself?
No. It can model sequence, status, float, and time effect. Responsibility and entitlement also require the contract, notices, communications, contemporaneous facts, and often legal interpretation.
Sources and scope
Follow the reference trail.
This guide is original educational commentary. Kairos reference records identify the source organizations, editions and scope behind this guidance. The original publishers retain their publications and rights.
10S-90: Cost Engineering TerminologyAACE International · checked 2026-08-01Recommended Practice 29R-03: Forensic Schedule AnalysisAACE International · checked 2026-08-01Delay and Disruption Protocol, second editionSociety of Construction Law · checked 2026-08-01