Notice of Delay Generator: 16-Step Forensic Guide (2026)

Name: Notice of Delay Generator
Availability: InStock
Author: Miracle Prompts

From Blank Page to Pro Prompt in Minutes.
MiraclePrompts.com is designed as a dual-engine platform: part Creation Engine and part Strategic Consultant. Follow this workflow to engineer the perfect response from any AI model.

1 Phase 1: The Engineering Bay

Stop guessing. Start selecting. This section builds the skeleton of your prompt.

1. Navigate the 14 Panels The interface is divided into 14 distinct logical panels. Do not feel pressured to fill every single one—only select what matters for your specific task.

Use the 17 Selectors: Click through the dropdowns or buttons to define parameters such as Role, Tone, Audience, Format, and Goal.

Power Feature
Consult the Term Guide

Unsure if you need a "Socratic" or "Didactic" tone? Look at the Term Guide located below/beside each panel. It provides instant definitions to help you make the pro-level choice.

2 Phase 2: The Knowledge Injection

Context is King. This is where you give the AI its brain.

3. Input Your Data (Panel 15) Locate the Text Area in the 15th panel.

Dump Your Data: Paste as much information as you wish here. This can be rough notes, raw data, pasted articles, or specific constraints.

No Formatting Needed: You don’t need to organize this text perfectly; the specific parameters you selected in Phase 1 will tell the AI how to structure this raw data.

3 Phase 3: The Consultant Review

Before you generate, ensure you are deploying the right strategy.

2. The Pro Tip Area (Spot Check) Before moving on, glance at the Pro Tip section. This dynamic area offers quick, high-impact advice on how to elevate the specific selections you’ve just made.

Strategic Asset
4. Miracle Prompt Pro: The Insider’s Playbook

Master the Mechanics: This isn't just a help file; it contains 10 Elite Tactics used by expert engineers. Consult this playbook to unlock advanced methods like "Chain of Thought" reasoning and "Constraint Stacking."

5. NotebookLM Power User Strategy Specialized Workflow: If you are using Google’s NotebookLM, consult these 5 Tips to leverage audio overviews and citation features.
6. Platform Deployment Guide Choose Your Weapon: Don't just paste blindly. Check this guide to see which AI fits your current goal:
- Select ChatGPT/Claude for creative reasoning.
- Select Perplexity for real-time web search.
- Select Copilot/Gemini for workspace integration.

4 Phase 4: Generation & Refinement

The final polish.

7. Generate Click the Generate Button. The system will fuse your Phase 1 parameters with your Phase 2 context.
8. Review (Panel 16) Your engineered prompt will appear in the 16th Panel.
Edit: Read through the output. You can manually tweak or add last-minute instructions directly in this text box.
Update: If you change your mind, you can adjust a panel above and hit Generate again.
9. Copy & Deploy Click the Copy Button. Your prompt is now in your clipboard, ready to be pasted into your chosen AI platform for a professional-grade result.

Quick Summary & FAQs
Need a refresher? Check the bottom section for a rapid-fire recap of this process and answers to common troubleshooting questions.

Notice of Delay: The Ultimate 16-Step Miracle Prompts Pro

Mastering the forensic art of the Notice of Delay is the definitive bridge from contractual vulnerability to claim security. This strategic tool empowers you to architect unassailable notifications that protect your commercial position, effectively manage client expectations, and secure your entitlement to time and money with absolute precision.

Step Panel Term Reference Guide

Step 1: Contract Form

Why it matters: Every contract suite (JCT, NEC, FIDIC) has unique "trigger" clauses and time-bars; identifying the specific form is the first step in avoiding disqualification.

