The forms and documents you need on an NEC contract
Which NEC documents come ready-made, which you must create yourself, who issues each one and what a notice or certificate must do to be valid.
On this page
NEC publishes the contract documents in a set format, but it gives you very little for the day-to-day paperwork: notices, certificates and logs are mostly yours to create. Unless your Scope (the document describing the works and any rules for how you communicate) names a particular system or format, any form is fine so long as it does what the contract requires. This guide covers the NEC4 Engineering and Construction Contract (ECC).
Documents that exist at the start
| Document | Completed by | What it does |
|---|---|---|
| Contract Data part one | Client | Fixes the Options, dates, periods, named people and many key values |
| Contract Data part two | You | Your fee percentage, key people, rates, and a first programme if you offer one |
| Scope | Client (plus yours for any design you do) | What the works are, plus constraints |
| Site Information | Client | What is known about the Site and surroundings |
| Activity Schedule or Bill of Quantities | You | Builds up the Prices |
| Form of agreement | Both parties | Makes the deal binding; many organisations use their own |
Documents you will meet during the job
Think of these by who sends them.
You send:
- Early warning notice (15.1), shared with the Project Manager, who is the person appointed by the Client to run the contract
- Compensation event notice (61.1, 61.3) and quotation (62.2, 62.3)
- Programme submission (31.1, 32.2)
- Application for payment (50.2)
- Defect notification, if you find one (43.2)
The Project Manager sends:
- Early Warning Register (15.2, 15.4)
- Instructions (14.3 and others), though the Supervisor, who checks quality, issues those about tests and Defects
- Reply to your notification (61.4) and their own assessment (64.1, 64.3)
- Payment certificate (51.1)
- Completion certificate (30.2) and take-over certificate (35.3)
- Final assessment (53.1), or you issue it if they fail to
Others:
- Pay less notice: either party, where Option Y(UK)2 applies (Y2.3)
- Defects Certificate: the Supervisor issues it, listing remaining Defects or stating none
What makes a form acceptable
The contract asks that a communication can be read, copied and recorded (13.1), and that each notification or certificate stands alone, not tucked inside something else (13.7). Beyond that, a form is better if it:
- Asks for the facts people forget, such as the date you became aware of a compensation event.
- Shows the role and clause on its face, so nobody has to guess what it is in two years' time.
- Feeds your register without retyping.
Other editions and contract types
- NEC3 ECC: the Contract Data is similar, but it uses Works Information and the Employer. There is no final assessment, and Defects clauses are numbered differently. See NEC3 vs NEC4.
- Short contracts: these come with simpler forms. See the short contract guide.
- Term service contracts: you also need a Task Order form and the Service Manager's equivalents. See Task Orders explained.
What people get wrong
- Assuming a form must look official. What counts is that it does the contractual job.
- Putting several subjects in one notice.
- Forgetting the Scope may name a communication system. If so, a message outside it may not count.
Related guides
- Registers every NEC contract needs
- NEC letters that work
- Clause 13: communications
- Managing NEC communications
This guide is general information, not legal advice. Check it against your contract.
