
On this page
- Why groundworks sits on the critical path
- Ground conditions that were not priced or programmed
- Utilities, diversions and live services
- Approvals, adoption and authority comments
- Package interfaces and enabling handover
- Typical delay drivers and early controls
- Every delay risk needs an owner before mobilisation
- Float should sit around the interfaces, not the easy work
- Early warnings protect the project only if they change behaviour
- What to do before the digger arrives
Why groundworks sits on the critical path
Groundworks delays rarely stay inside the groundworks package. Late formation, drainage or access works push frame, brickwork, plot release and often adoption milestones. Understanding the usual causes helps developers and project managers protect programme before mobilisation — not only after a delay notice arrives.
For duration expectations rather than delay causes, see Groundworks Programme: How Long Should a Commercial Groundworks Package Take?. For sequencing language, see new-build groundworks sequence.
Ground conditions that were not priced or programmed
Soft spots, obstructions, groundwater, contamination and made ground still account for a large share of early-works overruns. Where investigation is limited, the programme is built on assumptions. When those assumptions fail, excavation slows, temporary works change and design may need revisiting.
Mitigation starts with proportionate GI and a clear commercial approach to residual risk — see ground investigation services and ground conditions risk explained.
Utilities, diversions and live services
Uncharted services, late diversion lead-ins, undertaker response times and protection constraints regularly stop excavation. Trial holes and early diversion planning reduce — but do not eliminate — this risk.
The utility diversions for development sites guide covers the commercial and programme interfaces in more detail.
Approvals, adoption and authority comments
S278, S38 and S104 processes, Building Control inspections and water company comments can hold works even when plant is available. Incomplete submissions and late design changes are common causes.
See The S38 & S104 Programme Explained and S278 agreements explained for adoption and highway programme interfaces.
Package interfaces and enabling handover
Split packages create delay when formation ownership, site condition at handover, temporary drainage and access rights are unclear. Enabling works overruns put the main groundworks team on standby; unclear interfaces create disputes about who digs what.
See enabling works before construction and early contractor involvement.
Typical delay drivers and early controls
| Delay driver | Why it bites | Early control |
|---|---|---|
| Incomplete GI | Method, temporary works and disposal change mid-dig | Proportionate investigation before tender |
| Utility unknowns | Stops excavation; diversion lead-ins stretch | PAS 128 surveys, trial holes, early undertaker engagement |
| Adoption / highway comments | Rework of drainage or access design | Submit early; freeze design status before mobilisation |
| Shared access / logistics | Plant idle time; muck-away bottlenecks | Logistics plan and phased access rights |
| Design late or incomplete | Hold points, RFIs and variations | Clear “for construction” status and RFI discipline |
| Weather / groundwater | Excavation instability and stand-down | Contingency in programme; dewatering strategy where relevant |
Every delay risk needs an owner before mobilisation
Groundworks delays become harder to manage when risks are known but ownerless. A utility diversion, drainage approval, access route, inspection hold point or unresolved design query may be visible in meetings, but if nobody owns the next action it will still block the programme.
Risk ownership should be practical rather than ceremonial. The owner needs authority to chase, instruct, decide or escalate. A named person with no ability to move the issue is only a reporting point, not a control.
Before mobilisation, the project team should convert the risk register into a delivery list: what could delay the groundworks, what decision or evidence closes it, who owns that step, and by when. That is far more useful than a generic high-medium-low table.
Float should sit around the interfaces, not the easy work
Groundworks programmes often show neat activity durations for excavation, drainage and foundations, but the real uncertainty sits around the interfaces. Surveys, approvals, undertaker attendance, inspections, testing and handovers need realistic float.
Adding float to the wrong place does little. A generous allowance for excavation does not solve a late utility diversion. A longer drainage duration does not solve an unapproved outfall. The float needs to sit where the uncertainty lives.
A useful programme makes those interface allowances visible. It lets the team see whether a delay has consumed float or moved the critical path, rather than discovering the effect when the next trade is already booked.
Early warnings protect the project only if they change behaviour
Many groundworks delays are predictable before they are critical. The team may know a survey is late, a drawing is unresolved or an inspection route is unclear. The value of an early warning is that it changes the next action, not that it appears in a report.
Good early warnings are specific: what is at risk, what work face is affected, what decision is needed, who owns it and what date matters. Vague warnings about possible delay rarely drive the urgency needed to protect the programme.
Clients and principal contractors can encourage better warnings by responding constructively. If every warning becomes a blame exercise, subcontractors learn to wait until the issue is undeniable. That is usually too late for cheap mitigation.
What to do before the digger arrives
Pre-start programme readiness
- Confirm GI and utility information status
- Agree package interfaces and formation ownership in writing
- Identify authority approvals on the critical path
- Lock access, working hours and haul routes
- Agree inspection hold points that affect following trades
- Build contingency where residual ground or utility risk remains
If you are planning a commercial package and want a second view on sequencing risk, contact the team with drawings and target dates.
Related services & guides
Continue into the operational pages that sit behind this guidance.
Protecting a groundworks programme on a live scheme?
Share drawings, surveys and target dates and we can discuss sequencing, interfaces and where early clarity usually protects the critical path.
Related insights
More guidance from the Mainline knowledge centre.
Groundworks17 min readGroundworks Programme: How Long Should a Commercial Groundworks Package Take?
A commercial breakdown of groundworks programme durations — mobilisation, earthworks, drainage, foundations and external works — what drives the timeline and what causes slippage.
Last reviewed August 2026Read article
Site Preparation16 min readEnabling Works Before Construction: What Should Be Completed Before the Main Groundworks Package Starts?
What enabling works typically include, where they stop and groundworks begin, and what procurement teams should complete before the main package mobilises.
Last reviewed August 2026Read article
Groundworks18 min readPlanning a Groundworks Package for a Commercial Development
What a commercial groundworks package includes, how to brief and procure it, the information contractors need to price accurately, and where early planning changes the commercial outcome.
Last reviewed August 2026Read article