Overview of NEC4 programme provisions
The NEC4 Engineering and Construction Contract (ECC) places the programme at the centre of project management and contract administration. Unlike many standard forms of contract where the programme is a secondary document, the NEC4 ECC treats the accepted programme as the primary tool for managing time, risk, and change. For contractors working under NEC4, understanding the NEC4 programme requirements is not optional -- it is fundamental to protecting commercial interests and maintaining contractual compliance.
Three core clauses govern the programme under NEC4 ECC. Clause 31 establishes the requirements for what the programme must contain and the process for submission and acceptance. Clause 32 addresses the Contractor's obligation to submit revised programmes at regular intervals and following specific trigger events. Clause 36 governs acceleration, providing the mechanism by which the Project Manager may instruct the Contractor to achieve Completion before the Completion Date.
The programme's significance under NEC4 extends well beyond time management. It underpins the assessment of compensation events, supports the early warning and risk management process, and provides the baseline against which progress is measured. A contractor who fails to maintain an accepted programme NEC faces serious consequences: under Clause 50.5, if the Contractor has not submitted a programme or revision as required, one quarter of the Price for Work Done to Date is retained until the programme is submitted. This financial mechanism ensures that programme management receives the attention the contract demands.
What the accepted programme must show under Clause 31.2
NEC4 Clause 31.2 sets out a comprehensive list of information that the accepted programme must contain. This is not a general aspiration -- each element is a specific contractual requirement, and failure to include any item gives the Project Manager grounds to withhold acceptance.
The programme must show the starting date, all access dates, each Key Date with its associated condition, and the Completion Date. These are Contract Data entries that fix the temporal framework of the project. The programme must also show planned Completion -- the date by which the Contractor plans to complete all work. The distinction between planned Completion and the Completion Date is critically important and underpins the concept of terminal float.
Beyond these fixed dates, the programme must show the order and timing of the operations which the Contractor plans to carry out. This means the full logic-linked sequence of activities, showing how the Contractor intends to execute the works. The programme must include the order and timing of the work of the Client and Others as identified in the Scope, ensuring that dependencies on third parties are visible. It must show each date when the Contractor will need something from the Client, such as design approvals, access, or information releases.
The programme must identify float and time risk allowances. Float is the spare time within the programme logic that arises naturally from the sequencing of activities. Time risk allowances are buffers the Contractor has included within individual activity durations or sequences to account for foreseeable risks. The NEC4 ECC requires these to be shown separately, ensuring transparency about how the Contractor has built contingency into the programme.
The critical path must be identified -- the longest logical sequence of activities through the programme from the starting date to planned Completion (or to each Key Date). Health and safety requirements must be shown, reflecting the Contractor's obligations under CDM Regulations and other statutory provisions. The programme must also show any other information required by the Scope, which commonly includes resource profiles, procurement schedules, and method-related information.
Terminal float, total float, and free float in the NEC4 context
Float management under NEC4 is one of the most frequently misunderstood aspects of the contract. Three distinct types of float arise in NEC4 programme management, and each has different contractual implications.
Terminal float is the period between the Contractor's planned Completion and the contractual Completion Date. Under NEC4, this float belongs to the Contractor. The Project Manager cannot instruct the Contractor to bring planned Completion forward to absorb the terminal float, nor can the Client benefit from it when assessing compensation events. If the Contractor plans to complete four weeks before the Completion Date, that four-week terminal float is the Contractor's to use as contingency. This principle was established in the NEC3 case law and is reinforced under NEC4.
Total float is the amount of time an activity can be delayed without affecting planned Completion (or the Completion Date, depending on how the critical path is measured). Total float exists within the programme logic and arises from the sequencing of non-critical activities. Under NEC4, total float is treated as a shared resource -- it is available to either party on a first-come, first-served basis. Neither the Contractor nor the Client owns total float exclusively. When a compensation event is assessed, the impact is measured against the programme at the time the event occurs, and available total float may absorb some or all of the delay.
Free float is the amount of time an activity can be delayed without affecting the start of any immediately succeeding activity. Free float is a subset of total float and provides a measure of scheduling flexibility at the individual activity level. In Primavera P6, free float is calculated automatically and provides useful information for short-term planning and progress monitoring, though it receives less contractual attention than terminal and total float.
Getting these distinctions right matters enormously when assessing delay and preparing compensation event quotations. Contractors who do not clearly show terminal float in their programme risk having it consumed by Client-caused delays without compensation. Equally, contractors who treat total float as exclusively theirs may find their compensation event assessments challenged.
Programme submission timelines under Clause 31.1
NEC4 Clause 31.1 addresses the initial programme submission. If the Contractor is not required to submit a programme for acceptance with the tender (identified in Contract Data part two), the Contractor must submit a first programme for acceptance within the period stated in Contract Data part two after the Contract Date. This period is typically stated as a number of weeks -- commonly two to four weeks.
The Project Manager must respond to a programme submission within two weeks of receiving it. The response is either acceptance or notification of non-acceptance with reasons. If the Project Manager fails to respond within two weeks, the Contractor may notify the Project Manager that a reply is required, and if no response is received within a further two weeks, the programme is treated as accepted. This deemed acceptance mechanism protects contractors from delays caused by an unresponsive Project Manager, though in practice it is better to pursue active acceptance.
Under Clause 32.2, the Contractor must submit a revised programme at intervals no longer than the period stated in Contract Data part two. This interval is typically four weeks, though it varies by project. The Contractor must also submit a revised programme when the Project Manager instructs one, when a compensation event changes planned Completion or a Key Date, or when the Contractor becomes aware that the programme does not reflect actual progress or future plans.
Timing discipline is essential. Late submission gives the Project Manager grounds for non-acceptance under Clause 31.3, and persistent failure to maintain an accepted programme triggers the retention mechanism under Clause 50.5. Contractors should establish programme update cycles at the outset of the project and build them into their project management processes.
Reasons for non-acceptance under Clause 31.3
Clause 31.3 provides an exhaustive list of reasons for which the Project Manager may decline to accept a submitted programme. This is a closed list -- the Project Manager cannot refuse acceptance for reasons outside those stated. Understanding these grounds is essential for contractors preparing submissions and for commercial managers responding to non-acceptance notifications.
The Project Manager may not accept a programme if the Contractor's plans are not practicable. This means the programme must be realistic -- activity durations must reflect achievable production rates, logic must be sensible, and the overall plan must be deliverable with available resources. A programme showing unrealistic compression or illogical sequencing can be rejected on this basis.
Non-acceptance may occur if the programme does not show the information required by the contract. As outlined above, Clause 31.2 sets out specific information requirements. If the programme omits any element -- for example, if it does not show the critical path, or does not identify float and time risk allowances separately -- the Project Manager has grounds for non-acceptance.
The programme may be rejected if it does not comply with the Scope. The Scope may contain specific programming requirements such as phasing constraints, sectional completion requirements, or restrictions on working hours. A programme that does not reflect these constraints can be refused.
The Project Manager may also refuse acceptance if the programme does not show the operations of the Client and Others realistically, or if it has been submitted late. The requirement for realistic representation of third-party activities ensures that the programme functions as a genuine coordination tool rather than a one-sided planning document.
When the Project Manager does not accept a programme, they must notify the Contractor of each reason for non-acceptance within two weeks. The Contractor then has the opportunity to address the identified issues and resubmit. Commercial managers should treat non-acceptance notifications as formal correspondence requiring a structured response -- simply resubmitting without addressing the stated reasons will likely result in further non-acceptance.
Compensation events and the programme under Clause 63.5
The interaction between compensation events and the programme is one of the most commercially significant aspects of NEC4. Clause 63.5 establishes that the assessment of a compensation event uses the accepted programme current at the dividing date -- either the date of the Project Manager's notification of the event or the date of the Contractor's notification, depending on who raises it.
When assessing the time impact of a compensation event, the Contractor must demonstrate how the event affects planned Completion or any Key Date by reference to the accepted programme. This means the accepted programme NEC effectively serves as the delay analysis baseline. If the Contractor does not have an accepted programme at the time of the compensation event, the assessment becomes significantly more difficult, and the Project Manager may make their own assessment, which is unlikely to favour the Contractor.
The assessment must show the effect of the compensation event on the planned Completion by adding the event to the accepted programme and calculating the resulting delay. This is a prospective assessment -- it looks forward from the programme as it stood, rather than retrospectively analysing what actually happened. Time risk allowances are not removed from the programme for this assessment; they are treated as legitimate elements of the Contractor's plan.
Changes to planned Completion resulting from accepted compensation events feed directly into revised programme submissions. The Contractor's revised programme should incorporate the assessed effects of all implemented compensation events, providing an updated baseline for future assessments. This creates a rolling record of how the programme has evolved in response to change, which is valuable for both ongoing management and any subsequent dispute resolution.
Early warning and risk reduction meetings under Clauses 15 and 16
NEC4 introduced a significant change from NEC3 by replacing the early warning register with the Risk Register. This is more than a name change -- it reflects a broader emphasis on proactive risk management throughout the contract. The programme plays a central role in this process.
Under Clause 15.1, the Contractor and the Project Manager must each notify the other 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. These early warnings are recorded on the Risk Register, which is maintained by the Project Manager.
Clause 16 requires the Project Manager to hold risk reduction meetings to discuss matters on the Risk Register and decide on actions. The programme provides the context for these discussions: when the risk reduction meeting considers a potential delay, the accepted programme shows the current plan against which the impact can be assessed. Proposed mitigation measures -- resequencing work, adding resources, or changing methods -- can be evaluated by reference to the programme logic.
Contractors who actively engage with the early warning and risk reduction process gain significant advantages. Early notification of risks that may become compensation events establishes a clear record. The risk reduction meeting provides a forum for discussing programme impacts before they crystallise into formal disputes. And the Risk Register creates a documented trail of risk identification and management actions that supports both ongoing project management and retrospective analysis.
Failure to give early warning has consequences. Under Clause 63.7, if the Contractor did not give an early warning that an experienced contractor could have given, the compensation event is assessed as if the early warning had been given. This can reduce the assessed impact -- and therefore the time and cost recovery -- available to the Contractor.
How Primavera P6 supports NEC4 compliance
Primavera P6 is the industry-standard scheduling tool for NEC4 contract compliance, and for good reason. Its capabilities map directly to the contractual requirements of the NEC4 ECC programme.
P6 produces logic-linked programmes showing the order and timing of operations with genuine finish-to-start, start-to-start, finish-to-finish, and start-to-finish relationships. This satisfies the NEC4 Clause 31.2 requirement for programmes that show the planned sequence of work and the relationships between activities. Unlike bar chart tools that allow activities to be positioned without logic, P6 enforces logical dependency management, producing programmes that are both contractually compliant and analytically useful.
The critical path method (CPM) calculation engine in P6 automatically identifies the critical path through the programme and calculates total float and free float for every activity. This directly supports the Clause 31.2 requirements for critical path identification and float visibility. The Contractor can demonstrate which activities drive planned Completion and where flexibility exists within the programme.
Baseline management in P6 allows the Contractor to maintain the accepted programme as a baseline and measure actual progress against it. This is essential for the compensation event assessment process under Clause 63.5, where the accepted programme at the dividing date forms the basis of the time impact assessment. P6 stores multiple baselines, enabling the Contractor to maintain a history of accepted programme revisions.
P6's resource loading capabilities allow the Contractor to demonstrate that the programme is practicable -- a key acceptance criterion under Clause 31.3. By assigning resources to activities and generating resource histograms, the Contractor can show that labour, plant, and material requirements are achievable and do not exceed available capacity. Resource-loaded programmes also support claims for disruption or acceleration where resource levels must be demonstrated.
User-defined fields and activity codes in P6 enable the Contractor to tag activities with NEC-specific information: whether an activity carries time risk allowance, which early warnings or Risk Register items are associated with particular activities, and which compensation events affect specific parts of the programme. This structured data supports both day-to-day management and retrospective analysis.
Common mistakes contractors make with NEC4 programmes
Despite the clarity of the NEC4 provisions, contractors regularly make avoidable errors that undermine their commercial position. Understanding these common mistakes helps project teams avoid them.
Not maintaining an accepted programme. This is the single most damaging mistake. Without an accepted programme, the Contractor loses the baseline for compensation event assessments, weakens their position in dispute resolution, and triggers the retention mechanism under Clause 50.5. Some contractors allow their programme to lapse after initial acceptance, failing to submit revisions at the required intervals. This creates a gap in the contractual record that is difficult to fill retrospectively.
Failing to show terminal float separately. If the programme shows planned Completion at the same date as the Completion Date, the Contractor has no terminal float -- or, more accurately, has surrendered visibility of it. Terminal float should be clearly identifiable in the programme as the gap between planned Completion and the Completion Date. Contractors who compress their programme to show planned Completion at the Completion Date lose the protection that terminal float provides against Client-caused delays.
Not distinguishing float from time risk allowances. NEC4 Clause 31.2 requires both to be shown. Float arises naturally from the programme logic and is available to either party. Time risk allowances are deliberate buffers included by the Contractor to manage identified risks. Mixing these up -- or failing to show either -- gives the Project Manager grounds for non-acceptance and creates confusion when assessing compensation events.
Submitting programmes without proper logic. Bar charts with no logical links, or programmes with excessive constraints (such as mandatory start dates on every activity) rather than genuine logic, do not satisfy the contractual requirements. The Project Manager can reject such programmes as not showing the information required by the contract. More practically, programmes without proper logic cannot produce meaningful critical path analysis or float calculations.
Ignoring the two-week response cycle. When the Project Manager does not respond to a programme submission within two weeks, the Contractor has the right to notify and trigger the deemed acceptance mechanism. Contractors who fail to track response timelines miss this opportunity and allow programme submissions to remain in limbo indefinitely.
Treating the programme as a planning tool only. Under NEC4, the programme is a contract document with commercial and legal significance. Contractors who view it purely as a construction management tool -- and delegate it to a junior planner without commercial oversight -- risk creating programmes that undermine their own position on compensation events, time extensions, and dispute resolution.
When to engage a planning consultant
NEC4 programme management requires a combination of technical scheduling expertise and contractual knowledge. Many contractors have competent planners who can build and maintain programmes, but fewer have specialists who understand the contractual implications of every programming decision.
Engaging a specialist planning consultant is particularly valuable at project mobilisation, when the first programme must be developed and submitted for acceptance. Getting the initial programme right -- with proper logic, realistic durations, visible float and time risk allowances, and all the Clause 31.2 requirements satisfied -- establishes the foundation for the entire project. An experienced consultant ensures the first submission is accepted without the delays and commercial exposure that come from repeated non-acceptance.
Consultants add significant value during compensation event assessment. Demonstrating the time impact of a compensation event requires forensic analysis of the accepted programme, careful insertion of the event into the programme logic, and clear presentation of the resulting delay. This is specialist work that benefits from experience across multiple NEC4 projects and an understanding of how adjudicators and tribunals assess time claims.
When programmes fall behind or lapse, a planning consultant can help recover the position. Reconstructing an accurate programme from progress records, addressing outstanding non-acceptance issues, and re-establishing the programme update cycle requires focused effort that project teams -- already managing day-to-day construction -- may struggle to provide alongside their operational responsibilities.
For contractors managing multiple NEC4 projects, a planning consultant can establish standardised programming procedures, templates, and governance frameworks. Consistency across projects ensures that programme submissions meet contractual requirements every time and that the organisation builds institutional knowledge of NEC4 programme management.
Specialist P6 planning consultants who understand NEC4 bring the dual expertise that these contracts demand: technical mastery of the scheduling tool combined with contractual literacy that protects the Contractor's commercial position. In an environment where the programme drives time, cost, and risk management, this expertise is not a luxury -- it is a necessity.