The information obligations buried in NEC4, FIDIC and JCT

A commercial manager running NEC4 in one region, FIDIC on an international package and JCT on the domestic frame has a practical question: which document, produced on which date, decides whether a delay costs the contractor money. Most comparisons answer with a mood — keep records, give notice, update the programme — as though the three books were saying the same thing in different accents. They share exactly one thing. Entitlement is tied to information produced on a clock the other side can still read. After that they diverge almost completely.

The tempting assumption is that the three bury interchangeable information duties, and if that were true there would be a published common schedule of notices, programmes and records running across the unamended families. There is no such schedule. There are five kinds of duty, written in different places, running on different clocks, with different sanctions.

Three books on the table

What follows compares the published, unamended families as they are usually meant:

the NEC4 Engineering and Construction Contract (ECC)
the FIDIC Conditions of Contract for Construction (Red Book), First Edition 1999 and Second Edition 2017
the JCT Standard Building Contract With Quantities (SBC/Q), 2016 and 2024

Other members of each family — NEC4 Term Service and Professional Service, FIDIC Yellow and Silver, JCT Design and Build, Intermediate and Minor Works — carry analogous concepts under different numbering, and those numbers are not interchangeable. Particular conditions, Z-clauses, BIM protocols and information protocols sit on top of these texts. They are not read here.

Clause numbers appear only where the published heading, or well-known published wording, is certain. Where the duty is real but the numbering moves by form, the published concept is used instead: early warning, compensation event, Advance Warning, Engineer’s determination, Relevant Event, Relevant Matter. Short quotations are from that published wording as reported in official notes or clause commentary, not from a private circular. Treat all of it as a reading aid. It is not legal advice, and it is not a substitute for the printed conditions.

There is no fieldwork here, no survey, and no invented rate of failed notices. The evidence is the published families.

Five duties, not one filing system

Comparing them on collaborative spirit gets you nowhere. What matters is the five information objects the three texts actually write down.

The form of a communication — what counts as a notice, and what is only a remark.
The programme — whether it is a living accepted object, a revised submission, or a furnished master.
The warning that is not yet a claim — early warning, Advance Warning, or nothing of that name.
The record that substantiates — contemporary records, a register and an accepted programme, or particulars attached to a notice.
The notice that starts time or money — compensation event, Claim, Relevant Event and Relevant Matter.

Software explainers flatten those five into “document control.” The published headings do not.

What counts as a notice

All three families refuse the idea that a sentence in a meeting minute is automatically a notice. They do it in different clauses.

NEC4 ECC clause 13 requires communications in a form that can be read, copied and recorded. Clause 13.2 lets the Scope name a communication system; a communication that does not go through that system is not a valid communication. Clause 13.7 requires notifications to be communicated separately. An early warning stuffed into a weekly report is already the wrong object.

FIDIC writes the same refusal more bluntly in the 2017 book. Sub-clause 1.3 is Notices and Other Communications. The 2017 programme and progress-report clauses then say, in terms, that neither a programme nor a progress report is a substitute for a formal Notice. The 1999 book already required communications in writing and proper delivery; the 2017 text is trying to stop the argument that a bar on a Gantt chart was notice of a claim.

JCT SBC clause 1.7 is the published heading Notices and other communications. Service, reckoning of days and the effect of certificates sit in the same opening section. The later machinery — delay notices, loss-and-expense notifications, Architect/Contract Administrator’s instructions — assumes those communications can still be found. It does not assume they live in a personal inbox.

The obligation buried here sits before any claim: the project has to be able to show that a notice was a notice. Anyone who has watched an argument turn on whether a line in a minute counted will know how much rides on it.

Three books, three programmes

This is the largest structural difference of the lot, and the one that catches people moving between forms.

NEC4 — the Accepted Programme

NEC4 ECC clauses 31 and 32 make the programme a contractual information object. The Contractor submits a programme for acceptance. Clause 31.2 specifies what it must show, including the order and timing of the work of the Client and Others, and the dates when the Contractor will need information and other things from them. Clause 32.1 requires each revised programme to show actual progress, the effect of events, and how the Contractor plans to deal with delays. The Project Manager accepts or gives reasons for non-acceptance under clause 31.3. NEC4 added a published sanction if that response does not arrive after a further notified reminder.

That makes the accepted programme the baseline against which compensation events and delay are later read, whatever it looks like in the monthly pack. A planner who lets it go stale has already failed an information duty, months before anybody argues about money.

FIDIC — a programme that must be revised, and a report that is not a notice

