Issue 001 field guide

Questions to Ask Before Hiring an Architect

A Bay Area homeowner interview script for testing scope, fees, consultants, permits, budget reality, and construction support before signing.

Most homeowners think the first architect call is for chemistry. It is not. It is for clarity.

A beautiful portfolio can hide a messy scope. A confident fee can hide a pile of "not included." And a friendly promise about permits can collapse the moment your city sends comments.

This is the interview script: the questions that make scope, fees, consultants, budget, city review, and construction support visible before money starts moving.

Short answer

Ask questions that expose process, scope, handoffs, budget timing, permit responsibility, consultant responsibility, and construction-phase support. Do not ask for free design ideas on the first call. Ask how the architect thinks, what they include, what they exclude, and where homeowners usually get surprised. If the answers are vague, the proposal will probably be vague too.

What to remember

The decision rule

  • Interview for process, not taste.
  • Make exclusions a list, not a vibe.
  • Ask when cost reality enters the process. Early is cheaper than late.
  • If nobody owns consultant coordination and city comments, you do.
  • The best architects can explain the workflow in plain English.

Decision table

What should you do first?

You have an idea but no clear scope

Likely first step

Ask what first risk should be reduced before full design begins.

Architect makes sense when

They can name the constraint: feasibility, city review, budget, structure, or owner decisions.

Watch out

They jump straight to style without explaining sequence.

You are comparing proposals

Likely first step

Ask for included, excluded, reimbursable, hourly, and additional services as separate lists.

Architect makes sense when

They can make the fee readable without defensiveness.

Watch out

The proposal is vague and confident. Worst combo.

Your project needs permits

Likely first step

Ask who responds to city comments and how many response rounds are included.

Architect makes sense when

They have recent local experience with similar scope and can describe likely review friction.

Watch out

They promise speed without naming city-specific constraints.

Budget is tight

Likely first step

Ask when builder or estimator input enters the process.

Architect makes sense when

They plan budget checkpoints before drawings get emotionally expensive.

Watch out

They treat pricing as something that happens after design is basically finished.

Construction details matter

Likely first step

Ask what construction administration includes and what happens if you decline it.

Architect makes sense when

The project is complex enough that contractor questions need design-side answers.

Watch out

Nobody owns RFIs, submittals, field changes, or change-order review.

Start with the framing question

The first question is not "How much do you charge?" That question matters, but it arrives too early. The first question is: what problem are we solving first?

Some projects need design exploration. Some need feasibility. Some need a permit path. Some need a budget reality check before anyone falls in love with a scheme. If you skip that distinction, you may hire a good architect for the wrong first job.

Ask: "Based on what I have described, what is the first risk you would want to reduce before full design begins?"

  • A useful answer names a risk: zoning, planning review, hillside constraints, structural uncertainty, budget, existing conditions, consultant needs, or unclear owner priorities.
  • A weak answer jumps straight to style or full-service romance without explaining sequence.

Ask what the first phase actually produces

Architects use phase names that sound universal: pre-design, schematic design, design development, construction documents, permitting, bidding, construction administration. The names are familiar. The deliverables are not always the same.

One architect's schematic design phase may produce rough plans and a massing study. Another may include multiple layout options, exterior concept direction, preliminary consultant input, and a budget checkpoint.

Ask: "At the end of the first phase, what will I physically have? Plans, options, diagrams, a budget checkpoint, consultant notes, city feedback, or something else?"

  • You are listening for nouns.
  • Homeowners get into trouble when the proposal is all process words and no deliverables.

Make fee and scope readable

A good proposal should separate fixed-fee work, hourly work, reimbursable expenses, excluded services, and likely additional services.

Ask: "Can you show included services, excluded services, reimbursables, and possible additional services as separate lists?"

This is not nitpicking. It is the difference between comparing real proposals and comparing vibes with price tags.

  • What is fixed-fee vs hourly vs as-needed?
  • What triggers additional services?
  • What is excluded: consultants, permit fees, interiors, renderings, bidding support, CA?
  • How are revisions billed if the budget forces changes?

Ask about exclusions before discounts

Discount hunting is usually the wrong move. Scope clarity first, fee negotiation second.

Ask: "What is not included that homeowners often assume is included?"

