FIDIC Defects Notification Period Extension: A Notice Template You Can Adapt
A defect turns up in the last month of the Defects Notification Period — the pump seal fixed in March fails again in November — and both sides ask the same question: does the clock keep running, or does someone get to push it back? Sub-Clause 11.3 answers that, but almost nobody reads it until the deadline is close. This guide gives you the notice template, who is allowed to send it, and the two-year limit on how far it can go.
What the Defects Notification Period Extension Actually Does
The Defects Notification Period, or DNP, is the window after Taking-Over during which the Contractor remains on the hook to fix defects at its own cost. It typically runs for one year from Taking-Over unless the Contract Data states a different figure, and it ends with the Performance Certificate.
Sub-Clause 11.3 lets that window be pushed back in one specific situation: a defect or damage means the Works, a Section, or a major item of Plant cannot be used for the purpose for which it was intended. Rather than close the file on the scheduled date while something is still broken, the Contract lets the Employer extend the period until the problem is actually resolved.
This is not a general "add more time" power. It only bites when a specific defect is preventing actual use — a treatment plant that cannot run, a lift that cannot carry passengers. A cosmetic snag that does not stop anything being used does not, on its own, support an extension under this Sub-Clause.
Key Takeaway: Sub-Clause 11.3 extends the Defects Notification Period only when a defect or damage stops the Works, a Section, or a major item of Plant being used for its intended purpose — not for every minor snag still on the punch list.
Who Can Require It — and the Two-Year Cap
This is the Employer's entitlement, not the Contractor's. Under FIDIC 1999 it is treated as an Employer's Claim under Sub-Clause 2.5; under the 2017 Second Edition it runs through the unified Clause 20 claims procedure that now applies to both Parties. Either way, the Contractor cannot invoke Sub-Clause 11.3 to shorten or extend the period in its own favour — the initiative sits entirely with the Employer.
The extension itself is capped. Sub-Clause 11.3 states that the Defects Notification Period shall not be extended by more than two years beyond the expiry date stated in the Contract Data — regardless of how many separate defects arise or how many extension notices are issued during that time. Once that two-year ceiling is reached, no further extension is available under this Sub-Clause, whatever the state of the outstanding defect.
Timing matters as much as the ground relied on. Notice of the extension has to reach the Contractor before the original Defects Notification Period expires — an extension notice served after the period has already run out is simply too late to have effect.
Key Takeaway: Only the Employer can require an extension, it is capped at two years beyond the Contract Data expiry date no matter how many defects are involved, and the notice must go out before the original period ends.
Extension Notice Template — Copy and Adapt
Here is a skeleton for the Employer's notice. Replace everything in square brackets with the project's own facts, then delete the brackets.
Two things earn their place in that letter: the exact original expiry date, so the Contractor can check the notice was served on time, and why the defect stops actual use — not a general complaint that something is "not finished."
Key Takeaway: Name the original expiry date and explain precisely why the defect prevents intended use — those are the two facts the Contractor needs to test whether the notice is valid and on time.
Worked Example: A Filled-In Extension Notice
Here is the same template filled in for a water treatment plant where a recurring seal failure has kept one process train offline.
Notice what makes this checkable at a glance: the specific Section, the specific expiry date, and a failure history the Engineer can verify against its own inspection records in minutes rather than asking what "the defect" refers to.
Key Takeaway: Naming the affected Section, the exact original expiry date, and a short defect history turns the notice into something the Engineer can verify immediately, rather than a general assertion that needs a follow-up conversation.
FIDIC 1999 vs 2017: What Changed Under Sub-Clause 11.3
The two editions test the extension on different grounds, and this is the change Contractors are most often caught out by. Under the FIDIC 1999 Red Book, the Employer could require an extension whenever a defect or damage meant the Works, a Section, or a major item of Plant could not be used for its intended purpose — whatever the cause of that defect or damage.
The 2017 Second Edition narrows this considerably. It restricts the extension to cases where the defect or damage results from one of the Contractor-caused grounds listed in Sub-Clause 11.2(a)-(d). A defect that falls outside those specific grounds no longer supports an extension under the 2017 wording, even if it still prevents the Works being used.
The two editions also treat suspension differently. In both, a period of suspension does not, by itself, lengthen the Defects Notification Period — it runs as though the suspension had not happened. The 2017 edition adds a qualification: where the suspension was the Contractor's own fault, this protection no longer applies, so a Contractor-caused suspension cannot be used to argue the DNP should be treated as unaffected.
Key Takeaway: FIDIC 1999 lets any qualifying defect trigger an extension, whatever its cause. FIDIC 2017 narrows the trigger to defects caused by one of the specific grounds in Sub-Clause 11.2(a)-(d) — check which edition governs before assuming the ground applies.
Common Mistakes With This Notice
- Sending it after the original period expires. The notice has to land before the DNP's stated expiry date — after that, the entitlement is at serious risk, regardless of how genuine the underlying defect is.
- Treating any unfinished item as grounds for extension. Sub-Clause 11.3 requires the defect to stop the Works, Section, or major item of Plant being used for its intended purpose — a cosmetic snag list item does not qualify on its own.
- Assuming the 1999 test still applies under a 2017-based contract. The 2017 edition ties the extension to specific Contractor-caused grounds under Sub-Clause 11.2(a)-(d); a defect outside those grounds will not support an extension under that wording.
- Ignoring the two-year ceiling. No matter how many defects surface, the total extension available under Sub-Clause 11.3 stops at two years beyond the Contract Data expiry date.
- Assuming the Contractor can invoke this Sub-Clause. The entitlement runs one way — it is the Employer's claim to make, not a tool the Contractor can use to adjust its own liability period.
Key Takeaway: Most disputed extension notices fail on timing (sent after expiry), on the wrong test (a snag rather than a genuine loss of use), or on assuming the 1999 grounds apply to a 2017 contract.
Frequently Asked Questions
Who can require an extension of the Defects Notification Period — the Employer or the Contractor?
Sub-Clause 11.3 gives this entitlement to the Employer, not the Contractor. In the FIDIC 1999 Red Book it is treated as an Employer's Claim under Sub-Clause 2.5; in the 2017 Second Edition it runs through the unified Clause 20 claims procedure that now applies to both Parties. The Contractor cannot use Sub-Clause 11.3 to shorten or extend the period for its own benefit.
How long can the Defects Notification Period be extended?
The extension is capped at two years. Sub-Clause 11.3 states the Defects Notification Period shall not be extended by more than two years beyond the expiry date stated in the Contract Data, no matter how many separate defects or how many extension notices are given over that time.
Does FIDIC 2017 change who can trigger the extension?
Yes, and this is the change Contractors miss most often. Under FIDIC 1999, the Employer could require an extension whenever a defect or damage meant the Works, a Section, or a major item of Plant could not be used for its intended purpose, whatever the cause. The 2017 Second Edition narrows this: the Employer can only require an extension where the defect or damage results from one of the Contractor-caused grounds listed in Sub-Clause 11.2(a)-(d). A defect caused by something outside those grounds no longer supports an extension under the 2017 wording.
Does suspending the Works automatically extend the Defects Notification Period?
No. A period of suspension does not, by itself, lengthen the Defects Notification Period — it runs as though the suspension had not happened. The 2017 edition adds one qualification: a suspension caused by the Contractor's own default no longer benefits from this rule, so the Employer is not penalised by a delay the Contractor caused.
What happens if the Employer is late giving notice of the extension?
Notice has to reach the Contractor before the original Defects Notification Period expires. Miss that window and the Employer's entitlement to extend is at serious risk, on the same logic that time-bars a late Contractor notice under Sub-Clause 20.1 — a right that depends on a deadline does not survive missing it.
Authoritative Sources
This guide reflects the FIDIC Conditions of Contract and established construction-law commentary. For the primary materials, see:
- FIDIC Conditions of Contract — the official contract suite published by the International Federation of Consulting Engineers, which sets out the Sub-Clause 11.3 extension procedure referenced throughout this guide.
- 2017 Suite: Commentary on Clause 11 — Defects After Taking Over, Howard Kennedy — a clause-by-clause commentary covering the narrowed extension grounds and the suspension rule the 2017 Second Edition added to Sub-Clause 11.3.
About the Author
Muhammad M. Jiwani is a Project Director with 15 years' experience on major infrastructure and energy projects administered under FIDIC contracts. He writes from first-hand experience serving notices and managing contractual claims on live projects.