ClarusDocs
← All documents
Registers

NEC4 Communications Log Template

Written from experience on CTRL, Crossrail and Network Rail

This NEC4 communications log records every formal communication between the parties, including instructions, early warnings, notifications, submissions and replies, with the date each response is due. It is laid out in landscape so the whole register fits across the page.

Page 1 of the NEC4 Communications Log TemplateSee what you get →

Free: NEC4 CE letter sample →ClarusPM →

Completed except the facts only you know

£25 + VAT

£30 inc. VAT

  • Fills in: The register header for your project.
  • Stays [TO CONFIRM]: Names and references you haven’t given us. Entry rows are left blank.
  • A competent person must review before use.
  • Company logo in header
  • Delivered in minutes
  • Word document (.docx)
Build mine →

Template

£9 + VAT

£10.80 inc. VAT

Blank register — fill in yourself

  • Word document (.docx)
  • Guidance notes included
  • Instant download
  • Use on any project
NEC4 ECC clause 61.3 The 8-week CE notification rule in the main contract.Read the post →

Prices exclude VAT: UK customers pay 20% VAT; VAT is not charged for customers outside the UK.All documents are drafts. Placeholders marked [TO CONFIRM] must be completed with your site-specific details. A competent person must review before use on site.

What it's for

NEC4 runs on time limits. Missing a reply period or a notification deadline can cost money or time. A single log shows what has been sent and received, what is waiting for a reply, and when it is due, so nothing slips.

When you need it

From the start of the contract to the end, and kept up to date as each communication is sent or received.

Who signs it

It is not signed. It is kept by the contractor’s project manager, commercial manager or document controller.

What's inside

  • Contract details, including the named Project Manager and Supervisor and the period for reply from the Contract Data
  • A summary of the clause 13 rules: communications in a readable form, sent through the communication system in the Scope, and notifications kept separate
  • A 14-row log with reference, date, from, to, type, clause, description, response due, response received and notes
  • A table of common communication types, with their clauses and reply periods
  • A note on extending reply periods by agreement (clause 13.5)

FAQ

Does the log replace the communication system named in the Scope?
No. Communications must still be sent through that system. The log is your own record to track them.
Can reply periods be extended?
Yes, by agreement, before the reply is due. Record the agreed extension in the notes column.
Why keep notifications separate?
Clause 13.7 requires notifications under the contract to be communicated separately from other communications. A notice buried in another letter may not count.
What is [TO CONFIRM]?
Details only you know, such as names, references and dates. We never guess these. They appear as highlighted [TO CONFIRM] placeholders, and the register opens with a list of every one. The entry rows are always left blank: we never invent entries, so you record them as the work goes on.
Can I edit the document?
Yes. Both options are Word documents you can edit freely.
Do I still need to review it?
Yes. A competent person must check every document against the actual site and works before it is used. ClarusDocs gives you a complete first draft, not a substitute for that check.

Keeping this record every day? ClarusPM keeps it on a tablet on site and on the office computer. See ClarusPM →