A Project Manager can only reject your NEC4 programme for four reasons: it isn't practicable, it doesn't show what the contract requires, it doesn't represent your actual plans, or it doesn't comply with the Scope. Nothing else counts, including a late submission. Get the programme itself right against those four tests and acceptance stops being a lottery.
This is the practitioner half of our NEC4 programme requirements guide, which covers what clause 31.2 requires in reference form. This piece is the build: how to structure and check a programme in Primavera P6 so it clears clause 31.3 the first time it lands on the Project Manager's desk, not the third.
Check your programme's schedule quality first, free
A lot of what gets an NEC4 programme rejected is basic schedule quality: negative float, broken logic, hard constraints doing the job logic should do. Run your .xer or .xml through our free checker before you submit. Nothing is uploaded, stored or shared.
Run the free schedule check →Step 1: Read Clause 31.2 Before You Open P6
Know what you're building before you build it. Under NEC4 clause 31.2, the accepted programme has to show: the starting date, access dates, Key Dates and the Completion Date; your planned Completion; the order and timing of the operations you plan to do and of the work of the Client and Others; the dates when you will need access, acceptances, things provided by the Client and information from Others; provisions for float, time risk allowances, health and safety requirements and the procedures set out in the contract; a statement for each operation of how you plan to do the work and the principal resources; and anything else the Scope asks for. The clause does not use the words critical path or terminal float, but a Project Manager will expect to see the critical path, and the gap between your planned Completion and the Completion Date is where terminal float shows. Miss one of these and you've handed the Project Manager a ready-made rejection on ground two: it doesn't show the information the contract requires.
Step 2: Structure the WBS Against the Scope, Not Your Own Convenience
Build your WBS so its structure mirrors the Works Information or Scope document section by section, not around how your own team happens to be organised. When a WBS node maps directly to a Scope clause or a Works Information section, a reviewer checking ground four (does it comply with the Scope) can trace the programme against the contract in minutes. When it doesn't, they have to hunt, and a Project Manager who has to hunt is a Project Manager more likely to reject and ask you to resubmit.
Step 3: Build Real Logic Before You Touch a Constraint
Sequence the network with genuine predecessor and successor relationships that reflect how the work will actually happen: access sequencing, handover points, the order trades realistically follow each other in. Constraints are for genuine external fixed points (a statutory consultation date, a third-party access date), not a substitute for logic you haven't worked out yet. A programme held together by hard constraints instead of logic is the textbook example of ground one: it isn't practicable, because it doesn't actually show how the work happens, just when someone decided it should finish.
Step 4: Show Time Risk Allowances as Their Own Activities
This is the step most programmes get wrong, and it's a direct route to a ground-two rejection. Clause 31.2 requires time risk allowances to be shown in the programme. The contract does not prescribe how, but the clearest way is as visible, identifiable activities, not padding quietly folded into a task's duration. If you think an activity carries three weeks of genuine risk, model three weeks as its own risk-allowance activity in the logic chain, distinct from the productive work either side of it. Hidden allowance can't be checked, can't be agreed, and can't be protected when a compensation event later eats into it, because nobody outside your own head knows it was there.
Step 5: Model Terminal Float as Two Milestones, Not One
Terminal float is not the same thing as the total float sitting on your critical path, and mixing the two up is a common and avoidable error. Terminal float is the gap between your own planned Completion and the contractual Completion Date, and under NEC4 it belongs to the Contractor: the Project Manager cannot absorb it or instruct acceleration to protect it. Model it explicitly with two separate milestones, your own Planned Completion and the fixed Completion Date, connected by logic so the gap between them is a number anyone reviewing the programme can read directly, not something they have to infer from the Gantt.
Step 6: Load Resources That Reflect What You Can Actually Deliver
Resource and cost-load the programme against real availability, not a template carried over from the last job. An unresourced or unrealistically resourced programme is the most common route to a ground-three rejection: it doesn't represent your actual plans realistically, because on paper it shows work happening that your own resourcing can't support.
Step 7: Run a Schedule-Quality Check Before You Submit
Before this programme goes anywhere near the Project Manager, run it through a DCMA-style check: negative float, broken logic, out-of-sequence progress, excessive hard constraints. These are the same defects that make ground-one rejections ("not practicable") the most common and most avoidable of the four. We've written the detailed version of this step, including exactly how to read a DCMA-style result in P6 once you have one, or run your own check free right now against the programme you're about to submit.
Step 8: Assemble the Submission and Send It on Time
Package the programme with a short Basis of Programme narrative explaining your key assumptions and sequencing logic, plus anything else the Scope specifically asks you to submit alongside it. Submit within the period stated in Contract Data Part 1. Note what late submission does and doesn't do: it may put you in breach of a separate obligation to submit on time, but it is not one of the four grounds on which the Project Manager can refuse to accept the programme itself. A late programme still has to be assessed on its own merits against clauses 31.2 and 31.3, not waved through or rejected on lateness alone.
Step 9: Know the Four Grounds So You Can Pre-Empt Them
| Ground | What it actually means | Where planners usually trip on it |
|---|---|---|
| Not practicable | The plan as shown couldn't realistically be carried out | Hard constraints standing in for logic; sequencing that ignores real access or handover dependencies |
| Doesn't show required information | Missing one of the clause 31.2 content items | Time risk allowances folded into durations instead of shown as activities; no visible critical path or terminal float |
| Doesn't represent plans realistically | The programme doesn't reflect what the Contractor will actually do | Resourcing that can't support the durations shown; a programme copied from a template rather than built for this job |
| Doesn't comply with the Scope | The programme conflicts with a Scope requirement | A WBS or sequence that ignores a Scope-stated method, sectional handover, or access restriction |
Step 10: If the Project Manager Goes Quiet
The Project Manager has the period for reply, two weeks by default unless Contract Data states otherwise, to either accept the programme or notify non-acceptance against one of the four grounds above. If that period passes with no response, clause 31.3 lets you notify the Project Manager of that failure. If they still don't respond within a further one week of that notification, the programme is treated as accepted. This deemed-acceptance mechanism is new to NEC4 and it exists so a Project Manager can't simply sit on a submission indefinitely: use it, in writing, the moment the reply period actually expires, rather than continuing to chase informally.
Where People Get This Wrong
The most common failure isn't a badly built programme, it's a well-built one that doesn't show its own working. Time risk allowances get buried in durations because it's faster to pad a task than model a separate activity. Terminal float gets left as an implicit gap on the Gantt instead of two named milestones. Both are invisible to you because you know they're there. They're not invisible to a Project Manager reading strictly against clause 31.2, and "not shown" reads exactly the same as "not done."
The second failure is treating a rejection as personal or arbitrary when it almost always traces back to one of the four grounds above. If you get a non-acceptance notice, read it against this table before you resubmit. A ground-one rejection needs different fixing from a ground-two rejection, and resubmitting the same programme with cosmetic changes wastes another two-week cycle.
When to Bring in a Second Opinion
If a programme has been rejected more than once, or you want it tested against clause 31.2 before the Project Manager sees it rather than after, that's the point to get an independent read. Planned's NEC4 Programme Acceptance Review tests a programme against clause 31.2 and the clause 31.3 grounds before submission, or before you accept one you've received, with a written recommendation delivered inside the reply period.
Book a Free Consultation if you'd like a senior planner to look at a programme before it goes in, or run the free schedule check first to catch the basic quality issues yourself.
Frequently Asked Questions
What are the four grounds for rejecting an NEC4 programme?
Under clause 31.3, a Project Manager can refuse to accept a programme only if it isn't practicable, it doesn't show the information the contract requires, it doesn't represent the Contractor's plans realistically, or it doesn't comply with the Scope. Disagreeing with the Contractor's chosen method or sequence isn't a valid reason on its own, provided the programme meets those four tests.
How long does the Project Manager have to accept or reject a programme?
The period for reply, two weeks by default unless Contract Data Part 1 states a different period. The Project Manager must either accept the programme or notify non-acceptance with reasons within that period.
What happens if the Project Manager doesn't respond in time?
Clause 31.3 lets the Contractor notify the Project Manager that they've failed to reply. If the Project Manager still doesn't respond within a further one week of that notification, the programme is treated as accepted. This deemed-acceptance rule is new to NEC4.
Is late submission a valid reason for a Project Manager to reject a programme?
No. Late submission isn't one of the four grounds in clause 31.3. A late programme still has to be assessed on its content against clauses 31.2 and 31.3, not rejected for timing alone.
What's the difference between total float and terminal float?
Total float is the time an activity can slip before it affects the critical path. Terminal float is different: it's the gap between the Contractor's own planned Completion and the contractual Completion Date, and under NEC4 it belongs to the Contractor rather than being available for the Project Manager to absorb through acceleration instructions.