JCT Standard Building Contract: Traditional procurement route with clear Relevant Event mechanisms.
JCT Design & Build: Contractor holds design risk; notices must distinguish between Employer Changes and Design Development.
NEC3 Engineering & Construction: Requires strict adherence to Early Warning and Compensation Event notification timelines.
NEC4 Engineering & Construction: Evolution of NEC3 with stricter "divider dates" and deemed acceptance mechanisms.
FIDIC Red Book (Construction): Employer-design focus; Clause 20.1 time-bars are notoriously strict (28 days).
FIDIC Yellow Book (Plant & DB): Contractor-design focus; notices must align with "Fit for Purpose" obligations.
AIA A201 General Conditions: US standard; focuses on Claims for Additional Time and Consequential Damages waivers.
AIA A101 Owner / Contractor: Often paired with A201; defines the specific Agreement terms to be referenced.
ICC Model Contract: International standard used where neutral terms are preferred over common law bias.
GC21 General Conditions: Cooperative contracting model used primarily in Australian government projects.
AS 4000 (Australian Standard): Widely used general conditions requiring specific "Qualifying Cause of Delay" notices.
Government / Public Works: Heavily amended forms often shifting risk to the contractor; requires forensic notice compliance.
Simple Works Contract: Less formal, but still requires written notice to prevent "Time at Large" arguments.
Subcontract Agreement: "Back-to-back" provisions are critical; notice deadlines often tighter than the main contract.
Consultancy Agreement: For Architects/Engineers notifying clients of delays in deliverables or information flow.
Bespoke / Custom Contract: Non-standard terms; requires "First Principles" analysis of the notice clause.
Letter of Intent: Pre-contractual state; notices here establish precedence for the eventual formal contract.
Other: Specialized or hybrid forms not covered by standard suites.

Step 2: Sender Role

Why it matters: Your role dictates the leverage you hold. A Main Contractor notifies for relief; a PM notifies to enforce obligations.

Main Contractor: The primary entity responsible for delivery; holds the burden of proof for delay events.
General Contractor: US terminology; focuses on coordination of trades and managing the master schedule.
Subcontractor: Must notify the Main Contractor immediately to avoid "upstream" liability flow-down.
Trade Specialist: Niche installers whose delay often impacts the critical path of following trades.
Architect: Notifies the Client of design delays or acts as Contract Administrator assessing others' delays.
Lead Designer: Responsible for the design program; notifies if Information Release Schedules are missed.
Project Manager: Central hub; notifies all parties of macro-level delays affecting the overall business case.
Construction Manager: Manages trade packages; notifies the Client of package interface delays.
Employer / Client: Rare sender, but may notify of suspension or "Prevention" events to cap liability.
Developer: Notifies funders or tenants of handover delays.
Supplier / Vendor: Notifies of manufacturing or logistics delays (e.g., shipping, customs).
Consultant: Professional services providers notifying of delays in reports, surveys, or approvals.
Engineer: FIDIC role; acts as the impartial certifier of time extensions.
Quantity Surveyor: Focuses on the financial impact notification of the delay event.
Owner's Representative: Acts as the eyes and ears of the client; validates delay claims on site.
Joint Venture Partner: Notifies internal partners of risks affecting the SPV (Special Purpose Vehicle).
Facility Manager: Notifies of operational delays in occupied refurbishments.
Other: Unique project roles like Tenant Coordinator or Third-Party Monitor.

Step 3: Recipient Role

Why it matters: Notices sent to the wrong person are often invalid. You must identify the specific "Contract Administrator" defined in the agreement.

Employer / Client: The ultimate payer; notice ensures they are aware of completion date slippage.
Contract Administrator: The specific individual named in JCT forms to receive validity notices.
Project Manager (PM): The NEC Project Manager has specific powers to accept or reject Early Warnings.
Superintendent: Common in Australian standards; the certifier of EOT claims.
Main Contractor: The recipient for all Subcontractor notices.
Architect: Often the first point of contact for design-related delay queries.
Engineer: Under FIDIC, the Engineer must receive notice within 28 days to preserve rights.
Employer's Agent: The D&B equivalent of the Contract Administrator; holds decision-making power.
Quantity Surveyor (QS): Needs notice to value the "Loss and Expense" associated with the delay.
Lead Consultant: Coordinates the design team's response to the delay.
Commercial Manager: Focuses on the contractual validity and financial reserving for the claim.
Legal Counsel: Recipient for high-stakes, contentious, or arbitration-ready notices.
Project Director: Senior leadership oversight; usually for "Red Flag" major delays.
Development Manager: Represents the investment side; concerned with ROI impact.
Bank / Funder Monitor: Requires notice if the "Longstop Date" is threatened.
Dispute Adjudicator: Recipient when the delay has escalated to a formal dispute (DAB/DRB).
Insurance Representative: For delays involving physical damage (e.g., fire, flood) affecting policy coverage.
Other: Statutory authorities or third-party stakeholders.

