NEC Programme Compliance (Clause 31/32)
Also supports JCT and FIDIC programme requirements
Align your programme to the contract
Even a schedule that looks plausible can fall short of contract requirements or internal governance. Our NEC Programme Compliance service focuses on helping you meet Clause 31/32 acceptance requirements while still supporting JCT and FIDIC projects. We review and strengthen your plan to align with contract intent, client submission expectations and internal governance. This includes checking logic integrity, constraints, calendars, baseline status, progress rules and data‑date discipline to support clear reporting and smoother change discussions.
Who it’s for
Contractors and asset owners working under the NEC suite of contracts who need programmes that satisfy Clause 31/32 acceptance requirements. We also support JCT and FIDIC teams looking to align their schedules to client formats and internal governance. This service is valuable when programmes are submitted for acceptance, used for progress reporting or relied on in change discussions.
What it is
A contract‑aware programme review and improvement service. Our focus is on Clause 31/32 compliance for NEC projects, while also adapting to JCT and FIDIC submission standards. We evaluate and correct common problem areas: logic structure, constraints, calendars, baseline status, progress rules, data date discipline and alignment between the programme and the narrative. Outputs are provided in Primavera P6 or MS Project; where Asta or Synchro inputs are supplied, we align accordingly.
Why it matters
A programme can look reasonable but still fail basic contract expectations or stakeholder needs—especially when Clause 31/32 compliance is required. This leads to repeated revisions, inconsistent reporting and unclear change discussions. Compliance work helps bring the programme to a disciplined standard so it can be used with confidence by project, commercial and client teams.
Typical outputs
Compliance review & findings
A concise findings note highlighting gaps that affect programme use and submission quality, including Clause 31/32 alignment for NEC projects. We cover logic, constraints, calendars, baseline status, progress rules, data date and narrative alignment.
Compliance review & findings
Targeted corrections to improve structure and consistency. This includes link logic, constraint clean‑up, calendar alignment, milestone behaviour, WBS structure and activity naming rules – all refined to satisfy Clause 31/32 expectations for NEC and equivalent submission rules on JCT and FIDIC projects.
Update pack alignment
Standardised update approaches for reporting cycles. We help define cut‑off rules, progress rules and narrative structures so updates remain consistent with the accepted programme, with clear visibility of changes since the previous cycle.
Programme narrative
A concise narrative that matches the programme, capturing assumptions, constraints, key dates, sequencing rationale, interfaces and baseline or latest update status.
Change visibility support
Practical support to keep change information visible and traceable alongside programme cycles, supporting NEC compensation event workflows and JCT/FIDIC change discussions without turning the service into legal claims work.
Optional enhancements
-
Programme Assurance Passport – a one‑page assurance summary issued alongside submissions or reporting cycles where extra governance evidence is helpful.
-
Team alignment workshop – a short session to align project, commercial and planning inputs on submission expectations, progress rules, cut‑offs and evidence requirements.
-
Pack templates – simple templates for programme narratives, reporting, change tracking and progress evidence to support consistent presentation.
Our Process
1. Assess & align
Confirm the contract form (NEC Clause 31/32, JCT or FIDIC), client submission requirements, programme purpose and how it is used in reporting and change. Agree what “good” looks like for your project so the programme can be accepted and updated consistently.
2. Correct & strengthen
Apply targeted improvements to logic, constraints, calendars, baseline status and progress rules. Align the narrative and reporting pack so the submission and programme tell the same story and satisfy Clause 31/32 (or equivalent) expectations.
3. Embed the rules
Define update rules that keep the programme consistent over time – data dates, cut‑offs, progress rules, update cadence and minimum evidence expectations – so Clause 31/32 compliance (and equivalent JCT/FIDIC discipline) is maintained throughout reporting cycles.
All outputs pass through senior QA to ensure the plan is consistent, traceable and ready for review by internal and client teams.
Arrange an initial discussion
call 0330 223 7709 or email info@necplanningsolutions.co.uk
Benefits for your business
-
Cleaner submissions: Programmes and narratives that better match contract expectations and client formats, including NEC Clause 31/32 acceptance criteria.
-
More consistent reporting: Fewer shifts in dates caused by unclear progress rules, inconsistent cut‑offs or unstable logic behaviour.
-
Better change conversations: Change is easier to explain when the baseline status, update discipline and narrative are aligned with the contract, making Clause 31/32 compensation event discussions smoother.
-
Improved governance: Clearer traceability across updates, decisions and key changes, suitable for internal and client review.
Need a programme review before the next acceptance?
If you need NEC Clause 31/32 programme compliance with governed QA and audit‑ready outputs – while also covering JCT and FIDIC – NEC Planning Solutions can support your next project. Get in touch to discuss how this service can be tailored to your programme.
