NEC4 gives you one of the strongest programme disciplines in any standard contract — and says almost nothing about how that programme becomes management information. Clause 31 tells you what the programme must contain and clause 32 makes you keep it current, but the monthly translation of the Accepted Programme into something a director, a funder or the Project Manager reads is left entirely to you. For most SME contractors that translation is a hand-built Excel ritual that eats two or three days every period.
This page covers what NEC4 actually requires of your programme, what good reporting on top of it looks like, and how to automate the gap between the two.
Notice what none of these clauses produce: a management report. They produce contractual artefacts — an accepted programme, a revised programme, a register of notified risks — which is exactly why every NEC contractor ends up reinventing monthly reporting from scratch. The contract hands you rigorous inputs and leaves the output to you.
The Accepted Programme is built for the contract, not for the board. It is a defensible, logic-linked network — often several hundred activities — designed to survive scrutiny from the Project Manager and to support entitlement if things go wrong. That is precisely what it should be. It is also almost unreadable to the people who actually make the decisions.
A director doesn't need the 400-activity Gantt. They need position: are we on money, are we on time, and what do you need me to decide? Translating a contractual programme into those three answers is real analytical work — earned value off the progress, critical-path movement since the last accepted revision, the compensation-event exposure that hasn't hit the programme yet — and on most jobs it is done by hand, in a spreadsheet, by whoever had the time that month.
That hand-build is where the damage happens. Version drift creeps in as figures are copied between exports. Bad news gets quietly sanded down on its way up, not from dishonesty but because a dozen small human judgements sit between the schedule and the slide. And the baseline the report compares against is often one nobody can cleanly reconcile to the Accepted Programme, so the numbers invite an argument instead of settling one.
Under NEC4's period rhythm, this cost recurs every single period — not quarterly, not at milestones, but every four weeks for the life of the contract. The manual reporting tax you'd tolerate once a quarter is being levied thirteen times a year.
The fix isn't a longer report — it's a shorter one that leads with position and traces every figure back to the programme. A one-page Director's Brief on top of the Accepted Programme carries everything the board and the Project Manager need to act:
The one-page monthly format above, as an editable Word document — EVM position, critical path, early warnings, completion forecast and decisions-needed, laid out and ready to fill in. No signup, no email.
The template is the manual version, and it's a good starting format on its own. But under NEC4's period rhythm you're filling it in every four weeks, off a programme that has itself been revised and resubmitted — and that's exactly the recurring hand-build the discipline should be sparing you.
Aegis Command reads the programme file you already maintain — Primavera P6, Microsoft Project or Excel — and generates the earned value metrics, the critical-path analysis, the delay simulation and the monthly pack automatically, straight from the export you produce for acceptance anyway. Because the whole brief is generated from one source file, the planner, the PM and the directors are all reading the same numbers rather than three differently-built versions of them.
It's built by project-controls people, not general software people, and priced the way that suits a contractor rather than a corporate: unlimited users on every plan, priced on the value under management rather than per seat, with one project free forever at any size.
The programme submitted for acceptance must show, among other things, the planned order and timing of operations, the dates of access and key events, float and time risk allowance, and the resources you intend to use. The Project Manager can reject it on defined grounds, and until it's accepted you carry the risk of an unagreed programme.
At the intervals stated in the Contract Data — for most contracts a regular period, commonly every four weeks. Each revised programme shows actual progress, the effect of implemented compensation events, and how you plan to deal with any delays.
It's NEC4's name for the record of notified early warnings — what NEC3 called the Risk Register. The Project Manager maintains it, and it drives the early warning meetings under clause 15 where the parties agree how to avoid or reduce the matters raised.
No — the core clauses don't mandate EVM. But it's the cleanest way to satisfy the intent of progress reporting and to forecast Completion honestly, and many clients ask for it in the Scope or Works Information regardless.
Earned value management for contractors — CPI, SPI and EAC explained, with a worked example and a free calculator.
P6 reporting — from the .xer export to a report that gets read.
Pricing — banded on contract value, unlimited users, one project free forever.
Run one real NEC4 job on it and see the Accepted Programme turn into a one-page brief automatically, every period. Free for one active project, any size — the full product, no card.
Run one project free →