Contract basics

Meeting minutes as notice: NEC4, JCT and FIDIC

By the

A delay, a change in ground conditions or an informal instruction is raised at the progress meeting. The minutes record it, and the action column says "noted". It feels as if the matter is now on the record. Under NEC4, JCT and FIDIC it usually isn't a notice. It can still do two things that matter: show when you knew about the event, which is when most notice clocks start, and, if you let an inaccurate version stand, become the record that is used against you.

Who this is for: commercial managers, quantity surveyors and project managers at contractors and subcontractors who attend progress meetings, receive the minutes from the other side, and want to know what the minutes do and don't protect.

The short answer, by contract

ContractRules that matterDo minutes count as notice?What to do
NEC4 ECC13.2 communication system or address, 13.7 separate notifications, 61.3 eight weeks from awarenessUnlikely: a minute is not a separate notification sent through the communication system, and CECA says general minutes are not a document to rely onNotify the compensation event on its own; treat the minute as proof of when you became aware
JCT 2016 and 2024 (SBC, DB)1.7 service of notices; SBC 2.27 and DB 2.24 notice of delay forthwith; SBC 4.21 and DB 4.20 loss and expenseDoubtful, particularly if the other side wrote the minuteServe the notice of delay and the loss and expense notice yourself, under the clause
FIDIC 20171.3 Notices identified as Notices, in writing, through the stated system; 20.2.1 Notice of Claim within 28 daysVery unlikely: a minute is not identified as a NoticeGive the Notice of Claim within 28 days; use the minute as evidence of awareness

Projects change these rules through the Scope, Contract Particulars, Contract Data or amendments, so read yours before relying on any of this.

What the court said about minutes

The clearest UK authority we found is Steria Ltd v Sigma Wireless Communications Ltd [2007] EWHC 3454 (TCC). A sub-contract clause required the sub-contractor to give the contractor "written notice ... of the circumstances giving rise to the delay" within a reasonable period. One issue was whether written notice could extend to "minutes of meetings" (para 79).

HHJ Stephen Davies said it could not, at least not on its own (para 82):

"I also consider that the written notice must emanate from Steria. Thus for example an entry in a minute of a meeting prepared by [the employer's consultants] which recorded that there had been a delay ... and that as a result the sub-contract works had been delayed, would not in my judgment by itself amount to a valid notice."

The reasoning was that the other side "must know that Steria is contending" that the circumstances have occurred and have caused delay. The minute in that example was written by the employer's consultants, not by the sub-contractor, so it didn't show that the sub-contractor itself was making the claim.

Three limits. This was a first-instance decision on one sub-contract's wording, not on NEC4, JCT or FIDIC. The minute was the judge's example of what would not be enough, not the point the case turned on. And it dealt with a minute prepared by someone else, so it doesn't decide whether minutes you wrote yourself could ever work. We are not aware of a later reported decision on minutes. It is still the clearest UK guide we found to how a court is likely to see a "noted" entry.

Why minutes fail as notice

Three tests catch most of them.

  1. Who wrote it. If someone else drafted and circulated the minutes, such as the client's team or the other side's project manager, the notice doesn't come from you. In Steria the example minute was written by the employer's consultants.
  2. How it was sent. Where the Scope specifies a communication system, NEC4 clause 13.2 gives a communication effect when it is communicated through that system; if it doesn't, when it is received at the last address notified. Clause 13.7 requires a notification to be communicated separately from other communications, which NEC's User Guides say is "to avoid important things being overlooked". Minutes that cover many topics are the opposite. CECA's guidance on 13.7 says general "minutes of meetings" are "not a document to rely on", and that any specific elements should be abstracted from them and communicated separately. JCT clause 1.7 and FIDIC Sub-Clause 1.3 also govern how notices are served, FIDIC's more strictly than JCT's.
  3. What it says. Courts read a notice objectively, as a reasonable recipient would (Advance JV v Enisca Ltd [2022] EWHC 1152 (TCC), para 47, a case about payment notices). In Obrascon (a FIDIC 1999 Yellow Book case), a progress report saying that rain had affected the works was "clearly nowhere near a notice" (para 315). "Delay noted" in a minute is thinner still.

For how the clocks themselves work, see our guides to the NEC4 eight-week notice clock, the JCT extension of time and the FIDIC 28-day time bar.

What minutes can still do

They show when you knew

The clocks run from awareness, not from notice. Under NEC4 clause 61.3 it is when the Contractor becomes aware that the event has happened. Under JCT it is when delay becomes reasonably apparent. Under FIDIC 2017 it is when the Contractor became aware, or should have become aware. A minute that records your site manager raising the problem at a dated meeting is good evidence that the clock was running from that day. So an argument that the clock had not started is hard to run.

They can help if notice was late

