Delay Notice & Time Impact Analysis

Definition — what it is

A delay notice is the written notification, given within the time and manner the contract requires, that an event has occurred which the contractor contends will delay the work; a time impact analysis (TIA) is the schedule-based method that quantifies how much that event actually extended the project completion date. The two are inseparable in practice: the notice preserves the right to claim, and the analysis proves the entitlement. A TIA models the delaying event as a fragnet inserted into the CPM schedule as it existed at the time of the delay, and recalculates the network to show the effect on the critical path and the completion date. Together they address the three questions every extension turns on — was it timely noticed, did it affect the critical path, and who was responsible. A delay notice is not a claim for damages and a TIA is not a general assertion that the project is late; the notice is a rights-preservation instrument with a hard clock, and the TIA is a rigorous, prospective schedule demonstration, and treating either loosely is how valid entitlements are lost and weak ones are rejected.

Also known as: TIA, Time Impact Analysis, Delay Notice, Extension of Time Request, Schedule Delay Analysis

Why it matters — what it protects

The notice is a rights gate with an unforgiving clock, and missing it forfeits the claim regardless of merit. Contracts almost always require written notice of a delay within a defined window — often a matter of days — and to a specified party, and a contractor who experiences a genuine, compensable delay but fails to give timely notice can lose the entire entitlement on the procedural failure alone. The notice is worth little effort and protects enormous value, which is exactly why it is so often neglected until it is too late.

The TIA is what separates a delay that matters from one that does not. A project can be behind for many reasons, but only delay to the critical path extends the completion date, and only that delay is entitled to time. The TIA proves, using the schedule logic, whether the specific event actually pushed the finish or was absorbed by float, which is the difference between a defensible extension and an unsupported demand that the owner will reject.

It governs money as well as time. Whether a delay is excusable, compensable, or the contractor's own responsibility determines both entitlement to a time extension and entitlement to delay damages or the exposure to liquidated damages. Concurrent delay — where owner and contractor delays overlap — is the hardest and most litigated question, and the analysis is what apportions responsibility when both parties contributed.

It is the discipline that makes a delay claim survive scrutiny. Extension-of-time claims are examined by opposing schedulers, and a TIA built on a manipulated or stale schedule, or one that models the delay retrospectively to reach a desired answer, collapses. The rigor of the method — which schedule was used, how the fragnet was built, whether concurrency was addressed honestly — is what determines whether the entitlement holds, which is why the underlying CPM schedule must be valid and contemporaneous.

Lifecycle — how it moves

1. Delay event and recognition

   An event occurs — a differing site condition, a late owner decision, an unanswered RFI, an unusually severe weather period, an owner-directed change — and is recognized as potentially delaying. The recognition clock is the notice clock; a delay noticed only when it is obvious is often noticed too late.

2. Notice

   Written notice is given within the contractual window, to the specified party, describing the event and reserving the right to a time extension. Notice that is late, informal, or sent to the wrong party can forfeit the claim on procedure alone.

3. Contemporaneous documentation

   The event and its effects are documented as they happen — in daily reports, photos, correspondence, and the schedule — because the analysis will later depend on this record. Reconstructing the facts after the fact is the weakest form of proof.

4. Schedule selection

   The CPM schedule to be impacted is identified — ideally the accepted update in effect just before the delay, reflecting the project as it actually stood. Choosing a stale or manipulated schedule undermines the entire analysis.

5. Fragnet development and insertion

   The delay is modeled as a fragnet — the activities and logic representing the event — inserted into the selected schedule at the point it occurred, with durations and ties defensibly derived from the facts.

6. Recalculation and impact determination

   The network is recalculated to show the effect on the critical path and the completion date, isolating how much of the finish movement the event actually caused versus float it merely consumed.

7. Concurrency and responsibility analysis

   Overlapping delays are examined to apportion responsibility, distinguishing excusable, compensable, and non-excusable delay. This is the most contested step and the one most often done superficially.

8. Submission, negotiation, and resolution

   The analysis and entitlement request are submitted, negotiated, and resolved through a change order, a claim, or dispute resolution. A well-noticed, rigorously analyzed delay resolves far more readily than a late, hand-waved one.

Anatomy — the data it carries

Notice date and recipient

When notice was given and to whom, measured against the contractual window and the specified party. The procedural facts on which the entitlement first survives or dies.

