Defects under NEC: notification, correction and the Defects Certificate

Few things test the discipline of an NEC contract like a Defect. The edition you are working under — NEC3 or NEC4 — gives you a precise definition, a clear process for notifying and correcting, and a single document that closes the whole chapter: the Defects Certificate. Get the process right and quality disputes shrink; get it loose and the contract loses the certainty it was chosen for.

Defects are dealt with in section 4 of the Engineering and Construction Contract (the 40-series clauses, 40 to 45). The regime is one of the clearest parts of NEC: it tells the parties what a Defect is, who must notify whom, by when a Defect must be corrected, what happens when it is not, and how the contract finally signs off on quality. This article walks through that regime as it applies on a South African contract, and sets out exactly where NEC3 and NEC4 differ.

What counts as a Defect

The word "Defect" has a strict, defined meaning under NEC — it is not a loose synonym for shoddy work. A Defect is a part of the works which is not in accordance with the Works Information (NEC3) or the Scope (NEC4); or a part of the works which is not in accordance with the applicable law or the Contractor's design that the Project Manager has accepted. That is the whole test. The definition lives at clause 11.2(5) in NEC3 and at clause 11.2(6) in NEC4 — the clause number shifted, but the substance carried across essentially unchanged.

This precision matters. If the work conforms to the Scope, the applicable law and the accepted design, then it is not a Defect — no matter how unhappy anyone on site may be about it. Conversely, perfectly tidy work can still be a Defect if it simply does not match what the Scope required. That is exactly why the Scope (or Works Information) must be written carefully in the first place: it is the yardstick against which every alleged Defect is measured.

Notifying a Defect — the obligation runs both ways

NEC does not leave the Supervisor as the sole hunter of Defects. The obligation is mutual: the Supervisor and the Contractor each notify the other as soon as they find a Defect. A Contractor that quietly conceals its own non-conformance is in breach of this duty — under NEC the honest course is to put the Defect on the record, not to bury it. In practice this is one of the reasons NEC works so well as a collaborative form: both parties are pulling in the same direction on quality.

There is a window for all of this. Defects can be notified up to the defects date, a date that falls a stated period after Completion. That period is set in the Contract Data — commonly fifty-two weeks on a building or infrastructure contract, though it is whatever the parties have agreed. The defects date is the long-stop for raising new Defects: once it has passed, the Supervisor can no longer notify a Defect, even one that comes to light later. This is why diligent inspection in the months after Completion is so important, and why South African teams should never treat the post-Completion period as dead time.

The defects date is not the deadline for fixing Defects — it is the deadline for finding them. Miss it, and a genuine non-conformance can no longer be notified, however real it is.

The defect correction period

Once a Defect has been notified, the Contractor must put it right within the defect correction period — the time stated in the Contract Data for correcting a notified Defect. The period is a duration, not a fixed date, and it runs separately for each Defect. The Contract Data can also set out more than one correction period, so that, say, an urgent safety-related Defect carries a much shorter period than a minor cosmetic one. Tracking each period Defect by Defect is therefore essential; a single global deadline will not do.

The crucial question is when the clock starts. The correction period for a Defect begins when access to the affected work is available to the Contractor — it would be unfair to run the clock while the Contractor is locked out by other operations or by the Client's use of the works. NEC4 made this explicit, spelling out that the defect correction period starts when the Contractor is given access to and use of the part of the works affected, which removed a recurring argument under NEC3 about exactly when the period began.

When a Defect is not corrected in time

NEC does not rely on goodwill alone. If the Contractor fails to correct a notified Defect within its defect correction period, the contract gives the Project Manager a remedy: the Project Manager assesses the cost the Client would incur in having others correct the Defect, and the Contractor pays that amount. In effect, the Client may bring in another party to put the work right and recover the cost from the Contractor. The right is the Project Manager's to exercise, and the assessment is the Project Manager's to make — a reminder that, while the Supervisor polices quality, the commercial consequences of an uncorrected Defect sit with the Project Manager.

There is a related point worth flagging for SA teams. Where access was the reason the Contractor could not correct a Defect — for instance, the Client never gave access within the correction period — the contract recognises this, and the assessment reflects the cost of correction the Contractor would itself have incurred. NEC is careful not to penalise the Contractor for an obstruction that was not of its making.

Accepting a Defect

Sometimes it makes no commercial sense to correct a Defect at all. The work may be functionally fine, the cost of correction disproportionate, or the programme impact severe. NEC provides a sensible route: the Contractor and the Project Manager may agree that the Contractor need not correct a particular Defect. Either party can propose this. If they agree, the Contractor submits a quotation for the reduced Prices, an earlier Completion Date, or both, and — crucially — the Scope (or Works Information) is changed so that the work as built now conforms to it, and the Prices are changed accordingly.

That last step is the elegant part of the mechanism. By changing the Scope to accept the as-built work, the Defect simply ceases to be a Defect: the yardstick has moved to meet the work. It is a negotiated, recorded, two-signature decision — not a quiet site agreement to look the other way. Used properly, accepting a Defect lets a project move on pragmatically without abandoning the contract's discipline.

• Either the Contractor or the Project Manager may propose that a Defect is not corrected.
• The Contractor submits a quotation for changing the Prices, the Completion Date, or both.
• If they agree, the Project Manager changes the Scope (Works Information), the Prices and, if relevant, the Completion Date to reflect the acceptance.

The Defects Certificate

The whole regime culminates in the Defects Certificate. This is the formal document, issued by the Supervisor, that records either that the Contractor has no Defects left to correct, or that lists the Defects which remain uncorrected. It is the clean line under the quality chapter of the contract — a single, dated record of where the works stand on conformance.

Its timing is fixed and worth committing to memory. The Defects Certificate is issued at the later of the defects date and the end of the last defect correction period. The logic is straightforward: if a Defect is notified close to the defects date, its correction period may run on beyond that date, so the certificate must wait until that last period has expired before it can fairly be issued. The Supervisor cannot rush it, and cannot forget it.

1. The Supervisor and the Contractor test, inspect and notify Defects, each before the defects date.
2. The Contractor corrects each notified Defect within its defect correction period, once access is available.
3. Any Defect not corrected in its period is assessed by the Project Manager, and the Contractor pays for others to correct it.
4. The Supervisor issues the Defects Certificate at the later of the defects date and the end of the last correction period — listing any Defects that remain.

The certificate carries real commercial weight even though the Supervisor who issues it has no commercial role. On most South African ECC contracts it is the event that triggers the release of the remaining retention the Client has been holding, and it marks the point from which other end-of-contract obligations run. For the Contractor, in particular, the Defects Certificate is the document that finally unlocks money — which is exactly why neither party can afford to let the underlying process drift.

Pulling it together

The NEC defects regime is deliberately mechanical, and that is its strength. A Defect has a precise definition; either party must notify it; it must be corrected within a stated period that starts when access is given; failure to correct has a clear commercial consequence; a Defect can be formally accepted with a Scope and Prices change; and the Defects Certificate, issued at the later of two defined dates, draws the whole thing to a close. NEC3 and NEC4 run this regime in almost identical fashion — the principal differences being the rename of Works Information to Scope, the shift of the Defect definition from clause 11.2(5) to clause 11.2(6), and NEC4's helpful clarification that the correction period starts when access is given. Administer it tightly and the works are signed off cleanly, retention is released on time, and quality disputes have nowhere to hide.