Step 4: Primary Delay Cause

Why it matters: Causal link is king. You must categorize the root cause accurately to determine if it is a "Relevant Event" (Time) or "Relevant Matter" (Money).

Adverse Weather: Exceptionally adverse conditions; usually time only, rarely money.
Design Changes / Variations: Instructions changing the scope; usually entitles both time and money.
Late Instructions: Failure to provide necessary info by the "Information Release Schedule" date.
Late Information (RFI): Unanswered Requests for Information preventing progress.
Access Restrictions: Failure to give possession of the site or specific work areas.
Force Majeure: Events beyond control (war, epidemic); usually time only, no money.
Ground Conditions: Unforeseen physical conditions differing from the Geotech report.
Material Shortage: Industry-wide shortages; hard to claim unless "Force Majeure" applies.
Labor Strike / Dispute: specific strikes affecting the works; general strikes are often neutral events.
Utility Connection Delay: Statutory undertakers failing to connect power/water on time.
Damage by Others: Works damaged by the Employer or separate contractors.
Regulatory / Permit Delay: Authorities delaying planning or building control sign-off.
Discovery of Antiquities: Fossils or coins found; immediate stop-work instruction required.
Suspension of Work: Contractor suspends due to non-payment; strictly regulated by Construction Acts.
Owner Interference: The Client impeding the contractor (Prevention Principle).
Subcontractor Default: Insolvency or non-performance of a sub; usually a Contractor risk.
Contamination / HazMat: Discovery of asbestos or toxic waste not in the baseline data.
Other: Unique events like protestor action or drone interference.

Step 5: Specific Delay Trigger

Why it matters: Generalities fail in court. Pinpointing the exact "trigger" (e.g., "Revision C" vs. just "Design Change") adds forensic weight to the notice.

Revision to Drawings: A specific drawing issue (e.g., "Rev C changed column layout").
Unforeseen Physical Conditions: Rock where clay was shown; water table higher than documented.
Failure to Grant Possession: The gate was locked; the tenant had not vacated.
Delay in Approvals: Submittals or samples sitting with the Architect beyond the agreed turnaround time.
Extreme Precipitation: Rainfall exceeding the 1-in-10-year average for the location.
High Winds / Storms: Crane wind-off days exceeding the allowance in the program.
Global Supply Chain Issues: Embargoes or shipping canal blockages.
Customs / Import Holds: Materials stuck at the border due to bureaucratic changes.
Discovery of Asbestos: ACM found in voids presumed clear.
Archaeological Find: Bones or ruins requiring an indefinite halt for investigation.
Statutory Undertaker Delay: Power company failed to arrive on the booked date.
Change in Statutory Law: New building regs introduced post-contract.
Non-Payment by Client: Failure to honor a certified payment application.
Denial of Access: Neighbor refused crane oversail or scaffolding license.
Neighboring Site Issues: Vibration or subsidence claims from adjacent properties.
Civil Commotion / Riot: Public disorder preventing site access.
Insolvency of Key Supplier: Manufacturer bankruptcy requiring re-procurement.
Other: Specific localized triggers.

Step 6: Impact on Completion

Why it matters: Not all delays extend the contract. You must demonstrate the nexus between the event and the "Completion Date" to secure an Extension of Time (EOT).

Direct Critical Path Hit: The delay impacts an activity with zero float.
Consumption of Project Float: The delay eats into the buffer but doesn't yet push the end date.
Consumption of Terminal Float: Using up the contractor-owned float at the end of the job.
Concurrent Delay (Employer): Two events happening at once; usually grants time but not money.
Concurrent Delay (Contractor): Culpable delay running parallel to an excusable delay.
Sectional Completion Delay: Impacting a specific handover phase (Section 1, 2, etc.).
Practical Completion Delay: The ultimate handover date is pushed back.
Milestone Missed: Missing a payment trigger or key staging post.
Key Date Missed: Specific NEC term; implies damages if missed.
Impact Undetermined (Warning): "We are assessing the impact" (holding notice).
Potential Future Impact: An Early Warning of a risk that hasn't materialized yet.
Disruption (Productivity Loss): Work continues but at a slower, more expensive pace.
Resequencing Required: Changing the logic of the program to mitigate the hit.
Acceleration Required: Spending money to recover lost time.
Extended Preliminaries: Site running costs (cranes, cabins) running longer than planned.
No Critical Delay Yet: Notification for the record, preserving rights.
Total Project Suspension: Tools down; demobilization.
Other: Impact on third-party agreements or leases.