FIDIC Red Book sub-clause 8.3 is Programme in both editions. In the 2017 book the Contractor submits an initial programme within 28 days after the commencement Notice under 8.1, and a revised programme whenever the last one ceases to reflect actual progress or is otherwise inconsistent with the Contractor’s obligations. The published contents list is long: commencement and completion dates, access dates, the order of the works including design and Contractor’s Documents, progress to date, the effect of delay on other activities, and a supporting report. The Engineer can give Notice that the programme does not reflect actual progress or the Contract.

The monthly progress report sits beside that programme — sub-clause 4.21 in the 1999 book, 4.20 in 2017. It has to compare planned and actual progress and describe measures being taken to overcome delay. The 1999 text also requires the report to list notices given. The 2017 text keeps the report and then, as above, warns that it is not a Notice. Commentary on the 2017 book further ties the relevant progress report to the interim-payment application under sub-clause 14.3. So the information duty runs double: keep the programme honest, keep the monthly report complete, and treat neither of them as the claim.

JCT SBC — a furnished master, and information travelling the other way

JCT SBC clause 2.9 is the published heading Construction information and Contractor’s master programme. The Contractor provides the master programme; the Contract Particulars can require a critical path and other specified detail. The unamended revision duty is narrow. Commentary on the published SBC treats a revised master programme as following an extension of time under clause 2.28, or a pre-agreed adjustment, not as a monthly accepted living programme. The master programme is typically not a contract document.

The information clock JCT writes most clearly in this area runs the other way. Clause 2.11 is the Information Release Schedule: dates on which the Architect/Contract Administrator is to release further information. Clause 2.12 then covers further drawings, details and instructions. Failure to release what that schedule promised is a supply-of-information failure. It is not a substitute for the Contractor’s own delay notice.

A document controller who treats “update the programme” as a universal weekly duty is describing NEC4 and FIDIC 2017. They are not describing unamended JCT SBC.

Early warning and a delay notice are different animals

The three families use similar English for different legal objects. Confusing them is how a project talks itself into believing it has warned, and finds out later it has not claimed.

NEC4 — a reciprocal warning, a register, a meeting

NEC4 ECC clause 15 is Early warning. The published wording, as set out in NEC’s own process notes, requires the Contractor and the Project Manager to give an early warning by notifying the other as soon as either becomes aware of any matter which could increase the total of the Prices, delay Completion, delay meeting a Key Date, or impair the performance of the works in use. The duty is reciprocal. It is not a compensation-event notice. The same matter may later become one; the warning is a separate communication.

NEC4 renamed the old risk register the Early Warning Register so it would not be confused with a project-management risk log. The Project Manager prepares the first register within one week of the starting date, holds a first early warning meeting within two weeks, and then holds meetings at the interval stated in the Contract Data. Subcontractors may attend. After each meeting the Project Manager revises the register. The register records the matter, the agreed actions, and who is to take them. It is not an allocation of contractual risk.

The sanction is also published. If the Project Manager decides that the Contractor did not give an early warning an experienced contractor could have given, that fact is stated in the instruction to submit quotations (clause 61.5). The compensation event is then assessed as if the warning had been given. Silence is not free.

Secondary Option X10 (Information Modelling), if used, adds an early-warning duty for matters that could affect the Information Model, and requires an Information Execution Plan. The core ECC does not impose an information model, and treating X10 as if it were a core clause is a misreading of the published options — one that turns up often in BEPs.

FIDIC — a prompt in 1999, Advance Warning in 2017

The 1999 Red Book folds a contractor-side prompt about likely future events into the programme clause, sub-clause 8.3. It is not a register, not a meeting cycle, and not a claim.

The 2017 Red Book splits the objects. Sub-clause 8.3 remains Programme. Sub-clause 8.4 is Advance Warning: both Parties give advance notification of known or probable future events or circumstances that may delay the works, increase the Contract Price, or impair performance. That warning is still not a Notice of Claim. Sub-clause 3.8 adds management meetings; FIDIC does not publish an Early Warning Register.

A progress report that mentions a risk is, again, neither the warning nor the claim. The 2017 book is written to stop that collapse.

JCT — no published early-warning regime

Unamended JCT SBC has no clause headed early warning, and no Early Warning Register. Collaborative working may appear among the opening articles; it is not a notice clock.

What JCT does publish is a notice of delay to progress. Clause 2.27 is that heading. The duty arises when delay is, or should be, reasonably apparent. The notice carries particulars of the material circumstances and, where that is the case, identifies the Relevant Event. It is the start of the extension-of-time machinery in clauses 2.26 to 2.29, not a risk-reduction meeting. A project manager fresh off an NEC job who treats a 2.27 notice as an early warning will be surprised how little credit the file gives him later. The mistake runs both ways, and the two objects destroy each other either way.

The record that has to back it up

FIDIC is the family that names the record as a claims object.

