Notice requirements: how contractors lose claims they were right about

Read three things before the job starts

Every project should begin with a short exercise that most companies skip:

• The notice provisions themselves, listed with their deadlines.
• The definition of who must receive notice, which is frequently a specific role and address, not the project manager you talk to daily.
• The required form and method — written, certified mail, through a project management system, or a specific form.

Turn that into a one-page summary posted where the team can see it, listing each notice type, the deadline in days, who receives it and how it must be sent. That page prevents more losses than any contract negotiation.

How to write one without starting a fight

The fear that stops most notices is relational: nobody wants to look adversarial on day 30 of a two-year project. A well-written notice is not adversarial, and the tone is entirely controllable:

• State the facts, not the blame. What happened, when it was discovered, where.
• Reference the contract provision requiring the notice, briefly.
• Describe the potential impact on cost and schedule, and say clearly if it is not yet quantifiable.
• Reserve rights without threatening anything.
• Propose the next step — a site meeting, a direction, a decision needed by a date.
• Send it to the person named in the contract, by the required method, and copy the people you work with daily.

A useful framing when handing it over: "This is the notice the contract requires so we protect your options and ours." Owners who work with contractors regularly expect it, and its absence is more suspicious than its presence.

Make notices routine, not exceptional

The companies that never miss notices are not the ones with the best lawyers. They are the ones where sending a notice is ordinary administrative work:

• Superintendents are trained to report triggering events the same day, regardless of whether they think it matters.
• A single person owns notice compliance on each project.
• Templates exist for each notice type, pre-filled with the contract references.
• The weekly project meeting includes a notice check, alongside schedule and safety.
• Sending is never a judgment call about relationships. If the trigger occurred, the notice goes out.

Notices between the GC and the subcontractors

Subcontracts usually require the subcontractor to give notice in a shorter window than the prime contract allows the general contractor, precisely so the GC has time to pass it up the chain. That arrangement fails constantly, in both directions:

• Check the arithmetic of the deadlines. If your subcontract gives you five days and the prime gives the GC seven, the schedule works. If both say seven, the GC cannot possibly comply after hearing from you.
• Notice the GC even when the GC already knows. Their knowledge does not satisfy your contractual obligation, and it does not create their record.
• Ask what happened upstream. A subcontractor entitled to compensation may find the claim died because the GC never passed it on.
• General contractors should acknowledge in writing and say whether the notice was forwarded to the owner, which avoids a dispute between parties who need each other.
• Watch for pass-through arrangements, where a claim is pursued against the owner in the GC's name on the subcontractor's behalf, with the terms agreed in advance rather than improvised.

The trades that handle this well treat a notice to the GC as a normal courtesy of doing business, and their claims survive because the paperwork exists at both levels.

Project software helps, and it also creates traps

Most projects now run correspondence through a project management platform, which makes notice compliance easier to prove and easier to get wrong:

• Confirm the platform satisfies the contract. Some contracts still require certified mail or delivery to a specific address, and a message in a system does not meet that.
• Use the correct module. A comment on a daily log is not a notice; an RFI is not a claim; a document uploaded to a folder notifies nobody.
• Keep your own copies. Access to the platform frequently ends when the project does, and the records you need may be the ones you cannot reach.
• Set automatic deadline reminders tied to event dates rather than relying on memory during a busy month.
• Export correspondence periodically, so a dispute two years later does not depend on someone else's software subscription.

The records that make the notice worth something

A notice preserves the right; documentation proves the claim. The two work together and both are built in the field:

• Daily reports with crew counts, weather, work performed and the specific impacts observed.
• Photographs with dates, especially of conditions that will be covered or removed.
• Contemporaneous schedule updates showing the effect of the event, rather than a reconstruction months later.
• Cost tracking in a separate code for the affected work, from the first day.
• Correspondence kept in one place, in order, retrievable without an archaeology project.

If you are on the owner or GC side

• Respond to notices in writing, within any period the contract requires, even if only to acknowledge receipt.
• Investigate promptly, which is the entire purpose of the requirement.
• Do not treat a notice as an act of aggression. Punishing contractors for compliance produces silence, and silence is what turns small issues into large claims.
• Keep your own records, because a defense is documented the same way a claim is.
• Be careful about waiver: informally accepting late notices repeatedly can affect your ability to insist on the requirement later.

What a missed notice costs

Round numbers, for a $9 million commercial project:

• Differing site condition discovered during excavation, adding 18 days and $210,000 in direct cost.
• Contract requires written notice within 7 days of discovery; verbal discussion occurred, nothing was written.
• Claim denied on procedural grounds — the merits were never evaluated.
• At a 5% net margin, that project would have needed roughly $4.2 million in additional revenue to replace the loss.

The notice that would have prevented it takes about twenty minutes to write.

The mistakes that repeat everywhere

• Relying on verbal notice to a project manager who agreed at the time.
• Waiting until the cost is known before giving notice, when the deadline runs from discovery.
• Sending to the wrong person or by the wrong method.
• Disturbing a differing site condition before documenting and noticing it.
• Silence to protect the relationship, which almost always damages it later.
• Ignoring statutory deadlines that run in parallel with contractual ones.

Where to start

Take your current largest contract and build the one-page notice summary today: every notice type, its deadline, who must receive it and how. Create a template for each one. Assign a person. Add a line to the weekly meeting agenda. Then, on the next project, count how many notices you send that never turn into anything — that number is the measure of a functioning system, not of a difficult contractor. The ones that do turn into something will pay for the entire habit many times over.

Frequently asked questions

What happens if a contractor misses a notice deadline?

In many jurisdictions the claim can be denied on procedural grounds without the merits ever being evaluated, which is why missed notices cost contractors more money than estimating errors do. Notice provisions are enforced because they serve a purpose the owner can defend: the chance to investigate while evidence is still available, to mitigate the impact or to choose a different course before the cost is incurred. Two details cause most failures. The clock usually starts at discovery of the event rather than when the cost is finally quantified, so waiting until the numbers are known is often fatal, and verbal notice generally does not satisfy a written requirement even when everyone on site remembers discussing it. Waiver through a course of conduct is recognized inconsistently and is not a plan.

How do you send a notice without damaging the relationship?

By making it factual and routine rather than adversarial. State what happened, when it was discovered and where, reference the contract provision that requires the notice, describe the potential impact on cost and schedule while saying plainly if it cannot yet be quantified, reserve rights without threatening anything and propose a next step such as a site meeting or a decision needed by a date. Send it to the person named in the contract, by the method the contract requires, and copy the people you work with daily. A useful way to hand it over is to explain that it is the notice the contract requires so that both parties preserve their options. Owners who build regularly expect notices, and their absence is more concerning than their presence.

What records support a construction claim?

A notice preserves the right, but documentation proves the claim, and the two are built together in the field. The records that carry weight are daily reports containing crew counts, weather, work performed and the specific impacts observed, dated photographs especially of conditions about to be covered or removed, contemporaneous schedule updates showing the effect of the event rather than an analysis reconstructed months later, cost tracking under a separate code for the affected work starting on the first day, and correspondence kept in one organized place. The distinction that matters most in a dispute is between contemporaneous and reconstructed records: two honest sets of numbers prepared months apart will not be given the same weight.