How to write a programme narrative and schedule of changes
How to write a short programme narrative and schedule of changes that explains your NEC programme and makes it easier for the Project Manager to accept.
On this page
A programme without explanation invites questions. A short, well-structured narrative and a clear schedule of changes give the Project Manager what they need to accept the programme, or to give specific reasons that you can answer quickly. Clause 31.3 requires the Project Manager to accept or give reasons for not accepting, so your aim is to leave no reason to find.
What the narrative is for
Your contract sets what a programme must contain (clause 31.2). A narrative is not a contract requirement in every case, but it is good practice and often asked for in the Scope or Contract Data. Check yours. Its job is to explain what the bars and links cannot.
Keep it to two to four pages. The reader is busy and will read it once.
A structure that works
- Purpose and status. State whether this is a first programme or a revision, the data date, and the programme file name and version.
- Headline dates. Planned Completion against the Completion Date, and each Key Date. If any date has moved, say so here, not on page three.
- Critical path. Describe the longest path in plain words. Name the key activities and what drives them.
- Float and time risk allowance. Say what you have included and where. See float and time risk allowance explained.
- Key assumptions. Working hours, calendars, access dates, resource levels, sequences that depend on third parties.
- Constraints and interfaces. Possessions, road closures, permits, utility diversions, design information dates.
- Method and sequence. A paragraph or two on how the work will be done, where it affects logic.
- Risks. Link to the early warning register where relevant, without restating it. See early warning register template.
The schedule of changes
This is a table comparing the new programme to the last accepted one. It is the single most useful thing you can give a Project Manager.
| Ref | Activity | Previous | Now | Reason | Related event |
|---|---|---|---|---|---|
| 1 | Example activity | Start date | Start date | Short factual reason | Compensation event or instruction reference |
Include only real changes. Group them: changes caused by compensation events, changes caused by your own re-sequencing, changes in durations, changes in logic. Where a change is yours, say so. Honesty here builds trust and speeds acceptance.
Writing tips
- Use plain sentences, one idea each.
- Use the same terms as the contract: Completion Date, Key Date, Accepted Programme, Working Areas.
- State facts and dates, not opinions about the other party.
- Avoid claims language. A narrative is not a notice, and a delay claim belongs in a separate communication.
- Cross-reference activity IDs so the reader can find each point.
- Keep the narrative consistent with the programme file. A mismatch is a ready-made reason for non-acceptance.
Common errors
- Describing the programme in prose that repeats every bar.
- Hiding a forecast late completion in the middle of the document. See my programme now shows we will finish late.
- Changing logic without listing it in the schedule of changes.
- Leaving out the reasons for changed durations.
- Sending a narrative that refers to an earlier version of the file.
Before you submit
Check the programme against the clause 31 programme checklist, then read the narrative as if you were the Project Manager. Ask: can I find the completion date, the critical path and every change within two minutes? If not, rewrite it.
If you have no in-house planner, a CPMP planner can write the narrative with the programme and keep both aligned through each revision.
Related guides
- Clause 31 programme checklist
- Why NEC programmes are not accepted
- Revised programme submission timeline
This guide is general information, not legal advice. Check it against your contract.
