Time Impact Analysis in Construction: A Practical Guide for Contractors and Developers

Every construction project runs late in some way. Drawings arrive after the date they were promised, a utility diversion takes longer than planned, the client adds a floor, or a supplier misses a delivery window. The question is never really whether delays will happen, but who carries the cost and the time when they do. That is where a Time Impact Analysis (TIA) comes in.

In this guide we explain what a Time Impact Analysis is, when it should be used, how to prepare one step by step, and the mistakes that most often cause extension of time (EOT) claims to fail. It is written for contractors, developers, project managers and planners working on building and infrastructure projects across the Gulf, the Levant, the Mediterranean and beyond.

What Is a Time Impact Analysis?

A Time Impact Analysis is a forward-looking (prospective) delay analysis method. It measures how a specific delay event affects the project completion date by inserting a model of that event into the most recent accepted programme and recalculating the critical path.

Put simply, a TIA answers one question: “If this event happens, how much later will we finish?” The difference between the forecast completion date before the event and after the event is the time impact, and it forms the basis of an extension of time request.

The fragnet: the heart of every TIA

The delay event is modelled as a fragnet (short for “fragmentary network”): a small group of new activities and logic links that represent the event. For example, a late instruction to change façade panels might be modelled as three activities, “Instruction received”, “Redesign and approval of panels” and “Procurement of revised panels”, each with durations and linked into the existing façade installation activity.

When the fragnet is inserted into the programme and the schedule is recalculated, the software shows whether the event pushes out the completion date, and by how much.

Prospective versus retrospective analysis

A TIA is ideally prepared at the time of the event, using the programme that was current just before it occurred. This makes it a prospective method. It can also be used retrospectively, after the event has finished, but in that case it predicts what should have happened rather than what actually happened, which is a common point of challenge in disputes.

Why Time Impact Analysis Matters

The TIA is the method preferred by many standard contracts and industry guidance, including the Society of Construction Law (SCL) Delay and Disruption Protocol, for dealing with extension of time applications during the project. There are several reasons for this:

  • It is contemporaneous. Time is assessed while the project is running, so decisions on resources, acceleration and sequencing can be made with real information.
  • It is transparent. Both the contractor and the engineer or employer’s representative can see exactly which activities were added and how they affect the critical path.
  • It protects both parties. The contractor avoids liquidated damages for delays it did not cause, and the employer preserves its right to impose a revised completion date that is fair and defensible.
  • It reduces disputes. Claims that are assessed and agreed as they arise are far less likely to accumulate into a large global claim at the end of the project.

When Should You Use a Time Impact Analysis?

A TIA is most useful in the following situations:

1. During the project, for each significant delay event

Under FIDIC 2017 (Sub-Clause 20.2) the contractor must give notice of a claim within 28 days of becoming aware of the event and then submit a fully detailed claim within 84 days. A TIA is the natural way to substantiate the time element of that detailed claim.

2. When the contract requires a “prospective” assessment

Many contracts, particularly in the Middle East, require the extension of time to be assessed based on the programme at the time of the event. A TIA directly satisfies that requirement.

3. When the baseline and updates are reliable

A TIA is only as good as the programme it is built on. If the project has an accepted baseline programme and regular, well-maintained updates, a TIA is the right choice. If the programme is poor or was never accepted, another method, such as an as-planned versus as-built analysis, may be more realistic.

When a TIA may not be the best tool

After a project is finished and the actual delays are known, tribunals often prefer methods that reflect what really happened, such as a windows analysis or a collapsed as-built analysis. In those cases a TIA can still be useful, but it should be supported by as-built records.

How to Prepare a Time Impact Analysis: Step by Step

The following process reflects good practice under the SCL Protocol and is the approach we use at Stavitelia when preparing or reviewing EOT submissions.

Step 1: Identify the delay event and give notice

Define the event clearly: what happened, when it started, who is responsible under the contract, and which contract clause gives entitlement. Issue the contractual notice immediately. Missing a notice deadline can extinguish an otherwise valid claim, regardless of how good the analysis is.

Step 2: Select the correct programme

Choose the most recent accepted programme update before the event occurred. Check that it has been progressed to a data date close to the event and that the logic is sound, with no open ends, excessive constraints or negative float that would distort the results.

Step 3: Build the fragnet

Model the event as a set of activities with realistic durations and logical links. Base durations on records, such as correspondence, RFIs, instructions, supplier quotations and method statements, rather than on opinion. Keep the fragnet simple: it should represent only the event, not the contractor’s own inefficiencies.

Step 4: Insert the fragnet and reschedule

Insert the fragnet into a copy of the selected programme, link it to the affected activities and recalculate the schedule. Record the forecast completion date before and after insertion.

Step 5: Measure and explain the impact

The difference between the two completion dates is the time impact. Explain which path became critical and why. If the event only consumed float and did not affect completion, say so: under most contracts the contractor is not entitled to an extension in that case, unless the contract states that float belongs to the contractor.

Step 6: Check for concurrency

Review whether any contractor-caused delay was running at the same time on the critical path. Concurrent delay is treated differently under different contracts and jurisdictions. The SCL Protocol suggests that where true concurrency exists the contractor should receive time but not money for the overlapping period. Address concurrency openly in the submission; ignoring it is one of the fastest ways to lose credibility.