Step 7: Contract Clause Reference

Why it matters: A notice without a clause reference is just a letter. You must cite the specific "Relevant Event" or "Compensation Event" clause to trigger the mechanism.

Relevant Event (JCT): The mechanism for claiming additional time (EOT).
Relevant Matter (JCT): The mechanism for claiming additional money (Loss & Expense).
Compensation Event (NEC): The unified mechanism for both time and money in NEC contracts.
Early Warning (NEC): Clause 15 (NEC3) or 16 (NEC4); failure to issue this can reduce your payout.
Extension of Time (EOT): The general term for moving the completion date.
Force Majeure Clause: Usually Clause 19 (FIDIC) or similar; defines "Acts of God."
Variation / Change Clause: Claims arising from an instruction to alter the works.
Instruction Clause: Compliance with a formal instruction that causes delay.
Loss and Expense Clause: claiming the direct cost of the delay.
Suspension Clause: Rights to suspend for non-payment or safety.
Prevention Principle: Common law argument that the Employer cannot benefit from their own delay.
Time at Large: Argument that no completion date exists due to contract failure.
Notice of Claim (FIDIC 20.1): The strict 28-day notice requirement in older FIDIC forms.
Impediment or Prevention: Clauses dealing with the Employer blocking progress.
Exceptional Event: The new FIDIC 2017 term replacing Force Majeure.
Liquidated Damages Clause: Notifying to prevent the levying of LDs.
Common Law Rights: Relying on general legal principles regarding breach of contract.
Other: Bespoke clause insertions.

Step 8: Mitigation Measures

Why it matters: Every contract implies a "Duty to Mitigate." You must demonstrate you are actively trying to reduce the delay, or your claim may be slashed.

Re-sequencing Works: Swapping logic (e.g., starting internal fit-out before cladding is complete).
Working Overtime: Extending shifts to catch up (requires cost agreement).
Weekend / Night Work: 24/7 operations to recover critical path slippage.
Additional Labor Resources: Flooding the job with more operatives.
Additional Plant / Equipment: Bringing in extra cranes or excavators.
Changing Construction Method: Switching from in-situ concrete to pre-cast for speed.
Alternative Suppliers: Ditching a delayed vendor for a more expensive local one.
Accelerating Fabrication: Paying factory "rush fees."
Air Freight vs Sea Freight: Flying materials in to save weeks of shipping time.
Prioritizing Critical Path: Focusing all resources on the tasks driving the end date.
Reducing Scope (if agreed): Descoping elements to hit the date.
Partial Possession: Handing over parts of the building early to appease the client.
Protecting Works (Weather): Tenting or heating to allow work during storms.
Seeking Instructions: Asking the PM for direction on priority.
Negotiating with Utilities: Escalating connections to senior management.
None Possible at this Time: Stating clearly that mitigation is currently impossible.
Demobilizing to Save Cost: Sending labor away to stop the "cash burn" during a stop.
Other: Unique recovery strategies.

Step 9: Notice Formality Level

Why it matters: Context drives tone. A "Nuclear" legal letter on day one can destroy relationships; a "Chatty" email may not stand up in court.

Strictly Contractual: "Pursuant to Clause X, we hereby notify..." (Protective).
Formal Letter (Noticed): Standard business correspondence, formally issued.
Standard Notification Form: Using a pre-agreed template (e.g., NEC Early Warning form).
Early Warning (Collaborative): "We see a risk, let's solve it together" (NEC ethos).
Email (Confirmation of Verbal): "Following our chat on site, I am confirming..."
Site Meeting Minute Reference: Recording the delay in the official minutes.
Without Prejudice (Settlement): Discussing concessions without admitting liability.
Urgent / Immediate Notice: High-priority flag for safety or critical stops.
Condition Precedent Notice: Explicitly stating "This is a condition precedent notice."
Weekly Progress Report Update: Burying the notice in the regular reporting cycle (risky).
Defensive (Protecting Rights): Written solely to prevent future arguments.
Partnering / Alliance Style: "Best for Project" language.
Legal Counsel Drafted: Written by lawyers, signed by the project manager.
Request for Instruction: "Please instruct us on how to proceed."
Heads of Claim: High-level summary of the claim components.
Final Claim Submission: The definitive "Yellow Book" document.
Retrospective Notice: "We refer to the event of last month..." (Weakest form).
Other: Custom formality.

