How Poor Sequencing Creates Groundworks Delays

Many groundworks delays are caused by doing the right work in the wrong order: plots ahead of shared drainage, permanent roads before temporary access is resolved, or inspections booked before formation is ready. Plant stays on site while interfaces catch up — which looks like ‘slow groundworks’ from outside.

For a broad delay catalogue, see Common Reasons Groundworks Projects Are Delayed. This article focuses on sequencing mistakes. For a standard sequence language, see new-build groundworks sequence.

On housing sites, infrastructure often needs enough lead to give plots dry connections and usable access — but not so much lead that plots sit idle waiting for adoption milestones that do not block foundations. The balance is site-specific; plotworks explained and S38 & S104 programme help frame the interfaces.

A groundworks sequence is not just a list of activities in the order someone would like them to happen. It is a map of dependencies. If drainage needs an outfall, if plot foundations need inspected formation, or if wagons need a temporary road, those dependencies should sit visibly in the programme before dates are committed.

The common failure is to programme visible production but not the enabling condition behind it. A line may say 'start plot foundations', but the real dependency is access, setting out, design status, service clearance, inspection availability and drainage strategy. If one of those is missing, the activity starts in name only.

Dependency logic should be written in plain project language, not hidden in planning software. Site managers, commercial teams and subcontractors all need to understand what must be true before the next activity starts. That shared understanding is what prevents optimistic dates becoming arguments.

The best programmes make the stop/go points obvious. They show where an approval, survey, inspection, connection or handover gates the next package. That does not remove delay risk, but it makes the risk manageable before the site is waiting on it.

On housing sites, sequencing should be planned around plot release rather than groundworks productivity alone. Completing the biggest area of excavation may look efficient, but it may not release the homes that the build programme, sales strategy or follow-on trades need first.

Plot release usually depends on more than foundations. Access, plot drainage, service entries, inspection records, scaffold room, material routes and protection from later infrastructure works can all decide whether the next trade can start. If those items are not part of the release definition, the programme can show progress while the build team still cannot use the plot.

This is why plotworks planning often needs to be separated from general infrastructure planning. Estate roads and sewers may be best sequenced by corridor, adoption milestone or utility interface. Plotworks may be better sequenced by build wave, house type or handover gate.

A good sequence reconciles both views. It gives infrastructure enough lead to support plots, but it does not let infrastructure logic bury the plot release priorities that create value for the housebuilder.

Poor sequencing is expensive because it creates damage and rework as well as waiting time. Completed drainage may be crossed by later haul routes. Finished formation may be softened by uncontrolled water. Temporary access may be removed before peak wagon movements are finished. Each problem can look small until it repeats across a site.

Protection should be part of the sequence decision. If an activity has to happen early, the programme should explain how the completed work will be protected while later packages continue. Otherwise the project saves time in one week and spends more repairing the consequences later.

Rework also creates commercial uncertainty. If a completed area is damaged by follow-on access or another package, the question becomes who pays. A clearer sequence reduces that argument because it defines when an area is handed over, what condition it was in, and what restrictions apply afterwards.

The same logic applies to inspections. Backfilling or covering work before the inspection route is complete may appear to protect progress, but it can trigger opening-up, testing or evidence disputes later. A sequence that respects hold points is usually cheaper than one that tries to outrun them.

Utility companies, highway authorities, Building Control, warranty providers and adoption bodies do not always move at the pace of the groundworks programme. If their input is needed before work can proceed, the programme needs float and a named owner for the interface.

The most fragile programmes assume that external approvals will arrive exactly when needed. That may happen, but it is not a planning strategy. If a diversion, S278 comment, drainage approval or inspection slot is critical, the programme should show when the request is made and who is responsible for chasing it.

External interfaces are especially awkward because the groundworks contractor may not control them. The client or principal contractor may own the relationship, while the subcontractor carries the site delay. This needs to be recognised in the contract and programme rather than treated as a site-level inconvenience.

Where external interfaces are uncertain, it can be sensible to plan alternative work faces. That way the site is not wholly dependent on one approval or attendance slot. The alternative must be real, though: moving plant to another blocked area is not mitigation.

Enabling works that create access, welfare and utility protection must finish before peak dig productivity is assumed — see Enabling Works Before Construction. Building Control and adoption inspections must sit on the programme as hold points, not afterthoughts.

For duration expectations, see Groundworks Programme Duration or contact the team.