Project Manager replied late: is that a compensation event?
A late reply can be a compensation event under 60.1(6), but only a real effect on cost or dates earns you anything. Here is what to check and do.
On this page
The Project Manager has come back to you after the contract's reply period. You want to know whether that is automatically a compensation event, and whether it is worth doing anything about.
The short answer
On the wording, yes, if the contract required a reply and the period was missed (clause 60.1(6)). But the Prices and dates only change if the lateness had an effect, so the date alone does not decide it. Record both dates, check for an agreed extension, measure the effect, and notify within eight weeks if there is one. NEC3 and NEC4 ECC are effectively the same here.
What to do, step by step
- Note the dates. The due date, and the day the reply actually arrived or that nothing has.
- Look for an extension. Clause 13.5 permits one only when both sides agree ahead of the due date. If one was agreed in time, there is no late reply.
- Measure the effect. Did work wait? Did a price or delivery slot lapse? Did planned Completion move?
- If there is an effect, notify. Clause 61.3 applies, since silence is not an instruction or decision. The count starts when you realised the reply had been missed. The NEC4 subcontract allows seven weeks, not eight.
- If there is no effect, log it. A pattern can help in later talks with the Client.
- Use a stronger route if one exists. See the table.
| Reply you are waiting for | Normal NEC4 ECC period | Quicker route? |
|---|---|---|
| Response to your compensation event notice | One week (61.4) | Yes: give a failure notice, and after two further weeks it counts as an event |
| Response to your quotation | Two weeks (62.3) | Yes: failure notice, then accepted two weeks on |
| The Project Manager's own assessment | The time you had to quote (64.3) | Yes: failure notice, and your quotation counts as accepted two weeks later (64.4) |
| A programme sent for acceptance | Two weeks (31.3) | NEC4 only, through deemed acceptance |
| Any other submission or request for a reply | The period for reply (13.3, 13.4) | No. Clause 60.1(6) is your main remedy |
| Something the contract needs no reply to | None | Clause 60.1(6) does not apply |
If one of the quicker routes in the table fits, take it first, since it does not require proof of effect. Periods under the NEC4 subcontract are longer in places.
What to record
- Issue date, due date and actual reply date.
- What was waiting on the reply, and what it cost.
- Any request for more information that the Project Manager made, which may explain a timely rejection instead.
- Programme updates showing movement.
What not to do
- Do not notify every late reply. It strains relations and rarely pays.
- Do not say "we will raise it later". That can quietly become a missed time bar.
- Do not assume lateness alone creates money. If the reply did not cause the loss, there is little to assess.
- Do not forget that a reply asking for more information is still a reply.
When to get help
Ask a commercial manager when you are unsure whether the effect justifies a notice, and a planner when the critical path argument is contested. If the Project Manager says it made no difference, your records are the answer.
Example
A fictional Option B culvert job with a two-week reply period. You send a revised crane lifting plan for acceptance on 5 May. The reply is due on 19 May and arrives on 26 May.
- The lifts were not planned until early July: the event exists but nothing changes.
- The first lift was booked for 20 May on the critical path: about a week's delay, less any float, plus time-related cost and Fee.
- Your crane could not mobilise until 28 May regardless: the reply did not cause the loss.
Related guides
- Late reply to a communication: 60.1(6)
- Failure to reply: treated acceptance
- Period for reply explained
- Time bars explained
This guide is general information, not legal advice. Check it against your contract.