Delay event description

The specific event, when it occurred, and why it is claimed to delay the work, stated factually. Vague characterizations weaken both notice and analysis.

Contract clause basis

The provision under which the extension or compensation is sought — force majeure, differing site conditions, owner-caused delay, changes. Frames whether it is excusable, compensable, or neither.

Impacted schedule and data date

The specific CPM schedule and update used for the analysis. The choice of schedule is scrutinized first; a stale or wrong-data-date schedule is challenged immediately.

Fragnet activities and logic

The activities, durations, and relationships representing the delay and how they tie into the network. The core of the analysis, examined closely by any reviewer.

Critical-path impact

How the completion date and critical path change with the fragnet inserted, isolating finish movement from float consumption.

Float consumption

Whether the delay landed on the critical path or was absorbed by available float, which determines whether any extension is due at all.

Concurrent delay analysis

Any overlapping delays and how responsibility is apportioned between the parties. The most contested element and the one that decides compensability.

Excusable / compensable classification

Whether the delay entitles time only, time and money, or neither, based on the clause and the responsibility analysis.

Time extension and damages claimed

The days of extension sought and any delay damages, tied to the analysis rather than asserted.

Supporting documentation

The daily reports, correspondence, RFIs, photos, and records substantiating the event and its effect. The contemporaneous record the analysis rests on.

Method used

The delay-analysis methodology — time impact analysis, windows, as-planned versus as-built — and why it fits the facts. Method choice is itself contested.

Failure modes — how it breaks

Late or defective notice

The delay is real and the impact is genuine, but notice was given after the contractual window, informally, or to the wrong party. The entitlement is lost on procedure alone, and the most rigorous analysis in the world cannot revive a claim that was never properly noticed.

Impacting a manipulated or stale schedule

The TIA is run against a schedule riddled with hard constraints, open ends, or a wrong data date, or one not updated near the delay. The analysis inherits every flaw of the underlying network, and the opposing scheduler dismantles it by attacking the schedule before ever addressing the delay.

Retrospective analysis reverse-engineered to an answer

Instead of modeling the delay prospectively into the schedule as it stood, the analysis is built backward from the number of days the contractor wants, with a fragnet contrived to produce it. Reviewers recognize the reverse-engineering, and the credibility of the whole submission collapses.

Concurrency ignored or waved away

The analysis claims the full delay while ignoring that the contractor's own late work overlapped the owner's delay. When concurrency is exposed, the compensable portion shrinks or vanishes, and pretending it did not exist damages credibility on every other point.

Delay documented only in the daily report

The event is noted in the daily log and the team assumes their rights are preserved, but the contract required a separate formal notice that was never given. The log documents the event beautifully and preserves nothing, because it did not satisfy the notice clause.

Non-critical delay claimed as if it moved the finish

A delay to an activity with ample float is presented as extending the completion date. The schedule shows the float absorbed the delay entirely, no extension is due, and the claim is rejected because it never established critical-path impact.

Cause not tied to a contract clause

The analysis proves days of delay but never grounds them in a provision that makes them excusable or compensable. A delay the contractor itself caused, however well quantified, entitles it to nothing, and failing to establish the entitlement basis leaves the numbers unattached to any right.

Metrics — how it is measured

Notice timeliness

Whether notice was given within the contractual window and to the correct party. The threshold metric on which entitlement first survives, independent of the delay's merit.

Critical-path impact days

The days of completion-date movement the analysis attributes to the event. The quantified entitlement, distinct from total project lateness.

Concurrency share

The portion of the delay period during which both parties' delays overlapped. Directly reduces the compensable entitlement and is the most scrutinized figure.

Excusable vs compensable split

How the claimed delay divides into time-only and time-and-money entitlement. Determines the financial outcome, not just the schedule outcome.

Schedule validity indicators

The DCMA-style quality of the impacted schedule — open ends, constraints, lags. Weak indicators predict the analysis will be attacked at its foundation.

Documentation sufficiency

Whether the contemporaneous record substantiates the event and its effect. Measures how well the claim will withstand an opposing review.

Resolution outcome ratio

Days granted versus days claimed across resolved delays. A track record indicator of how rigorous and credible the project's delay analyses are.

The AI shift — what actually changes

Conversational