Exclusions are not automatically red flags. Silence is the red flag. A cleanly excluded service can be budgeted. A hidden service becomes a fight.

  • Structural engineering.
  • Survey and existing-conditions documentation.
  • Geotechnical, civil, arborist, or Title 24 work.
  • Permit fees and city resubmittals.
  • Interior design and procurement.
  • Bidding support and construction administration.

Ask who hires each consultant

Bay Area residential projects often need more than an architect. The question is not only which consultants are needed. The question is who hires them, who pays them, who coordinates them, and who checks their work against the drawings.

Ask: "Which consultants do you expect for this project, and which ones do you usually coordinate?"

Then ask the annoying but necessary follow-up: "Do I contract with them directly, or do they contract through you?"

  • Direct owner contracts can be fine.
  • Architect-managed consultant teams can be fine.
  • The bad version is when nobody knows who is responsible until the permit set stalls.

Ask for local permit realism, not promises

Do not ask, "Can you get this permitted fast?" It invites optimism. Ask about the actual review path.

Ask: "Have you permitted similar work in my city in the last one to two years? What happened?"

For Bay Area homeowners, the city matters. San Jose, Palo Alto, San Francisco, Berkeley, Mill Valley, Cupertino, and county areas do not behave like one generic permitting machine.

  • Planning review.
  • Building review.
  • Design review or discretionary approvals.
  • Fire comments.
  • Utility or drainage issues.
  • Tree, slope, or historic constraints.

Ask who answers city comments

Plan-check comments are normal. Planning comments are normal. Correction rounds are normal. What is not normal is discovering late that nobody budgeted for them.

Ask: "When the city sends comments, who responds, and how many response rounds are included?"

This question should produce a precise answer: included until permit issuance, included for one round, hourly after the first round, excluded if comments are caused by owner changes, or handled by a permit expediter.

  • If the city asks for technical clarification, who responds?
  • If the city asks for design changes, how are those billed?
  • If the owner changes scope during review, what resets?

Ask when budget becomes real

The Bay Area failure mode is painfully predictable: everyone loves the design, the drawings get heavy, the permit path advances, and then construction pricing arrives like a piano dropped from a window.

Ask: "At what point do you recommend builder or estimator input?"

Architects are not contractors, and most do not guarantee construction cost. That is fine. But they should be able to explain how they keep design ambition from outrunning budget reality.

  • Early contractor input.
  • Cost consultant review.
  • Alternates and scope reductions.
  • A smaller feasibility phase before full drawings.
  • A defined redesign rule if pricing comes back high.

Ask how many options you are buying

Homeowners often assume design includes endless options. It does not. More options mean more time. More time costs money.

Ask: "How many design options or layout directions are included in the proposal?"

This is not about limiting creativity. It is about protecting the relationship. If you want a deep exploration process, pay for it knowingly.

  • How many design options are included?
  • How many revision rounds are included?
  • What counts as owner-driven redesign?
  • When do additional services begin?

Ask what the drawings are for

Not every drawing set has the same purpose. A permit set is not always a pricing set. A pricing set is not always a construction set. A beautiful concept package is not a permit package.

Ask: "What will this drawing set be good enough to do: permit, price, build, or all three?"

The drawings should match your next decision. If the next decision is feasibility, you may not need full construction documents yet. If the next decision is hiring a builder, thin permit drawings may not be enough.

  • Permit set.
  • Pricing or bid set.
  • Construction document set.
  • Interior or finish package.
  • Clarification sketches during construction.

Ask about interiors before interiors become chaos

Interior scope hides in plain sight. Homeowners hear architect and assume lighting, cabinetry, tile, fixtures, furniture, and finish selections are handled. Sometimes they are. Often they are not.

Ask: "What interior decisions are included in your scope, and what should I plan to handle separately?"

No one wants to discover during construction that the owner is now the unpaid interior coordinator. That job is real, and it eats weekends for breakfast.

  • Lighting plans and fixture selection.
  • Cabinet elevations and appliance coordination.
  • Finish schedules and tile layouts.
  • Plumbing fixtures and hardware.
  • Procurement, ordering, substitutions, and tracking.

Ask about construction administration

Construction administration, often shortened to CA, is the architect's role after drawings are issued. It can include site visits, contractor questions, submittal reviews, clarification sketches, pay application review, change-order review, and punch-list support.

Ask: "Do you provide construction administration, and what does that include here?"

