Who Owns the Line? Commercial Discipline for Client-Supplied Design Information

Client-supplied design information often arrives with an air of completeness. A drawing package is issued, a specification is attached, a model is shared, and the commercial conversation moves quickly to programme and price. The risk is that receipt is treated as reliance, and reliance is treated as responsibility. For UK commercial teams, the important question is not simply what information has been provided, but what the contractor has agreed to do with it.

A contractor may be engaged to build to the client’s design. That is a different bargain from taking on design responsibility. The distinction matters because it shapes liability, insurance, pricing and the conduct expected on site. Where the boundary is left unclear, it is often tested after a problem emerges: a clash, a performance shortfall, a late revision or an interface that no one owned. By then, commercial positions have usually hardened.

Begin with reliance, not receipt

The first control is contractual. Does the contract state that the contractor is entitled to rely on client-supplied information? Does it require the contractor to check that information, and if so, for what purpose? A duty to review for buildability, coordination or constructability is not the same as a duty to adopt the design as one’s own. The wording should distinguish between noticing an issue and accepting responsibility for resolving it.

A practical reliance schedule helps. It should identify the documents relied upon, their revision status, the date of issue and any stated limitations. It should also record what the contractor is not relying on, such as information still marked preliminary or subject to third-party approval. Without that discipline, a contractor can find that a general review obligation has been read as an endorsement of the whole design.

Fitness for purpose is a different promise

The phrase fitness for purpose deserves careful attention. If a contractor designs, it may be asked to warrant that the result is fit for its intended use. If a contractor merely builds to a client’s design, the position is usually different, but the difference can be eroded by conduct. Offers to improve a detail, propose an alternative or make something work on site may be treated as design input if they are not properly recorded.

Before tender, the team should identify any performance requirements that sit close to the design boundary. A specification may describe an outcome rather than a method. A client may ask the contractor to confirm that a system will achieve a certain rating or capacity. Those requests should be priced and documented, not absorbed into general coordination. If a fitness-for-purpose obligation is accepted, it should be explicit, insured and reflected in the subcontract chain.

Map the interface gaps

Client-supplied design rarely stops neatly at every point where construction begins. There are often gaps between architectural intent, structural requirements, building services coordination and trade contractor information. Secondary steel, builders’ work, fire stopping, glazing interfaces and connection details are common examples. The commercial risk is not the existence of gaps; it is the assumption that someone else will fill them without instruction or payment.

A responsibility matrix is more useful than a general statement of cooperation. It should name the party responsible for each design element, the party responsible for checking it, and the party responsible for coordinating it with others. Where responsibility is genuinely unresolved, the tender should say so. A provisional sum or a clearly stated qualification is preferable to a silent acceptance that later becomes a variation dispute.

Place professional indemnity cover where the risk sits

Design risk should be matched by appropriate professional indemnity cover. If the contractor is accepting design responsibility, the team should confirm that the policy responds to the relevant scope, that the limit is adequate and that exclusions do not undermine the cover. Contractual liability, retroactive dates and the treatment of client-supplied information are all worth checking before signature rather than after a claim.

Where the client is retaining design responsibility, the contractor may still need evidence of the client’s cover. That evidence should be reviewed with the same care as any other commercial document. A certificate of insurance is not a substitute for understanding the scope of cover. If reliance on another party’s insurance is part of the bargain, the contract should say so clearly.

Make acceptance visible

Documented acceptance is a commercial control, not an administrative habit. A design information register should record what was received, when, in what revision and with what status. Transmittals should state whether information is issued for construction, for review, for information or for record. Responses should avoid language that implies approval of the design as a whole when the contractor is only confirming receipt or raising a query.

This matters in practice because site teams communicate constantly. An email saying that a detail can be made to work may be read later as an assumption of responsibility. A marked-up drawing may be treated as a design instruction. A meeting note may record agreement without recording the commercial basis. The register and the transmittal trail should give the project a consistent account of who accepted what.

Keep change control close to design development

Client-supplied design often develops after tender. Revisions arrive, queries are raised and assumptions change. Each of those events can carry cost and time consequences. The contract should provide a clear route for design changes, including how late information is handled and how the programme is adjusted. The project team should track design freeze dates and treat post-freeze changes as commercial events, not as normal coordination.

At SEH Ltd, the working principle is straightforward: price the risk before it lands on site, and record the position while the facts are fresh. A contractor does not need to distrust every drawing it receives. It does need to know whether it is building to information, reviewing information or adopting information. Those are different commercial acts, and they deserve different paper.

The checklist is therefore simple. Confirm reliance. Define fitness for purpose. Map interfaces. Verify insurance. Document acceptance. Control change. When client-supplied design is handled with that discipline, the contractor can build with confidence without quietly acquiring a design liability it never intended to price.