Your design has been rejected by the Project Manager: next steps
How to sort valid from invalid reasons for a refused NEC design, what clocks start, and when a rejection becomes a compensation event.
On this page
The Project Manager (the person who runs the contract for the Client) has refused to accept your design. What you do next depends on the reason given.
The short answer
Start with the reason given. Where the Project Manager says the design breaks the Scope (the document setting out what you must deliver) or the applicable law, or lacks information needed to assess it, you fix and resubmit at your own expense. For any other reason, the refusal is a compensation event under 60.1(9). Either way, the affected work waits for acceptance. The rules are identical in NEC4 and NEC3 (clauses 21.2, 13.4 and 60.1(9)).
What to do, step by step
- Note the date. Two periods begin: resubmission within the period for reply in Contract Data (13.4), and eight weeks to notify an event once aware (61.3).
- Hold the affected work (21.2). If you build ahead and the design then changes, the rework is on you.
- Sort each comment using the table below. One reply can mix valid and invalid reasons.
- Reply in writing, as separate communications if needed: resubmit, ask for clearer reasons, notify, or all three. NEC4 requires reasons detailed enough for you to correct the matter.
- Give an early warning (15.1; 16.1 in NEC3) and update your programme if time is at risk.
Sorting the reason you were given
| What was said | Valid? | What follows |
|---|---|---|
| Does not meet a stated Scope section | Yes, if correct | Correct and resubmit, no event |
| Breaks a stated law or regulation | Yes, if correct | Same |
| Cannot assess without a calculation or survey | Yes (13.4) | Supply what is reasonably needed |
| Client would rather have another solution | No | Event under 60.1(9); or ask for an instruction changing the Scope |
| Expensive to maintain, though the Scope says nothing on it | No | Event under 60.1(9) |
| Drawing marked up, no reason stated | Unclear | Ask which of the two grounds in 21.2 applies to each comment |
| Silence | A separate problem | Event under 60.1(6) after the reply period passes |
| Accepted before, then withdrawn | A separate problem | Event under 60.1(8) |
What to record
- The rejection, its date and the stated reason.
- Your submission contents, checked against the Scope's list of required items.
- Your questions and the answers.
- The time lost on affected activities.
What not to do
- Do not quietly redraw to the Project Manager's taste. If you amend and resubmit without recording your position, the change looks like your own decision, and changes to your design made at your own request are excluded from 60.1(1).
- Do not send a package missing a required calculation. That gives the Project Manager a good reason.
- Do not accept "just a comment" as an answer. Ask for acceptance or a statement of reasons.
When to get help
If the Client really wants something different, the proper route is an instruction under 14.3, which counts as a compensation event under 60.1(1). Involve your commercial manager so it is priced before anyone commits. Seek advice if a repeated rejection threatens a Key Date.
Example
A fictional sports hall canopy on Option A is designed in aluminium to the loads and fire rating in the Scope. The Project Manager refuses it because the Client's facilities team likes steel. On day 3 you ask which Scope requirement the canopy fails. On day 6 the Project Manager concedes there is none and issues an instruction for steel, which you price before building anything.
Wording that works: "Clause 21.2 allows two grounds for refusing our design, and we cannot see which Scope requirement or law it fails. If the Client wants another solution, please instruct it."
Related guides
- Contractor's design
- Compensation events in plain English
- The Project Manager has not replied to our compensation event notice
- Period for reply explained
This guide is general information, not legal advice. Check it against your contract.
