Will an early warning be read as admitting we are at fault?

Why raising an early warning does not admit blame under NEC, and how to word one so it records the risk without handing the other side a weapon.

Early warning and riskScenario3 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

Your team has spotted a problem, but nobody wants to put it in writing in case the Client later says "you told us it was your fault". Under NEC, that fear is misplaced, although the wording you choose still matters.

The short answer

Raise it. The early warning clause (15.1 in NEC4, 16.1 in NEC3) asks either side to flag anything that could affect cost, time or quality, whoever caused it. It is a duty, not a confession, and it decides nothing about who pays. The real danger is staying quiet: if you could have warned and did not, the Project Manager (the person the Client appoints to run the contract day to day) can say so under clause 61.5, and the related compensation event may then be priced as though you had warned.

What to do, step by step

  1. Send the warning as soon as you are aware of the matter. Do not hold it back while you decide where the blame lies.
  2. Describe what you can see: what is wrong, where, and which programme date or key date it could touch.
  3. Use "could" for the effects. You are describing a possibility, not a forecast.
  4. Suggest a next step, such as a short meeting or an option you want to test.
  5. Keep the cause out unless it is plain and neutral. "Rebar delivered to Bay 3 does not match the current drawing" is a fact. "Our supplier got it wrong" is a story.
  6. Work out the commercial position separately. If the matter may be a compensation event, a notice is a different document with its own deadline: see does an early warning count as notifying a compensation event.

What to record

  • The date and time you became aware, because the warning will be used as evidence of that date.
  • Who attended the early warning meeting and what was agreed.
  • The entry on the early warning register, and any action given to each side.
  • The facts behind the warning: photos, delivery notes, drawing numbers, emails.

What not to do

  • Do not write "due to our error" or "the Client has failed". Both are conclusions, not facts.
  • Do not add "we accept responsibility for any delay". A warning does not need it.
  • Do not mark the warning "without prejudice". It is a contract communication, not a settlement offer, and the label muddies its status.
  • Do not delay the warning to polish it. A late warning defeats its purpose.
  • Do not hide an error your own team made. Just do not turn the warning into a statement about fault.

When to get help

Speak to your commercial manager if the warning could be the first step towards a claim. If a formal dispute is already running, take legal advice on how you word anything further. A planner can help if the warning is about programme dates and you need the effect on the critical path set out cleanly.

Example

A pipe-laying subcontractor learns its pipe supplier has had a plant breakdown, so the delivery could slip by a week. The site team worries it looks like their problem, but warns anyway: "Pipe delivery for Section 2 may arrive a week late. This could delay Key Date 2. We are checking alternatives and suggest a short meeting." At the meeting, the Project Manager points out that the Client's follow-on trade could start later than planned, and a small resequence removes most of the delay. The warning cost nothing, and the risk belonged to the subcontractor either way.

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

Was this useful?