A design and build split — an architect or designer producing drawings, a separate contractor pricing and building them — is a common and often sensible way to run a project. It also introduces a boundary between two parties that needs managing deliberately, because neither side automatically knows what the other has assumed.
Understanding where responsibility sits, and how queries are meant to flow between design and site, explains why some projects run smoothly through this arrangement and others get stuck in the gap between the two.
Clarifying who is responsible for what
In principle, the architect or designer is responsible for the design meeting the brief, being buildable and complying with relevant regulations, while the builder is responsible for constructing it to that design and to a proper standard of workmanship. In practice, both roles blur at points, and it's worth having an explicit conversation at the outset about who signs off what.
Structural design, for instance, is often produced by a separate structural engineer working alongside the architect, and it's worth being clear from the start whether the architect or the builder is coordinating that input, so nothing falls into a gap between the two.
Involving the builder early enough to matter
A design finalised in full before a builder ever sees it can end up with details that are difficult, expensive or simply impractical to build as drawn. Involving the builder — even informally — during design development gives buildability a voice before it's locked into a finished set of drawings.
This doesn't mean the builder redesigns the project; it means practical questions about sequencing, structure and site conditions get raised while changes are still cheap to make, rather than during a tender process when the design is already fixed.
How site queries are meant to flow
A vague or informal query process — asking whoever answers the phone, or relying on a text message that gets lost — is a common source of delay and of decisions made on site that nobody signed off properly.
- A query arises on site — a dimension doesn't work, a detail is unclear
- It's raised through a named, agreed route — usually the designer, sometimes the engineer directly
- A written answer comes back, ideally with a marked-up drawing if it changes anything
- The answer is recorded and, where it affects other trades, communicated to them
Keeping one current drawing set
It's surprisingly common for a builder to be working from an earlier drawing revision than the one the architect has since updated, particularly on a project with several design changes along the way. This creates real risk — work built to superseded information sometimes has to be redone.
A clear system for issuing and version-controlling drawings, so everyone on site is definitely working from the current set, is a basic but genuinely important part of this relationship working smoothly.
Where the interface actually breaks down
The most common failure point is nobody clearly owning the space between design and construction — a detail that's neither fully specified by the designer nor confidently interpreted by the builder, left to be resolved informally on site under time pressure. Naming a single point of contact for queries, and holding to it, closes most of this gap.
The second most common failure is drawings changing without a clear record of what changed and why, which makes it hard to establish afterwards who agreed to what — this is avoidable with basic version control and a habit of confirming changes in writing.
Common questions
Should the builder be involved before the design is finished?+
Ideally yes, at least informally, so buildability questions can be raised while the design can still change cheaply. A builder seeing a completed drawing set for the first time at tender stage has no opportunity to influence details that might have been simpler to build another way.
Who resolves a site query — the architect or the builder?+
This should be agreed explicitly at the start of the project, usually the architect or designer, sometimes with a structural engineer involved for anything affecting structure. What matters is that everyone knows the route in advance.
How do we avoid the builder working from an old drawing?+
Use a clear version-control system — dated revisions, clearly marked as superseded when replaced — and confirm at the start of each site visit that everyone is working from the current issue.
Ask us how we work alongside your architect
We agree a clear query route and drawing version control with your designer before work starts on site.