NEC letters that work: what each one should say

What every NEC letter needs, plus plain wording you can adapt for replies, chasers, defects, programme requests and extensions of time for a reply.

Communications and records3 min read

On this page
  1. The header block
  2. Wording to adapt
  3. Habits that make letters land
  4. Related guides

Most NEC letters need the same few things: the contract and your reference, the date, who it is from and to (by role, not just name), the clause you are acting under, what you are doing, and what you need back by when. NEC rarely prescribes a format, so check whether your Scope (the document describing the works) names a system or layout before using anything below. The wording here is invented for illustration, written for NEC4 ECC, and you will need to adjust roles and clause numbers on other forms.

The header block

Put these lines at the top of every letter:

  • Contract name and number
  • Your reference (a prefix for the type of letter, then a number)
  • Date issued
  • From and to, each with role under the contract
  • Clause relied on
  • Subject, in one line
  • Reply needed by, or "none"

Send each notification as its own letter (13.7). A letter covering three subjects makes it easy for the reader to miss one.

Wording to adapt

Replies you receive. The Project Manager (the person the Client appoints to run the contract day to day) answers your notification in one of two ways: it is a compensation event, which is the contract's term for something that can change your price or dates, or it is not, with a stated reason (61.4). Your next letter either supplies a quotation by the due date, or asks for the missing facts behind a refusal.

Chasing before the formal step. "Our reference [x] was due a reply on [date]. We have no record of one. Please say when we can expect it. This is a reminder only, not a notification under the contract." Use this when you want to stay friendly and keep your formal rights intact.

Formally notifying silence (61.4, 62.6, 64.4). State the clause, the reference, the date the reply was due, and that no reply came. For a quotation, say which quotation you want treated as accepted.

Asking for more time (13.5, 62.5). Give the old date, the proposed date and the reason, and ask for agreement before the original date passes.

Notifying a Defect (43.2). Date found, location, what falls short and which part of the Scope it breaches, with a photograph attached.

Challenging a refusal of acceptance (13.4). A refusal of your submission should come with a reason the contract allows. If it does not, ask in writing for the reason and the specific points to fix.

Revised programme requests (32.2). The Project Manager can instruct one, naming the matter driving it. Reply with the revision inside the period for reply.

Longer letters have their own guides: the early warning notice template, the compensation event quotation template, and the programme submission template.

Habits that make letters land

  1. Name the clause. It tells the reader what kind of communication this is and which clock starts.
  2. One purpose per letter. A notice mixed with a complaint gets a muddled answer.
  3. Say your role when it could be unclear. A delegate should say they act for the Project Manager under 14.2.
  4. Stay neutral. Facts and the contractual step first. Argument, if needed, comes later and reads better after a civil start.
  5. Do not over-template. A generic letter with no specific facts is easy to dismiss, especially when replying to a refusal.
  6. Do not paste NEC clause wording into your own forms. A short clause number does the job.

For how to send and log letters, see managing NEC communications.

This guide is general information, not legal advice. Check it against your contract.

Was this useful?