The role of the Project Manager under NEC3 and NEC4

Under both NEC3 and NEC4, the Project Manager is the engine room of the contract. Appointed by the Employer (NEC3) or Client (NEC4), the PM runs the contract day to day — instructing, deciding, assessing and certifying — and the project lives or dies by how well that role is played.

If you have worked on an NEC contract in South Africa, you will know the Project Manager is not a passive overseer. The PM is named in the Contract Data and given a long list of express powers and duties throughout the conditions. Almost every important decision on the project flows through this one role: what gets built, how the programme is accepted, how risk is managed, how change is priced, and how the Contractor gets paid. Get the PM right and the contract administers itself. Get it wrong — late replies, vague instructions, no records — and disputes follow.

Crucially, the PM acts on behalf of the Employer/Client, but the role is not a free agent. The PM exercises a defined contractual function within stated time limits, and is bound by the overriding duty to act in a spirit of mutual trust and co-operation. This article walks through what the PM actually does under NEC3 and NEC4 ECC, and — just as importantly — what the PM does not do.

Giving instructions and changing the Scope

The PM's most visible power is the right to give instructions to the Contractor. The most significant of these is an instruction changing the Works Information (NEC3) or the Scope (NEC4) — in other words, changing what the Contractor is required to build or how. Such an instruction is one of the principal triggers for a compensation event, because changing the Scope changes the deal that was priced.

The PM also instructs on a wide range of operational matters: stopping or not starting work, dealing with objects of value or historical interest found on the Site, searching for Defects, and resolving ambiguities or inconsistencies in the documents. An NEC instruction must be given to the Contractor and put in writing — verbal directions on site that never make it into the record are a common source of grief. On a South African project where claims may later be tested before adjudication or arbitration, the discipline of written, dated, clearly-worded instructions is everything.

Accepting the programme (clause 31)

The programme is the heartbeat of an NEC contract, and the PM is its gatekeeper. Under clause 31, the Contractor submits a first programme for acceptance (and revised programmes thereafter), and the PM must respond within two weeks. The PM either accepts the programme or states a reason for not accepting it. The conditions limit the reasons the PM may give — for example, that the programme is not practicable, does not show the information the contract requires, does not represent the Contractor's plan realistically, or does not comply with the Works Information/Scope.

This is where one of the headline NEC3-versus-NEC4 differences for the PM appears. Under NEC4, if the PM does not reply to a submitted programme within the time allowed, the Contractor may notify the PM of that failure; if the PM still does not respond within a further period, the programme is treated as accepted — so-called deemed acceptance. NEC3 has no such automatic sanction in the programme provisions. NEC4 therefore puts real pressure on the PM to engage with the programme promptly rather than letting it drift.

Running the early warning process

NEC's celebrated early warning mechanism is a shared duty, but the PM is at its centre. Both the PM and the Contractor must notify each other as soon as either becomes aware of a matter that could increase the total of the Prices, delay Completion, delay a Key Date, or impair the performance of the works in use. NEC4 broadened the trigger slightly to include any matter that could increase the Contractor's total cost.

Once a matter is on the early warning register — called the Risk Register in NEC3 and renamed the Early Warning Register in NEC4 — the PM may instruct the parties to attend an early warning meeting (an NEC3 risk reduction meeting). The PM typically chairs these meetings, where attendees co-operate to make and consider proposals for how to avoid or reduce the effect of the risk, seek solutions that give best value to those who pay for it, and decide actions and who will take them. This forward-looking, collaborative habit is exactly what the spirit of mutual trust and co-operation is meant to produce.

The early warning meeting is the cheapest insurance on the project: a problem solved around the table before it crystallises almost always costs less in time and money than the compensation event that follows when it does not.

The compensation event procedure — the PM's core engine

If the programme is the heartbeat, the compensation event (CE) procedure is the nervous system, and the PM runs almost all of it. The mechanics live in clauses 61 to 65, and the PM is involved at every step.

