Stop chasing programmes. Start seeing the pattern
A monthly programme return is only useful if it is accurate and if you can act on it. Contract Status gives you the record of what was required, submitted, accepted, late and missing, for every contract, without a monthly round of e-mails.
A day with NEC, without it and with it
| When | Without it | With Contract Status |
|---|---|---|
| Start of month | You send the request for programmes to every Project Manager, and start a spreadsheet. | Submission dates are already set. The tracker shows who is due, and takes account of contracts that stopped needing a programme part-way through. |
| Mid-month | You chase the same three people. One says they sent it. To whom? | The To Review list shows what is waiting for a reply, oldest first, with what is overdue and what is due this week. |
| Review time | You read a programme against 31.2 on your own, with a checklist and a highlighter. | Where AI is switched on, a first review lists what passed, what did not and why. The Project Manager still decides. |
| Reporting | You build a chart by hand, and someone challenges the numbers. | PMO Insights has the charts and a PDF, filtered by period or programme manager. The numbers link to real records. |
| Quarter end | You compare contracts using several people's definitions of "on track". | Contract health applies the same NEC rules to each contract, using its own periods. |
What you can answer for
Clause references are the standard NEC4 ECC. The programme clauses have the same numbers in NEC3.
Is there an Accepted Programme?
The first accepted programme comes from the replies themselves, alongside anything marked by hand, and differences are flagged. Under 63, delay is measured against the Accepted Programme, and under 64.2 a contract without one is assessed on the Project Manager's view.
Are revised programmes coming in?
Clause 32.2 expects them at the Contract Data interval. The tracker shows required, submitted and missing by month. You can tell a late first submission from a late resubmission.
Are replies going back in time?
Clause 31.3 gives two weeks. Replies that are late are visible by contract and by person responsible, because a late reply is a compensation event under 60.1(6), and NEC4 adds treated acceptance.
Who keeps getting it wrong?
Insights shows the subcontractors with the most problems and those repeatedly not accepted, so a word in the right ear replaces a generic reminder.
Which reviews are worth your time?
PMO users can review programmes on all the account's contracts, keep private review notes, and use the AI review if your organisation has it switched on. XER, PDF and Excel files are read; MS Project .mpp files are not yet.
Beyond programmes
Contract Intelligence covers overdue items in every register. Administrators load payment dates in one go, so you can see who applied on time and whether certificates followed within a week.
Numbers you can take elsewhere
You probably have a programme-level dashboard already, and you do not want another one to look after. The data feed gives Power BI or Excel 12 registers, locked to your company, and never includes drafts or personal details. It is switched on for your account when you want it, and every key can be revoked.
Inside the app, My Dashboard lets each person arrange their cards and charts, with programme submissions on time, late and missing by month for PMO users. Register reports print cleanly or download as spreadsheets, with a replies column.
The review itself
A programme review usually means a Project Manager relying on somebody else's reading. Here the reviewer's notes sit with the programme and stay private to the client side, the reply offers the contract's own reasons, and the decision goes back on the record with its date. If a submission is not accepted, the request for a revised programme goes on the other side's Action List and closes by itself when they submit it. That is one less thing for you to chase.
Set the rules once
Programme guidance, reply periods and field names are set for the whole account by your administrators, and each contract can differ. Keep the terms you already use in reports: Tranche, AMP and so on can be renamed or switched off.
See it, try it, read up
Overseeing several contracts as a PMO
A PMO needs one view across NEC contracts. In Contract Status: contract cards, portfolio health, the most urgent deadlines and programme insights.
See the exampleMy programme has not been accepted
A contractor's programme is not accepted. In Contract Status: the stated reason, the revised programme request and the revised programme that answers it.
See the exampleReviewing a programme on time
A Client team reviews a submitted programme. Contract Status lists what is to review, keeps private review notes and offers the reasons the contract gives.
See the exampleSee PMO Insights for yourself
We will show the tracker, the To Review list and the reports on sample contracts.