HB Thompson Group Project Definition · Architecture · Project Build
Architecture

What Does an Architect Actually Do Before Drawing the Design?

Henry B. Thompson, Architect

Most people picture the start of an architectural project as a sketch — a floor plan taking shape on trace paper, a first elevation. In practice, a meaningful amount of an architect's work should happen before a design is proposed.

The construction industry is familiar with preconstruction — the estimating, scheduling, procurement planning, logistics, constructability review, coordination, permitting and trade input that take place before work begins in the field.

Far fewer people, even within the industry, think about pre-design with the same discipline.

But many of the questions commonly addressed during preconstruction shouldn't wait until construction is approaching. They should begin informing the project during pre-design and continue through design — while the project can still respond to them.

Design is a response, not a starting point

A design developed before the conditions of the project are understood is necessarily based on assumptions. Those assumptions may prove correct, but until they've been tested against the place, the people, the investment, regulations, existing conditions and the realities of building, the design has little to anchor it.

Pre-design is where that understanding begins. The objective isn't to solve the architecture before designing it. It's to establish the conditions the architecture will need to respond to — so that when design begins, it begins from understanding rather than assumption.

What happens before a design is proposed

Programming

Understanding what the project needs to accomplish

Conversations that establish how you actually live or work, what's not functioning about the current situation, what matters most and what the project needs to accomplish — distinct from what form the solution might take.

Existing conditions

Documenting what's actually there

Measured drawings, surveys and existing construction documents establish the physical conditions from which the project begins. Structure, building systems, site conditions and other existing constraints can materially influence what is reasonable to do next.

Zoning, code and approvals

Establishing the regulatory conditions

Setbacks, height, lot coverage, allowable use, building requirements and approval pathways aren't simply permitting issues to address after design. They establish conditions the design may need to work within — or intentionally seek relief from.

Feasibility

Testing whether the project is achievable

Early diagrams, massing studies and other investigations can test whether the program, site, regulations, existing conditions and investment are reasonably compatible before substantial design effort is committed to a direction that may not work.

Investment, cost and schedule

Establishing the realities the design needs to respond to

Cost and time aren't conditions to introduce after the architecture has been developed. Order-of-magnitude estimating, schedule requirements and major project constraints should begin informing decisions while scope, size, systems, assemblies and priorities can still respond.

Construction and specialist input

Bringing downstream knowledge upstream

Constructability, procurement, logistics, major building systems and specialized trade knowledge can influence fundamental design decisions. When that information is relevant, bringing it into pre-design or design allows it to shape the project rather than correct it later.

By the time design begins, we should understand far more than what rooms are needed or how large the building might be.

Why this order matters

Estimating, scheduling, procurement planning, logistics, constructability, coordination, permitting and trade input are often described as preconstruction activities. Many of them are. But many should also begin much earlier.

The issue isn't that these activities don't belong in preconstruction. It's that preconstruction shouldn't be the first time the project confronts them.

Better pre-design makes preconstruction better

Preconstruction remains essential. There will still be detailed estimating, buyout, procurement, construction scheduling, logistics, trade coordination, mobilization planning and the many other activities required to prepare a project for physical execution.

But when cost, schedule, constructability, procurement, approvals and specialized knowledge have already informed the project, preconstruction can become a period of refinement, validation and preparation rather than correction. The estimator is refining the cost picture rather than revealing it for the first time. Procurement is advancing decisions rather than forcing wholesale substitutions. Trade coordination is resolving increasingly detailed conditions rather than discovering fundamental conflicts. Construction planning is developing how the project will be executed rather than questioning whether the design can reasonably be executed at all.

Good pre-design doesn't eliminate preconstruction. It changes what preconstruction has to fix.

Resolve decisions while they are still information

There's a practical reason for bringing this thinking forward. A decision represented by information can still be tested, compared and changed. Once that decision becomes purchased material, fabricated work or construction in the field, changing it becomes progressively more difficult and expensive.

That's why the work before design matters. And it's why the boundary between architecture and construction shouldn't prevent construction knowledge from informing the project while it is still being defined and designed.

The objective isn't to make every decision before design begins. It's to bring the right information into the project early enough to influence the decisions it should inform.

Ready to talk through what your project actually needs?

Discuss Your Project