What "execution partnership" actually means

The term gets used loosely in local practice, and it's worth being specific about what it means — and what it doesn't.

An execution partnership, as I practise it, begins with a completed design. Not a sketch. Not a concept. A design that has been through the client, through planning if required, and that has been confirmed as the direction. My role is to take that direction forward without losing it.

That means producing construction documents that reflect the design intent at a level of detail a contractor can build from. It means being on site regularly enough to catch the decisions that get made in the absence of a drawing — because they always get made, and they usually go wrong. It means knowing when to escalate a question to the principal architect and when to resolve it on the ground.

What it doesn't mean: it doesn't mean redesigning. It doesn't mean undercutting the original practice's fee by offering a cheaper version of the same service. It doesn't mean taking a project to a place the client hasn't agreed to.

The best partnerships I've had are ones where the other practice trusted me enough to not feel the need to check every decision. That trust takes time to build. I protect it accordingly.