The programme for acceptance: getting your NEC programme accepted

Under the NEC3 and NEC4 Engineering and Construction Contract, the programme is far more than a Gantt chart on the site office wall. It is the legal yardstick against which delay, disruption and the entitlement to more time and money are measured — and an Accepted Programme is the single most valuable commercial asset a Contractor can hold.

South African construction teams who come to the NEC from JBCC or FIDIC are often surprised by how seriously the contract treats programming. In the NEC the programme is woven into the assessment of compensation events, the timing of access to site, and the calculation of how much time the Contractor is entitled to. Get the programme right and accepted early, keep it current, and you arm yourself for every conversation that follows. Neglect it, and you forfeit much of the protection the contract was designed to give you.

Clause 31: the first programme for acceptance

The starting point is clause 31. The Contractor either submits a programme with the tender, or — if the Contract Data does not identify a programme by name — submits a first programme for acceptance within the period stated in the Contract Data after the Contract Date. This is not a courtesy document. It is a contractual deliverable, and on most projects a slice of the Price for Work Done to Date is withheld until a first programme showing the information the contract requires has been submitted.

So what must that programme actually show? Clause 31.2 sets out a demanding list. The programme must show:

• the starting date, access dates, Key Dates and the Completion Date;
• planned Completion (the date the Contractor genuinely plans to finish, which may be earlier than the contractual Completion Date — the gap between the two is terminal float that belongs to the Contractor);
• the order and timing of the operations the Contractor plans to do the work in;
• the order and timing of the work of the Client (the Employer, in NEC3) and of Others;
• the float and the time risk allowances built into the programme;
• the health and safety requirements;
• the dates by which the Contractor needs access to each part of the site, information and acceptances from others, and the dates Plant and Materials and other things are to be provided by the Client;
• for each operation, a statement of how the Contractor plans to do the work, identifying the principal Equipment and other resources to be used — in other words, the method statements.

A note on terminology that trips people up: NEC4 renamed the Employer to the Client and the Works Information to the Scope. The substance of clause 31 is materially the same across the two editions, but the words on your particular contract will follow whichever edition you signed. We use the NEC4 terms below with the NEC3 equivalents in brackets where it matters.

The Project Manager's reply: two weeks, four reasons

Once a programme is submitted, the clock starts. The Project Manager must reply within two weeks, either accepting the programme or stating the reasons for not accepting it. This time limit is real and it is reciprocal — the same discipline the contract imposes on the Contractor to submit applies to the Project Manager to respond.

Crucially, the Project Manager cannot reject a programme for any reason that takes their fancy. The contract limits the grounds for non-acceptance to exactly four. A programme may be rejected only because:

1. the Contractor's plans are not practicable;
2. it does not show the information the contract requires;
3. it does not represent the Contractor's plans realistically; or
4. it does not comply with the Scope (the Works Information, in NEC3).

If the Project Manager's reason for rejection falls outside these four, it is not a valid reason under the contract. That matters in practice: a Project Manager who withholds acceptance because they dislike the sequence, or because they want the Contractor to finish sooner, or simply to keep negotiating leverage, is not exercising a contractual power. Knowing the four grounds turns a vague stand-off into a focused conversation about which specific deficiency must be fixed.

The Project Manager does not get to redesign your programme. They may accept it or give you one of four specific reasons not to — anything else is not a reason the contract recognises.

When a programme is accepted, it becomes the Accepted Programme. From that moment it is the baseline. When a compensation event is later assessed, the effect on the Completion Date and on Key Dates is judged against the Accepted Programme current at the dividing date of that event. No Accepted Programme means no agreed baseline — and that is a battle you do not want to fight retrospectively.

Clause 32: keeping the programme alive

A programme is not a once-off submission. Under clause 32, the Contractor submits revised programmes — at the intervals stated in the Contract Data, when instructed to by the Project Manager, and when the Contractor chooses to. Each revised programme must show the actual progress achieved on each operation and its effect on the rest of the work, how the Contractor plans to deal with any delays and correct notified Defects, and any changes the Contractor proposes to the plan. Each revision that is accepted becomes the new Accepted Programme.

This is where many South African projects quietly lose ground. The first programme is submitted, accepted, filed — and then never refreshed. Eighteen months later, when a dispute arises over a delay, there is no current Accepted Programme to demonstrate the effect of an event. The Contractor is left arguing from memory and reconstructed records. Discipline around clause 32 is what keeps the baseline meaningful.

NEC3 vs NEC4: deemed acceptance changes the game

The single most important difference between the editions on programmes is deemed acceptance, introduced by NEC4 at clause 31.3. Under NEC3, if the Project Manager simply sat on a submitted programme and never replied, the Contractor's only remedy was to treat the silence as a compensation event for a late reply — useful, but it did not produce an Accepted Programme.

NEC4 closes that gap. If the Project Manager does not reply to a submitted programme within the time allowed, the Contractor may notify the Project Manager of that failure. If the Project Manager then still fails to reply within one week of that notification, the programme is treated as accepted. In other words, persistent silence now works in the Contractor's favour rather than leaving the project without a baseline.

Why the Accepted Programme is your most valuable asset

It is worth being blunt about the commercial stakes. Almost every entitlement to extra time and money under the ECC is assessed by reference to the Accepted Programme. When a compensation event arises — a change to the Scope, late access, an instruction, a physical condition — its effect on Completion is measured against the planned Completion and the time risk allowances shown in the Accepted Programme. If those allowances and that float are not on the programme, you cannot point to them when it counts.

An up-to-date Accepted Programme protects the Contractor in three concrete ways. It fixes the baseline so delay is measured fairly. It records the float and time risk allowances that determine who absorbs slippage. And it documents the dates the Contractor needs access, information and free-issue items — so that when the Client is late, the breach is visible and quantifiable. A stale or absent programme surrenders all three advantages at once.