NEC subcontracts explained: ECS, the short subcontract and how they link to the main contract
How NEC subcontracts work, who acts as Project Manager at subcontract level, and what flows down from the main Engineering and Construction Contract.
On this page
An NEC subcontract is a separate contract between the main Contractor and the Subcontractor. It is not a section of the main contract, and the Client is not a party to it. That is the first thing to hold on to, because almost every subcontract problem comes from forgetting it.
The NEC subcontract forms
The two forms most subcontractors meet are:
- The Engineering and Construction Subcontract (ECS). The full form, used where the subcontract work is significant, designed or complex. It follows the same structure as the Engineering and Construction Contract (ECC): core clauses, main Option clauses, secondary Options and Contract Data.
- The short subcontract. A shorter, simpler form for lower-value or low-risk work, with fewer clauses and no heavy procedure. The NEC4 version is the Engineering and Construction Short Subcontract (ECSS). Check which form you have been given, because the rules differ from the ECS: for example, under the NEC4 ECSS a compensation event is notified within three weeks (61.3), programmes are sent as the Scope says with no acceptance step, and there are no Key Dates.
Both are used with the same family of main contracts, but a subcontract does not have to match the main contract's version or Option. The main contract and the subcontract can use different main Options, so a Contractor on Option C can let a package on Option A. Look at the front page and Contract Data to see what you actually have, and check which edition it is, because the periods differ between NEC3 and NEC4.
How the subcontract links to the main ECC
The link is commercial and practical, not legal. The Subcontractor has no contract with the Client, and the Client has none with the Subcontractor. In the main ECC, clause 26 (subcontracting) keeps the Contractor responsible for Providing the Works as if it had not subcontracted (26.1). The Contractor submits each proposed Subcontractor's name for the Project Manager's acceptance (26.2) and, unless the subcontract is an unamended NEC form or the Project Manager agrees otherwise, the subcontract documents with pricing removed (26.3). So the main contract controls who you can be, and sometimes what your terms say.
What links the two contracts is the Contractor's own obligations. If the Client changes the Scope (Works Information in NEC3), the Contractor may have a compensation event on the main contract and need to pass a change down to you. If the main programme moves, your dates may move too.
Who is the "Project Manager" at subcontract level
In the ECC the Project Manager is a named role, usually acting for the Client. At subcontract level the position is different. In the NEC4 ECS the Contractor takes over both the Client's and the Project Manager's positions, so it gives your instructions, replies to your notifications and assesses your compensation events. The Supervisor does not simply disappear: tests can still involve the main contract Supervisor, and the Subcontract Data asks for the names of the main contract Client, Project Manager, Supervisor and Adjudicator. The Client's Project Manager has no authority under your subcontract.
So when you receive an instruction, acceptance or assessment, it should come from the Contractor under your subcontract, not from the Client's team. Check your Contract Data to see how the roles are named and who is given authority. Do not assume the main contract Project Manager can instruct you directly.
What flows down, and what does not
| Flows down in practice | Does not flow down automatically |
|---|---|
| The Contractor's dates, Key Dates and Working Areas where your subcontract adopts them | The Client's right to instruct you |
| Scope and quality requirements you have been given in your Subcontract Scope | Main contract notification periods (the unamended NEC4 ECS gives you seven weeks to notify a compensation event, not the ECC's eight) |
| Consequences of the Contractor's own compensation events | Payment dates from the main contract |
| Z clauses and other terms if the subcontract copies them in | Dispute resolution under the main contract (though the NEC4 ECS lets the Contractor bring you into a main contract adjudication on the same matter) |
Whether something flows down depends on the words in your subcontract and Contract Data. Read the Subcontract Contract Data and every Z clause. If the subcontract says a main contract term applies, that is what binds you. If it does not say so, it does not apply just because the main contract says it.
Why back-to-back matters
A subcontract is "back-to-back" when its dates, procedures and risk allocation line up with the main contract. Where they do not, the party in the middle carries the gap. Usually that is the Subcontractor, who may be asked to meet shorter notice periods or accept risk the Contractor itself does not carry. See preparing a subcontract package for the Contractor's side, and time bars for subcontractors for the deadlines that catch people out.
What to check on day one
- Which form and which version of NEC you have been given.
- The Subcontract Contract Data, completed by both parties.
- Every Z clause and any amendments to the core clauses.
- Who acts in the Project Manager role and who is the Supervisor.
- The programme requirements and when you must submit and update your programme (see clause 31 programme checklist).
- The notification and payment periods in your own subcontract.
Treat the subcontract as heavily amended until you have read it. Subcontract Z clauses often change the periods and procedures described in guides like this one.
Related guides
- Preparing a subcontract package
- Time bars for subcontractors
- Compensation events in plain English
- How payment works under NEC
This guide is general information, not legal advice. Check it against your contract.