Step 10: Supporting Documentation

Why it matters: "He who owns the records, owns the claim." A notice is only as strong as the evidence attached to it.

Updated Program / Schedule: The .mpp or .xer file showing the new end date.
Impacted Baseline Program: Comparing the "As-Planned" vs. "As-Built."
Site Diaries / Daily Logs: Contemporaneous records of who was doing what.
Progress Photos: Date-stamped visual evidence of the delay (e.g., flooded trenches).
Weather Reports (Met Office): Official data proving the 1-in-10-year event.
Meeting Minutes: Agreed records of discussions.
Copies of Late Instructions: The email trail proving the information was late.
RFI Logs: The register showing the RFI aging status.
Drawing Revision Register: Proof of the design churn.
Supplier Correspondence: Letters from the factory confirming the delay.
Subcontractor Notices: The notices received from the supply chain.
Cost Impact Assessments: The "Quantum" calculation (Spreadsheet).
Expert Report: Independent opinion on the delay cause.
Delay Analysis (TIA / IAP): Time Impact Analysis or Impacted As-Planned method.
Notice of Non-Conformance: Proof of defective work causing the stop.
Instruction to Stop Work: The formal order to suspend.
Police Report (Theft/Damage): Third-party verification of criminal damage.
Other: Emails, sketches, or whatsapp screenshots.

Step 11: Financial Implications

Why it matters: Delay usually costs money. You must signal your intent to claim costs early, or the client may assume the delay is "cost neutral."

Claim for Loss & Expense: Direct costs incurred due to the delay.
Relief from Liquidated Damages: Asking not to be fined for being late.
Cost Neutral (Time Only): EOT only; no extra money requested.
Additional Preliminaries: Cost of site management, cabins, and power for the extended period.
Inflation / Fluctuation Costs: Increased material costs due to the timeline shift.
Disruption Costs: Loss of productivity (the "thickening" of costs).
Acceleration Costs: The price of speeding up to recover.
Storage Costs: Warehousing materials that cannot be installed yet.
Demobilization / Remobilization: Costs to leave and return to site.
Interest on Late Payment: Statutory interest on held cash.
Defined Cost (NEC): The specific cost components allowed under NEC options C/D/E.
Fee / Overhead & Profit: The contractor's margin on the delay costs.
Insurance Claim: Costs covered by CAR (Contractors All Risk) policy.
Head Office Overheads (Hudson/Emden): Formula-based recovery of off-site overheads.
Subcontractor Claims: Passing up the costs from the supply chain.
Recovery of Aborted Costs: Money wasted on work that was scrapped.
To Be Determined Later: Reserving the right to quantify later.
Other: Unique financial heads.

Step 12: Notification Timing

Why it matters: Time-bars are absolute killers. In many contracts (NEC, FIDIC), if you miss the window (e.g., 8 weeks), you lose your entitlement forever.

Immediate (Upon Awareness): The gold standard; notify as soon as the risk is spotted.
Within 7 Days of Event: Common tight deadline for initial notices.
Within 14 Days of Event: Standard JCT-style window.
Within 28 Days (FIDIC Strict): The rigid FIDIC 20.1 bar; miss this and the claim dies.
Within 8 Weeks (NEC): The NEC compensation event bar; fairly generous but absolute.
As Soon As Practicable: Vague legal term; allows some wiggle room but risky.
Prior to Event (Early Warning): Notifying a risk *before* it happens (Proactive).
Retrospective (Late Notice): Notifying after the fact; requires "Reasonable excuse" arguments.
Ongoing / Continuing Event: Notifying that a delay has started and is continuing.
Final Account Stage: Leaving it all to the end (High risk of failure).
Monthly Update: Including it in the monthly board report.
After Mitigation Failed: Waiting until you couldn't fix it yourself.
Before Next Payment Cycle: Timing it to get into the next valuation.
Following Risk Reduction Meeting: Formalizing the outcome of a meeting.
Start of Work Suspension: Must notify immediately upon down-tools.
End of Delay Event: Notifying that the delay has ceased (Step 2 of the process).
Within Contract Time Bar: Adhering strictly to the specific clause days.
Other: Custom timing.

