What to Bring to Your First Meeting with an Architect: A Homeowner's Checklist

Your first meeting with an architect is not a casual coffee chat. It's a working session — and how prepared you are directly affects how useful it is.

I've done hundreds of these initial consultations. The ones that go badly aren't the ones where the project is complicated or the budget is tight. They're the ones where the homeowner walks in without basic information and we spend most of the meeting just establishing facts that should have been gathered in advance.

The ones that go well? The homeowner comes in with documents, a rough number, honest answers to hard questions, and a sense of what they're trying to solve. We leave with a real plan.

Here's exactly what to bring — and what to be ready to discuss.

Documents to Bring

Property Survey

If you own the land already, bring a copy of your property survey. This is the legal document that shows your lot boundaries, dimensions, easements, and the location of any existing structures. Your title company provided one at closing — check your home purchase paperwork or contact the title company if you can't find it.

Why it matters: Setbacks, buildable area, and easement locations determine what can actually be designed before a single sketch is drawn. Your architect will reference this document constantly in the early phases.

Property Deed

Bring a copy of your deed or know your parcel number. This helps your architect pull up the official tax records, verify the legal description, and confirm zoning without relying on your memory of what the real estate listing said.

HOA Documents (If Applicable)

If your property is in a homeowners association, bring the CC&Rs (Covenants, Conditions, and Restrictions) and any architectural review guidelines. HOAs can impose significant restrictions on height, exterior materials, roof pitch, garage placement, and more — restrictions that can override local zoning.

I've seen homeowners spend months on designs that the HOA architectural review board rejected because nobody read the rules at the start. Twenty minutes with your CC&Rs before the first meeting can save months of redesign.

Existing Drawings (For Renovations)

If you're renovating an existing structure, bring whatever drawings you have — original construction documents, as-built drawings, permits pulled for prior work, anything. Even if what you have is incomplete, it's a starting point. Measuring and documenting an existing structure takes time and costs money; anything you already have reduces both.

Inspiration Photos

Bring 10–20 photos of buildings, spaces, or details that resonate with you — not necessarily the exact style you want, but images that capture something. A particular quality of light, a way an interior feels, an exterior material you keep coming back to.

These aren't a brief. They're a starting point for a conversation. The goal is to help your architect understand your aesthetic instincts quickly, so they're not designing toward a target they've had to guess at.

Budget: Be Honest About What You Can Spend

This is the part most homeowners dread. And I understand why — it feels exposing, like telling a car salesman exactly how much you have in your pocket.

But this framing misunderstands the relationship. Your architect isn't trying to extract money from you. They're trying to design a project that can actually be built. And they cannot do that without knowing your real number.

Don't give a range. If you have $500,000 to spend on construction, say $500,000. If you say "$450,000 to $550,000," a good architect will design to $550,000 because that's the only way to give you the full picture of what's possible. If you then build at $450,000 it will feel like a compromise — even though you set the range.

Be clear about what's included. Is your number the total project cost (land + construction + architect fees + landscaping), or just construction? Does it include furniture and finish fixtures, or just the shell? Different people define "budget" differently. Your architect needs to know which version you mean.

Share any financing constraints. If you're working with a construction loan, that affects the project phasing and timeline in ways an architect needs to account for from the start.

Questions to Have Ready

A good architect will ask you a lot of questions in this first meeting. But you should also come with your own list. Not because you'll necessarily get through all of them, but because formulating the questions helps you understand what you actually care about.

Strong questions to bring:

• What's your experience with projects like mine? (Scale, type, budget range, similar site constraints)
• How do you handle it when the design exceeds the budget? What's their actual process for value engineering?
• Who will be my primary contact? In larger firms, the principal you meet in the first meeting may hand the project off to a junior designer. Know this upfront.
• What does your fee cover, and what's extra? Structural engineering coordination? Interior design? Construction administration visits?
• What do you need from me to stay on schedule? Decision timelines, response times, document delivery.

For a complete list of questions that separate good architects from great ones, see our post on questions to ask before hiring an architect.

Photos of Your Property

If you're working on an existing property — whether a renovation or a new build on land you already own — bring photos. Lots of them.

What to photograph:

• Wide shots from all four sides of the lot or structure. The architect needs to understand the orientation.
• The street view — how the property sits in relation to the road and neighboring properties.
• Any significant features — a slope, a mature tree line, a view corridor, a problem drainage area, an existing structure you're working around.
• For renovations: every room, shot from each corner. Architectural photography it's not. But systematic coverage beats artistic angles when someone is trying to understand a space.
• Any existing issues — water damage, foundation cracks, drainage problems, anything you're already aware of.

You don't need professional photos. Phone camera is fine. Clarity and coverage matter; composition doesn't.

Timeline Expectations

Come prepared to answer: when do you need this done?

Be honest, and be specific. "As soon as possible" doesn't help anyone design a project schedule. "We need to be in the house by our daughter's first birthday in September" is actually useful information.

Also be prepared to hear that your timeline may not be realistic — and to have a real conversation about what that means. The architectural design process alone (before construction even starts) typically takes 6–12 months for a custom home. Permit review in many jurisdictions adds another 2–6 months. Construction is typically 12–18 months beyond that.

If you need to be in a house in 18 months, the answer might not be a custom new build. Your architect should be the one to tell you that clearly — and a good one will — but you need to give them your real constraints for that conversation to happen.

What the Architect Will Ask You

This is the part most homeowners don't think to prepare for. Your architect will come with questions too — and the quality of your answers shapes the project more than any document you bring.

Expect to be asked:

How do you live? Not abstractly — specifically. Where does your family gather in the mornings? Do you cook together or does one person cook while others stay out of the way? Do you work from home, and if so, how much acoustic separation do you need? Do you have kids, dogs, regular guests, a complicated schedule that needs a mudroom with storage for three different sports seasons?

What do you hate about where you live now? This is one of the most useful questions an architect can ask, and the most useful answer you can give. The best new homes are designed in direct response to the specific frustrations of the old one.

What do you love about where you live now, and want to keep? People often forget to answer this half. The architect needs to know what's working so they don't accidentally design it away.

What are your priorities if it comes down to trade-offs? Square footage vs. finish quality? Kitchen vs. primary suite? Views vs. privacy? Third bedroom vs. a better main living space? Every project involves trade-offs. Knowing your hierarchy in advance helps your architect make better decisions during design.

What's your risk tolerance for the unusual? Are you open to a design that's distinctive and unconventional, or are you building something that needs to be resellable in a traditional market? Neither answer is wrong. But they lead to very different buildings.

What a Good First Meeting Looks Like

By the end of a good first meeting, you should leave with:

• A clear sense of whether this architect is a real fit for your project and your personality
• A rough understanding of what your project might cost and how long it might take
• A list of any additional information the architect needs before they can scope the work
• A next step — either a follow-up meeting, a proposal, or a site visit

If you leave without knowing what happens next, ask before you walk out the door. The first meeting should always end with a concrete next step.

And if something felt off — the architect talked more than they listened, couldn't give you straight answers on fees or timeline, or seemed uninterested in your property constraints — trust that instinct. First meetings are data. Use them.

For more guidance on finding the right fit, see our post on how to find the right architect for your project.