Notice Builder
An event on site triggers a contractual notice obligation with a deadline. Notice Builder reads the contract, finds the governing clause, computes the deadline, and drafts the serve-ready notice — recipient, delivery method, and a letter where every assertion cites a contract clause. Drafting assistance, not legal advice.
What it does
Most construction disputes that fail do so on a notice technicality, not the merits: the notice was late, went to the wrong person, or went by the wrong method, and a legitimate delay or change claim was waived. Notice Builder closes that gap. You tell it what happened — the event type and a short narrative — and give it the contract. It finds the notice provision that governs that event type, reads the notice period, and computes the deadline from the event date you supplied.
It then drafts a complete, properly-addressed notice: the notice type, the deadline (with the clause it came from and days remaining), who must be served and by what delivery method, the letter itself, the governing clauses it relied on (quoted so you can verify the read), and the supporting documents to attach. A confidence score is shown; below the threshold the result is flagged REVIEW.
The engine is conservative about facts: the narrative comes from what you describe, the contractual assertions come from the clauses it cites, and where a needed fact is missing it leaves a marked placeholder rather than inventing one.
Notice Builder is a drafting tool for construction professionals. It is not a lawyer and does not create an attorney-client relationship. Notice requirements, day-counting, and waiver consequences are legal questions — the engine surfaces the clause it relied on and the deadline it computed so a human can check both, and for high-stakes claims you should have counsel review the draft before it is served.
When to use it
- A delay event — owner-caused delay, late owner deliverable, or differing weather. Draft the delay / time-impact notice the same day to preserve the schedule claim.
- A differing site condition — unforeseen rock, contaminated soil, an unmarked utility. The clause usually has a short stop-and-notify trigger.
- A directive to proceed without a signed change — protect the right to be paid with a constructive-change notice before the change order is papered.
- Non-payment — a pay application unpaid past the contract window. The notice is the predicate for suspension, interest, or lien rights.
- Before a claim — claim-preservation and acceleration notices keep the door open while the commercial conversation continues.
What to provide
The contract and what happened. Paste or upload the contract text (prime contract, subcontract, or the relevant general conditions — the full agreement is best so the engine can find the clause, the period, the designated recipient, and the required delivery method). If Contract Review already ran, the contract carries straight over on the chain.
Pick the event type — delay, differing site condition, change directive / constructive change, non-payment, claim preservation, or acceleration — and describe the event in a sentence or two, including the date it occurred and the impact: "Owner's structural RFI response returned 9 days late on 6/3; steel erection on hold; crane on standby."
Step by step
Open the engine
Sidebar → Engines → Notice Builder (Post-award).
Provide the contract
PDF or pasted text. Or chain in from Contract Review — the contract carries over automatically.
Select the event type
Delay, differing site condition, change directive, non-payment, claim preservation, or acceleration.
Describe what happened
A short narrative with the event, the date, and the impact. This is what the formal notice is written around.
Run the draft
20–40 seconds.
Check the deadline and the cited clause
Confirm the engine found the right notice provision and counted the days correctly — both are shown with the draft.
Edit and serve
Put it on letterhead, adjust the language, have counsel review where the stakes warrant, then serve by the method the contract requires. Export to PDF from the result.
Understanding the results
The date to serve by, computed from the event date and the clause's notice period, with the days remaining. The single most important output — shown in red.
The kind of notice the event calls for (e.g. Notice of Delay & Intent to Claim), framed under the matching contract provision.
Who must receive the notice and by what method (certified mail, designated portal, email to the owner's rep) — read from the contract's notice provisions.
A complete, serve-ready notice: reference line, statement of the event, contractual basis, reservation of rights, and a request to confer. Ready to paste onto letterhead or export to PDF.
The clauses the draft relied on, quoted so you can verify the engine read the contract correctly.
The records to attach or reference so nothing that proves the claim is left out (date-stamped correspondence, the affected schedule activity, cost logs).
How clearly the engine found the notice clause and period. Below the threshold the result is flagged REVIEW — have counsel confirm the type, the deadline, and the draft before serving.
Every control, explained
Run draftConsumes one run. 20–40 seconds.
Contract textPDF upload or pasted text. The agreement the engine reads for the notice clause, period, recipient, and method.
Event typeSelects which family of notice clause the engine looks for and how the letter is framed.
Event detailsYour narrative of what happened, when, and the impact. The factual basis of the notice.
Export PDFRenders the drafted notice as a PDF for letterhead or filing.
Chain from Contract ReviewCarries the reviewed contract into Notice Builder so you never re-upload it.