NEC4 recognises digital contract management systems. That recognition comes with a sharp edge for any team still sending notices by email.
A clause written for the digital age
When NEC4 was published, clause 13.2 was one of its quieter innovations. It says that if the Scope specifies a communication system, a communication has effect only when it is communicated through that system. If no system is specified, a communication has effect when it is received at the last address notified by the recipient.
Dr Stuart Kings, one of the nine drafters of NEC4, described the clause at Sypro’s October webinar as “quite fundamental and groundbreaking” because it formally recognised web based contract administration platforms. The implication is simple. Where the Scope names a system, that system is the contract’s official channel. Everything else is conversation.
The email trap
Old habits persist. A Project Manager responds to a compensation event from their phone. A commercial manager sends a notification by email because the deadline is today and the platform login has expired. A site team issues an instruction in meeting minutes.
Stuart has seen where this leads: “I have known disputes arise, because organisations were using a web based system, but then communicated outside of the system via email or different systems, and it wouldn’t be a valid communication contractually.”
The consequences can be severe. NEC4 is full of time limits. A contractor that believes it notified a compensation event within the eight week window in clause 61.3 may discover it never validly notified at all. A Project Manager who thinks they replied to a quotation in time may find the quotation has been treated as accepted. The party relying on the email is the one left exposed.
Responsibility for using the correct channel sits with the sender. It is no answer to say the other party knew about the email, or replied to it, or discussed it at a progress meeting. If the Scope specifies a system, the contract is clear that the communication takes effect only when it goes through that system. Teams that switch between channels depending on convenience are building a record that the other party can pick apart, one notice at a time.
The risk runs both ways. A client that issues an instruction by email may later find the contractor arguing it was never validly given, and the Project Manager’s own replies are subject to the same rule.
The courts have shown how much weight informal messages can carry. In Jaevee Homes Ltd v Fincham [2025] EWHC 942 (TCC), a demolition contract agreed over WhatsApp was held to be binding, and a formal subcontract emailed later was not. The same judgment found that a second payment application sent in a single month was invalid. Under NEC4, the danger runs in the opposite direction. Where the Scope specifies a communication system, a notice sent by WhatsApp may have no contractual effect at all.
Notifications must also stand alone
Clause 13.7 adds a second discipline. Notifications and certificates required by the contract must be communicated separately from other communications. CECA’s NEC4 bulletin on communication flow warns against relying on general meeting minutes for these items. Where a notice is needed, it should be lifted out of the minutes and issued on its own.
Taken together, clauses 13.2 and 13.7 mean that a notice buried in an email chain may fail twice over: sent through the wrong channel, and not issued as a separate communication.
Why it matters for disputes
Poor contract administration consistently ranks among the leading causes of construction disputes. Arcadis’s Global Construction Disputes Report has repeatedly identified failure to properly administer the contract as the most common cause, and the 2024 Construction Adjudication in the United Kingdom report from King’s College London and The Adjudication Society found half of respondents citing inadequate contract management.
Communication failures are a large part of that picture. When the record of who said what, and when, is scattered across inboxes, a dispute becomes an argument about facts before it ever reaches the merits. A specified system gives both parties one auditable, time stamped record.
Five steps to stay on the right side of 13.2
Read the Scope. Before the contract starts, check whether a communication system is specified and exactly what it is. If one is named, it governs every contractual communication.
Give everyone access on day one. Set up accounts for the Project Manager, Supervisor, contractor’s team and any delegates before the starting date. Access problems are not a defence to a missed timebar.
Agree the rule at the launch event. Make it explicit that formal communications go through the system and nowhere else. Emails and calls are fine for discussion, but they are not the record.
Separate notices from minutes. Use the system to issue each notification or certificate on its own, as clause 13.7 requires.
Watch the clock. Use dashboards that flag what is due and what is overdue, so that replies go out within the contractual period rather than after it.
A single source of truth
Clause 13.2 does more than settle a technical question about notices. It gives project teams a reason to put every communication in one place, visible to all parties and fully auditable. Used properly, the specified system becomes the single source of truth that prevents disputes about what was communicated, and lets the parties focus on what actually matters.