Step 7: Prepare the submission

A strong TIA submission typically includes:

  • A narrative describing the event, the entitlement clause and the notices issued.
  • The programme used, with its data date and acceptance status.
  • The fragnet, with the source of each duration.
  • Before and after schedule printouts and the critical path comparison.
  • The extension of time requested and, where relevant, the associated prolongation costs.
  • All supporting records, indexed and cross-referenced.

A Simple Worked Example

Consider a 24-month residential tower with a contractual completion date of 30 June. In month 9 the employer instructs a change to the structural design of the podium transfer slab.

  1. The latest accepted update (data date 31 March) forecasts completion on 30 June, with the transfer slab on the critical path.
  2. The fragnet includes “Revised design by employer’s consultant” (21 days), “Engineer’s approval” (14 days) and “Additional reinforcement procurement” (10 days), linked before “Pour transfer slab”.
  3. After rescheduling, the forecast completion moves to 4 August, a time impact of 35 days.
  4. A review shows no contractor delays on the critical path during the same period, so there is no concurrency.
  5. The contractor requests a 35-day extension of time and the associated time-related costs, supported by the instruction, design submissions and supplier quotations.

Because the analysis is clear and based on the accepted programme, the engineer can verify it quickly and make a fair determination, rather than letting the issue escalate.

Common Mistakes That Weaken a TIA

Using an unreliable programme

If the baseline was never accepted or the updates have broken logic, the results can be dismissed as unreliable. Fix programme quality issues first, and disclose any corrections you make.

Inflated fragnet durations

Durations that are not backed by records invite rejection. Every duration should be traceable to a document.

Ignoring mitigation

Contractors generally have a duty to take reasonable steps to mitigate delay. Show what was done, such as resequencing, adding resources or working extra shifts, and how it was reflected in the analysis.

Late notices

Under FIDIC 2017 the 28-day notice period is a condition precedent. A perfect TIA cannot rescue a claim where notice was never given in time.

Treating the TIA as a one-off

Delay events interact with each other. Each new TIA should be inserted into the programme that already includes previously agreed events, so that the analysis builds a consistent picture over the life of the project.

Time Impact Analysis and Other Delay Analysis Methods

The TIA is one of several recognised methods. The right choice depends on the timing of the analysis, the quality of the records and the requirements of the contract.

  • As-planned versus as-built: compares the original plan with what actually happened. Simple, but weak at proving causation.
  • Impacted as-planned: inserts delays into the baseline programme only. Quick, but often criticised for ignoring actual progress.
  • Windows (time slice) analysis: examines the project in periods using contemporaneous updates. Strong for retrospective claims.
  • Collapsed as-built (but-for): removes delay events from the as-built programme to see when the project would have finished. Useful when no reliable baseline exists.

Many successful claims use a TIA during the project and a windows analysis afterwards to confirm the results with actual data.

Practical Tips for Contractors and Developers

  • Invest in the baseline. A well-built, accepted baseline programme is the foundation of every future time claim.
  • Update monthly. Regular updates with accurate progress and documented logic changes make each TIA faster and more credible.
  • Keep a delay register. Log every potential event, its notice date and its status so nothing falls through the cracks.
  • Record everything. Daily reports, site photos, RFIs and minutes are the evidence that turns an analysis into an entitlement.
  • Get an independent review. A second pair of eyes, from a planner or claims consultant who was not involved day to day, often spots logic errors and weak points before the engineer does.

Frequently Asked Questions About Time Impact Analysis

How long does it take to prepare a TIA?

For a single, well-defined event on a project with a reliable programme, a TIA can often be prepared in a few days. Complex events, poor programme quality or missing records can extend this to several weeks, which is why good record keeping from day one matters so much.

Which software is used for a Time Impact Analysis?

Most TIAs are prepared in Oracle Primavera P6 or Microsoft Project, as these are the tools commonly specified for contract programmes. The method itself does not depend on the software; what matters is that the programme logic is transparent and the fragnet can be reviewed by the other party.

Does a TIA prove entitlement to money as well as time?

No. A TIA demonstrates the effect of an event on the completion date. Entitlement to additional payment depends on the contract clause relied on and must be supported separately, usually with records of time-related costs such as site overheads, supervision and equipment.

Can the engineer reject a TIA?

Yes. The engineer may challenge the programme used, the fragnet durations, the logic or the treatment of concurrency. A clear, record-based submission makes rejection far less likely and gives a solid foundation if the matter later goes to a dispute board or arbitration.

Conclusion

A well-prepared Time Impact Analysis is one of the most effective tools for managing delay on a construction project. It turns a disagreement about dates into a transparent, evidence-based calculation that both parties can test. For contractors it protects against unfair liquidated damages; for developers it provides a defensible basis for adjusting the completion date and controlling cost.

The key ingredients are always the same: timely notices, a reliable programme, a fragnet built from records, an honest treatment of concurrency and mitigation, and a clear submission.

Need help with a delay or extension of time claim? Stavitelia prepares and reviews Time Impact Analyses, FIDIC claims and delay assessments for contractors and developers. Book a call to discuss your project.

Get new guides by email

Join the Stavitelia Insights newsletter: practical notes on delay analysis, FIDIC claims and cost control, about once a month. Unsubscribe any time.

Scroll to Top