Contractor Design Responsibility in Groundworks Projects

This guide explains contractor design responsibility on UK groundworks and infrastructure packages — what it means in practice, how it is allocated under common contract forms, and where ambiguity creates programme delay, variation disputes and adoption failure.

Developers must decide early which elements are contractor-designed, consultant-designed, or approval-dependent on third parties. Relying on the contractor to sort out adoption, utilities and highway comments without a clear matrix is a common source of final-account pain.

Quantity surveyors should price and administer contracts against an explicit design responsibility schedule — not assumptions inferred from generic design-and-build labels.

Procurement managers need employer's requirements, Scope and tender documents that align planning commitments, adoption strategy and design allocation before award.

Project managers must coordinate design submissions, authority approvals, temporary works control and CDM interfaces with the same clarity as physical construction.

Housebuilders on phased estates need to know whether the civils contractor owns detailed drainage and road design or only construction to consultant layouts — plot release depends on it.

Main contractors carrying subcontract design portions need PI cover, warranties and Scope flow-down that match what each party actually designs.

This guide links to NEC vs JCT, Groundworks Tendering, ECI, S38 & S104, S278, Utility Diversions, Drainage Adoption, Attenuation Systems, Ground Conditions, Infrastructure Bonds, Roads & Sewers Contractors and Groundworks Costs.

Contractor design responsibility in UK groundworks sits anywhere from a narrow contractor-designed portion to full design-and-build liability, depending on the contract, scope, and amendments. In practice, the biggest risk is ambiguity: if the employer's requirements, technical approvals, and statutory interfaces are not clearly allocated, the contractor, developer, and design team can all end up arguing over who owns the problem.

Contractor design responsibility means the contractor is responsible for preparing, completing, coordinating, and often warranting the design of specified parts of the works. Under JCT design and build, the contractor designs the works it is required to design, but the unamended form does not automatically make it responsible for the adequacy of all employer-provided design. Under NEC ECC, the contractor designs only the parts of the works the Scope says it must design, and the wording of the Scope is critical.

In groundworks, that can include temporary works, permanent works, drainage layouts, earthworks profiles, pavement build-ups, retaining structures, site-wide levels, attenuation systems, and utility coordination where the contract transfers that risk.

Design responsibility is not the same as obtaining statutory approval. A contractor may design adoptable drainage but the developer may still own S104 agreement execution, bond provision and land rights — see Infrastructure Bonds & Sureties.

A written design responsibility matrix attached to the contract beats generic design-and-build labels in tender documents.

Design and build procurement is common on groundworks-heavy schemes because it creates a single point of responsibility for design completion and construction. That approach can help with programme, buildability, and cost certainty, but only if the employer's requirements are clear enough to define what is included and what remains a developer or consultant risk.

By contrast, a traditional route keeps most design with the employer's consultants, while the contractor builds to the issued design. Even then, groundworks contractors often carry discrete design duties for temporary works, excavation support, piling, shoring, access roads, or specialist systems such as attenuation tanks and drainage components.

Two-stage and ECI routes develop design allocation during Stage 1 before construction commitment — useful when adoption, utilities and ground risk are not frozen at tender.

The Groundworks Tendering Guide supports evaluation of design capability and scope clarity — not only price.

A performance specification defines the outcome rather than prescribing every detail. For groundworks, that often means requirements such as carriageway load capacity, allowable settlement, discharge rates, water quality performance, infiltration limits, adoptable standards, or finished levels rather than a fully drawn solution.

This is useful where the contractor is better placed to engineer the solution, but it also shifts risk. If the spec says the system must achieve a set performance and the contractor designs the means, the contractor may bear the cost of making the design work, unless the contract says otherwise.

Performance specs are common for attenuation systems, pavement design and settlement criteria. Tender returns must state what investigations and assumptions underpin the proposed solution.

Employers should attach minimum information — GI summary, levels, discharge rates, adoption intent — so contractors price performance rather than guess.

Contractors should flag underdefined performance criteria as commercial risk at tender, not discover them at authority comment stage.

Temporary works are the short-term arrangements needed to build the permanent works, such as excavation support, propping, falsework, working platforms, haul roads, temporary drainage, and access arrangements. HSE and BS 5975-based practice make clear that temporary works require careful design, checking, and coordination, even where they will later be removed.

