Do you need the Project Manager's acceptance before appointing a subcontractor?

Yes, under clause 26. See what to submit, the reasons a refusal can rest on, and the risk if you have already appointed the firm.

Subcontractors and supply chainScenario3 min read

On this page
  1. The short answer
  2. What to do, step by step
  3. What to record
  4. What not to do
  5. When to get help
  6. Example
  7. Related guides

You want to put a firm on site and wonder whether the Project Manager (the person who runs the contract for the Client) has any say. Usually, yes.

The short answer

You must submit the proposed Subcontractor's name and wait for acceptance before appointing it (clause 26.2). You may also need to submit the subcontract documents for acceptance (26.3). Submit early: the Project Manager answers within the reply period set in your Contract Data, and may come back with questions or a refusal that restarts the clock. Pure suppliers and some hire arrangements may fall outside the contract's definition of a Subcontractor, so check that first. Acceptance does not reduce your responsibility: under 26.1 you stay answerable as if you had done the work yourself.

What to do, step by step

  1. Decide whether the firm is a Subcontractor as the contract defines it.
  2. Submit the name (26.2 in both NEC4 and NEC3).
  3. Submit the documents with prices stripped out (26.3). You can skip this for an unamended NEC form, or where the Project Manager has told you it is not required. NEC3 asks for the conditions of contract, except where an NEC contract is proposed.
  4. On cost-based main Options, check what pricing information has to go in (26.4 in NEC4).
  5. Hold the order. Even a letter of intent, or letting the firm mobilise, counts against you if acceptance has not come.
  6. Chase on the reply date. Silence can be a compensation event under 60.1(6), but it is not acceptance.
  7. File the acceptance against the package so the commercial team can see it.

What to record

  • The date you submitted, what you attached and who received it.
  • Any request for more information and your reply.
  • The written acceptance or refusal.
  • The date the firm was needed to meet the Accepted Programme (the programme the Project Manager has accepted).

What not to do

  • Do not appoint and ask later. Appointing a Subcontractor for substantial work before acceptance is termination reason R13. The Client may only rely on it once the Project Manager has notified the default and it remains unresolved after the set period: four weeks under NEC3 and the NEC4 ECC, three under the NEC4 subcontract. Look at 91.2 in your own copy.
  • Do not assume small packages are safe. R13 may not bite, but the failure remains and can feed a dispute about costs.
  • Do not rely on a Client preference. A preference for another firm is not a listed reason, unless the Scope restricts who you can use.

When to get help

Bring in your commercial manager if the Project Manager withholds acceptance on grounds the contract does not list, since that may be a compensation event under 60.1(9). If the firm is already working, submit at once, explain exactly what happened and ask for acceptance. Owning up late beats being found out on audit. Take legal advice if a notice of default arrives.

Example

A fictional contractor plans a piling subcontractor for week 8. The name goes to the Project Manager in week 3, with the unpriced order. The Project Manager asks for the firm's design method statement, which the Contractor supplies in week 4. Acceptance arrives in week 5, and the order is issued that day. A submission in week 7 would have put the start date at risk.

Cover note idea: "Please accept [firm] as Subcontractor for [package] under clause 26.2. The draft subcontract is attached, unpriced. The order must be placed by [date] if we are to keep to the Accepted Programme."

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

Was this useful?