Late drawings: can you claim a compensation event?
Whether late Issued For Construction drawings give you a compensation event depends on who was meant to supply them and what the programme says.
On this page
The drawings you need to start work have not arrived, and you want to know whether the delay is something the Client pays for. NEC has no event called "late drawings", so you have to fit your facts to one that exists.
The short answer
It depends on who was supposed to provide them and what the Accepted Programme (the programme the Project Manager has accepted) shows. Late drawings usually count when the Client, or a designer working for it, owed them and they arrived after the programme date. If your own designer was late, they are not. Work out which event fits, then notify within the time limit.
What to do, step by step
- Find the day you knew the date was missed. Under NEC4 clause 61.3 the limit is eight weeks from when you became aware the event had happened, or seven in the NEC4 subcontract. NEC3 is worded around awareness of the event itself, so its clock can start sooner.
- Look at the Scope. It allocates design, not the title block on a drawing. See who was meant to provide them.
- Pick the matching event.
| Facts | Event |
|---|---|
| The Client had to provide the drawings, and they came after the programme date | 60.1(3) |
| A separate designer counted as Others missed the times on the programme | 60.1(5) |
| Drawings arrived on time but changed the requirement, once instructed | 60.1(1) |
| A reply you were owed under the contract was late | 60.1(6) |
| Another Client breach caused it and nothing else fits | 60.1(18), as a fallback |
| Your own designer slipped for its own reasons | None. The risk is yours |
- Notify even without a price. A notice needs the event and the clause you rely on. Expect an answer from the Project Manager within a week, or two weeks under the NEC4 subcontract.
- Give an early warning too. A warning does not count as a notification, so do both.
- Check the programme. The test is measured against the date on the Accepted Programme, not your preferred date or one noted in minutes. A newer programme that shows a date but was never accepted does not count, so the last accepted one rules. With no date shown for the drawings, 60.1(3) is much harder to run. With no Accepted Programme at all, the Project Manager forms its own view of the time effect.
What to record
- A drawing register showing date needed, date promised and date received.
- The Scope clause allocating design.
- The programme revision and date relied on.
- Where the drawings sat on the critical path, and what site resources were idle.
What not to do
- Do not wait for a perfect price before notifying.
- Do not assume your early warning counted as notice.
- Do not rely on a programme the Project Manager never accepted.
- Do not expect a late warning to wipe out the event. The Project Manager may argue a reduction for it, but not removal.
When to get help
Bring in a commercial manager if the answer depends on the Scope's design split, and a planner if your own work was already behind, since delay is measured on the programme current when you notify. Take legal advice if a large sum depends on a breach argument under 60.1(18).
Example
A fictional Option A medical centre. The Scope says the Client's engineer provides slab drawings, shown on the Accepted Programme for 10 June. They arrive on 1 July. You notify under 60.1(3) on 12 June. Planned Completion moves two weeks, because a re-sequence recovers the third. Forecast cost for staff and cabins is £18,000 plus the Fee.
Because the dividing date is 12 June, nearly all of this is forecast and is not revised later if wrong, so get the quotation right.
Related guides
- Late access to site
- Our own designer is late with drawings
- Time bars explained
- What is an early warning?
This guide is general information, not legal advice. Check it against your contract.
