NEC PROGRAMME COMPLIANCE
NEC Clause 31/32 acceptance: stop fighting over rejected programmes
NEC Clause 31/32 accepted programme support for contractors and asset owners
CLAUSE 64.1: THE COMMERCIAL CONSEQUENCE
Without a current accepted programme when a compensation event arises, the Project Manager assesses the time impact using their own method. That assessment stands unless it goes to dispute. Programme compliance is not administrative discipline. It is the mechanism that protects your right to assess time.
We build, review and maintain programmes that meet Clause 31/32 acceptance requirements, satisfy the Project Manager's scrutiny, and keep your CE position protected through delivery. Not legal claims work. Programme-led compliance support that operates inside the contract mechanism.
NEC ACCREDITED
APMG QUALIFIED
P6 / MS PROJECT / ASTA
NEC / JCT / FIDIC
WHY PROGRAMMES GET REJECTED
Three reasons the Project Manager does not accept your programme
Most rejections are not about the dates. They are about missing information, unstable logic, or a programme that does not show what Clause 31.2 requires.
- 01
The required information is incomplete or missing
01
Clause 31.2 lists specific information the programme must show. If float, time risk allowances, order and timing of work, or other planned dates are absent, the PM has contractual grounds to withhold acceptance. The programme may be technically competent but still non-compliant.
Cl.31.2 information requirements
- 02
02
The logic does not support the dates
Open-ended activities, hard constraints masking float, missing predecessor/successor relationships, and calendars that do not reflect working patterns. The PM reviews the logic, not just the Gantt chart. If the logic does not support the sequence, the programme is not practicable under Clause 31.3.
Cl.31.3 practicability
- 03
03
The programme has not been revised at the required intervals
Clause 32.2 requires revisions at intervals no longer than those stated in the Contract Data, typically four weeks. A programme accepted at mobilisation that has not been revised in three months is technically accepted but commercially useless for CE assessment. The baseline drifts, and Clause 64.1 exposure increases with every missed revision.
Cl.32.2 revision intervals
Clause 32 compliance maintained through delivery. On a £50M+ NEC3 gas infrastructure package, programme compliance was maintained through monthly Clause 32 revision cycles from baseline to practical completion, with accepted programme status preserved throughout for CE assessment purposes. View case study ›
WHAT THE CONTRACT REQUIRES
The nine things Clause 31.2 says your programme must show
Each of these is a specific information requirement. If any are missing, the Project Manager has grounds to withhold acceptance under Clause 31.3. Our compliance review checks every one.
- REQUIREMENT 1
Starting and Completion dates for each operation
Every activity in the programme must show when it starts and when it finishes. Activities without dates or with zero duration placeholders do not satisfy this requirement.
- REQUIREMENT 2
Order and timing of work
The programme must show the intended sequence: what comes first, what follows, what runs in parallel. Logic links must support the sequence, not just the bar chart layout.
- REQUIREMENT 3
Float and time risk allowances
Float must be visible. Time risk allowances must be shown where the contractor has included them. If these are not shown, the PM cannot evaluate whether the programme is realistic and practicable.
Most common rejection trigger
- REQUIREMENT 4
Health and safety requirements
Key health and safety activities, constraints and requirements must be reflected in the programme where they affect the sequence or timing of operations.
- REQUIREMENT 5
Procedures for the work
Where specific procedures are required by the Works Information (Scope in NEC4), these should be reflected in the programme as activities, constraints or sequencing.
- REQUIREMENT 6
​Dates for provision of information and other things
Dates when the contractor needs information, access, materials, approvals or other things from the client or third parties. These establish the interface obligations that drive change discussions.
- REQUIREMENT 7
Other information required by the Works Information
The Works Information (or Scope) may require additional programme content specific to the project, such as commissioning sequences, testing phases, or sectional completion dates.
- REQUIREMENT 8
Dates for meeting Conditions for Key Dates
Where Key Dates are specified in the Contract Data, the programme must show when and how these will be met. Missing Key Dates is a compliance gap with direct commercial consequences.
- REQUIREMENT 9
​Effects of implemented compensation events
Once a CE is implemented, its effect on planned Completion must be shown in the programme. A programme that does not reflect implemented CEs is not current under Clause 32 and weakens subsequent CE assessments.
Commonly missed on revisions
WHAT WE PRODUCE
Outputs that get the programme accepted and keep it compliant
Each output is structured to satisfy Clause 31/32 requirements and withstand PM scrutiny.
REVIEW OUTPUT
Compliance review and findings
A concise findings note identifying every gap that affects acceptance: Clause 31.2 information requirements, logic integrity, constraint behaviour, calendar alignment, baseline status and narrative consistency.
-
Gap-by-gap assessment against Clause 31.2 requirements
-
Logic and constraint integrity check
-
Calendar, float and time risk allowance review
-
Priority actions ranked by acceptance risk
CORRECTION OUTPUT
Submission-ready programme improvements
Targeted corrections to logic, constraints, calendars, WBS structure, activity naming and milestone behaviour. The programme is brought to a standard that satisfies acceptance criteria before submission.
-
Logic repair and constraint clean-up
-
Calendar alignment to actual working patterns
-
Float and time risk allowances made visible
-
Reviewed by an NEC Accredited Project Manager before submission
NARRATIVE OUTPUT
Programme narrative matched to the schedule
A concise written basis of schedule covering assumptions, constraints, key dates, sequencing rationale, interfaces and baseline status. Written to match the programme logic so both documents tell the same story at submission.
-
Assumptions and constraints explicitly documented
-
Sequencing rationale traceable to the logic
-
Submission-ready format for PM review
ONGOING OUTPUT
Update rules and revision discipline
Defined update rules that keep the programme compliant through delivery: data dates, cut-offs, progress rules, revision cadence and minimum evidence expectations. So Clause 32.2 compliance is maintained, not just achieved once at mobilisation.
-
Update cadence aligned to Contract Data intervals
-
Cut-off and progress rules documented
-
Revision cycle embedded for Clause 32.2 compliance
-
CE implementation reflected at each revision
WHO IT'S FOR
WORKS FOR
Contractors whose programmes have been rejected, are at risk of rejection, or need to maintain accepted status through delivery
Particularly valuable where programme acceptance has stalled, Clause 64.1 exposure is increasing, or the team needs to establish a revision cycle that satisfies Clause 32.2 intervals.
HOW IT WORKS
Assess, correct, embed the rules
Scope confirmed in writing before any chargeable work begins. Can run as a one-off review or as retained compliance support through delivery.
STAGE 01
Assess and align
Confirm the contract form (NEC3/NEC4/JCT/FIDIC), client submission requirements, programme purpose and how it is used in reporting and change. Agree what the programme must show to satisfy acceptance.
Written scope before billing
STAGE 02
Correct and strengthen
Apply targeted improvements to logic, constraints, calendars, baseline status and progress rules. Align the narrative so the submission and programme tell the same story and satisfy Clause 31/32 expectations.
NEC-accredited governance check before submission
STAGE 03
Embed the revision cycle
Define update rules that keep the programme compliant through delivery: data dates, cut-offs, progress rules, revision cadence. So Clause 32.2 compliance is maintained at every interval, not just at mobilisation.
Retained or one-off
PRICING
One-off review or retained compliance support
Pricing reflects programme complexity, the number of compliance gaps, and whether this runs as a one-off review or retained support through delivery cycles.
ENGAGEMENT STRUCTURE
FIXED-FEE OPTIONS
Fixed fee where scope allows, otherwise a defined upper limit. Confirmed before any chargeable work begins.
SCOPE CONFIRMED IN WRITING
Outputs, fee and timeline confirmed before chargeable work begins.
INITIAL SCOPING AT NO CHARGE
A short call to confirm fit, scope and next step.
MINIMUMS AGREED UPFRONT
Any monthly cycle or minimum period is confirmed before work starts.
NEW £
ONE-OFF REVIEW
From £950
COMPLIANCE CHECK + FINDINGS
Logic-linked programme with key dates and sequencing. PDF and native file. Submission-ready.
REVIEW & CORRECTION
From £1,950
FIX TO ACCEPTANCE STANDARD
Full tender programme with narrative, phasing and milestone plan. Clarification defence.
NEW £
RETAINED COMPLIANCE
Scoped
ONGOING CL.32.2 SUPPORT
Multi-package and framework bids scoped to submission requirements.
LIVE
Retainer pricing confirmed after project review. See full pricing
FURTHER READING
Practical guidance on NEC programme compliance
CLAUSE 31
NEC Clause 31 Programme Acceptance: The Complete Guide
What the accepted programme protects, how deemed acceptance works, and why a programme accepted at mobilisation provides almost no commercial protection by month six.
CHECKLIST
NEC4 Programme Compliance: A Practical SME Checklist
A practical checklist for UK contractors to protect margin, improve cashflow, and strengthen CE time discussions with compliant programme updates.
TIME RISK
Why You Need Reasonable Time Risk Allowances in NEC Contracts
How time risk allowances interact with programme acceptance and CE assessment, and why showing them is a Clause 31.2 requirement.
PROGRAMME RESOURCE
BEFORE YOUR CLAUSE 31 OR CLAUSE 32 SUBMISSION, CHECK THIS LIST
A practical pre-submission checklist for NEC4 programme acceptance. Built for contractor teams who need to check Clause 31.2 completeness, programme logic and submission risk before issue.
Direct PDF download, no email required.
PDF DOWNLOAD
NEC4 PROGRAMME ACCEPTANCE CHECKLIST
The pre-submission gate. What to verify in your P6 or MS Project file before you press submit.
A working list of the contract-data, Clause 31.2, logic-integrity and submission-package checks that decide whether a programme is ready for acceptance. Written for the person preparing the submission. Useful to planning managers, commercial teams and project leads who need to know where the risk sits. Includes the Clause 31.3 time-bar machinery that is often missed.
âś“ Single page A4
âś“ Clause 31.2 / 31.3 / 50.5
âś“ Print or screen tick
Need to get your programme accepted?
Send your current programme for an initial review of compliance against Clause 31.2 requirements, at no charge. We will identify the gaps and confirm the scope to fix them, in writing, before any chargeable work begins.
Or tell us the contract type, programme status and submission deadline. We will confirm the right approach.
Initial programme review at no charge, with no obligation to proceed.