Step 13: Tone of Voice

Why it matters: The "personality" of the notice affects the Recipient's reaction. Aggression breeds defense; collaboration breeds solution.

Professional & Objective: "Just the facts"; the safest default.
Firm & Assertive: Making it clear you will not back down on entitlement.
Collaborative / Partnering: "We are in this together, help us solve it."
Highly Legalistic: Citing case law and clauses; signals a dispute is brewing.
Warning / Cautionary: "If you don't do X, Y will happen."
Defensive / Protective: Written to shield against a counter-claim.
Urgent / Action-Oriented: Demanding immediate decisions.
Conciliatory / Diplomatic: Softening the blow of bad news.
Fact-Based / Dry: Removing all emotion; purely data-driven.
Detailed & Explanatory: Telling the whole story to ensure understanding.
Brief & To the Point: Minimalist; effectively a "heads up."
Notification Only (No Blame): "For your information, this is happening."
Requesting Help: Asking the Client to intervene (e.g., with neighbors).
Without Prejudice: Using the legal shield for negotiation.
Escalating the Issue: Going over the PM's head.
For the Record: "We told you so" (Paper trail building).
Contractually Rigid: Sticking to the exact wording of the contract form.
Other: Custom tone.

Step 14: Desired Outcome

Why it matters: A notice without a "Call to Action" is useless. You must clearly state what you want the Recipient to *do* with this information.

Grant of Extension of Time: The primary goal; moving the completion date.
Relief from Liquidated Damages: Confirming LDs will not be levied.
Agreement to Pay Loss & Expense: Getting the checkbook open.
Instruction to Accelerate: "Do you want us to speed up at your cost?"
Instruction to Proceed: Asking for the green light on a change.
Risk Reduction Meeting: Calling a Clause 16 (NEC) meeting to solve the issue.
Revised Completion Date: Formalizing the new end date.
Waiver of Requirements: Asking to skip a spec to save time.
Acceptance of Liability: Getting the Client to admit it's their fault.
Approval of Variation: Signing off the scope change.
Quotation Request: Asking for a price for the delay measures.
Stop the Clock: Freezing the contract period.
Record of Event Only: Creating a baseline for a future claim.
Prevention of Future Claims: Ensuring this doesn't snowball.
Release of Retention: If delay impacts sectional handover.
Negotiated Settlement: "Let's do a deal now."
Formal Determination: Asking the Engineer/Architect for a ruling.
Other: Specific outcome.

Execution & Deployment

Step 15: Context Injection: Paste the specific clause numbers, dates of the event, and the exact project address/name. This grounds the AI in your specific reality.
Step 16: Desired Output Format: The system generates a forensic prompt. Copy this output and paste it into your chosen AI model to generate the actual legal/contractual notice.

💡 PRO TIP: The "Condition Precedent" Trap: In modern contracts (especially NEC4 and FIDIC 2017), the notification clause is often a "Condition Precedent." This means if you fail to notify within the specific window (e.g., 8 weeks), you lose all entitlement to time and money, regardless of how valid your claim is. Never wait for full information—notify the "possibility" of delay immediately to stop the clock on the time-bar.

✨ Miracle Prompts Pro: The Insider’s Playbook

