NEC clause 13 communications: how to send a notice that counts
A plain walk through NEC clause 13: the form, timing and replies that decide whether your notice, submission or answer is valid.
On this page
Clause 13 is the rulebook for every formal message on an NEC contract. If a notice does not follow it, it may not count, even when everyone understood what you meant. A compensation event or a defect dispute can turn on that. The clause is almost the same in NEC3 and NEC4, apart from one NEC4 addition about communication systems.
What each part does for you
- 13.1: put it in a form that can be read, copied and recorded. A phone call does not do it. An email can, provided nothing else in your contract rules email out.
- 13.2: when it takes effect. In NEC4, if the Scope names a communication system, the message takes effect when sent through that system. Otherwise, as in NEC3, it takes effect when it arrives at the last address notified. That sets when the clock starts.
- 13.3: the default reply time. Answers are due within the period for reply, the number of days or weeks set in Contract Data, unless the contract gives a particular answer its own period.
- 13.4: replies to anything submitted for acceptance. The Project Manager, the person the Client appoints to run the contract, must either accept or give reasons. You then resubmit within the period for reply. A bare "rejected" is not enough, and NEC4 expects reasons detailed enough for you to fix the problem.
- 13.5: extending a period. Only if the Project Manager and you agree before the reply is due. Agreeing after the deadline has gone does not fit the clause.
- 13.6: certificates. Say who issues them and who must receive them. Send to everyone named.
- 13.7: keep notifications separate. A notification the contract requires must be sent on its own, apart from other communications. NEC4 says the same of certificates. Meeting minutes are a poor place to bury one.
- 13.8: withholding acceptance. Doing so for a reason the contract states is not a compensation event. For a reason it does not state, 60.1(9) can apply.
Example: the damper delay
Imagine a hospital job where the period for reply is two weeks. At a progress meeting on 2 May your site manager says a late fire damper delivery is a compensation event, and the minutes note it. You send a formal notice on 16 June.
Was the minute a notification? Weakly at best, because 13.7 wants notifications separate. Does it matter? Perhaps not, if 16 June falls inside the 61.3 notification period counted from when you became aware. If it does not, it matters a great deal.
A one-paragraph email on 2 May, sent separately by the proper route, would have avoided the whole debate.
Mistakes to avoid
- Bundling. One letter containing an instruction, a notification and a reply saves time today and causes doubt later.
- Assuming a portal upload counts. If the Scope names a system, use it. If it names none, a shared folder may not satisfy 13.2.
- Old addresses. Tell people formally when an office or inbox changes.
- Replying without reasons. It looks like a refusal to engage and may fail 13.4.
- Thinking only your replies are timed. 13.3 binds the Project Manager and Supervisor too, and a late reply from them can be a compensation event under 60.1(6).
- Treating silence as agreement. Generally it is not. NEC4 has a few specific treated-acceptance routes, such as programmes under 31.3, each with its own steps.
Quick pre-send check
- Is it written, in the contract language, and recordable?
- Does it go through the named system or the notified address?
- Is it separate if it is a notification?
- Does it say which clause it is made under?
- Have you logged the receipt date and the date a reply is due?
Related guides
- Communications under NEC
- Period for reply explained
- Notice sent by email, not the communication system
- Time bars for subcontractors
This guide is general information, not legal advice. Check it against your contract.
