What Does an Architect Actually Do? (And What They Don't Do)

Ask most people what an architect does and you'll get some version of "they design buildings." Which is technically true in the same way "a chef cooks food" is technically true. It's accurate and completely inadequate. The gap between that simplistic understanding and what architects actually do every day is enormous — and that gap is where most homeowner-architect relationships break down.

If you're about to hire an architect for your dream home, you need to understand what you're actually paying for. Not in the abstract sense, but in the practical, here's-what-happens-on-Tuesday sense. And equally important: you need to understand where the architect's role ends and other professionals — especially your builder — take over.

Phase 1: Understanding (Schematic Design)

The first thing an architect does isn't draw. It's listen.

Schematic design — the first formal phase of an architectural project — is fundamentally about understanding. Your architect is learning about you: how you live, what you value, what frustrates you about your current home, what excites you about your future one. They're studying your site: its orientation, its topography, its climate, its views, its constraints.

Good architects during this phase ask questions that feel surprisingly personal. What time do you wake up? How do you feel about morning light? Do you cook facing the wall or facing the room? Where do you go when you want to be alone? These aren't small talk — they're design inputs. Every answer shapes the spatial strategy they'll develop.

The output of schematic design is typically concept sketches, bubble diagrams, and preliminary floor plans. These aren't detailed enough to build from — they're conversation starters. "Is this the right direction? Does this spatial relationship work? Should we explore an alternative?"

This phase is where your preparation matters most. If you've taken Foundations of Architecture and arrived with a thoughtful design brief or concept sketches, you've just compressed weeks of exploratory conversation into a single productive meeting.

Phase 2: Refinement (Design Development)

Once the schematic direction is approved, the architect develops it. Design development is where the concept becomes specific: rooms get real dimensions, windows get real sizes and positions, the structure starts being considered, and materials enter the conversation.

This is the phase where most of the creative problem-solving happens. Your architect is simultaneously solving spatial problems (how do these rooms relate?), structural problems (how does this building stand up?), environmental problems (how does this building manage heat, light, and air?), and aesthetic problems (how does this building express its intentions?).

During design development, your architect is also coordinating with other consultants. The structural engineer is analyzing load paths and sizing beams. The civil engineer might be reviewing drainage and site access. The energy consultant could be modeling thermal performance. The landscape architect might be developing the site plan.

Your architect is the conductor. They're ensuring that all of these technical requirements converge into a design that still looks and feels like the home you envisioned — not a committee-designed compromise.

Phase 3: Documentation (Construction Documents)

This is the phase most people don't know exists — and it's where architects spend the largest percentage of their time. Construction documents (CDs) are the detailed technical drawings and specifications that tell your builder exactly how to construct the building.

CDs include floor plans at a larger scale with every dimension, wall type, and material noted. They include sections cut through the most complex parts of the building. They include detail drawings that zoom into specific connections — how the window frame meets the wall, how the roof edge is finished, how the deck attaches to the house.

They also include a written specification — a document that lists every material and product by name, manufacturer, and quality standard. The spec tells the builder that the timber cladding isn't just "cedar" — it's "Western Red Cedar, kiln-dried, clear vertical grain, 19mm thick, fixed with stainless steel ring-shank nails at 450mm centers."

This level of specificity serves two purposes. First, it ensures the builder prices the project accurately. If the documents say "cedar cladding" without specifying the grade, thickness, and fixing method, three builders will price three different products and you'll be comparing apples to oranges. Second, it protects you — if the finished product doesn't match the specification, you have documentation to reference.

This is also where the architect-builder relationship is most critical. A good builder will review CDs during the documentation phase and flag anything that's impractical, overly expensive, or unclear. Smart architects welcome this feedback because it prevents construction-phase surprises.

Phase 4: Construction Administration

Here's the phase that separates full-service architecture from "design only" services — and it's the one most homeowners undervalue until they're deep in construction wondering who's supposed to be answering questions.

Construction administration (CA) means the architect remains involved during construction, typically visiting the site periodically to review progress, answer builder questions, and ensure the design intent is being maintained. When the builder encounters something unexpected — a site condition that differs from the survey, a product that's been discontinued, a structural connection that's unclear — the architect provides direction.

CA also includes reviewing the builder's payment claims, issuing change orders when the design needs to adjust, and assessing whether the finished work meets the documented standard. At the end of construction, the architect walks the site and creates a deficiency list — items that need correction before the project is considered complete.

This phase costs money (typically included in the architect's percentage fee), and some homeowners try to skip it to save on architectural fees. This is almost always a false economy. Without CA, design intent can drift, substitutions can go unchecked, and problems that could have been caught with a site visit become expensive fixes after the fact.

What Architects Don't Do

Understanding the boundaries of an architect's role is just as important as understanding the role itself.

Architects don't build the house. This sounds obvious, but the line between design and construction gets blurry. Your architect specifies what to build and how it should look. Your builder determines how to construct it — the sequence of operations, the equipment needed, the subcontractor coordination, the timeline management. Some architects have strong construction knowledge (a valuable trait), but the builder owns the construction methodology.

Architects don't manage the construction budget day-to-day. They design to a budget, and they review payment claims, but the builder manages costs during construction. If you want rigorous cost tracking, that's a conversation with your builder or a quantity surveyor, not your architect.

Architects typically don't select your furniture. Interior design and architecture overlap significantly in residential projects, but they're distinct disciplines. Some architects offer interior design services. Many don't. If interior design is important to you (and it should be — a beautiful house with terrible furniture is still disappointing), clarify early whether your architect handles interiors or whether you need a separate interior designer.

Architects don't handle permitting for you. They prepare the drawings that get submitted for permit, but the application process, the fees, and the communication with the local authority are typically your responsibility — though some architects offer this as an additional service. Ask about it.

The Architect-Builder Dynamic

This is the relationship that makes or breaks residential projects, and it's one of the most important things I teach in Foundations of Architecture.

When it works, it's a partnership. The architect brings design vision, technical knowledge, and creative problem-solving. The builder brings construction expertise, material knowledge, and practical wisdom about what's efficient and durable. Together, they produce something neither could achieve alone.

When it doesn't work, it's adversarial. The architect designs details the builder considers impractical. The builder makes substitutions the architect considers unacceptable. The homeowner is caught in the middle, unsure whose judgment to trust.

The best way to avoid the adversarial dynamic is to bring architect and builder together early. If you're interviewing architects, ask how they feel about early builder involvement. If you're interviewing builders, ask how they feel about architect-designed projects. The answers tell you a lot about how each professional views collaboration.

Your role as the homeowner is to be the bridge — the person who ensures both professionals understand your values, your priorities, and your non-negotiables. The more clearly you can articulate what matters to you (which is exactly what FOA teaches), the easier it is for your architect and builder to align around your vision.

Understanding what an architect actually does empowers you to be a better client, a more informed decision-maker, and a genuine collaborator in the design of your home. You don't need to do their job. You need to understand their job well enough to work alongside them effectively.

Foundations of Architecture is a GAS Studio venture that teaches homeowners how to think like an architect — so they can design homes worth building.

This entry is part of our Systems & Scale series, where we break down the processes and frameworks behind great work.