For complex work, deleting the architect from the construction phase can be false economy. Someone will answer field questions. If it is not the architect, it may be the contractor, the owner, or nobody until the mistake is installed.

  • Site visits.
  • RFIs and contractor questions.
  • Submittal reviews.
  • Change-order review.
  • Punch-list support.
  • Field clarification sketches.

Ask how communication actually works

A project can survive imperfect drawings more easily than it can survive chaotic communication. You need to know how the architect runs the work.

Ask: "Who will be my day-to-day contact, and how often do we meet?"

Also ask: "What do you need from me to keep the project moving?" Homeowners like to evaluate professionals, but owners create delays too.

  • Who is the main contact?
  • How often do meetings happen?
  • How are decisions tracked?
  • How are approvals documented?
  • What owner decisions are needed early?

Ask references about the boring stuff

Do ask for references, but do not ask only whether the finished project looked good. Ask the questions that reveal process.

The best reference call is not a testimonial hunt. It is a risk interview.

Ask whether the proposal was clear, what changed, how extra services were explained, how budget pressure was handled, how city comments were handled, and whether communication stayed organized.

Red flags worth taking seriously

A red flag is not a personality flaw. It is a project risk signal.

Be careful if the architect refuses to discuss budget early, cannot explain exclusions, treats city review as a formality, promises speed without naming constraints, dismisses consultants as minor details, avoids talking about construction administration, or makes the proposal sound complete while keeping the scope vague.

Good design matters. But a homeowner does not live inside a portfolio. You live inside the contract, the budget, the permit path, and the construction process.

Before you hire

Questions that expose the real scope

01

What problem are we solving first: design, approvals, cost, or documentation?

Different first problems need different first steps. Misfit starts here.

02

What will I physically have at the end of the first phase?

You are listening for nouns: plans, options, diagrams, consultant notes, budget checkpoints, city feedback.

03

What is included and excluded as a bullet list?

Narrative scopes are where surprises hide. Lists force clarity.

04

Which consultants do you expect, and who hires them?

Consultants are often separate fees. The expensive mistake is failing to assign ownership.

05

Have you worked with my city recently, and what review path do you expect?

Bay Area permitting is local. You want recent, specific realism.

06

Who responds to city comments, and how many rounds are included?

Cities comment. The question is whether response and resubmittal are budgeted.

07

When does construction pricing become real?

Beautiful drawings with brutal bids are not a strategy.

08

How many options and revision rounds are included?

Design exploration is real labor. Know what you are buying.

09

What interior decisions are included?

Lighting, cabinetry, fixtures, tile, and procurement can become a hidden second project.

10

Do you provide construction administration?

If the architect disappears after drawings, contractor questions become your problem by default.

Provider paths

Architect is one path, not the only path.

Use this as a routing map before outreach. The goal is not to avoid architects. The goal is to avoid buying the wrong kind of help first.

Path Best for Watch out Ask first
Licensed architect Custom homes, complex additions, hillside lots, design-led remodels, high-value projects Can be overkill for simple permit drawings or budget-first ADU work. Will you be architect of record, and what is excluded from your fee?
Residential designer Remodel layouts, additions with clear constraints, homeowner-friendly design help License boundaries matter; structural and code complexity may need architect/engineer support. Who signs, stamps, or coordinates the permit set if the city asks?
Design-build firm Owners who want one team handling design, pricing, and construction Less independent pricing leverage. The same team is designing and selling the build. When do I get a realistic construction number, and can I keep the plans?
Permit drawing team ADUs, garage conversions, as-builts, small additions, settled designs Not the same thing as a full architectural design process. What city comments do you handle, and what requires outside engineering?

FAQ

How many architects should I interview?

Three is usually enough if your brief is clear. If you are interviewing ten, the brief is probably the problem.

Should I ask for free design ideas?

No. Ask about process, constraints, and relevant experience. Free sketches are often expensive later because they skip the hard parts.

Should I ask for references?

Yes, but ask references about communication, budget handling, scope changes, and city comments, not just whether the final photos look good.

What is the biggest red flag?

A vague scope paired with confident pricing. That combo is how projects get stupid fast.

Should I choose the architect with the best portfolio?

Not by itself. Portfolio fit matters, but process fit matters more. The best portfolio in the world will not save a project with unclear scope, no budget checkpoints, and weak communication.

Find your path