The delay picture becomes something you can interrogate as events unfold rather than reconstruct months later. You ask which current events might require notice and by when under the contract, whether a specific event landed on the critical path in the latest schedule, or how much float a delayed activity had, with the schedule and contract clauses cited so the notice clock is never missed for lack of visibility.

Generative

Building the analysis gains a drafting assistant: from the delay event and the contemporaneous record, a model drafts the delay notice with the contract clause and the required timing, and proposes a candidate fragnet — activities, durations, and logic ties — for insertion into the selected schedule, together with a first-pass narrative, which the scheduler and claims specialist rigorously validate before anything is relied upon.

Orchestrated

The delay instruments stop being standalone. The notice clock is tracked from the event against the contractual window, the analysis is tied to the correct accepted CPM update rather than a stale one, the supporting daily reports, RFIs, and correspondence are assembled around the event, and the resulting entitlement flows into a change event or claim so time and money stay connected to the schedule proof.

Autonomous

The routine motion runs continuously: potential delay events are surfaced from the daily reports, RFI aging, and schedule slippage, and the notice deadline is computed and escalated so it is never missed; the contemporaneous record around each event is assembled; and schedule-validity issues that would undermine an analysis are flagged early, while the notice decision, the fragnet construction, the concurrency judgment, the entitlement classification, and the claim itself remain firmly human — the system prepares and warns, the professionals decide.

Prompts — put it to work

Tool-agnostic and copy-ready. Adapt the specifics — thresholds, contract windows, cost codes — to your own project before you run them.

Conversational — Catching events that need notice before the clock runs out.

Scan our daily reports, RFI log, and latest schedule update for events over the past two weeks that might require a delay notice under our contract, and tell me which notice deadlines are approaching. For each candidate event, give me the date it occurred or was recognized, a factual description, the contract clause that might apply, whether it appears to affect a critical or near-critical activity in the current schedule, and the date by which notice must be given under our notice provision. Rank by how close the notice deadline is, and flag any event where the deadline may already have passed so I can assess the exposure immediately.

What good output looks like: A ranked list of candidate delay events with the applicable clause, critical-path relevance, and the computed notice deadline, surfacing any deadline at risk of being missed, cited to the daily reports, RFI log, and schedule.

Follow-ups:

• Draft the notices for the events whose deadlines are closest.
• Which of these events actually landed on the critical path versus absorbed into float?
• For any deadline that already passed, what are our options?

Generative — Drafting a notice and a candidate fragnet for a specific delay.

Help me prepare a delay notice and a draft time impact analysis for the following event. A differing site condition — undisclosed rock — was encountered during excavation on the date I will give you, requiring additional drilling and blasting. Draft the written notice citing the differing-site-conditions clause, describing the event factually, and reserving our right to an extension of time and associated costs, formatted for the party our contract specifies. Separately, propose a candidate fragnet to model the impact: the added activities, estimated durations from the quantities I will provide, and how they should tie into the excavation logic in our current accepted schedule update. State every assumption explicitly and identify exactly what contemporaneous documentation I must assemble to substantiate this before the analysis can be relied upon.

What good output looks like: A properly grounded draft notice and a candidate fragnet with explicit assumptions and a documentation checklist, presented for the scheduler and claims specialist to validate rather than as a finished analysis.

Follow-ups:

• Which accepted schedule update should we impact, and why that one?
• Model two scenarios and show whether the delay lands on the critical path.
• What concurrency, if any, do our own excavation delays introduce here?

Orchestrated — Assembling the full record behind a delay event.

For the owner-directed change that stopped level 3 work last month, assemble the complete delay record and tie the instruments together. Confirm whether and when a delay notice was given and whether it met the contractual window and recipient; identify the accepted schedule update in effect just before the event as the correct one to impact; gather the daily reports, correspondence, RFIs, and photos from the delay period that substantiate the event and its effect; and identify any overlapping contractor-caused delays in the same window that would raise concurrency. Return a package summary that tells me the strength of the notice, the right schedule to use, the supporting documentation on hand versus missing, and the concurrency exposure, each tied to its record.

What good output looks like: A package summary assessing notice sufficiency, the correct schedule to impact, documentation on hand versus missing, and concurrency exposure, each element cited to its record, with the legal and entitlement judgments reserved for a human.

Follow-ups:

• List exactly what documentation is missing that I need to gather before submitting.
• How does the concurrent contractor delay affect the compensable portion?
• Once validated, open a change event and connect the entitlement to it.

