Most people who hire an architect have only a vague sense of what the architectural design process actually involves. They know it starts with a conversation and ends with a building, but the middle — the months or years between those two points — is largely opaque. That opacity creates problems: clients who don’t understand the process make decisions at the wrong time, resist necessary phases, underestimate how much input is required from them, and are consistently surprised by things that are completely predictable if you know what’s coming.
I’ve walked clients through the architectural design process hundreds of times. The explanation I give them in that first meeting has evolved considerably from when I started practicing. The version I give now is honest about what each phase costs in time and money, clear about what the client needs to contribute at each stage, and direct about where projects typically go off track and why.
The Architectural Design Process: What Actually Happens Between the First Meeting and the Finished Building
This article gives you that explanation — the architectural design process from the perspective of someone who lives it every day. Not the idealized diagram from a textbook, but the actual sequence of events, decisions, and deliverables that move a project from an idea to a building. Whether you’re a client considering hiring an architect, a student entering the profession, or a design professional looking for a clear framing of the process, this is the guide I wish had existed when I started.
Why the Architectural Design Process Has Phases
The architectural design process is structured in phases because design decisions have a natural sequence — some must be made before others can be resolved. You have to know what the building is before you can figure out how to structure it. You have to know how to structure it before you can coordinate the mechanical systems. You have to coordinate the systems before you can produce the detailed drawings that contractors will build from.
Every phase of the architectural design process represents a different level of commitment. Early phases make decisions that are cheap to change. Later phases make decisions that are expensive to change. By the time you’re in construction documents, changing the location of a staircase is a major disruption. By the time you’re in construction, it costs real money and real time. The phases exist to ensure that decisions get made in the right order, at the right level of detail, at the point in the process where changing them is still manageable.
The architectural design process additionally structures the relationship between architect and client. Each phase ends with deliverables — drawings, reports, cost estimates — that the client reviews and approves before the team proceeds. Those approval moments are the checkpoints that prevent design from drifting away from what the client actually wants and what the budget can actually support.
| 💡 The single most important thing to understand about the architectural design process is that decisions become more expensive to change as the process advances. A change in programming costs nothing. The same change in construction documents costs hours of rework. The same change in construction costs real money. The phases exist to get decisions made while they’re still cheap. |
Phase 1: Pre-Design — Programming and Project Definition
The architectural design process begins before any design happens. Programming is the phase where the project is defined: what does the building need to do, for whom, in what context, and with what resources? The output of programming is not a design — it’s a brief. A clear statement of what the project is, what spaces it requires, what relationships between those spaces matter, what the site conditions are, what the budget is, and what constraints apply.
Solid programming in the architectural design process is comprehensive and specific. It defines not just square footage but the quality of spaces — the height a room needs to feel right, the relationship between interior and exterior that matters for this program, the acoustic requirements, the daylighting goals. It identifies the users of each space and how they move through the building. It establishes the budget range with enough specificity that design decisions can be evaluated against it from the start.
Programming is also where the site is analyzed. A site visit, a review of zoning and land use regulations, an assessment of existing conditions — all of this becomes the factual foundation on which design will be built. The architectural design process that skips thorough programming produces designs that solve imagined problems rather than real ones. I’ve seen projects where the beautiful design that emerged from schematic design had to be fundamentally reconceived because the programming hadn’t accurately captured what the client actually needed.
Phase 2: Schematic Design — The Big Ideas Take Shape
Schematic design is the phase where the architectural design process becomes visually recognizable as architecture. This is the phase where the fundamental organization of the building is established: the relationship of spaces to each other and to the site, the massing and volume of the building, the primary structural approach, the overall character of the design. Schematic design doesn’t resolve everything — it resolves the biggest things, the decisions that everything else depends on.
The formal deliverables of schematic design in the architectural design process are typically plans, sections, and exterior elevations drawn at a scale that shows the overall organization but not the details. A preliminary cost estimate accompanies the design, giving the client a first look at whether the schematic design fits the budget. This is the most important budget checkpoint in the architectural design process — if the design doesn’t fit the budget at schematic design, the team adjusts here, before investing in design development.
Client engagement during schematic design in the architectural design process is critical. The architectural design process expects clients to be active participants at this phase — not passive recipients of a presentation but engaged collaborators who can articulate whether the design responds to the program, whether the character feels right, whether the spatial organization makes sense for how they actually live or work. Clients who disengage at schematic design almost always find themselves reacting to design development work that doesn’t quite fit what they wanted — because the direction wasn’t established clearly enough at schematic design.
Phase 3: Design Development — Resolving the Design
Where schematic design establishes the big ideas, design development in the architectural design process is where those ideas get tested and resolved in detail. The structural system gets engineered. The mechanical, electrical, and plumbing systems get designed and coordinated with the architecture. Materials and assemblies are selected and detailed. The building envelope — how the walls, roof, and windows are put together — gets worked out. The design that was a coherent concept at schematic design becomes a buildable proposition at design development.
Design development is consistently the most intensive phase of the architectural design process for the team. The number of decisions that need to be made — and the number of consultants who need to be coordinated — grows significantly. The structural engineer is working. The MEP engineers are working. Specialty consultants for acoustics, lighting, sustainability, or accessibility may be engaged. The architect’s role is as much coordination as design — making sure that the systems are integrated, that conflicts are resolved, and that the design intent survives the practical constraints that detailed engineering reveals.
From the client side, design development in the architectural design process requires a different kind of engagement than schematic design. The questions being resolved are more technical — window specifications, structural connections, mechanical system types — and clients need to understand which decisions require their input and which are the architect’s professional call. Good architects are clear about this distinction: they present options where client preference matters and make recommendations where technical expertise is the appropriate basis for decision.
| Phase | Primary Goal | Key Deliverables | Client Role |
| Pre-Design / Programming | Define the project | Program brief, site analysis, budget range | Primary driver — deep engagement required |
| Schematic Design | Establish the concept | Plans, sections, elevations, prelim cost estimate | Active review and approval of direction |
| Design Development | Resolve the design | Developed drawings, specs, updated cost estimate | Decision-making on materials and systems |
| Construction Documents | Document for construction | Full drawing set, specifications, final estimate | Review and approval before bidding |
| Permitting | Regulatory approval | Permit application, agency review responses | Documentation support |
| Bidding / Procurement | Select contractor | Bid package, bid analysis, contract recommendation | Decision on contractor selection |
| Construction Administration | Oversee building | Site visits, RFI responses, submittals, punchlist | Availability for decisions, timely payment |
Phase 4: Construction Documents — The Full Instructions
Construction documents are the complete technical description of the project. This phase of the architectural design process produces the most voluminous and most technically demanding work. Every wall assembly, every connection detail, every door schedule, every material specification — all of it goes into the construction document set.
The standard of care for construction documents in the architectural design process is completeness and coordination. Completeness means that everything a contractor needs to build the project is in the documents. Coordination means that the architectural drawings, structural drawings, and MEP drawings are consistent with each other — that the beam shown on the structural drawing fits within the ceiling shown on the architectural section, that the duct shown on the mechanical drawing doesn’t run through the column shown on the structural drawing.
From the owner’s perspective, construction documents in the architectural design process can feel like a black box — the team is heads-down producing documents and there’s less visible activity than in schematic design or design development. But this phase is when the project becomes truly buildable. The decisions made here directly determine the quality and cost of the built result. Construction documents that are complete and well-coordinated produce bids that are close together, predictable, and close to the estimate. Incomplete or poorly coordinated documents produce wide bid spreads, change orders, and conflict.
Phase 5: Permitting — Regulatory Approval
The permitting phase in the architectural design process involves submitting the construction documents to the relevant regulatory authorities — typically the local building department — for review and approval. Depending on jurisdiction, other agencies may be involved: planning, fire, health, environmental, historic preservation, or others specific to the project type or location.
Permitting timelines vary enormously. In some jurisdictions, building permits for residential projects are issued over-the-counter in days. In others, complex projects in dense urban environments can take six months to a year or more. The permitting phase of the architectural design process is often the least predictable in terms of timeline, and clients consistently underestimate how long it takes.
In the permitting phase of the architectural design process, the architect responds to plan check comments — the questions and required changes that the reviewing agency identifies — in a timely and complete way. A thorough and experienced architect anticipates most plan check issues before submission and addresses them in the documents, minimizing the back-and-forth that extends permitting timelines. First-time applicants and architects unfamiliar with a jurisdiction’s specific requirements typically experience more rounds of review.
Phase 6: Bidding and Contractor Selection
Once permits are obtained, the bidding phase of the architectural design process involves sending the full document set to a shortlist of qualified contractors, hosting a pre-bid meeting to answer questions, receiving and evaluating bids, and recommending a contractor for the client’s selection.
The quality of the construction documents directly affects the bidding phase of the architectural design process. Complete, well-coordinated documents produce bids that are close to each other and close to the estimate — because all the contractors are pricing the same thing with the same information. Incomplete documents produce wide bid spreads because contractors make different assumptions about the undefined scope, and they include different amounts of contingency for the unknowns.
Bid evaluation in the architectural design process is not just about price. The architect evaluates each bid for completeness — are all the specified items included? — and for qualifications. The lowest bid from an unqualified contractor is not a good deal. The recommendation to the client should be based on price, qualifications, references, schedule, and the architect’s professional judgment about the contractor’s ability to deliver the project well.
Phase 7: Construction Administration — The Design Gets Built
Construction administration is the critical phase of the architectural design process where the building is physically constructed. The architect’s role shifts from producing design to observing that the design is being built correctly. Site visits, responses to contractor questions (called Requests for Information or RFIs), review of contractor submittals (shop drawings, material samples, product data), and oversight of the change order process are the primary activities.
Construction administration is often undervalued by clients who treat it as optional rather than essential to the architectural design process. The reality is that no set of construction documents, however complete, can anticipate every condition or answer every question that arises during construction. The architect’s presence during construction — observing the work, resolving ambiguities, identifying issues before they become problems — is what ensures that the design intent survives the transition from drawing to building.
Projects completed without adequate construction administration — a core part of the architectural design process — consistently have more problems than those with it. Not because contractors are incompetent — most are skilled professionals — but because construction is complex, conditions in the field don’t always match what the drawings show, and decisions that seem small in isolation can have significant consequences for the finished building. An experienced architect in construction administration catches those issues early, when they’re still manageable.
| 💡 Construction administration is where the architectural design process either holds together or falls apart. The architect who disappears after handing over the construction documents and then wonders why the finished building doesn’t match the design has misunderstood their professional responsibility. Presence during construction is how design intent becomes built reality. |
What the Architectural Design Process Requires from Clients
Every phase of the architectural design process is a collaboration between architect and client. The quality of the process — and of the result — depends significantly on what the client brings to it. These are the things that make the difference between a smooth process and a difficult one:
Clear decision-making authority: The architectural design process generates decisions continuously. Having a single, clearly authorized decision-maker on the client side — or a very small group with clear internal alignment — prevents the delays and reversals that come from unclear authority or disagreement among multiple stakeholders with different views.
Timely responses: The architectural design process has momentum. When architects need information or approvals to move forward and clients take weeks to respond, the schedule suffers and often the budget does too. Responsive clients get better results from the process — not because the architect works harder, but because the process flows without unnecessary interruption.
Honest communication about priorities: Clients who clearly communicate what matters most — whether it’s budget, schedule, spatial quality, sustainability, or design ambition — give architects the information they need to make good tradeoffs when tradeoffs are necessary. Clients who don’t articulate their priorities force architects to guess, and the guesses aren’t always right.
Willingness to engage at each phase: The architectural design process expects clients to engage actively at certain moments — reviewing schematic design, making material decisions during design development, approving construction documents before bidding. Clients who defer or disengage at these moments often find themselves with a building that doesn’t quite fit what they wanted — because their input at the critical decision points wasn’t there.
Where the Architectural Design Process Most Commonly Goes Wrong
Having worked through the architectural design process on many projects of different types and scales, the failure modes are remarkably consistent. They’re not random — they’re predictable, and most of them are preventable.
Scope creep in schematic design: Clients who keep adding program elements after schematic design has established the project scope create a design that grows incrementally beyond what the budget supports. Each addition seems small; collectively they move the project significantly. The discipline of closing the program before schematic design begins is essential to controlling cost.
Budget-design disconnect: Schematic designs that are significantly over budget before design development begins. The architectural design process expects the preliminary cost estimate at the end of schematic design to serve as a budget check. Teams that proceed to design development without resolving a significant schematic design budget overrun are setting up for a difficult value engineering exercise later — often at a point where changes are more expensive and more disruptive.
Compressed construction documents: Clients who apply schedule pressure to compress the construction documents phase often get incomplete documents that generate expensive field questions and change orders. The construction documents phase takes as long as it takes to do it right. Compressing it transfers cost from design to construction — usually at a ratio that’s unfavorable for the client.
Inadequate construction administration: Clients who reduce or eliminate construction administration to save on fees — and then discover that the building wasn’t built as designed. The fee savings are almost always smaller than the cost of the problems that result.
How Long Does the Architectural Design Process Take?
The timeline of the architectural design process varies enormously depending on project scale, complexity, and jurisdiction. As a general reference:
- Programming: 2–8 weeks, depending on project complexity
- Schematic Design: 4–12 weeks for most residential projects; longer for complex commercial
- Design Development: 6–16 weeks for most projects
- Construction Documents: 8–20 weeks for most projects; longer for complex or large projects
- Permitting: 2 weeks to 12+ months depending on jurisdiction and project type
- Bidding: 3–6 weeks
- Construction: 3 months to several years depending on scale
For a typical custom residential project, the architectural design process from programming through permit takes 12–18 months before construction begins. This surprises many clients, who assume the design can be completed in a few weeks. Understanding the actual timeline of the architectural design process is essential for realistic project planning — and for not making commitments about occupancy dates that the process can’t deliver.
Frequently Asked Questions About the Architectural Design Process
Can phases of the architectural design process be skipped to save time or money?
Technically yes, practically no — not without consequences. Each phase of the architectural design process exists because it resolves decisions that subsequent phases depend on. Skipping schematic design and going straight to construction documents produces documents that are faster but often require extensive revision because the fundamental design questions weren’t resolved first. Skipping design development produces construction documents that aren’t adequately engineered. The fees for each phase are far smaller than the cost of the problems that arise when phases are compressed or skipped.
When in the architectural design process should the contractor be involved?
Traditional practice involves the contractor only after construction documents are complete, for bidding. Increasingly, experienced clients and project teams engage the contractor earlier — during schematic design or design development — for preconstruction cost and constructability input. This approach, called Construction Manager at Risk or early contractor involvement, is particularly valuable for complex projects where constructability issues and cost management benefit from contractor knowledge during design. It adds cost upfront but often reduces overall project cost and risk.
How does the architectural design process differ for renovations versus new construction?
The phases are the same, but the content of each phase is different. Renovation projects begin with an existing building survey — a thorough documentation of existing conditions — that new construction projects don’t require. The programming phase must account for what the existing building provides and what it constrains.
Construction documents for renovations often include demolition drawings showing what to remove. And construction administration for renovations is typically more intensive because existing conditions discovered during construction — hidden systems, unexpected structural conditions, hazardous materials — require more frequent decision-making.
What is the architect’s role after the building is complete?
The architect’s formal involvement ends at project closeout — the final punchlist, the certificate of substantial completion, the delivery of as-built documentation. Some architects maintain ongoing relationships with clients for post-occupancy evaluation, helping assess whether the building performs as intended and identifying lessons for future projects. This post-occupancy engagement is valuable but uncommon in standard practice. For complex buildings with sophisticated systems, the architect may also provide assistance during the warranty period when system issues arise.
The Architectural Design Process Is a Structured Path Through Complexity
The architectural design process exists because building design is genuinely complex — more complex than it appears from the outside, and more complex than any single mind can hold simultaneously. The phases structure that complexity into manageable segments, each resolving a layer of questions so the next layer can be addressed.
What I’ve come to appreciate about the architectural design process after years of practice is that its structure is not bureaucratic — it’s functional. The phases exist because decisions have a natural sequence. The deliverables exist because commitments need to be documented. The approvals exist because alignment between architect and client needs to be confirmed before proceeding. When the process is followed with discipline, it consistently produces better results than shortcuts.
The best clients are the ones who understand the architectural design process well enough to engage with it intelligently — who know what each phase is trying to accomplish, what their role is at each stage, and why the process takes as long as it takes. With that understanding, the collaboration between architect and client becomes genuinely productive, and the building that results reflects both the architect’s expertise and the client’s knowledge of their own needs.
These articles from the Architecture cluster go deeper on specific aspects of the process:
→ What architecture is and what architects do: What Is Architecture? Definition and Real Scope of the Discipline — Understanding the architectural design process is easier when you understand what architecture as a discipline actually is — and what architects are responsible for beyond producing drawings.
→ The portfolio that results from the process: Architecture Portfolio: How to Build One That Gets You Work — The architectural design process produces the work that goes into an architect’s portfolio. This article covers how to present that work effectively — what firms and clients actually look for.
→ How design gets communicated visually: Architectural Rendering Techniques: A Practical Guide — At each phase of the architectural design process, the design needs to be communicated to clients, consultants, and contractors. This article covers the rendering and visualization techniques that make design legible at every stage.