The Project Manager is paid by the Client: can you expect fair decisions?
How far an NEC Project Manager has to act by the book rather than for the Client, and what to do if you think decisions are being steered.
On this page
Your Project Manager is appointed and paid by the Client, and a recent decision looks suspiciously like the Client's wish list. You are not powerless, but the contract tests the decision, not the motive.
The short answer
Not impartial in the way an Adjudicator is. The Adjudicator is the one role NEC describes as acting impartially. The Project Manager, who is the person the Client appoints to run the contract day to day, must still follow the contract's procedures and tests, and act as the contract states (clause 10.1 in both editions), with mutual trust and co-operation applying too (10.2 in NEC4). So challenge each decision on whether it meets the test the contract sets, and do not start by alleging bias.
What the contract does and does not say
- Can the Project Manager work for the Client? Nothing in the clauses covered here forbids it. Contract Data names the individual, and 14.4 lets the Client swap them.
- Can the Client say what outcome it wants? Where the decision is a choice, like whether to alter the Scope, yes. Valuing an event is different, because the contract supplies the test.
- Must the Project Manager be fair? The contract demands that they act as it states, with trust and co-operation. General law may add to that for anyone deciding between parties, but how far it goes needs legal advice on the actual facts.
- What checks a bad decision? An Adjudicator can review and revise it.
| Properly done | Not properly done |
|---|---|
| Discussing a Scope change with the Client and following its choice | Rejecting an event because the Client has no budget |
| Testing a quotation hard and asking for a revision with reasons | Holding a reply back for Client sign-off beyond the time allowed |
| Telling the Client what events are likely to cost | Assessing at a figure the Client set in advance |
What to do, step by step
- Answer each decision on its merits. Name the test that applies and why it is met.
- Protect your deadlines first. The eight weeks to notify under 61.3 and the four weeks to refer under W1 keep running while you are suspicious.
- Keep records of any remark suggesting the Client decided. Record what was said and who said it.
- Ask for reasons. A refusal of acceptance should give enough detail for you to put it right (13.4).
- Raise it calmly at senior level as a question about how the process is running.
- Refer it if needed. An adjudication does not require a finding of bias, only that the decision was wrong.
What to record
- The decision, its date and the clause it relies on.
- Anything referring to the Client's budget or instructions.
- Your request for reasons and the reply.
- The working behind any assessment, or the lack of it.
What not to do
- Do not allege bad faith without advice. It is serious and can damage your own case.
- Do not let suspicion delay a notice or referral.
- Do not make it personal. Dispute the numbers and the reasoning.
When to get help
Speak to your commercial manager as soon as a pattern appears, and take legal advice before any allegation. A planner can test an assessment against the Accepted Programme.
Example
A Project Manager rejects a quotation and issues their own assessment, with no working shown. The contractor notices it matches the Client's remaining contingency exactly. It does not allege bias. It asks for the working, receives none, and refers the assessment, arguing from the numbers.
A way to put it: "Your reply of 3 June gave no reason from clause 61.4. Please confirm which reason you rely on. We are treating your reply as a decision under the contract and reserve our position."
Related guides
- The NEC Project Manager
- Mutual trust and co-operation
- Adjudication under NEC
- Time limits for NEC disputes
This guide is general information, not legal advice. Check it against your contract.