On groundworks projects, temporary works are often the contractor's responsibility unless the employer retains a specialist designer. That includes sequencing and stability during deep excavations, trench support, dewatering interfaces, and platform design for cranes, piling rigs, and plant.

Temporary/permanent overlap creates disputes when haul roads, platforms or support later form part of finished works — define transition and who pays for redesign and checking.

CDM duties require coordination of temporary works with the permanent design. Design responsibility matrix should name temporary works designer, checker and approver.

Permanent works are the parts intended to remain in place for the long term, such as foundations, roads, retaining walls, drainage assets, and completed earthworks. Where the contractor has design responsibility, it must ensure those works satisfy the Scope, statutory requirements, and the relevant adoptable or technical standards.

In groundworks, permanent works design can overlap heavily with civil engineering design, especially where roads, sewers, site levels, earthworks, retaining structures, and drainage are all interdependent. This is where design coordination matters most, because changing one element can affect many others.

Latent ground conditions can force permanent works redesign — contract must state whether that is employer risk, compensation event, or variation.

Contractors should maintain a design coordination register linking earthworks, drainage, roads and structures with revision status and approval milestones.

Drainage responsibility is one of the most disputed areas on development projects. Section 104 adoption is relevant to sewers and related drainage assets intended for adoption by the water company, while assets mainly serving highway drainage, land drainage, or groundwater are not automatically covered in the same way.

Design responsibility should be split clearly between the drainage consultant, contractor, and adopting authority. The contractor may be responsible for construction to an adopted standard, but the employer often retains strategic design risk unless the contract transfers it expressly.

The Drainage Adoption Process guide covers S104 technical approval — contractor design duty should include producing submission-quality details if Scope allocates detailed design.

Highway drainage under S38 may sit with a different approval track than foul and surface water under S104 — integrated design coordination is not optional.

Employers retaining strategic outfall and capacity risk should not imply contractor owns hydraulic redesign when undertaker comments arrive.

Attenuation systems are often at the centre of groundworks design risk because they combine drainage, storage volume, maintenance access, structural loading, and adoption considerations. Recent guidance has expanded the practicality of adopting certain below-ground attenuation forms, including arch-shaped structures, provided the design satisfies the relevant standards and water company requirements.

If the contractor is required to design the attenuation system, it must prove hydraulic capacity, cleaning access, groundwater protection, and compatibility with any highway loading or adopted asset requirements. If those requirements are only partly defined, disputes often arise over whether the contractor was pricing a concept or a finished adoptable solution.

Read Attenuation Systems for Developers for planning, adoption and maintenance interfaces that should appear in the design brief.

Performance specs for discharge rate and storage without maintenance access detail are a common dispute trigger.

Roads and sewers are usually split between highway and drainage regimes, which creates a classic responsibility trap on mixed-use or housing schemes. Section 38 and Section 278 works affect adoptable roads and works in the highway, while Section 104 governs sewer adoption for qualifying drainage assets.

The contractor may be asked to design and build all or part of the roads and sewers package, but the developer still needs the technical approvals, land rights, programme coordination, and adoption strategy aligned from the outset. A common problem is assuming a drainage layout approved in principle will also satisfy road levels, services, and adoptability without redesign.

The S38 and S104 Programme Explained, S278 Agreements Explained, Adoptable Roads Explained and Roads & Sewers Contractors Guide support integrated planning — design responsibility should mirror the same integration.

Contractor-designed pavement build-up must meet authority standards — employer concept levels alone do not discharge design duty if Scope transfers detailed highway design.

Utility diversions are a frequent groundworks interface risk because existing services can constrain foundations, drainage runs, roads, and excavations. Asset owners retain ownership of the apparatus, but the contractor is normally responsible for coordinating safe construction, verification, and avoidance of service strikes during the works.

Good practice is to identify utilities early, confirm records with detection and verification, and allocate diversion design and execution responsibilities before starting on site. Where the contract makes the contractor responsible for diversions, the scope should define whether that includes design, permits, outage planning, protection, and third-party approvals.

The Utility Diversions for Development Sites guide maps undertaker processes — scope must state whether contractor designs diversion layouts or only builds undertaker-approved designs.

Provisional sums for diversions without design status create scope creep when the contractor is assumed to own detailed design.

Service protection and verification during excavation are normally contractor coordination duties even when diversion design sits with undertakers.

