If you're the Subcontractor on an NEC4 job, your programme runs on the same clauses as the main Contractor's. That's the easy part. The hard part is that your programme only protects you if it actually makes it into the Contractor's own Accepted Programme, and your compensation-event clock can run out weeks before you'd expect, because it starts from when you became aware, not from when the main contract's version of the same clock starts.

This piece covers what's genuinely different about being the Subcontractor rather than the Contractor: the same clause numbers, a different risk profile. For the mechanics of building a programme that clears clause 31.3 in the first place, our Clause 31 walkthrough and free health-check tool below cover the schedule-quality groundwork either party needs.

Check your programme's schedule quality first, free

Before you submit anything to your Contractor, run your .xer or .xml through our free checker: negative float, broken logic and hard constraints are as much a problem in a subcontract programme as a main one. Nothing is uploaded, stored or shared.

Run the free schedule check →

Step 1: Read Your Own Contract Data, Not the Main Contract's

Start here, before you open P6. NEC4's Engineering and Construction Subcontract (ECS) shares its clause numbering with the main Engineering and Construction Contract (ECC): clauses 31, 32, 50 and 61 mean the same thing in both. What doesn't automatically carry across is the timing. The period for your first programme submission, the interval between revised programmes, and your own compensation-event notification period are all set out in your subcontract's own Contract Data Part 1, and there's no rule that says they match the main contract's periods. Read your subcontract's Contract Data before you assume anything about deadlines, and calendar every date it sets independently of whatever you know about the main contract's timetable.

Step 2: Build Your Programme to Trace Into the Contractor's WBS

Structure your programme's WBS so it maps cleanly onto the sections of the Contractor's Works Information or Scope that describe your package, the same principle a main Contractor applies against the Employer's Scope. Add a distinct Activity Code identifying your own subcontract package, so your activities are traceable as a discrete, extractable set within whatever larger programme software the Contractor manages centrally, whether that's their own P6 environment or a schedule they rebuild from what you submit. A Subcontractor's programme that can be lifted cleanly into someone else's file is far more likely to actually get used in it.

Step 3: Protect Your Own Time Risk Allowances and Terminal Float