Under FIDIC 2017, if the Engineer gives notice within 14 days that a Notice of Claim was late, the contractor can explain in its fully detailed Claim why the late submission is justified (Sub-Clauses 20.2.2 and 20.2.5). FIDIC's non-exhaustive list of circumstances that may be taken into account includes evidence of the other party's prior knowledge of the event and how far it would be prejudiced. Minutes showing the other side knew about the problem are the kind of evidence that fits. But the outcome is discretionary, and if the Engineer gives no such notice within 14 days the Notice of Claim is deemed valid. It is a fallback, not a plan.

They become the record

In Gestmin SGPS SA v Credit Suisse (UK) Ltd [2013] EWHC 3560 (Comm), Leggatt J said the best approach for a judge in a commercial case "is ... to place little if any reliance at all on witnesses' recollections of what was said in meetings and conversations, and to base factual findings on inferences drawn from the documentary evidence and known or probable facts" (para 22). That was a Commercial Court case about witness evidence generally, not about minutes, and the judge accepted that oral evidence still has a role. A minute is not conclusive. But documents written at the time tend to outweigh recollection years later, and if the minute is wrong and you never said so, you are arguing against your own silence.

When the minutes are wrong

  1. Read them the day they arrive. Compare them with your own notes. Check the action column and any "noted" entries about delay, instructions or ground conditions.
  2. Reply in writing, to the author and every attendee. List each correction specifically. Do it before the next meeting. Check the Scope, Employer's Requirements or meeting protocol for a stated period.
  3. Ask for the correction to be recorded. The next minutes should show it under matters arising, so the corrected version is what carries forward.
  4. Don't treat the correction as a notice. Send any notice separately, under the clause, referring to the meeting.
  5. Keep your email. If the author won't amend the minutes, a dated email setting out your version is still evidence of what you said, before any dispute started.

A short request to correct the minutes

Request to correct minutes of [meeting type] held on [date]

Project: [name]. Contract: [NEC4 ECC / JCT SBC or DB / FIDIC 2017], as amended.

We have reviewed the minutes issued on [date]. They are not accurate in the following respects:

  • Item [no.]: the minutes record [what they say]. What was said was [your version].
  • Item [no.]: [the matter] was raised by [name] on our behalf and should be recorded as [your wording].

Please amend the minutes and record this correction under matters arising at the next meeting. This email is not a notice under the contract. We will give any notice separately under the relevant clause.

For the notices themselves, see our notice templates for NEC4, JCT and FIDIC.

Where OnNotice fits

Minutes are a typical place for an entitlement to sit unnoticed. OnNotice reads the text of project email as it arrives, including minutes sent in the body of a message. It flags events that may carry an entitlement, cites the governing clause, and counts the deadline from the date of the email, which is an approximation of when your team became aware. Every flag links back to the original email in a tamper-evident record.

If minutes arrive as an attached PDF or Word file, OnNotice stores the attachment as evidence with the email, but it doesn't read inside attachments at the moment, so a person still needs to read them. It drafts the notice; a person decides what gets sent. See how it works.

For the wider picture across NEC4, FIDIC and JCT, see why contractors lose entitlements to time-bars. For instructions that arrive in chat rather than in minutes, see our guide to WhatsApp instructions under NEC4, JCT and FIDIC.

Sources


This is general information about how NEC4, JCT and FIDIC typically treat meeting minutes and notices, not legal advice for your contract. Notice rules are often changed by the Scope, Contract Particulars, Contract Data or amendments, so have a contracts specialist confirm the position on your project.

Frequently asked questions

Do meeting minutes count as a valid notice?
Rarely, and not by themselves. In Steria v Sigma [2007] EWHC 3454 (TCC), the court held that, under that clause, the written notice must come from the party claiming, and that an entry in a minute prepared by someone else recording a delay would not by itself be a valid notice. That was a decision on one sub-contract's wording, but NEC4 clauses 13.2 and 13.7 and FIDIC Sub-Clause 1.3 add channel and identification rules that a minute rarely meets. JCT clause 1.7 is looser on method, so under JCT the answer rests more on who gives the notice and what it says.
If the minutes record the delay, has the notice clock started?
Possibly, yes. Most of the clocks run from awareness: NEC4 61.3 from when the Contractor becomes aware of the event, JCT from when delay becomes reasonably apparent, FIDIC 2017 from when the Contractor became aware or should have. A dated minute that records your team raising the problem is evidence of when you knew. It can start the clock without ever counting as the notice.
How long do I have to object to inaccurate minutes?
The sources we reviewed give no period for objecting to minutes under NEC4, JCT or FIDIC. Some projects set one in the Scope, Employer's Requirements, preliminaries or a meeting protocol, so check those first. Without one, correct them in writing before the next meeting, which is typically when the previous minutes are approved, while everyone's memory is fresh.
Can I use minutes I wrote myself as my notice?
The Steria point, that notice must come from the claimant, doesn't rule it out, but the minute would still have to meet the contract. Under NEC4 it must be a separate notification sent through the communication system (13.2, 13.7). Under FIDIC 2017 it must be identified as a Notice (1.3). Minutes that cover a dozen other topics rarely do either. Send the notice on its own.

Found this useful? Share it with your team