How to Identify Delay Events in the TIA Method

One of the biggest mistakes in construction claims and delay analysis is not the delay itself… it’s failing to properly identify and document the event when it first arises.

Here is an example of a real-world case scenario involving:
• Design changes in retaining walls
• Specification changes in ceramic tiles
• Hidden variations embedded in consultant responses and material submittals

And one lesson stood out clearly:

A strong claim is not built on emotion.
It is built on documentation, chronology, detail, and timing.

What many project teams overlook is that delay events are often hidden inside:

* Material submittal comments
* RFI responses
* Consultant remarks
* Informal instructions

By the time the impact becomes obvious (procurement delays, redesign, re-approvals, extended lead times), the contractual notice period may already be gone.

What separates experienced planners and claims professionals is their ability to:
✔ Identify delay events early
✔ Understand contractual entitlement
✔ Connect cause → effect → consequence
✔ Explain the “story” behind the event clearly

Because in reality, claims are not prepared for the client.

They are meant to be prepared for someone who has no prior knowledge or familiarity with the project

The details matter.

The chronology matters.

The notices matter.

And most importantly: communication across the project team matters.

This is why project controls and claims management are far more than schedules and paperwork — they are strategic risk management tools that can protect millions in project value.