Delay Analysis Methods: Match the Method to the Records You Have

Delay analysis methods are the techniques used to measure how a delay event affected a construction programme's completion date. The main methods are as-planned vs as-built, impacted as-planned, time impact analysis, windows analysis and collapsed as-built. The right one depends on the records you hold and when the analysis is done.

Here is where it usually goes wrong. The job is running late, an extension of time claim has to go in, and someone picks a method because they have heard it is the one superintendents prefer. Halfway through, it turns out the programme was only updated twice since award, the as-built dates are scattered across diaries, and the method chosen needs records the job never kept. The analysis gets forced, and the other side picks it apart.

The method is not a preference. It is a consequence of the records you have.

What are the main delay analysis methods?

Most delay analysis in Australia draws on the same family of techniques, and the Society of Construction Law Delay and Disruption Protocol is often used as a reference point for how they work. In plain terms:

  • As-planned vs as-built. Compares the baseline programme with what actually happened and attributes the differences. Simple to follow, but it does not show cause and effect well on its own.
  • Impacted as-planned. Adds delay events to the baseline and measures how far completion moves. Quick, but it ignores actual progress, so it is easy to challenge.
  • Time impact analysis. Inserts each delay event, as a short fragment of activities, into the programme updated to just before the event. It shows the effect at the time it happened.
  • Windows analysis. Splits the job into periods and measures how much delay occurred in each one, using the programme updates that bound each window.
  • Collapsed as-built. Starts from the as-built programme and removes the delay events to show when the job would have finished "but for" them.
Table of five delay analysis methods: as-planned vs as-built, impacted as-planned, time impact analysis, windows analysis and collapsed as-built, with a short description of each
Each method answers the same question, how much time did the event cost, from a different starting point.

None of these is right for every job. Each one asks for a different set of records, and each one is stronger or weaker depending on whether those records exist and agree.

Which method suits the records you hold?

Start with what you have, not with the method you would like to use. Look at three things: the baseline, the updates and the as-built record.

  • Baseline only. If the contract programme was never updated, you are limited to impacted as-planned. It can support a claim early in a job, but expect it to be challenged on a late or disputed claim.
  • Baseline plus regular, accepted updates. This is where time impact analysis and windows analysis work best. The updates give you a reliable picture of the job just before each event, and the result is far harder to dispute.
  • Baseline plus as-built records, few updates. As-planned vs as-built or collapsed as-built can still work, provided the diaries, RFIs and dated photos let you rebuild actual start and finish dates.

Timing matters too. A time impact analysis done when the delay happens supports a claim while the job is live. A windows or collapsed as-built analysis is usually done later, when the full as-built record is available.

High-rise towers under construction wrapped in green mesh, with tower cranes against a blue sky
On a multi-storey job, delays to the structure, facade and services can overlap. The method has to separate them.

Your contract may also say how delay is to be shown. Read the extension of time clause before choosing, because a method the contract does not support will not help you. This is general information, not legal advice, so get legal input where the claim is large or disputed. For what the superintendent expects to see in the claim itself, see extension of time claims.

Why do capable builders still pick the wrong method?

It is rarely a lack of knowledge. Your PM and CM know what delayed the job. The method goes wrong because of how the analysis is started.

  • The method is chosen first and the records are checked later, so the analysis is forced to fit.
  • Impacted as-planned is used on a late claim because it is quick, and the other side points out it ignores what actually happened on site.
  • The baseline has broken logic or hard constraints, so every method run on it gives an unreliable critical path.
  • Concurrent delays caused by the builder are left out, which undermines the whole result.
  • The programme updates were never formally submitted, so their status as evidence is unclear.
Diagram matching project records to delay analysis methods: baseline only to impacted as-planned, baseline with regular updates to time impact or windows analysis, baseline with as-built records to as-planned vs as-built or collapsed as-built
The records you hold narrow the choice of method before any analysis starts.

Every one of these is easier to avoid during the job than to fix after it. The method you can use at the end depends on the habits you set at the start.

How do you keep every method open during the job?

The strongest position is one where any method could be used, because the records support all of them. That comes down to a few habits.

  • Agree the contract programme after award and keep the Basis of Schedule that explains it.
  • Update the programme fortnightly or monthly, submit each update, and save it as a separate version.
  • Record actual start and finish dates against programme activities, not just in the diary.
  • Keep diaries, RFIs, instructions, weather records and dated photos linked to the areas they describe.
  • Notify delays promptly and model the likely effect while the facts are fresh.
Worker in gloves cutting steel with an angle grinder, sending a shower of sparks
What the trades do each day becomes the as-built record. Capturing it against the programme keeps every method available.

The move from tender programme to contract programme is the right moment to set this up, because it fixes the baseline that every later analysis is measured against.

 

FAQs

Which delay analysis method is the best?

There is no single best method. Time impact analysis and windows analysis are generally the most robust when regular programme updates exist. Where they do not, the right method is the one your records can actually support.

Can a delay analysis be done after the project finishes?

Yes. Windows, as-planned vs as-built and collapsed as-built analyses are often done after completion using the as-built record. They are only as reliable as the diaries, updates and other records behind them.

How does concurrent delay affect the analysis?

Where a builder delay and a qualifying delay affect completion at the same time, the contract and the analysis both need to deal with it. A credible analysis identifies concurrent delays rather than leaving them out, and your contract sets how they are treated.

Should a builder outsource delay analysis?

If your PM and CM are running the job and the programme has not been kept current, an experienced planner can review the records, recommend a method that fits them and build the analysis faster than a stretched site team. Your team still supplies the facts; the planner turns them into evidence.

Who offers delay analysis and forensic programme analysis in Australia?

FeelDX is an Australian project controls specialist firm with a construction background that provides delay analysis, forensic programme analysis and EOT support for builders, along with programme status updates, construction programmes, Basis of Schedule and 3D and 4D visualisation.

How does FeelDX analyse delays on your project?

FeelDX combines planning and visualisation so you can show how the job is being built, how long it will take and what it looks like, and reduce risk before a delay turns into a dispute. For delay analysis, that means checking your records first, recommending the method they support and turning the programme into evidence: what happened, when, what was affected and whether it hit the critical path. Where it helps, a 3D or 4D sequence shows the delay in context. See our project controls services and planning and visualisation technology.

  • Planning Lead. Once you give the go-ahead, a Planning Lead is assigned and introduced, so you know who you are working with.
  • Kick-off. A short meeting with your PM or CM on the delay events, notices issued, contract requirements and the records available.
  • High-level WBS and analysis windows. The first hold point: you confirm the programme structure, the method and the periods to be analysed before the detail is built.
  • First draft with review time. The analysis arrives with enough time for your team to review and challenge it before the claim or response is due.

Send us your contract programme, the updates issued so far and the delay notices, and we will come back with the method your records support and a proposed approach and timeline.

Talk to FeelDX.
📞 1800 FEELDX (1800 333 539) | 🌐 www.feeldx.com