The "Silent Confirm" Hack: Send a meeting minute referencing the delay. If they don't object within 7 days, it becomes a record.
The RFI Trojan Horse: Disguise a delay notice as an innocent "Request for Information" about the missing design info.
The "Update Program" Trick: Submit a revised program showing the delay. If the PM accepts the program, they implicitly accept the delay logic.
The "Risk Register" Entry: Add the item to the Risk Register immediately. It proves you notified the team collaboratively.
The Weekend Email: Send notices late Friday. It often burns into their response time before they see it on Monday. (Aggressive).
The "Reference Sandwich": Cite the specific clause, then the event, then the clause again. It forces the recipient to look up the contract.
The Photo-Bomb: Attach 20+ photos to the notice. It makes it undeniable that the event is real and significant.
The "Duty to Mitigate" Shield: Explicitly list 3 things you are doing to solve the problem. It prevents them claiming you sat on your hands.
The "Reservation of Rights" Footer: Always end with "We reserve our rights to time and money" to prevent accidental waivers.
The "Draft for Discussion" Feint: Send a draft notice first to gauge reaction, then formalize it. Good for maintaining relationships.

📓 NotebookLM Power User Strategy

Source Selection: Upload the full Contract PDF, the Schedule of Amendments, and the Project Minutes for the last 3 months.
Audio Overview: Generate an Audio Overview to simulate a "Legal Counsel Briefing" listening to the contract's specific risks regarding notice timing.
Cross-Examination: Ask NotebookLM: "Based on Clause X, what is the exact deadline for this specific weather event notice?"
Gap Analysis: Compare your draft notice against the uploaded Contract. Ask: "Does this draft satisfy all requirements of Clause 20.1?"
Synthesis: Ask NotebookLM to generate a table of all "Condition Precedent" clauses in your specific uploaded contract to ensure you never miss a deadline.

🚀 Platform Deployment Guide

Claude 3.5 Sonnet: The Master Diplomat. Use Claude for drafting notices that need to be legally watertight but tonally collaborative to preserve client relationships.
ChatGPT-4o: The Bulk Generator. Best for creating variations of the same notice (e.g., "Give me one aggressive version, one soft version, and one formal version").
Gemini 1.5 Pro: The Contract Analyst. Use its massive context window to upload the entire JCT/NEC contract and ask it to cross-reference your notice against every single clause.
Microsoft CoPilot: The Workflow Integrator. Use it to draft the notice directly within Outlook or Word, pulling context from your recent email threads about the delay.
Perplexity: The Case Law Researcher. Use it to find relevant legal precedents (e.g., "Walter Lilly v Mackay") to support your argument if the client rejects your notice.

Quick Summary & FAQs

⚡ Quick Summary

The Notice of Delay Generator is a forensic prompt engineering tool designed to help construction professionals draft contract-compliant notifications. It navigates the complexities of JCT, NEC, and FIDIC forms to secure Extensions of Time and protect against Liquidated Damages through precise, time-barred correspondence.

📊 Key Takeaways

Contract Specificity: Tailors output for 17 specific forms including JCT, NEC3/4, and FIDIC Red/Yellow books.
Time-Bar Compliance: Addresses critical notification windows (7, 14, 28 days, or 8 weeks) to avoid "Condition Precedent" failure.
Causal Linkage: Forces the user to distinguish between "Relevant Events" (Time) and "Relevant Matters" (Money).
Mitigation Evidence: Prompts the user to list active measures (e.g., re-sequencing, overtime) to satisfy the "Duty to Mitigate."
Tone Control: Adjusts the formality from "Collaborative Early Warning" to "Strictly Contractual" based on project relationships.

❓ Frequently Asked Questions

Q: What is a "Condition Precedent" in delay notices?
A: It is a clause stating that if you fail to notify within a set time (e.g., 28 days in FIDIC), you lose all entitlement to time and money, regardless of the delay's validity.

Q: Can I use this for both JCT and NEC contracts?
A: Yes. Step 1 allows you to select your specific contract suite, ensuring the output uses the correct terminology (e.g., "Relevant Event" for JCT vs. "Compensation Event" for NEC).

Q: Why is the "Tone of Voice" selection important?
A: A notice serves two purposes: legal compliance and relationship management. Selecting the right tone ensures you protect your commercial position without unnecessarily destroying client relationships.

⚓ The Golden Rule: You Are The Captain
MiraclePrompts gives you the ingredients, but you are the chef. AI is smart, but it can make mistakes. Always review your results for accuracy before using them. It works for you, not the other way around!
Transparency Note: MiraclePrompts.com is reader-supported. We may earn a commission from partners or advertisements found on this site. This support allows us to keep our "Free Creators" accessible and our educational content high-quality.

The Ultimate Notice of Delay Generator