Across every sector of capital project delivery — federal construction, transit infrastructure, international EPC, commercial general contracting — there is a category of financial loss that is almost entirely preventable and almost always avoidable in hindsight. A contractor performs work outside the original scope. The work is real. The cost is real. The entitlement to compensation is real. And the claim goes uncompensated because a written notice was not submitted within the window specified in the contract.
The notice window problem is not a legal technicality. It is one of the most consistent sources of unrecovered cost on capital programs, and it is almost never caused by contractors who do not know they have rights — it is caused by contractors who do not know the clock has started.
How Notice Requirements Work
Capital project contracts — across virtually every framework, from federal FAR-based agreements to FIDIC Yellow Book EPC contracts to public owner general conditions — contain provisions that require written notice as a precondition to a claim. The logic is reasonable from the owner's perspective: the owner needs to know about changed conditions, differing site conditions, or scope growth in time to investigate the circumstances, mitigate costs, and make decisions. A contractor who waits until project completion to raise a claim deprives the owner of that opportunity.
The specific notice requirements vary widely. Federal contracts often require notice within 10 days of the event giving rise to the claim. FIDIC contracts specify 28 days. Many public owner general conditions have their own timeframes, sometimes as short as 7 days, sometimes as long as 60. The triggering event also varies — some contracts require notice from the date the contractor first encountered the condition, others from the date the contractor knew or should have known about it, others from the date of the owner's direction.
What does not vary is the consequence of missing the window. Most contracts contain explicit waiver language: failure to provide timely written notice in accordance with the contract constitutes a waiver of the right to claim additional time or compensation for that event. Courts and arbitration panels have consistently enforced these provisions.
Why Windows Get Missed
The contractual notice requirement creates a specific operational problem: it requires the project team to connect what is happening on the ground — a changed condition encountered by a field crew, a design change issued by the owner, a differing site condition discovered during excavation — to a specific contract clause with a specific time requirement, in real time.
This connection rarely happens automatically. Field teams report problems. Project managers assess impacts. Controls teams track costs. But the formal review of contract notice requirements, cross-referenced against specific events and their contractual trigger dates, is typically performed by project attorneys or senior contracts staff — people who are not monitoring the schedule and cost data in real time.
By the time the notice requirement is identified, the window has often closed. The event is documented in daily reports. The cost is tracked in the cost system. The impact is visible in the schedule. Everything needed for a successful claim exists except the timely written notice that would make it payable.
The Schedule-Contract Disconnect
The core of the notice window problem is a disconnect between two data systems that are almost never read together: the project schedule and the contract.
The schedule contains the events — work activities with actual start dates, delayed predecessors, out-of-sequence sequences, milestone slippage. The contract contains the rights — the clause language specifying when notice is required, what it must contain, and how it must be delivered. The event that triggers a notice obligation is visible in the schedule. The obligation itself is in the contract. A project team that monitors each system independently misses the connection.
On a program with thousands of schedule activities and a contract that runs hundreds of pages, making this connection manually — for every event, every reporting period, across the full program timeline — is not realistic. Which is why, on most programs, it does not happen. Notice windows close unnoticed. Claims go unfiled. Compensation is forfeited.
What Multi-Modal Cross-Referencing Changes
The only systematic solution to the notice window problem is reading the contract and the schedule as a single dataset. When a schedule activity actual start date, predecessor delay, or milestone miss is detected, the corresponding contract clause review should be automatic — identifying whether the event constitutes a compensable occurrence, what the applicable notice period is, and how many days remain before the window closes.
This is not a legal function. It is a data function. The clause is text. The event is a data point in the schedule. The connection between them is a query that can be automated against a system that has ingested both.
On a transit megaproject, this means the project controls team knows about a differing site condition notice obligation within hours of the crew encountering the condition. On a federal construction program, it means a design change that triggers a REA requirement is flagged before the data date rolls past the contractual window. On an international EPC program governed by FIDIC, it means 28-day notice obligations for variation orders are tracked automatically against the schedule activity dates that initiated them.
The claims that get lost are not lost because the entitlement was weak. They are lost because the paperwork was late.
The Forensic Intelligence Engine reads your contract language alongside your schedule data and flags contractual notice obligations before the window closes — regardless of whether you are operating under a federal contract, a public owner agreement, or an international FIDIC framework.