In the 1999 Red Book, sub-clause 20.1 requires the Contractor, after a notice of claim, to keep such contemporary records as may be necessary to substantiate the claim. The Engineer may monitor that record-keeping, instruct further records, inspect them, and take copies. A fully detailed claim, with supporting particulars, follows within 42 days of awareness of the event — not 42 days after the notice. The 28-day notice and the 42-day particulars are two different clocks running from the same awareness date.

The 2017 Red Book moves claims into clause 20 and defines a fully detailed Claim under 20.2.4 as a submission that includes a detailed description of the event, a statement of the contractual or other legal basis, all contemporary records on which the claiming Party relies, and detailed supporting particulars of the payment or extension claimed. Commentary on the 2017 text treats contemporary records as records prepared at the same time as, or immediately after, the event. The Engineer’s agreement or determination then sits in sub-clause 3.7 (it was 3.5 in 1999). Dispute adjudication moves to clause 21.

NEC4 ECC does not use the phrase “contemporary records” as a claims defined term. The records duty is distributed: communications that can be recorded (clause 13), the Early Warning Register (clause 15), the Accepted Programme and its revisions (clauses 31 and 32), quotations for compensation events (clause 62), and whatever the Scope requires. That distribution is stricter than it looks. A compensation event assessed against a stale programme, or against an early warning that was never separately notified, is already an information failure.

JCT SBC does not name contemporary records either. The records duty arrives as particulars. The delay notice under 2.27 has to be particularised. Loss and expense is a separate published block: clause 4.20 Matters materially affecting regular progress, 4.21 Notification and ascertainment, 4.22 Relevant Matters. The printed 2016 wording still used in 2024 commentary requires the Contractor to notify the Architect/Contract Administrator as soon as the likely effect of a Relevant Matter on regular progress becomes, or should have become, reasonably apparent; to follow that notification with an initial assessment and such information as is reasonably necessary for ascertainment; and to update it. The Architect/Contract Administrator or Quantity Surveyor then notifies the ascertained amount within 42 days of the initial assessment and information, and within 28 days of each update.

Clause 4.20 makes entitlement subject to compliance with 4.21. That is the published hook. How far an English tribunal will treat it as a condition precedent is case law, not a statistic, and it is not restated here. The information point does not need the case: the printed SBC already ties money to a notification plus an assessment the other side can use.

Where there is a Contractor’s Designed Portion, clause 2.40 is As-built Drawings. Schedule 1 is the Design Submission Procedure. Those are information duties about design, not about delay. They still have to produce a retrievable object.

How time and money actually start

The warning and the record do not start entitlement. A separate notice does. The three families name that notice differently, and two of them split time from money.

NEC4 uses one machinery for both: compensation events, clauses 60 to 65. Clause 60.1 is the published list of events. If the event arises from the Project Manager or the Supervisor giving an instruction or notification, issuing a certificate, or changing an earlier decision, the Project Manager notifies it (clause 61.1). Otherwise the Contractor notifies. Clause 61.3 is the published time bar: if the Contractor does not notify a compensation event within eight weeks of becoming aware that the event has happened, the Prices, the Completion Date and a Key Date are not changed, unless the event is one of those instructed or certified events. Eight weeks is not twenty-eight days, and it is not “as soon as reasonably apparent.” It is a third clock.

FIDIC uses Claim. In 1999, Contractor claims sit in 20.1 and Employer claims in 2.5; the 28-day notice is the condition that later argument keeps returning to. In 2017, Employer and Contractor claims share clause 20, and 20.2 is Claims for Payment and/or EOT. An initial Notice of Claim is due within 28 days of awareness, or of when the Party should have been aware. The fully detailed Claim is due within 84 days. The 2017 book also puts a published duty on the Engineer to flag a late notice before rights are treated as lost. The determination is 3.7, not a compensation-event quotation.

JCT SBC splits the objects. Time is clauses 2.26 to 2.29: related definitions, notice of delay, fixing Completion Date, Relevant Events. Money is clauses 4.20 to 4.24: regular progress, notification and ascertainment, Relevant Matters, addition to the Contract Sum. The same physical event can be both a Relevant Event and a Relevant Matter. The published conditions still want two notifications, two sets of particulars, and two decisions — one fixing a Completion Date, one ascertaining loss and expense. A single email saying “delay and cost as discussed” is neither of those two objects.

One late design issue, three paper trails

Take a late design issue that delays a follow-on trade. The facts are the same in all three. The published information trail is not.

Under NEC4 ECC the Project Manager or the Contractor gives an early warning as soon as the matter could delay Completion, as a separate communication, and the Project Manager enters it on the Early Warning Register. An early warning meeting follows if instructed, or at the stated interval. If the matter is a compensation event, it is notified under clause 61 — by the Project Manager if it is an instructed change to the Scope, by the Contractor otherwise, inside eight weeks of awareness. A quotation follows. Each revised programme shows the effect and how the delay will be dealt with. Missing the early warning changes the assessment. Missing the compensation-event notice can end the entitlement.