1. Notification (clause 61). Some events the PM notifies (for example, a PM instruction changing the Scope); others the Contractor notifies. The PM decides whether the event is a compensation event and instructs the Contractor to submit a quotation, or states why it is not. Watch the eight-week timescale within which a Contractor must notify an event it has become aware of.
2. Quotation (clause 62). The Contractor submits a quotation — changes to the Prices and any delay to Completion or a Key Date — within three weeks of being instructed. The PM may instruct alternative quotations based on different ways of dealing with the event.
3. Assessment (clauses 63 and 64). The PM replies to the quotation within two weeks — accepting it, instructing a revised quotation, or notifying that the PM will make its own assessment. That own assessment (clause 64) is then made where, for example, the Contractor has not submitted a required quotation in time, has not assessed it correctly, or has not submitted the programme information the assessment needs. Assessment is based on the effect on Defined Cost plus the Fee, with the prevailing programme used to judge any delay.
4. Assumptions (clause 61.6). Where the effects of an event are too uncertain to forecast reasonably, the PM states the assumptions on which the quotation is to be based. If a stated assumption later proves wrong, the PM corrects it as a new compensation event — a sensible way to keep a fair-but-uncertain event moving.
5. Implementation (clause 65). Once a quotation is accepted or the PM's own assessment is made, the CE is implemented. A vital NEC principle: implemented compensation events are not revisited even if the forecast on which they were based proves inaccurate. This finality is what gives NEC its forward-pricing certainty.

Here the second big NEC3-to-NEC4 shift for the PM bites. Under NEC4, if the PM fails to reply to a Contractor's quotation within the time allowed, the Contractor can notify that failure, and continued silence results in the Contractor's quotation being treated as accepted — deemed acceptance again. Under NEC3 there was no such automatic consequence; a PM could leave a quotation unanswered and the Contractor's main remedy was to press the point. NEC4 deliberately removed that comfort, sharply incentivising the PM to keep to time.

Certifying payment — and where NEC3 and NEC4 part ways

The PM is also responsible for the money flowing to the Contractor, and this is one of the clearest differences between the two editions. Under NEC3, at each assessment date the PM assesses the amount due to the Contractor and issues a payment certificate. The initiative sits with the PM.

NEC4 reversed the starting point. The Contractor now submits an application for payment on or before each assessment date, and the PM certifies against that application. If the Contractor applies, the amount due is based on the application as corrected; and if the PM does not certify within the prescribed period, the Contractor's application can become the amount due by default. This aligns NEC4 with a payor-pays-on-application logic that South African contractors will recognise, and it places a firm onus on the PM to assess applications properly and on time. The PM must also make any necessary corrections — both editions allow the PM to correct a previous wrong certification in a later one.

What the PM does NOT do

A persistent misconception on site is that the Project Manager is the quality police. It is not. Under both NEC3 and NEC4, checking the quality of the work — carrying out tests and inspections and notifying Defects — is the job of the Supervisor, a separate named role. The PM and the Supervisor are deliberately distinct: the PM manages cost, time, change and the commercial running of the contract, while the Supervisor watches conformity with the Scope. Blurring the two leads to confused records and weakened claims.

• The PM gives instructions and changes the Scope; the Supervisor checks work against that Scope.
• The PM accepts the programme and assesses compensation events; the Supervisor notifies Defects.
• The PM certifies payment; the Supervisor's tests and inspections feed quality, not the money certificate directly.

Both, however, share the same overriding obligation: to act in a spirit of mutual trust and co-operation. The NEC philosophy is that the PM's powers are to be used to make the project succeed, not to gain tactical advantage.

Conclusion

The Project Manager is the busiest and most influential role on an NEC contract. Instructing change, accepting the programme, chairing early warning meetings, running the full compensation event procedure, and certifying payment — all of it sits on the PM's desk, all of it runs against the clock, and under NEC4 the deemed-acceptance provisions mean missed deadlines have real, automatic consequences. A disciplined PM who keeps to time, records every decision, and works collaboratively is the single biggest factor in whether an NEC project finishes on programme and out of dispute.