TL;DR

The NEC4 Project Manager holds significant unilateral powers under the contract, including the ability to change the Scope, assess compensation events, and certify payments—but these powers come with strict timescales and duties.

Common pitfalls include failing to issue early warnings, missing assessment deadlines for compensation events, and not maintaining the Risk Register—all of which can lead to disputes and cost overruns.

Practical, proactive contract administration—not just reactive oversight—is essential to avoid the most frequent PM errors on site.

---

The NEC4 Project Manager: Powers, Duties, and Common Pitfalls

If you work daily with the NEC4 Engineering and Construction Contract (ECC), you already know the Project Manager (PM) is the linchpin of the contract administration system. The PM is not an engineer’s representative or a client’s agent in the traditional sense—they are the single point of control for the contract’s core processes: early warning, compensation events, programme, and payment.

But with great power comes great responsibility—and plenty of room for error. In this post, we’ll strip away the theory and focus on what the PM actually does, where they commonly trip up, and how to avoid those traps on site.

---

What Powers Does the NEC4 Project Manager Have?

The PM’s authority is defined primarily in **clause 14** of the ECC. They act on behalf of the Client, but within the contract’s framework. Key powers include:

**Changing the Scope** (clause 14.3): The PM can instruct changes to the Scope at any time, provided they follow the compensation event procedure.

**Assessing compensation events** (clause 63): The PM assesses the time and cost impact of compensation events, using defined rules for time-risk allowances, fee percentages, and defined cost.

**Certifying payments** (clause 50): The PM certifies the amount due to the Contractor each assessment period, including any retention or early completion bonuses.

**Accepting or rejecting the programme** (clause 31): The PM must decide whether a programme complies with the contract—if not, they can issue a rejection.

**Instructing early warnings** (clause 15): The PM can require the Contractor to give an early warning if they believe one is needed.

**Deciding on disputes** (clause W1/W2): The PM may also have a role in the first stage of dispute resolution, depending on the chosen dispute resolution option.

These powers are not unlimited. The PM must act **impartially** (clause 10.2) and in accordance with the contract. They cannot, for example, unilaterally change the contract price without following the compensation event mechanism.

---

The PM’s Core Duties (and Where They Often Fail)

1. Early Warning – The First Line of Defence

**Clause 15** requires both the PM and the Contractor to give early warnings of any matter that could affect time, cost, or quality. The PM’s duty is to ensure the early warning register is maintained and that meetings are held as needed.

**Common pitfall**: The PM ignores early warnings until they become full-blown issues. For example, a Contractor might flag a potential ground condition change at a weekly progress meeting, but the PM does not formally record it or hold a risk reduction meeting. By the time the issue materialises, the compensation event is already disputed, and the programme is blown.

**Real scenario**: On a highway project, the Contractor warned the PM that a utility diversion was behind schedule. The PM took no action, assuming the Contractor would manage it. The utility delay caused a three-week programme overrun. The PM then rejected the compensation event, claiming the Contractor should have mitigated it. The dispute went to adjudication—and the PM lost because they failed to act on the early warning.

**Action**: Always record early warnings formally, even if you think they’re minor. Use the Risk Register (clause 15.1) and hold risk reduction meetings promptly.

2. Compensation Event Assessment – Timing Is Everything

The PM must assess compensation events within strict timescales. Under **clause 62.3**, the PM has either two weeks (or a period stated in the Contract Data) to assess a notified compensation event. If they miss the deadline, the Contractor’s quotation is treated as accepted.

**Common pitfall**: The PM delays assessment because they’re waiting for more information, or because the project is busy. This can lead to the Contractor’s quotation becoming binding—often with inflated costs.

**Real scenario**: On a building refurb, the Contractor notified a compensation event for additional steelwork. The PM was waiting for a structural engineer’s report and didn’t respond within the two-week period. The Contractor’s quotation for £45,000 was deemed accepted. The PM later discovered the actual cost should have been £28,000—but it was too late.

**Action**: Set calendar reminders for every compensation event notification. If you need more information, request it formally under clause 62.1, and stop the clock. Do not let deadlines slip.

3. Programme Management – Don’t Just File It

The PM must accept or reject the programme within two weeks of submission (clause 31.3). Rejection must be for valid reasons stated in the contract—not because you don’t like the look of it.

**Common pitfall**: The PM accepts a programme that is non-compliant—e.g., missing float, no method statements, or incorrect logic. Later, when a delay occurs, the accepted programme becomes the baseline, and the PM has no grounds to challenge the Contractor’s assessment.

**Action**: Before accepting a programme, check it against the requirements in clause 31.2—especially the order and timing of operations, float, and risk allowances. If it’s wrong, reject it with clear reasons.

4. Payment Certification – Accuracy Matters

Under **clause 50**, the PM certifies the amount due. This includes the Contractor’s application, any retention, and any compensation events that have been implemented.

**Common pitfall**: The PM certifies based on the Contractor’s application without checking it against actual progress or the programme. This can lead to overpayment, which is difficult to recover later.

**Action**: Cross-reference the Contractor’s application with the accepted programme and site records. If you’re unsure about a line item, ask for supporting evidence before certifying.

5. Risk Register – A Living Document

The Risk Register (clause 15.1) must be maintained by the PM. It should record early warnings, their potential effects, and actions to reduce them.

**Common pitfall**: The Risk Register is created at the start of the project and never updated. By month six, it’s irrelevant, and the PM has no basis for making decisions about risk allocation or compensation events.

**Action**: Update the Risk Register after every early warning meeting. Use it as a tool for decision-making, not just a compliance document.

---

Avoiding the Common Pitfalls – Practical Tips

**Use the contract’s time bar provisions to your advantage** – If the Contractor fails to notify a compensation event within eight weeks (clause 61.7), you can reject it. But don’t rely on this as a first line of defence—it’s a safety net, not a strategy.

**Communicate in writing** – The NEC4 is a paper-intensive contract. Every instruction, notification, and assessment should be in writing (clause 13.1). Verbal agreements are a recipe for disputes.

**Train your team** – The PM is often a single person, but the contract administration touches everyone on the project team. Make sure site supervisors understand early warning and compensation event basics.

**Don’t be afraid to seek advice** – If a compensation event is complex, bring in a commercial manager or quantity surveyor early. The two-week assessment clock doesn’t wait.

---

Key Takeaways

The NEC4 Project Manager has broad unilateral powers, but these are balanced by strict duties and timescales—especially for early warnings, compensation events, and programme acceptance.

Common pitfalls include missing assessment deadlines, failing to act on early warnings, and accepting non-compliant programmes—all of which can lead to financial loss and disputes.

Proactive contract administration—maintaining the Risk Register, setting calendar reminders, and checking programme compliance—is the best way to avoid these traps.

Remember: the PM must act impartially and in accordance with the contract. Personal bias or laziness will be exposed in adjudication.

*For more practical NEC4 guidance, explore our other posts in the Contract Admin category.*