Missed a Construction Claim Notice Deadline? What Contractors Should Check Next
Published · Last updated · 4 min read

Is the claim dead? Not necessarily. But do not assume it survives either.
In this article
- 1. What deadline actually applied?
- 2. What actually triggered the notice period?
- 3. Was anything communicated before the formal notice?
- 4. Who knew what, and when?
- 5. What happened because the notice was late?
- What to do once you discover the missed deadline
- How Hecato reconstructs the notice history
Missing a construction claim notice deadline can put recovery at risk. Whether the claim is actually barred depends on the executed contract, the notice requirement, what triggered it, the project record, governing law and potentially issues such as actual notice, waiver and prejudice.
There is no single US rule. Courts differ in how strictly they enforce construction notice provisions, and none of those factors should be assumed to rescue a late claim automatically. (American Bar Association)
The immediate job is to reconstruct exactly what the contract required, what happened and what was communicated before deciding the claim is dead.
1. What deadline actually applied?
Start with the executed contract, not the standard form you think the project was based on.
Check the:
- prime agreement or subcontract
- general and supplementary conditions
- amendments and exhibits
- notice provisions
- changes and delay provisions
- claims procedure
- flow-down requirements
There may be multiple deadlines. A contract can separately require notice of an event, initiation of a formal Claim, cost or schedule information and continuing updates.
Subcontracts can create another layer because the subcontractor may need to notify the general contractor early enough for the GC to preserve its own rights upstream.
AIA A201-2017 notice requirements: a worked example
Under the unmodified AIA A201-2017, Section 15.1.3.1 generally requires certain Claims to be initiated within 21 days after the event giving rise to the Claim or after the claimant first recognizes the condition giving rise to it, whichever is later.
Other provisions can impose different requirements. Section 3.7.4, for example, addresses differing site conditions, while Section 15.1.5 addresses Claims for additional cost and can require notice before proceeding with affected work.
Delivery mechanics matter too. Under Section 1.6.2, Claim notices have specific delivery requirements. An ordinary project email should not automatically be assumed to satisfy them.
But your project may not use the unmodified A201-2017. Supplementary conditions, owner forms and negotiated amendments routinely change these provisions.
Read the executed agreement.
2. What actually triggered the notice period?
This is often where the real dispute begins.
Depending on the contract, the clock might run from:
- occurrence of an event
- discovery of a condition
- recognition of the condition giving rise to the claim
- receipt of a direction
- another defined contractual trigger
Do not automatically use the date when the full financial or schedule impact became clear.
For example, if an owner decision is delayed, the relevant date might relate to when the decision was required, when work became affected, when the contractor recognized the problem or another trigger specified by the contract.
Likewise, the fact that a later schedule analysis finally quantified a delay does not necessarily mean the notice period started on that later date.
Build the chronology from contemporaneous records rather than memory.
3. Was anything communicated before the formal notice?
A missing formal notice does not necessarily mean nothing was communicated.
Search for:
- emails and letters
- RFIs
- meeting minutes
- daily reports
- change logs
- schedule narratives
- owner or architect instructions
- potential change orders
- cost and labor records
The question is not simply:
"Did the owner know about the problem?"
Ask instead:
What did they know, when did they know it, who told them and what did they do in response?
That evidence may matter when contractual compliance, actual notice, waiver or prejudice are assessed. Whether it matters legally depends on the contract and applicable law.
Example: wrong notice recipient
A subcontractor encounters an unexpected condition and immediately emails the GC's superintendent and project manager.
The subcontract, however, requires formal notice to a specific representative.
Those emails may be important evidence of what the GC knew and when. But knowledge by the project team should not automatically be treated as compliance with a contractual requirement to notify another person.
4. Who knew what, and when?
Reconstruct both sides of the project record.
For the contractor or subcontractor:
- Who first identified the event?
- When did project management know?
- When did the commercial team know?
- When was a potential cost or time impact recognized?
For the owner or GC:
- Were they told about the condition?
- Did they inspect it?
- Did they direct the work?
- Did they discuss cost or schedule consequences?
- Did they ask for pricing or supporting records?
This is particularly important where extra work has already been performed.
A written directive, field instruction, RFI response, change discussion or evidence that the other party requested and observed the work may all be relevant.
They do not automatically override a notice provision. They are facts that need to be assessed against it.
5. What happened because the notice was late?
Notice provisions often give the receiving party an opportunity to investigate, mitigate, document the event or make a different decision before costs accumulate.
So establish what actually happened.
For example:
- Could the owner have chosen another solution?
- Was a condition concealed before inspection?
- Could sequencing have changed?
- Was the owner already investigating the issue?
- Were the disputed costs being tracked?
- Was the potential delay already reflected in schedules?
In some jurisdictions and circumstances, prejudice may matter when a notice requirement is enforced. Other courts may enforce contractual language more strictly.
"The owner wasn't prejudiced" is therefore something to investigate, not a universal answer to a late claim.
What should you do once you discover the missed deadline?
First, preserve the contemporaneous record. Secure the relevant emails, messages, daily reports, photographs, schedules, RFIs, change records, cost records and subcontractor correspondence.
Second, do not compound the problem. A missed initial deadline may not eliminate later requirements for continuing notice, claim updates, cost information or schedule submissions. Issue any currently required communication promptly in accordance with the contract.
Third, escalate material positions for appropriate contractual and legal review. Public projects may also involve statutory, regulatory or administrative claim requirements beyond the contract itself.
Do not assume rules applying to one state, one contract form or one private project apply everywhere.
This article provides general information about construction claim administration and does not constitute legal advice.
How Hecato reconstructs the notice history
Late-notice investigations usually involve information scattered across the contract and months of project records.
With Hecato, contractors can upload the:
- executed contract and amendments
- relevant claims and notice provisions
- emails and RFIs
- instructions and meeting minutes
- daily reports
- change records
- schedules
- relevant cost and time records
Hecato maps the contractual requirements against the project record, reconstructs the event-and-notice chronology, identifies relevant communications and organizes the evidence supporting the claim position.
It does not decide whether a late claim is legally enforceable.
It gives your commercial, claims and legal teams a much better factual record for answering the question:
What exactly happened before, during and after the supposed missed deadline?
Once the immediate issue is resolved, the same process can be used proactively: map notice obligations on live projects before claims arise so teams know what must be communicated, to whom and by when.