The role of the Contractor under NEC3 and NEC4

Under the NEC suite, the Contractor is far more than a builder who turns up and gets paid at the end. The Contractor is an active, time-bound participant in a collaborative project-management machine — and understanding exactly what NEC3 and NEC4 ask of you is the difference between a profitable contract and a claims battlefield.

The NEC Engineering and Construction Contract (ECC) places the Contractor at the centre of a tightly choreographed process of programming, early warning, compensation events and payment. For South African contractors — many of whom cut their teeth on GCC or JBCC — the NEC mindset can feel unfamiliar at first. It is proactive rather than reactive, it runs on strict timescales, and silence has consequences. This article walks through the Contractor's core obligations and rights under both NEC3 and NEC4 ECC, and flags the practical differences between the two editions that actually change how you work on site.

Providing the Works: the Contractor's headline obligation

The Contractor's fundamental duty is set out in clause 20.1: to Provide the Works in accordance with the contract documents. The wording is deceptively simple, but the source document changed between editions, and the change matters.

• Under NEC3, the Contractor Provides the Works in accordance with the Works Information — the document that describes what is to be built and any constraints on how it is to be done.
• Under NEC4, the same role is performed by the Scope. The concept is identical; the terminology was simplified and aligned across the NEC4 suite.

If something is necessary to Provide the Works but is not shown in the Works Information / Scope, the Contractor is generally obliged to do it. Conversely, anything that is an error or inconsistency in those documents is the Employer's (NEC4: Client's) risk and is corrected through the compensation event process — not absorbed quietly by the Contractor. Reading the Scope carefully against the drawings and specifications, and notifying ambiguities early, is therefore one of the most valuable things a site team can do in the first weeks of a contract.

Design obligations

Whether the Contractor designs any part of the works depends on what the Scope says. NEC allocates design through the Works Information / Scope and the chosen main and secondary Options. Where the Contractor is responsible for design, that design must be submitted to the Project Manager for acceptance before the relevant work proceeds. By default the Contractor's design must comply strictly with the Works Information / Scope — effectively a fitness-for-purpose-style obligation. That liability is reduced to the reasonable skill and care normally expected of a professional only where secondary Option X15 (limitation of the Contractor's design liability to reasonable skill and care) is included in the contract. The point for the Contractor is simple: know precisely which elements you are designing, because that scope drives both your professional-indemnity exposure and your right to compensation if the design brief changes.

The programme: clauses 31 and 32

If there is one discipline that separates a well-run NEC contract from a troubled one, it is the programme. NEC treats the programme as a live management tool, not a tender-stage formality filed and forgotten.

Under clause 31, the Contractor submits a first programme for acceptance — either with the tender or within the period stated in the Contract Data. That programme must show far more than bar lines. It typically includes the starting and completion dates, planned Completion, the order and timing of operations, float, time risk allowances, the dates the Contractor needs access and information, and how the Contractor plans to do the work.

The Project Manager then either accepts the programme or states reasons for not accepting it. The permitted reasons are limited — for example, that the programme is not practicable, does not show what the contract requires, does not represent the Contractor's plans realistically, or does not comply with the Scope. Once accepted, it becomes the Accepted Programme, and under clause 32 the Contractor must keep it current by submitting revised programmes at the intervals stated in the Contract Data and whenever circumstances require.

An up-to-date Accepted Programme is the Contractor's single most powerful commercial asset. It is the baseline against which every compensation event is assessed — without it, your entitlement to time and money is far harder to prove.

Early warning: the heart of the NEC philosophy (NEC3 clause 16 / NEC4 clause 15)

This duty — clause 16 in NEC3, renumbered clause 15 in NEC4 — obliges the Contractor to give an early warning as soon as it becomes aware of any matter that could increase the total of the Prices, delay Completion or a Key Date, or impair the performance of the works in use. This is a no-fault, forward-looking duty: it does not matter whose risk the matter is. The Contractor and the Project Manager both have the obligation, and both rely on it to manage problems while there is still time to act.

Matters notified are recorded in the Risk Register (NEC3) — renamed the Early Warning Register in NEC4 — and either party may instruct the other to attend an early warning meeting (NEC3 calls these risk reduction meetings). At those meetings the parties cooperate to find solutions, decide actions, and record who does what. There is a real commercial sting in failing to warn: if the Contractor did not give an early warning that an experienced contractor could have given, a later compensation event is assessed as if the warning had been given — potentially reducing what the Contractor is paid.

Compensation events: clauses 61 and 62

Compensation events are the mechanism by which the Contractor's time and money are adjusted for events that are at the Employer's / Client's risk. The process is strict, and the timescales are real obligations — not guidelines.

1. When a compensation event arises that the Project Manager has not notified, the Contractor must notify it within eight weeks of becoming aware of the event. Miss that window for an event you should have notified, and you can lose your entitlement to changed Prices and dates altogether.
2. Once instructed, the Contractor submits a quotation — comprising the change to the Prices and any delay to the Completion Date (and any Key Dates), measured by the effect on planned Completion shown on the Accepted Programme — normally within three weeks.
3. The Project Manager then replies within two weeks: accepting the quotation, asking for a revised one, making their own assessment, or notifying that the event will not be a compensation event.

Correcting Defects and the defects process — clause 4

A Defect is work that does not comply with the Scope / Works Information or the applicable law and the Contractor's design. The Supervisor and the Contractor notify each other of Defects, and the Contractor must correct each notified Defect within the defect correction period stated in the Contract Data, with the period running from Completion or from notification, as the contract provides. Defects found before Completion are corrected before the defects date; uncorrected Defects ultimately lead to an assessed cost of correction. The Defects Certificate is issued at the later of the defects date and the end of the last correction period — a milestone the Contractor should actively manage towards.

Payment — and the biggest NEC3 vs NEC4 change for the Contractor

Here is the difference every South African Contractor moving from NEC3 to NEC4 needs to understand, because it changes who drives the cash flow:

• NEC3: the Project Manager assesses the amount due at each assessment date and certifies payment. The Contractor's role is to provide records to support that assessment, but the initiative sits with the PM.
• NEC4: under clause 50.2 the Contractor applies for payment on or before each assessment date. If the Contractor does not apply, the amount due is limited (broadly) to the previously certified amount — so the duty to apply on time is now squarely the Contractor's, and missing it directly affects your cash flow.

NEC4 also introduced deemed acceptance to discourage administrative silence. If the Project Manager does not respond within the relevant period to a Contractor's quotation for a compensation event, the Contractor may notify this; failure to respond to that notification can result in the quotation being treated as accepted. A comparable deemed-acceptance discipline applies to programme submissions. NEC3 has no equivalent — a non-responsive PM under NEC3 simply leaves the Contractor without acceptance and forces a different route. For the Contractor, the NEC4 regime is a genuine protection, but only if you operate the notification mechanics correctly.

In NEC4, the Contractor holds the pen on payment. Apply on time, every time — an unsubmitted application is unbilled work, and the contract no longer requires the Project Manager to chase it for you.

Conclusion: the proactive Contractor wins

Across both editions, NEC rewards the Contractor who manages the contract actively: an Accepted Programme that is genuinely current, early warnings raised the moment a risk appears, compensation events notified and quoted inside the timescales, Defects corrected on time, and — under NEC4 — payment applications submitted without fail. The differences between NEC3 and NEC4 mostly move responsibility and initiative towards the Contractor, especially on payment and through deemed acceptance. That is an opportunity, not a burden, for a contractor who keeps disciplined records. The risk is that these obligations are scattered across emails, spreadsheets and site diaries until a deadline is quietly missed.