The role of the Supervisor under NEC3 and NEC4
On every NEC contract there is one person whose only concern is whether the works are actually being built right — not whether they are on time, not whether they are within budget, but whether they conform to what the Employer asked for. That person is the Supervisor, and understanding where their authority begins and ends is one of the most useful things a South African project team can learn.
NEC contracts deliberately split the management of a project between two named individuals. The Project Manager looks after time, cost and the commercial running of the contract. The Supervisor looks after quality and conformance. Confusing the two — or letting one person quietly do both jobs — is one of the most common reasons NEC contracts drift away from the discipline that makes them work. This article sets out exactly what the Supervisor does under the NEC3 and NEC4 Engineering and Construction Contract (ECC), how the role differs between the two editions, and why the boundary with the Project Manager matters in practice.
Quality, not commerce: what the Supervisor is for
Under both NEC3 and NEC4, the Supervisor is appointed by the Employer (the Client in NEC4 language) and named in the Contract Data. Their single, focused purpose is to check that the Contractor builds the works in accordance with the documents that describe the required quality and specification. Under NEC3 that document is the Works Information; under NEC4 the same document is called the Scope. The terminology changed, but the function did not: this is the master description of what is to be provided and how, including drawings, specifications, standards, and any constraints on how the work is carried out.

The Supervisor's toolkit is built around a handful of related duties: carrying out tests and inspections, watching and marking equipment, Plant and Materials, notifying Defects, requiring the searching for hidden Defects, and ultimately issuing the Defects Certificate. None of these touch price or programme — those belong to the Project Manager. The Supervisor is, in effect, the contract's quality conscience.
The Supervisor versus the Project Manager
The clearest way to hold the two roles apart is to remember a single rule: the Supervisor cannot change the Scope. Only the Project Manager can instruct a change to the Works Information or Scope, and such an instruction is what triggers a compensation event and the commercial machinery that follows. The Supervisor measures the work against the Scope as it stands; the Project Manager is the only one who can move the goalposts.
The Project Manager decides what the works must become; the Supervisor checks that they have become it. Keep those two pens in two different hands and the contract stays honest.
This division has real consequences on a South African site. If a Supervisor spots that a detail is impractical and tells the Contractor to build it differently, they have stepped outside their authority — that instruction has no contractual force and creates exactly the kind of grey area NEC was designed to eliminate. The correct route is for the Supervisor to flag the issue, very often through the early warning process, so the Project Manager can decide whether to instruct a change. Drawing this line cleanly is the foundation of disciplined NEC administration.
- Project Manager — time, cost, programme acceptance, compensation events, payment certificates, and any instruction changing the Scope.
- Supervisor — tests, inspections, notifying Defects, watching and marking Plant and Materials, searching for Defects, and the Defects Certificate.
- Shared discipline — both must act so that the contract operates in a spirit of mutual trust and co-operation, and both communicate in a form that can be read, copied and recorded.
Testing and inspection
Testing and inspections are dealt with in the contract's clause 4 (the 40-series in the ECC). The Scope or Works Information lists the tests and inspections required, who carries them out, the materials, facilities and samples to be provided, and the place at which each is done. The Supervisor and the Contractor each have the right to watch the other's tests, and the Supervisor must be notified before tests so they can attend.
A point worth stressing for SA teams: two distinct cost rules apply, and they should not be confused. First, if a test shows the work is not in accordance with the Scope, the cost the Contractor and Client incur in repeating the test after the Defect is corrected is borne by the Contractor — this rule turns on a Defect being found. Second, and independently of whether any Defect is found, if the Supervisor does not do a test or inspection within the time allowed and so causes the Contractor extra cost or delay, that is a compensation event (clause 60.1(11)) — assessed, naturally, by the Project Manager, not the Supervisor.
A Defect has a precise meaning
Under NEC, a Defect is not simply poor workmanship. It is a part of the works that is not in accordance with the Scope (NEC4) or Works Information (NEC3), or work that does not comply with the applicable law or the Contractor's own accepted design. If it conforms to the Scope, it is not a Defect — however unhappy anyone may be with it. That precision is exactly why the Scope must be written carefully in the first place.
Notifying Defects and the correction period
When the Supervisor finds work that does not meet the Scope, they must notify the Contractor of the Defect. Equally, the Contractor must notify the Supervisor of any Defect it finds — the obligation runs both ways. Each notification must happen before the defects date, the date stated in the Contract Data (typically a number of weeks after Completion) up to which Defects can still be notified.
Once a Defect is notified, the clock starts on the defect correction period — the time stated in the Contract Data within which the Contractor must correct that Defect. Critically, the period for a given Defect begins when access is available, and it can differ for different types of Defect if the Contract Data sets out more than one period. The Supervisor's job is to track these correction periods rigorously, because an uncorrected Defect at the end of its period carries cost consequences for the Contractor.
The quality loop the Supervisor runs
Access, watching, and the searching for Defects
The Supervisor's powers do not stop at finished work. They may watch the Contractor's tests, attend inspections, and they have the authority to mark equipment, Plant and Materials outside the Working Areas — for example at a precast yard or steel fabricator — so that ownership and conformance can be tracked even before the items reach site. Marking is the contract's way of giving the Client comfort over materials it may already be paying for.

