Preconstruction
Notice Clocks in Construction Contracts: How to Find Them Before You Price
Notice clocks hide in claims, changes, payment and closeout clauses, and addenda move them. Here is how to read for them, register them, and decide what to price.
The job is three months in. A revised detail lands, the field team starts the work, and someone asks whether you sent notice. Somebody opens the contract and finds the clock started the day the detail arrived. It ran out last week.
That clause was in the bid package. It was there on bid day, and nobody carried it into the estimate or the project's first week.
Most teams find notice clocks after an event, when they are looking for a way to get paid. By then the clause is reading you, not the other way round. The cheaper time to find them is before the price goes in.
Most project software is built to send a notice once someone decides one is needed. This guide works from the other end: start with the contract, find every clock in it before you price, and tie each one to its trigger, its deadline, and what it costs if missed, cited to the page.
Know where the clocks hide
Notice clocks rarely sit under a heading called "notice." They live inside clauses about claims, changes, site conditions, delays, payment, allowances, and closeout. A search for the word "notice" will miss half of them.
Read these places on every package:
- General conditions or general provisions. Claims, changes, differing site conditions, delays, and disputes.
- Special or supplementary provisions. Owner-specific edits that shorten or override the general clock.
- Division 01 specifications. Administrative sections often carry their own response windows.
- Addenda. A changed clock in Addendum 3 governs over the original page you already read. This is where teams get caught most often: the estimate was built on the original, the project team works from the original, and the addendum quietly moved the deadline.
The public DFW Airport package we use as an example (PA1971, bid March 2026) shows how short a clock can be:
…within ten (10) calendar days after either occurrence of the event… and before beginning the work… [failure to give notice] is a waiver of any claim for such additional compensation and also any claim for additional time resulting therefrom.
What it means: Ten calendar days, counting weekends, from the event or from when you first recognize the condition. Notice is also due before the claimed work begins. Miss it, and you lose the time as well as the money.
That clause is one page in a package of 22 documents and 571 pages of specifications. The other clocks are scattered through the rest.
The contractor must give a price quote for an allowance item within 7 calendar days (Spec 01 30 00). No payment is made for costs incurred more than 90 days before the invoice (§100-5, GP-59). The same clause sets a 7-day deadline to pass retainage down to subcontractors, a payment obligation rather than a notice clock, but one that sits in the same place and is just as easy to miss. None of them is in the claims section.
When two clocks disagree
The most expensive clock is the one that changed and nobody noticed. The general provisions give one deadline. The special provisions or an addendum change it. The estimate and the project team keep working to the first one.
Illustrative example: the general provisions give 10 calendar days to notice a claim, counted from the event or from first recognition. A special provision for owner-directed changes cuts that to 7 days, counted from the date of the written direction. Same subject, different trigger, different count. A team working from the general provisions would be late without knowing it.
When you find a clock, search the special provisions and every addendum for anything that touches it. The version that governs is the one that counts.
Read each clock for five things
A deadline on its own is not enough. Two clauses with the same number of days can behave very differently.
- Trigger. Does the clock start at the event, at first recognition, at receipt of a direction, or at the owner's decision? "Whichever comes first" means the earliest date governs.
- Unit. Calendar days or working days? On a 10-day clock, a long weekend changes the answer.
- Form and recipient. Written notice to whom, and through which process? An email to the field inspector may not satisfy a clause that names the Engineer. An RFI is not automatically notice either; see the anatomy of a good RFI.
- Sequence. Is notice required before the work starts? Is there a second deadline, such as an updated claim after the work is done?
- Consequence. Does the clause say waiver, bar, or loss of entitlement? Does it cover time as well as money?
Don't carry over habits from the forms you know. AIA A201-2017 gives 21 days to start a claim. The DFW package gives 10 days and adds a pre-work requirement.
Build a notice register before you price
Put every clock into one register, cited to its source. A row that says "claims: 10 days" is less useful than one that shows the trigger, the page, and the consequence.
| Field | Question it answers |
|---|---|
| Source | Which document, revision, section and page? |
| Trigger | What event starts the clock? |
| Deadline | How many days, calendar or working? |
| Form and recipient | What must be sent, to whom, and how? |
| Sequence | Is notice needed before work, and is a follow-up due? |
| Consequence | What right is lost if notice is late? |
| Responsible party | Who on the project team gives the notice? |
| Bid decision | Priced, qualified or carried, and why? |
The last two rows are the ones most teams skip. A clock with no named owner tends to get missed.
Decide: price it, qualify it, or carry it
A notice clock is a commercial risk, so treat it like one.
- Price it when the clock is short and the job is likely to see changes. A 10-day window on a fast-track rehab job may need more project-management time in the estimate.
- Qualify it when the clock is unworkable as written. Raise it as a bid question, or state the assumption in your qualifications if the bid documents allow it.
- Carry it knowingly when the risk is acceptable. Record why, so the decision survives the handover from estimating to operations.
Then hand the register to the project team on day one. The estimate is the first place a notice clock can be missed. The first project meeting is the second. And the same clocks come back at the end of the job; see unapproved change orders at closeout.
Where Halozen sits
This is the register Halozen produces for every package we review: every clock, every addendum change, each row cited to the clause and page. Your team decides what to price, qualify or carry.
Common questions
What is a notice clock in a construction contract?
It is a clause that sets a deadline for written notice after a defined event, such as a change, a claim, or a site condition. Missing it can waive or limit a right to more money or more time.
Does an RFI count as notice of a claim?
Not automatically. An RFI asks a question, while a notice clause usually requires a specific form, content, and recipient. Check what the contract requires.
If the owner already knew about the issue, is late notice still a problem?
Don't count on owner knowledge to save you. Whether actual knowledge excuses late notice depends on the contract wording and applicable law. Send the notice the contract asks for.
Should notice risk be priced into the bid?
When the clock is short and changes are likely, it often should be. Notice takes project-management time, and a missed notice can cost the full value of a change. Decide on each clock and record the reason.
Where do notice clocks go after award?
Into the project team's hands, as a register with triggers and owners. The same clocks come back at closeout.
Find every notice clock before you price.
Send us one live bid package. We'll return every notice clock in it, including the ones the addenda changed, each with its trigger, deadline and consequence, cited to the clause and page. Scope and fee agreed up front.