Traditional vs Design and Build: An Honest Comparison

Table of Contents

Article written by: Stuart Deadman

As the Managing Director of Bespoke Construction Group Ltd, Stuart’s main responsibilities consist of building relationships with our clients and pushing projects along the appropriate chains of operations. Stuart is a problem-solver and fulfils his role by leading and connecting with his “power team” who are all leaders in their own right and each have a part to play.

A client’s first interaction with Stuart will likely be at the initial meeting in which he plays a pivotal role. From the very beginning, Stuart will be working hard to identify a solution that will work for the client, and with a keen eye for design and a personable approach, he’s an invaluable asset at this initial stage, getting to know both the project and the client.

Ask most people in construction which procurement route is better, and you’ll learn more about how they make their money than which one actually serves the client. Here’s a straight answer instead.

What the difference actually is

In traditional procurement, the design team, architect, structural engineer, and so on, work directly for the client, and the contractor is brought in once the design is largely complete, usually at or near tender. In design and build, the contractor takes on responsibility for the design as well as construction, either novating the existing design team or building their own.

The textbook framing is about risk transfer. The practical framing is about who is actually accountable when something doesn’t go to plan, and how much control the client keeps over decisions along the way.

When traditional procurement genuinely serves the client better

When the client, or their architect, wants to hold onto design control throughout, and is prepared to manage the interfaces between separate consultants and a contractor themselves, or through a project manager. It tends to suit clients with a strong, clear vision they don’t want diluted by a contractor’s own preferences.

When design and build genuinely serves the client better

When the client wants one point of accountability for cost, programme and design risk, rather than several. It tends to suit clients who want cost certainty locked in earlier, and who are comfortable trusting a contractor with more of the design decision-making within an agreed brief.

The myth architects have about design and build

That it means losing control of the design. Done properly, with the original design team novated rather than replaced, an architect can retain far more design influence under D&B than the reputation suggests, the difference is who they’re contractually answering to, not how much say they have.

The myth clients have about traditional procurement

That it’s automatically slower or more expensive. It isn’t inherently either, what it requires is someone managing the interfaces between consultants properly. When that happens well, traditional procurement can be just as efficient. When it doesn’t, that’s where the reputation comes from.

If this reads like a sales pitch for design and build

It shouldn’t. Both routes work well in the right circumstances and badly in the wrong ones. The honest answer to “which is better” is closer to “which is better for this client, this project, and how much control they want to keep,” not a blanket recommendation either way.

FROM THE INSIGHTS HUB

How We Think

Pre-Construction
JCT Design and Build gets mentioned in almost every conversation about procurement route, and almost nobody outside a QS or contracts team could actually explain what it does differently from a standard building contract. Here’s the commercial reality of it, not the legal detail, that’s not something to take from a website article, whoever’s writing it.
Pre-Construction
What value engineering actually means, and a real example of where the cost went without the design suffering.
Pre-Construction
A stage-by-stage look at where early contractor involvement actually adds value, and where it doesn’t.