Under FIDIC Red Book 2017 a Party gives an Advance Warning of the probable event. The monthly progress report describes the delay and the measures being taken; that report is not the Claim. A Notice of Claim goes in within 28 days of awareness. Contemporary records start, and stay open to inspection. The fully detailed Claim — description, legal basis, records, particulars — follows within 84 days. The programme is revised when it no longer reflects progress. The Engineer agrees or determines. A bar on last month’s Gantt chart does none of that work.

Under JCT SBC there is no early-warning step in the unamended conditions. When delay is reasonably apparent the Contractor gives a 2.27 notice with particulars and, if that is the case, names the Relevant Event. If regular progress is materially affected, a separate 4.21 notification starts loss and expense, with an assessment and the information needed for ascertainment, then monthly updates. The Architect/Contract Administrator fixes a new Completion Date if that is fair and reasonable. The master programme is revised if an extension is given. If the late design issue is a failure against the Information Release Schedule, that is a supply-of-information fact. It still does not replace the Contractor’s notices.

Duty	NEC4 ECC	FIDIC Red Book (2017)	JCT SBC/Q
Form of communication	Clause 13: must be readable, copyable, recorded; a nominated system can be mandatory (13.2)	Sub-clause 1.3: Notices and Other Communications	Clause 1.7: Notices and other communications
Programme	Accepted Programme (31–32); each revision must show actual progress and how delay will be dealt with	Programme (8.3): revised whenever it stops reflecting progress; the monthly report is separate and is not a Notice	Master programme (2.9); revision typically follows an extension of time, not a monthly duty
Early warning	Early Warning (clause 15), reciprocal; Early Warning Register opened within one week, first meeting within two	Advance Warning (8.4, new in 2017); still not a Notice of Claim	No published early-warning regime in the unamended conditions
Records	Distributed across clause 13, the Early Warning Register, the Accepted Programme, and compensation-event quotations	Contemporary records is a defined claims object (20.1 / 20.2.4)	Particulars attached to the delay notice (2.27) and the loss-and-expense notification (4.21)
Notice that starts time or money	Compensation-event notice within eight weeks of awareness (61.3)	Notice of Claim within 28 days; fully detailed Claim within 42 days (1999) or 84 days (2017)	2.27 notice of delay and 4.21 loss-and-expense notification — two separate clocks

Three families. One event. Five kinds of document, on three clocks, with three ways to lose the point.

What none of this settles

It does not show that one family is “more digital.” NEC4 clause 13.2 allows a communication system in the Scope; it does not require a common data environment. FIDIC and JCT can be performed on paper if the notices are in the required form. A cloud folder full of unnotified PDFs satisfies none of them.

It does not show that software, a mandate, or a model will save a claim. The published sanctions are about whether a notice was a notice, whether a programme was the programme, and whether particulars arrived on the clock. They are not about a platform.

It does not show an industry rate of failed notices, lost early warnings, or rejected programmes. There is no survey here and no site sample. Commentary and reported cases exist; they are not a denominator.

And it does not read Z-clauses, particular conditions, or a project’s information protocol. Those documents can tighten or loosen every clock above. A job that has amended the eight-week bar, or the 28-day Notice of Claim, or the 4.21 particulars, is no longer the published family.

So the assumption fails. The three families bury specific duties — communications, programme, warning, records, claim notice — in different clauses, under different names, with different consequences for silence.

Two things worth doing before the first notice is due

The first belongs to whoever runs the commercial function on the job, and it should happen in the week the contract is executed rather than the week something goes wrong. Sit down with the planner and the document controller, with the amended conditions open rather than the standard book, and write out the clocks this particular contract imposes: which communications have to travel separately, who owes the programme and how often, which warning is not a claim, what has to be particularised and by when. One side of A4, pinned where the team can see it, naming the person who owes each object. It is unglamorous and it takes a morning. Repeat it every time somebody new takes the commercial lead, because the clocks leave with them otherwise.

The second belongs to the client, employer or appointing party, because they are the ones instructing the amendments. Every Z-clause and particular condition that moves a notice period, or adds an information protocol on top of the printed form, changes what the project has to produce and when — and it is worth saying plainly in the tender documents which objects you expect, in what form, and through which route, instead of leaving bidders to discover it at the first compensation event. Then resource it. Keeping a register current, revising a programme monthly, and building particulars while the event is still fresh are somebody’s actual hours, not an overhead line that survives the first cost-cutting exercise. A team that prices that properly and drops it in month four has bought the worst of both: the cost of the discipline and none of the record.