A time impact analysis (TIA) models a delay event in a selected schedule and compares the resulting milestone forecasts with the calculation before the event. The event is represented by a small network of activities, called a fragnet, tied into the existing logic. The difference between the before and after completion dates is the modeled impact of that event.
The result depends on the selected update, event timing, durations, relationships, calendars and scheduling settings. A credible explanation identifies those choices and the records supporting them.
How it works
- Choose the reference schedule. Usually the accepted update with a data date closest to, and before, the start of the event. Its progress should be accurate as of that cutoff.
- Define the event. What happened or is expected to happen, when, and which work it touches, supported by records such as the RFI, the change order or directive, correspondence and daily logs.
- Build the fragnet. New activities with durations and relationships that represent the event, for example “Redesign footing” followed by “Re-submit and approve rebar shop drawings” ahead of “Pour footing F-12”. Record the basis for each duration.
- Insert and recalculate. Tie the fragnet into the reference schedule without changing anything else, then recalculate with the same settings.
- Compare. Measure the change in the contract completion date and key milestones, and identify the path that now drives them.
- Document. Show the before and after schedules, the fragnet, the settings and any assumptions, so another scheduler can reproduce the result.
Because everything else is held constant, the method isolates the event’s modeled effect on that version of the plan. That is its strength and its limit: it shows what the schedule logic predicts, not what actually happened afterwards.
Worked example
Illustrative: an analysis starts with a documented pre-event update with a data date of May 31. The contract completion date is November 14. In that update, the path through “Pour footing F-12” has two working days of total float.
On June 3 the engineer issues a revised footing design. The fragnet adds:
| Fragnet activity | Duration | Logic |
|---|---|---|
| Revise and re-issue footing design | 3 working days | Starts June 3 |
| Revised rebar shop drawings: submit and approve | 2 working days | After the design revision |
| Pour footing F-12 | existing | Now waits for the approved shop drawings |
The fragnet puts five working days ahead of the footing pour. With two days of float available, the completion forecast moves from November 14 to November 19, three working days later, under a simplified model with an unchanged calendar and no competing driving path.
That is a modeled result under stated assumptions, not an automatic three-day time extension. If the contractor was also late on a different critical activity at the same time, the delays may be concurrent. If the contract says float belongs to the project, the owner may argue the first two days were available to absorb the event. Those are contract questions.
TIA vs other delay methods
| Method | Uses | Typical question |
|---|---|---|
| Time impact analysis | Pre-event update plus a fragnet | What does the plan predict this event will do? |
| Prospective TIA | The same approach, done while the work is still ahead | How much time should a change order include? |
| Windows analysis | Successive updates over the project | Which path drove delay in each period? |
| As-planned vs as-built | Baseline and actual dates | How did the plan compare with what happened? |
AACE’s forensic schedule analysis practice classifies TIA-style approaches as modeled, additive methods, applied to a single base schedule or to several updates in turn. The delay analysis methods guide compares them in more detail.
What a reviewer needs
- The original reference file and its data date.
- The event activities, their relationships, and the basis for each duration.
- The calculation settings and a clear account of any other changes.
- The before-and-after milestone comparison and affected path.
- The records needed to assess contractual requirements separately.
An event lasting five days does not necessarily cause five days of completion delay. Similarly, a modeled completion impact does not determine responsibility, notice compliance or compensation. Those questions need the contract and supporting evidence.
Common mistakes
- Using a stale update whose progress no longer reflects the site at the time of the event.
- Changing other things in the impacted run, such as durations or calendars, so the difference isn’t only the event.
- Fragnet durations with no basis, or durations that include the contractor’s own delays.
- Ignoring float, either by assuming every day of event duration becomes a day of delay, or by ignoring negative float already in the update.
- Skipping concurrency. If another delay was driving completion at the same time, the modeled impact may overstate the event.
- Treating the output as entitlement, without checking notice provisions, risk allocation and no damages for delay clauses.
- Never checking against the as-built record when the analysis is done after the fact.
Read the worked time impact analysis guide, see how concurrent delay is tested, or explore the Schedule Forensics learning hub.
This is general information, not legal advice. Delay entitlement depends on the contract and the governing law.
FAQ
What is a time impact analysis?
A time impact analysis (TIA) models a delay event by inserting a small network of activities, called a fragnet, into a schedule update that represents the project just before the event. The schedule is recalculated, and the change in the forecast completion or milestone dates is the modeled impact of that event.
What is a fragnet?
A fragnet, short for fragmentary network, is the set of new or changed activities and relationships that represent an event, such as a design change, a late owner decision or a differing site condition. It is tied into the existing schedule logic at the points where the event affects the work.
Is a time impact analysis prospective or retrospective?
It is most often used prospectively, to estimate the effect of an event while the work is still ahead, which is how many contracts expect time extension requests to be supported. It can also be applied after the fact, but then the modeled result should be checked against what actually happened.
Does a TIA prove entitlement to a time extension?
No. A TIA estimates the schedule effect of an event under stated assumptions. Entitlement also depends on the contract: who bears the risk of the event, whether notice was given on time, whether there was concurrent delay, and what the contract says about float. Those questions need the contract and the evidence.
What standards describe time impact analysis?
AACE International Recommended Practice 52R-06 covers prospective time impact analysis, and RP 29R-03 on forensic schedule analysis classifies modeled methods, including the additive approaches a TIA uses. In the UK, the Society of Construction Law's Delay and Disruption Protocol discusses time impact analysis among its delay analysis methods.