The float rules run the same way down the contractual chain as they do at main contract level. Total float is generally available on a first-come, first-served basis, so either party's compensation events can absorb it. Time risk allowances and terminal float are different: both are owned by whichever party built them into the programme, and neither is available to be used up by someone else's compensation event. As the Subcontractor, that means your own time risk allowances and your own terminal float (the gap between your planned completion and your subcontract's Completion Date) belong to you, not to the Contractor, and not to the Contractor's own client. Model them as their own identifiable activities or milestones, distinctly coded, exactly as covered in our Clause 31 walkthrough, so the protection is visible in the file and not just understood in your head.

Step 4: Get Proof Your Programme Is Actually in the Accepted Programme

This is the step that catches more subcontractors than any P6 setting. Under the main contract, the Accepted Programme has to show the work of Subcontractors, but that only protects you if the Contractor's submission to the Project Manager genuinely reflects the detail of your own programme, not just a summary bar with your package name on it. If a delay traces back to your work and the Accepted Programme never showed the logic and dates that explain it, the Project Manager assesses the compensation event against what the Accepted Programme actually says, not against what you know you submitted. A Contractor who tracks your progress internally but never folds your detail into their own Accepted Programme can lose the time entitlement for both of you, and it's your delay that gets blamed.

Don't assume this happens automatically. Ask for it in writing: request written confirmation, or better, an extract of the current Accepted Programme showing your package's activities, at every programme revision, and keep the dated correspondence. If your activities aren't visibly there, that's a live risk to raise immediately, not something to discover during a dispute.

Step 5: Track Your Own Compensation Event Clock, Independently

Clause 61.3 bars a compensation event claim if it isn't notified within eight weeks of becoming aware the event happened, unless the event originates from an instruction, notification, certificate or changed decision from the party administering your contract. That eight-week clock runs from when you, the Subcontractor, became aware, which is very often earlier than when the Contractor becomes aware of the equivalent impact on their own contract with their client. Don't wait for the Contractor's paperwork to prompt you. The moment you're aware something has affected your programme, record the date and log a notebook entry against the affected activity in your own P6 file, so you have a defensible, contemporaneous record of when your own clock started, independent of anyone else's.

Step 6: Know What an Unaccepted Programme Costs You in Cash

This is a leverage point worth understanding in both directions. Where no accepted programme is identified, the party administering the contract can retain one quarter of the Price for Work Done to Date until an acceptable programme is in place. As the Subcontractor, that means a programme sitting in limbo isn't just a compliance gap, it can directly delay a quarter of your own payment. Keep programme submission ahead of your payment cycle, not squeezed against it, and don't let a slow acceptance process from the Contractor become your own cash-flow problem by default: chase acceptance in writing, and know that the retention is a real, contractual number if it isn't resolved.

Step 7: Check Your Subcontract Is Genuinely Back-to-Back Before You Rely on It

A Contractor generally needs the Project Manager's acceptance for subcontract conditions that aren't a straightforward NEC contract on matching terms, which pushes most subcontracts toward the same NEC family. "Same family" is not the same as "identical terms", though, and true back-to-back alignment between the main contract and a subcontract is rare in practice. Check these four points at the start of the relationship, not after a dispute:

Check What to look for
Compensation event categories Does your subcontract's list of compensation events match the main contract's, or does it exclude anything the main contract would have covered?
Assessment basis Are your CEs assessed on the same basis (defined cost plus fee, or another method) as the main contract, or could a difference leave a gap between what you can recover and what the Contractor can recover above you?
Notification and response timescales Are your periods (first programme, revisions, CE notification) the same length as the main contract's, shorter, or longer? A shorter subcontract period is common and easy to miss if you're used to the main contract's numbers.
Programme content requirements Does your subcontract ask for the same clause 31.2 content the main contract does, or has something been dropped or added in the Z clauses?

Where you find a gap, it isn't necessarily a problem to fix immediately, but it is risk that should be identified and priced or managed consciously, rather than discovered for the first time when a claim depends on it.

Where People Get This Wrong

The most common mistake isn't a badly built programme. It's a well-built one that stays a Subcontractor's private document instead of becoming part of the Contractor's own Accepted Programme. The clause exists to protect Subcontractor time and cost, but the clause protects what the Accepted Programme actually shows, not what you know you sent. If you've never asked to see your own package reflected in the current Accepted Programme, that's the single highest-value check to start doing at every revision from here on.

The second common mistake is running your compensation-event clock off the Contractor's timetable instead of your own. Your eight weeks start when you became aware, on your own contract, and nobody upstream is going to notify you when that clock is closing.

When to Bring in a Second Opinion

If you're not confident your programme submissions are actually landing inside the Contractor's Accepted Programme, or your subcontract's periods and categories haven't been checked against the main contract, that's worth an independent read before it becomes a dispute rather than during one. Planned's NEC4 Programme Acceptance Review covers clause 31.2 and 31.3 acceptance-readiness for contractors and subcontractors alike, with a written recommendation delivered inside the reply period.

Book a Free Consultation if you'd like a senior planner to look at your subcontract programme and its route into the Accepted Programme, or run the free schedule check first to catch the basic quality issues yourself.

Frequently Asked Questions

Does an NEC4 subcontractor have the same programme obligations as the main contractor?

The clause numbers are the same, because the Engineering and Construction Subcontract shares its numbering with the main Engineering and Construction Contract. The practical obligations differ in timing (set independently in your own Contract Data) and in risk, because a subcontractor's protection depends on their programme detail actually being reflected in the Contractor's own Accepted Programme.

What happens if my programme detail isn't included in the Contractor's Accepted Programme?

A compensation event is assessed against what the Accepted Programme shows, not against what you separately submitted. If your package's activities and logic aren't visible in the version the Contractor submits to the Project Manager, a delay that's genuinely yours to be compensated for can go unrecognised, because the record that decides it doesn't show your detail.

How long do I have to notify a compensation event as a subcontractor?

Clause 61.3 sets an eight-week bar from when you became aware the event happened, unless it originates from an instruction, notification, certificate or changed decision, in which case notification happens at that point instead. That eight weeks runs on your own awareness, independently of when the main contractor becomes aware of any equivalent impact on their contract.

What happens if there's no accepted subcontract programme in place?

Where no accepted programme is identified, the party administering the contract can retain one quarter of the Price for Work Done to Date until an acceptable one is submitted and accepted. It's a direct cash-flow consequence, not just a compliance point.

Is a subcontract automatically back-to-back with the main NEC4 contract?

Not automatically. A Contractor generally needs the Project Manager's acceptance for subcontract conditions that depart from a matching NEC contract, which pushes most subcontracts toward the same family of terms, but genuine back-to-back alignment on compensation event categories, assessment basis and timescales is still worth checking explicitly rather than assuming.

About Planned Ltd

Planned Ltd is a project planning and controls consultancy for construction and infrastructure: planning and scheduling, project controls, delay and claims, schedule assurance, and Primavera systems and training.

Written by our planning team and reviewed by the Director.