7 Common Pitfalls When Managing Subcontractor Delay Under NEC4

Subcontractor delay is one of the quickest ways for a contractor to lose control of delivery and lose control of narrative, especially on NEC4 projects where the programme, records, and mitigation behaviour are constantly under scrutiny.

A key reality: even when the root cause sits in the supply chain, the prime contractor is accountable for managing it.

The Project Manager will judge you on three things:

• do you have a credible, logic-linked plan that shows dependencies and interfaces?

• did you act early and reasonably to reduce the impact?

• can you evidence what happened, what you did, and what decisions were needed?

If you can’t show those, your position becomes harder to explain and harder to defend.

Here are seven pitfalls that repeatedly undermine contractors when subcontractors slip - and the practical controls that prevent the situation turning into an entitlement and margin problem.

1. Subcontractor slippage is not modelled in the logic network

What it looks like

The subcontract scope is a single bar or a milestone. The real chain—submittals, procurement, access, install, test, handover—is missing.

Why it hurts

If you can’t show the impact pathway, you can’t show what the delay actually drove. You end up with narrative, not cause-and-effect.

Fix

Model the subcontract as a controllable chain and tie it into the main plan at real interfaces. Minimum standard: key gates + logic ties + handover points + critical hold points.

2. “It’s their problem” behaviour

What it looks like

You escalate and wait. Recovery actions are not owned, dated, or programmed.

Why it hurts

NEC governance rewards active management. Passive posture turns supply chain slip into “contractor-managed risk”.

Fix

Run subcontractor delay like a controlled incident: clear recovery requirements, action owners, decision-by dates, and mitigation reflected in the programme and narrative.

3. Blending causes so the story becomes “the job is hard”

What it looks like

Subcontract underperformance, late design, access restrictions, permits, outages - mixed into one combined delay story.

Why it hurts

Blending makes it difficult to demonstrate what actually drove completion. It invites the PM to treat delay as shared or contractor-driven.

Fix

Split causes early (subcontract performance vs employer constraints vs third-party constraints), then test each against the critical path. Only keep true completion drivers in formal reporting.

4. Weak supply chain “flow-down” controls

What it looks like

Subcontract updates don’t align to your reporting cycle. Their commitments aren’t recorded. Their plan isn’t logic-linked to yours.

Why it hurts

You can’t prove you managed and mitigated reasonably if your supply chain record is weak. You also lose leverage with the subcontractor.

Fix

Align subcontractor reporting to your data date cadence. Require a logic-linked micro-programme (or at least gate plan) and run a subcontract delay register with evidence references.

5. “Accelerate” with no executable recovery model

What it looks like

Promises to add labour or work weekends, but no resequence, no access/logistics changes, and no clear constraints management.

Why it hurts

Mitigation only counts if it’s executable. If it’s not planned and evidenced, it’s just reassurance.

Fix

Produce 2–3 real recovery options, each with constraints, resources, and programme effect shown. Programme the mitigation so it’s visible and reviewable.

6. Making the programme optimistic to hide slippage

What it looks like

Remaining durations untouched, constraints used to force dates, progress overstated.

Why it hurts

Once programme credibility collapses, every future discussion (progress, change, time impact) becomes harder and slower.

Fix

Keep the programme honest: strict data date discipline, realistic remaining durations, minimal constraints with reasons, and a clear narrative of mitigation and forecast.

7. No decision-grade pack for the PM

What it looks like

Long emails and meeting frustration, but no structured summary, no programme extracts, no clear decisions required.

Why it hurts

PMs act on structured options and clear decision requests. If you don’t present the decision, the project drifts and the position weakens.

Fix

Use a repeatable “Subcontractor Delay Decision Pack”:

• summary (what happened, dates, impacted chain, forecast)

• programme extract (critical chain + interfaces)

• mitigation options (with pros/cons and decision-by dates)

• evidence index (instructions, minutes, resource plans, procurement proofs)

If you want subcontractor delay management to be fast and defensible:

• give every interface and gate an ID that appears in programme, minutes, and registers

• align supply chain reporting to the same data date and revision rhythm as the main programme

That is how you stay in control when the job gets busy: not more meetings - better structure.