When the Project Manager Will Not Approve Your NEC3 Programme
Under NEC3, the accepted programme is central to project control. It is the reference point for progress, compensation events and the effect of change. When a programme is not accepted, uncertainty grows quickly and positions can harden just as quickly.
Start with the stated reasons
The first step is to examine the project manager's reasons carefully. NEC3 does not allow programme acceptance to be withheld arbitrarily. If the concern is genuine, the quickest route is usually to address it directly and resubmit.
Typical issues include missing contractual information, logic that does not look practicable, durations that appear unrealistic or insufficient alignment with the scope and planned delivery method.
Use the process constructively
In many cases, a short review meeting is more effective than a long exchange of letters. If the project manager thinks the programme is too optimistic or incomplete, it is often possible to work through those points and produce a version that both parties can use with confidence.
That collaborative approach is usually better for the project than letting the issue drift while everyone continues to work from different assumptions.
Protect the record while you keep the job moving
Even while acceptance is outstanding, the contractor should continue to manage and update the latest programme. Submissions, comments and revisions should all be documented properly so there is a clear history of what was provided and how the concerns were addressed.
That record can become important later if there is disagreement about whether acceptance was reasonably withheld or about what should have been used to assess a compensation event.
Escalation should be a last resort
If the process stalls completely, contractual escalation may become necessary. Before reaching that point, it is usually worth using early warnings, structured meetings and focused revisions to narrow the issues.
The commercial reality is simple: the project is usually better served by securing an accepted programme than by arguing indefinitely about why one does not yet exist.
Key Takeaways
- Under NEC3, programme acceptance should be tied to stated contractual reasons, not general dissatisfaction.
- Where the comments are valid, address them quickly and resubmit a realistic, contract-compliant programme.
- Keep a clear record of submissions, feedback and revisions while continuing to manage the work transparently.
- Escalation may sometimes be necessary, but practical engagement is usually the better first route.
Key Points
- NEC3 project managers must state specific contractual reasons for refusing programme acceptance.
- Resubmitting a revised programme is usually faster and more effective than escalating a dispute.
- Documenting all submissions and feedback creates a reliable record for future compensation event assessments.