NEC4 Contract Management Software: A 2026 Guide

01Early warnings

NEC4 ECC clause 15. FIDIC 2017 sub-clause 8.4, Advance Warning. JCT has no direct equivalent, the nearest being the duty to notify delay.

The early warning is the cheapest clause in the contract and the most under-used. It costs nothing to raise, it obliges both parties to meet and consider how to avoid or reduce the effect, and it creates a dated record that the matter was known about. Its whole value is timing. An early warning raised in week one is a risk you can still design out. The same matter raised in week nine is a claim.

What a contract management system adds is discipline and shared sight. The register lives in one place, both parties see the same entries, the risk reduction meeting has an agenda that writes itself, and nothing depends on whether a particular person remembered to copy in the right people. What it cannot do is decide that something on site is worth warning about. That judgement is still made by a human, on a particular day, in a particular set of conditions.

02Compensation events

NEC4 ECC clauses 60 to 65. JCT Relevant Events and Relevant Matters, plus Variations. FIDIC 2017 clause 20 Claims and clause 13 Variations.

Compensation events are where the commercial position of a project is actually decided, and where the procedure is least forgiving. There are notification duties, quotation periods, assessment periods, and a deemed-acceptance mechanism if a reply does not arrive in time. Under clause 61.3 a Contractor that does not notify within eight weeks of becoming aware of an event may lose entitlement to time and money altogether, and there are equivalent traps on the other side of the table if the Project Manager does not respond.

This is the procedure contract management software is best at. It turns a set of deadlines into a workflow, it makes the clock visible to both parties, and it keeps the paper trail in an order that will survive an audit or an adjudication. It is genuinely hard to run compensation events well at scale without a system of some kind.

The limit is the same as for early warnings, and it is worth being precise about it. The workflow begins at the moment someone decides an event has happened, or might have happened. Everything before that moment, the ground conditions in the diary, the standing time on a plant record, the instruction given verbally at a Thursday progress meeting, sits outside the system until a person carries it in.

03Payment

NEC4 ECC clauses 50 and 51. JCT interim payments under section 4. FIDIC clause 14. Payment and pay less notices under the Construction Act apply across all of them.

Payment is the procedure with the hardest statutory edges. Assessment dates, due dates, final dates for payment, payment notices and pay less notices are all time-bound, and in the UK the Housing Grants, Construction and Regeneration Act sits behind whichever form you are using. Miss a pay less notice and the notified sum becomes payable, whatever the underlying valuation says.

Systems help here by tying dates to a calendar rather than to a person, by holding the assessment and its backup in one record, and by giving both parties the same view of what has been notified and when. The friction that remains is upstream: assembling the substantiation, the Defined Cost records, the timesheets, the delivery tickets, the plant returns, so that an assessment can be made confidently and defended later.

04Programme

NEC4 ECC clauses 31 and 32, plus clause 62.2 for compensation event programmes. JCT master programme clause 2.9. FIDIC clause 8.3.

NEC treats the programme as a live management document rather than a filing requirement. It has to show the Accepted Programme, planned Completion, float, time risk allowances, and the order and timing of the work, and it has to be revised at the stated interval. A programme that is not accepted, or that has drifted from what is happening on site, weakens every other procedure that depends on it, compensation event assessment most of all.

Contract management systems handle the submission, acceptance and revision cycle: who submitted what, when, whether it was accepted, and on what grounds it was not. Keeping the programme itself honest is a separate discipline, and it depends on progress information arriving from site quickly enough to be worth planning around.