Team assembly

For the project, not to a template

We assemble the team for the project. A shed needs different disciplines from a public building, and a different person suits a rooftop addition from a new build.

It is not one fixed office working on every job — we pick the disciplines for the task. Design disciplines.

The typical line-up

• architect — the building as a whole,
• structure — our core,
• mechanical — takes the most room in the structure,
• electrical,
• fire,
• energy,
• depending on the project, acoustics, geotechnics, transport, landscape.

If you bring a discipline

If you have your own architect or services engineer, we are glad to work with them: they join the shared model, in the same workflow. Do I need my own architect.

What we show you

Who is who. We do not work with anonymous disciplines: we tell you who is responsible for a part and who signs it. Qualification, signature, liability.

Where the mistakes arise

Not inside the disciplines but at their boundaries — where everyone assumed the other would do it. So we record in writing who designs what, who gives data to whom, and who coordinates. Boundaries of responsibility.

The point

The team fits the task, not the other way round. And we write the boundaries down, because “I thought you were doing that” is the commonest design mistake.