Slow Down to Go Faster: Why Building Knowledge Should Come Before Design on Complex Refurbishments

The Pressure to Move

There's a familiar pattern in development. A building is acquired, the design team is appointed, and the pressure to reach RIBA Stage 4 begins almost immediately. Tender packages are assembled, contractors are lined up, and a start on site date is pencilled into the programme before anyone has properly asked the most important question: what has this building been through, and what is it actually telling us?

On a new-build project, you're largely working with knowns. The ground conditions are investigated, the structure is designed from scratch, and the programme reflects what you're building. On a complex refurbishment, particularly where a large building has sat vacant and deteriorated over years, sometimes decades the rules are entirely different. The building has a history and that history matters.

Vacant buildings don't stand still. Roof failures admit water. Water accelerates structural decay. Moisture migrates into masonry, substructures, and service voids. Temporary repairs made by previous owners may have masked more serious underlying issues. What looks like a straightforward envelope problem on a surface-level inspection can reveal something entirely different once you're on site and the building opens up. Discovering that on week six of a programme is a very expensive lesson.

Front-Load the Right Investigations

The answer isn't to slow the project down indefinitely it's to front-load the right investigations so that when design and construction do begin, they're grounded in reality. This means investing properly in building condition surveys, structural appraisals, services investigations, and in most cases intrusive opening-up works before design is fixed. It means reviewing available archive drawings, understanding previous uses, and interrogating the building's maintenance history. The design process should respond to what the building tells you, not the other way around.

In our experience, this is where developer instinct and good project management can pull in opposite directions. The instinct is to move, to justify the acquisition cost, to satisfy funders, to demonstrate progress. The job of a good development manager is to hold that tension and make the case for front-loaded investigation, even when the pressure to proceed is real. The cost of a thorough pre-design appraisal is trivial against the cost of abortive design work, or worse, discovering a structural issue mid-contract.

Phasing as a De-Risk Tool

Phasing, used intelligently, is one of the most powerful tools available on a complex refurbishment. Making a building wind and watertight in Phase 1, roof repairs, window replacements, external envelope stabilised, does several things at once. It arrests further deterioration. It allows the building to dry out and be properly assessed in a stabilised condition. It de-risks the cost plan for subsequent phases, because you're no longer pricing on assumptions. And if funding or market conditions shift, you haven't committed full construction costs before you're ready to.

The Case for Slowing Down

None of this is an argument for analysis paralysis. There's a point where investigation has to give way to programme, and where decisions need to be made with imperfect information. But on a large, complex building with a complicated history, the developers who take time to understand what they're dealing with before they build tend to deliver more predictable outcomes, fewer abortive costs, and better buildings. The discipline of slowing down at the right moment is what allows everything that follows to move faster and with confidence.