Who should a subcontractor send an early warning to?

A subcontractor's early warning goes to the main contractor, not the Project Manager. Learn how to word it, what it must cover and what it does not replace.

Subcontractors and supply chainScenario3 min read

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

You have spotted a problem on site and you work for a subcontractor. Who do you tell?

The short answer

Tell the main contractor, in writing, as soon as you are aware. Under the subcontract (clause 15.1 in NEC4, clause 16 in NEC3) the main contractor is your counterparty. The Project Manager (the person who runs the main contract for the Client) sits outside your subcontract and has nothing to do with how it operates. If the matter also affects the main contract, passing it up is the main contractor's job under its own clause, so do not assume it has happened.

What to do, step by step

  1. Warn as soon as you know. The contract sets no fixed number of days.
  2. Issue it as a standalone communication, in the format your Subcontract Scope specifies, not tucked into a daily report or meeting minute (13.7).
  3. State what it threatens. The contract names four targets: the Prices, Completion, a Key Date, and performance of the work in use. A risk that only adds to your own cost is also worth raising.
  4. If it is pressing, ask for a meeting. Under 15.2 either party can require the other to attend one.
  5. Flag it if you think the main contract is hit too, so the main contractor can act fast.
  6. If the problem is also a compensation event, notify that separately. The warning neither starts nor stops your seven weeks under 61.3.

Who talks to whom

Chain link Warnings pass between Register held by
Main contract Contractor and Project Manager Project Manager
Subcontract You and the main contractor Main contractor
Sub-subcontract Lower tier and whoever employs it That employer

The NEC4 subcontract offers one link between the layers. When a main contract matter also touches your work, the main contractor can instruct you to join its own early warning meeting with the Project Manager. NEC3 has no direct equivalent, so agree it informally.

What to record

  • The date you first knew of the problem.
  • The warning, how it was sent and when.
  • Any meeting held and the actions agreed.
  • Your separate compensation event notice, if there is one.

What not to do

  • Do not rely on a chat with the Project Manager. It does not count as a warning under your subcontract. Site conversations are fine for information if the main contractor knows, but follow up in writing.
  • Do not bury the warning in a progress report.
  • Do not stay silent for fear of blame. A warning says nothing about liability.
  • Do not delay for a safety issue. Tell anyone who can act first, then record it properly.

When to get help

Ask your commercial manager if the main contractor ignores your warnings, because an experienced subcontractor that could have warned and did not can face a statement under clause 61.5, which may reduce what it recovers. On a non-NEC subcontract with no warning clause, tell the main contractor in writing anyway.

Example

A fictional fencing subcontractor hears that its powder-coater is running a three-week queue. It writes to the main contractor: "Early warning, clause 15.1. Coating is three weeks behind. This could push back our Completion and Key Date 4 for the north boundary. Options: a second coater, or a different finish. It may touch your own programme to the Project Manager, so please call a meeting this week."

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

Was this useful?