The Supervisor may also instruct the Contractor to search for a Defect — to open up, uncover or test part of the works where the Supervisor suspects something is wrong but it is not yet visible. Here the cost rule mirrors testing: if the search reveals a Defect, the Contractor bears the cost of searching and correcting; if it reveals no Defect, the instruction to search becomes a compensation event, assessed by the Project Manager. This balance discourages frivolous searches while keeping the Supervisor's hand strong where there is genuine concern about hidden non-conformance.
The Defects Certificate
The Supervisor's process culminates in the Defects Certificate. This is the formal record either that the Contractor has no notified Defects left to correct, or that lists those that remain uncorrected. It is issued at the later of the defects date and the end of the last defect correction period — so if a Defect is notified close to the defects date, the certificate waits until that Defect's correction period has run out before it is issued.
The Defects Certificate matters commercially even though the Supervisor who issues it has no commercial role: it is the trigger that, among other things, releases the second half of any retention the Client has been holding. It is the clean line under the quality chapter of the contract — a single, dated document that says the works conform, or precisely where they do not.
- The Supervisor tests and inspects the works against the Scope (Works Information under NEC3).
- A Defect is notified — by either the Supervisor or the Contractor — before the defects date.
- The Contractor corrects the Defect within its defect correction period, once access is available.
- The Supervisor issues the Defects Certificate at the later of the defects date and the end of the last correction period.
What NEC4 changed
The Supervisor's core function survived intact from NEC3 into NEC4, but the 2017 edition sharpened the language and tidied some edges:
- Works Information became Scope. The single most visible change — same role, plainer word. The defined term Defect carried across from NEC3 to NEC4 essentially unchanged: work that is not in accordance with the Scope, the applicable law, or the Contractor's accepted design.
- Clearer correction triggers. NEC4 made it more explicit that the defect correction period for a Defect starts when access to and use of the affected work is given to the Contractor, reducing arguments over when the clock began.
- The boundary stayed firm. NEC4 retained the strict separation between the Supervisor's quality authority and the Project Manager's commercial authority — the Supervisor still cannot change the Scope.
- Communication and records. NEC4's general drift toward clearer, time-bound communications applies to the Supervisor too, reinforcing that notifications of Defects are formal contractual communications, not casual site chatter.
Getting the role right on a South African contract
In practice, the value of the Supervisor lies in discipline. Tests must be witnessed and recorded, Defects must be notified in the proper form and within the proper window, correction periods must be tracked Defect by Defect, and the Defects Certificate must be issued on the correct date. When this is done well, quality disputes shrink, retention is released cleanly, and the Project Manager is free to concentrate on time and money without becoming the de facto quality police. When it is done loosely — verbal instructions, undated notifications, blurred lines with the PM — the contract loses the very clarity it was chosen for.
How Contractly keeps the quality loop tight
Contractly gives the Supervisor a dedicated, auditable place to run the whole cycle: log tests and inspections, raise and serve Defect notifications in the correct contractual form, and watch every defect correction period count down so nothing slips past the defects date. Because the platform separates the Supervisor's actions from the Project Manager's commercial workflow, the NEC boundary is built into the software — not left to memory. When the time comes, the Defects Certificate is generated against a complete, dated record. See the features or Book a demo to see the quality loop running on your own contracts.


