My NEC subcontractor is behind programme: what the main contractor should do
How a main contractor should respond when an NEC subcontractor falls behind programme: protect your main contract dates and your rights against them.
On this page
Your subcontractor is falling behind. The drawings say one thing, the site says another, and your own Completion Date or a Key Date to the Client is at risk. This guide is written for the main Contractor. The Subcontractor's side is covered in the main contractor's delays are costing me time.
The short answer
Establish why they are late before you decide what to do. If the delay is the subcontractor's own, you have rights and should use them in writing, early. If any of it comes from you, the Client or another trade, you may owe the Subcontractor time or money, and you need to know that before you issue a threatening letter. Under clause 26 of the main ECC you remain responsible to the Client for subcontracted work either way.
What to do, step by step
- Compare the facts to the programme. Take the Subcontractor's latest programme, the progress record and the site. Check what should be finished, what is, and which activities are driving the finish. See clause 31 programme checklist.
- Check whose programme it is. Look at your subcontract to see which programme is the baseline, whether you accepted it, and whether it complied with the requirements in the Subcontract Data. Under the unamended NEC4 subcontract (ECS) you have three weeks to accept a programme or give a reason, and if you stay silent and the Subcontractor notifies the failure, it is treated as accepted after a further two weeks. See why NEC programmes are not accepted.
- Look for your own part in the delay. Late access, late information, other trades in the way, changes to Scope. Check whether the Subcontractor gave early warning or notified an event.
- Raise it formally. Give an early warning if you have not, and call an early warning meeting where the subcontract provides. See early warning register template.
- Ask for a revised programme showing how and when the Subcontractor will recover, using the clause and period in your subcontract. If you decline to accept it, the reason has to be one of the four in clause 31.3: the plans cannot practicably be carried out, required information is missing, the programme does not realistically represent the Subcontractor's plans, or it does not comply with the Subcontract Scope. See revised programme submission timeline.
- Agree recovery actions. Extra resource, shifts, resequencing or reordered materials. Confirm in writing who pays, so it is not later said you instructed an acceleration.
- Protect your main contract position. Check whether you need to notify the Client of a delay, or give your own early warning.
- Escalate if recovery does not follow. Review the termination and default provisions in your subcontract, and any contractual remedies for delay. Take legal advice before you issue any notice of default or termination.
What to record
- The baseline programme and every revision, with the date you accepted or rejected each.
- Progress records, labour returns and photos from site.
- All early warnings, meeting notes and the agreed actions.
- Any instructions you gave that could have affected their sequence.
- The knock-on effect on your own programme and dates.
- Any delay damages provisions in the subcontract, and how you calculated any sum.
What not to do
- Do not issue a default notice before you know whether you caused part of the delay.
- Do not instruct acceleration informally and then refuse to pay for it.
- Do not simply reject their programme without giving one of the four reasons the contract allows. A reason outside the contract can itself be a compensation event.
- Do not wait until the end of the job to raise delay damages.
- Do not ignore that you also owe the Client the finished Works.
When to get help
Bring in a planner when the delay is complex, when several subcontractors are interacting, or when you need to separate the Subcontractor's delay from yours. See delay analysis basics. Involve your commercial manager before you promise any money or threaten any remedy. Take legal advice before you terminate, withhold money on the ground of delay, or apply damages.
Example
A Subcontractor has a Key Date for completing a chamber so that the Contractor can start testing. Two weeks before it, only half the work is done. The Contractor checks the records: access was late by four days because of its own earlier overrun. It notifies the issue, agrees that the Subcontractor will have those four days, and asks for a revised programme showing the remaining delay and a recovery plan. The remaining delay is the Subcontractor's own, and the Contractor writes to say so.
Related guides
- Delay analysis basics
- Revised programme submission timeline
- Early warning register template
- Preparing a subcontract package
This guide is general information, not legal advice. Check it against your contract.