Professional indemnity insurance is relevant where the contractor or its designers are carrying design risk, because the policy is commonly the first financial backstop for design negligence claims. On design-and-build groundworks, contractors should check that PI cover extends to the actual design scope, including drainage, temporary works, and specialist civils elements.

Design warranties and collateral warranties matter because funders, purchasers, and future owners often want direct rights against the designer or contractor. Warranties should match the design responsibility matrix; otherwise, a party may give a warranty for work it did not actually control.

Employers should require PI evidence for design portions at tender and renewal confirmation during the works.

Collateral warranty schedules should follow the matrix — warranting adoptable drainage design requires the party who actually produced and approved that design.

Under JCT Design and Build, the contractor is responsible for completing the design of the works it undertakes, but the detail of liability depends heavily on the employer's requirements and amendments. In amended forms, contractors are often made the single point of design responsibility, including for errors or inadequacies in employer-provided information.

Under NEC ECC, responsibility follows the Scope: the contractor designs only the items the Scope allocates to it, and if X15 is used, that can alter the design obligation toward reasonable skill and care. For groundworks, NEC can work well if the Scope cleanly separates drainage, roads, earthworks, temporary works, and utility interfaces.

Read NEC vs JCT for Groundworks Projects for wider compensation event and change mechanics when design development continues on site.

Amended JCT clauses that transfer employer information risk need explicit tender disclosure — contractors price unknown design liability into contingency or exclusions.

The main commercial risk is scope creep: a contractor prices one design burden, then ends up carrying another after approvals, adoption comments, utility conflicts, or statutory changes emerge. The next biggest risk is delay, because drainage approvals, utility diversion agreements, and highway authority sign-off can sit on the critical path.

Other common risks include latent ground conditions, differing site levels, contaminated land, groundwater, and the need to redesign to meet adoption or loading criteria. If the contract does not define who owns those risks, the project team often discovers the gap after excavation has already started.

Design responsibility ambiguity inflates groundworks costs through redesign, standing time and repeat submissions — model the risk at feasibility.

Bond and adoption delay from redesign sits on the developer cashflow even when the contractor carries design duty — programme risk is shared commercially.

Developers should define the procurement strategy early and make sure the employer's requirements, planning commitments, and adoption strategy are aligned. They also need to secure land rights, technical approvals, and third-party interface agreements for highways, drainage, and utilities before relying on the contractor to sort it out.

In practice, the developer should decide which elements are meant to be contractor-designed, which remain consultant-designed, and which depend on external approval. That allocation should be reflected in the contract, schedules, and design responsibility matrix.

Planning conditions and LLFA submissions should be consistent with the design split — do not commit to adoptable SuDS in planning if the contract only requires contractor to build a concept.

Land rights and easements for off-site sewers remain employer duties even when the contractor designs the pipe alignment.

Contractors should check the scope carefully, price the actual design burden, and identify ambiguities before contract award. They should also confirm who is producing the drainage, highways, temporary works, and utility diversion design, and whether they are required to obtain adoption-ready approvals.

During delivery, the contractor must coordinate design, construction, inspections, temporary works control, and statutory compliance under CDM and any relevant highway or water company requirements. If the scope is unclear, the contractor should treat that as a commercial and technical risk issue, not an assumption.

Maintain design trackers, submission logs and approval comment closure registers alongside physical progress.

Flow-down design duty to specialist subs with matching PI and warranties where subs produce portion designs.

Typical disputes involve whether the contractor was responsible for design adequacy or only construction to an employer-issued concept. Others arise over whether drainage or attenuation schemes were meant to be adoptable, whether highway works were included in the price, or whether utility diversion works were provisional or fully designed.

Another frequent issue is the split between temporary and permanent works, especially where a temporary platform, haul road, or excavation support later becomes part of the finished works. That overlap can create arguments about who should pay for redesign, checking, and sign-off.

Employer's requirements inconsistencies — planning drawings versus tender Scope — are a root cause. QS teams should reconcile before award.

Late undertaker or authority comments are often argued as employer change versus contractor design duty — contract change mechanisms (NEC vs JCT) need to be used early.

Why disputes happen so often: employer's requirements, adoption criteria, approvals, and construction risk are often not aligned before tender, so the parties later disagree about what the contractor actually priced.

Use this checklist before tender issue and contract award on groundworks packages with contractor design elements.