Client staff are giving your site team orders: how to handle it under NEC

What to do when the Client instructs your site team directly instead of through the Project Manager, and how to protect your time and money.

Communications and recordsScenario3 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. Ways the Client side can fix it
  6. When to get help
  7. Example
  8. Related guides

The Client's site lead keeps asking your foreman for changes, and none of it comes through the Project Manager. The Project Manager is the person the Client appoints to run the contract day to day, and under NEC they are the one who gives instructions.

The short answer

Ask the Project Manager to confirm in writing which requests are instructions, and propose a fix: either all requests go through them, or they formally delegate the action. Under clause 14.2 the Project Manager can delegate any of their actions after telling you, and that can include someone on the Client side. Until that is in place, a direct request has no standing as an instruction under 14.3, which leaves you carrying the risk.

What to do, step by step

  1. List the requests. Date, who asked, what changed. Send the list to the Project Manager and ask which are instructions.
  2. Start the eight weeks. For any request with an effect on cost or time that does not clearly arise from the Project Manager's own action, the time limit in clause 61.3 is already running. Notify without waiting for their answer.
  3. Hold off the open ones. Do not start requests marked as undecided until you have a written position.
  4. Set a site rule. Every Client request is logged, and the log goes to the Project Manager weekly until the pattern stops.
  5. Offer a fix. A named delegate, or a quick same-day instruction form, solves it for everyone.

What to record

  • Each request: date, person, wording, the area of work.
  • Any work started and any work deliberately held.
  • The effect on the programme and the cost of anything built.
  • Your letters to the Project Manager and their replies.

What not to do

  • Do not obey and say nothing. You then have work with no entitlement behind it, and anything that departs from the Scope might be treated as a Defect.
  • Do not accuse the Client of bad faith. Present it as a process problem that is exposing both sides.
  • Do not ignore the Client either. Mutual trust and co-operation (10.2 in NEC4) does not override who holds which power, but a calm tone keeps the relationship intact.
  • Do not wait for the Project Manager's reply before notifying.

Ways the Client side can fix it

Fix Works best when Watch out for
Delegation under 14.2 A Client lead is on site every day Keep it narrow and keep the list current
A weekly review of requests Minor preferences A review is not an instruction
Replacing the Project Manager (14.4) The role is not being performed Earlier decisions still stand
Amending the contract (12.3) The Client wants formal change control Needs both parties' signed agreement, so it is slow

When to get help

Bring in a commercial manager as soon as a pattern appears, since several small unnotified changes add up. A planner can show the combined programme effect. If the Project Manager disowns decisions you relied on, take legal advice before the position hardens.

Example

On a rail depot fence job, the Client's engineer asks for three gate changes and a relocated bollard over two weeks. The contractor sends one table listing all four, notifies those with an effect, and suggests a delegation for finishes below an agreed value. The Project Manager replies the next day, ruling on two requests and delegating the rest.

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

Was this useful?