Autonomous — Standing policy for protecting delay rights.

Monitor our project for delay exposure continuously under these rules. Surface potential delay events from the daily reports, RFI aging against activity float, and schedule slippage, and for each compute the notice deadline under our contract and escalate to the project manager well before it expires, so a notice deadline is never missed for lack of visibility. Assemble the contemporaneous record around each candidate event as it accrues. Flag schedule-validity problems — hard constraints, open ends, a stale data date — that would weaken any future analysis, so they are corrected while the schedule is current. Never send a delay notice, never build or finalize a fragnet, never judge concurrency, never classify a delay as excusable or compensable, and never submit a claim; every one of those is a human decision — prepare the material, warn on the deadlines, and route the decisions to the project manager and claims specialist with your reasoning.

What good output looks like: Continuous delay-exposure monitoring that protects notice deadlines and assembles the record, where the notice, the analysis, concurrency, classification, and the claim always remain human decisions, fully audited.

Follow-ups:

• Show me every approaching notice deadline and the record assembled for each event.
• Which schedule-validity issues should we fix now before they undermine a future TIA?

Get the full Construction AI Prompt Catalog — every prompt in the library in one document.

Maturity — locate yourself honestly

0. Level 0 — Reactive and undocumented

   Delays are recognized late, notice is missed or informal, and any analysis is reconstructed after the fact from a stale schedule, so entitlements are routinely lost.

1. Level 1 — Noticed and analyzed

   Notices are given and TIAs are prepared, but the underlying schedule quality, concurrency treatment, and documentation are inconsistent.

2. Level 2 — Rigorous and contemporaneous

   Notices are timely and properly directed, TIAs impact the correct accepted update, concurrency is addressed honestly, and the contemporaneous record is maintained.

3. Level 3 — Assisted

   Candidate events and notice deadlines are surfaced, notices and fragnets are drafted, records are assembled, and schedule-validity issues are flagged for human review.

4. Level 4 — Monitored

   Event detection, deadline protection, record assembly, and schedule-quality flagging run within guardrails, while notice, fragnet construction, concurrency, classification, and claims stay human.

Common questions

What is the difference between excusable, compensable, and non-excusable delay?

A non-excusable delay is one the contractor is responsible for, entitling it to neither time nor money and often exposing it to liquidated damages. An excusable delay is caused by something beyond the contractor's control that is not the owner's fault either — severe weather or a true force majeure event is typical — entitling the contractor to a time extension but usually not to delay damages. A compensable delay is caused by the owner or those it is responsible for, entitling the contractor to both a time extension and its delay costs. Which category a delay falls into is governed by the contract clauses and the responsibility analysis, and it determines the entire financial outcome, not just the schedule.

What is concurrent delay and why is it so contested?

Concurrent delay occurs when an owner-caused delay and a contractor-caused delay overlap in time, each independently affecting the completion date during the same period. It is heavily litigated because it directly reduces what the contractor can recover: courts and contracts vary, but a common outcome is that during true concurrency the contractor may be entitled to a time extension yet barred from delay damages, because it would have been delayed anyway by its own actions. Because concurrency can eliminate the compensable portion of a claim, both sides analyze it aggressively, and an analysis that ignores obvious concurrency loses credibility across the board.

Why must a TIA impact the schedule as it stood at the time of the delay?

Because entitlement depends on whether the event affected the critical path given the project's actual state when it occurred, not the state it started in or ended in. A prospective time impact analysis inserts the delay fragnet into the accepted schedule update in effect just before the event and recalculates forward, which reflects the real conditions, sequence, and float available at that moment. Using a stale baseline, or reverse-engineering the answer into a schedule chosen for convenience, produces a result that does not represent what the delay actually did and that an opposing scheduler will readily dismantle.

If I document a delay thoroughly in my daily reports, is that enough to preserve my claim?

Usually not, and assuming so is one of the most common and costly mistakes in delay management. Daily reports are invaluable contemporaneous evidence, but most contracts require a separate, formal written notice of delay, given within a specific window and to a specified party, to preserve the right to an extension or damages. A delay perfectly documented in the daily log but never formally noticed can be defeated on the procedural failure alone. Document the event in the log and also give the contractual notice; they do different jobs, and only one of them protects the right.