Do I need my own architect?
Not required, but possible
Section titled “Not required, but possible”You do not have to bring your own architect — if you do not have one, we bring the discipline.
If you do have one, we are glad to work with them. We assemble the team for the project, and if you bring an architect or services engineer, they join the shared model and the same workflow.
What that means in practice
Section titled “What that means in practice”A shared model
Section titled “A shared model”The disciplines work in one model, not in files sent to one another. Model-based collaboration · IFC and data exchange.
A shared programme
Section titled “A shared programme”The disciplines build on one another. If one of them is external, the programme is still one.
Boundaries recorded in writing
Section titled “Boundaries recorded in writing”With an external discipline this matters especially: who designs what, who gives data to whom, who coordinates, and what happens on a change. Boundaries of responsibility.
Liability
Section titled “Liability”Every drawing is signed by its own discipline’s designer, whether ours or yours. The general designer does not take over the disciplines’ liability — what they undertake is consistency and coordination. Qualification, signature, liability.
What still differs with us
Section titled “What still differs with us”If you bring an architect, the difference remains: with us the structure is part of the concept. We work with the architect, but we state the structural consequences in the first week. How this general design differs.
The point
Section titled “The point”Bring an architect and it is still one process. One condition: write the boundaries down at the start, not during the argument.