Choosing an architect is one of those decisions that can feel easier than it actually is. You look at a few portfolios, find a firm whose work you like, have a couple of conversations, and eventually someone sends over a proposal. At that point, it's tempting to focus on the number at the bottom and decide whether the designs are worth the fee. I'd look at it differently. You're not just hiring someone to draw your house. You're hiring someone who may influence the layout, budget, timeline, permits, consultants, contractor relationship, and dozens of decisions you'll make along the way. And the architect who creates the best-looking house isn't necessarily the architect who will be the best fit for your project. I've found that the more useful questions are the ones that reveal how an architect actually works. Who will handle your project? How do they control the budget? What happens when you change your mind? What happens when the contractor finds a problem? What's included in the fee—and what isn't? Those details rarely show up in a portfolio. They tend to show up six months later, when you're already committed. So before you sign an agreement, ask questions that go beyond “Can you design what I want?” Here are 12 questions that can tell you a lot about the architect you're about to hire—and what working with them will actually be like.
Our Methodology
We focused on the questions that reveal what it's actually like to work with an architect—not just the quality of their portfolio. We looked at relevant experience, scope and fees, communication, budget management, and construction involvement. We also considered how clearly an architect explains responsibilities, additional costs, revisions, and what happens when problems arise. The goal isn't to identify the “best” architect. It's to help you determine whether an architect's experience, process, and working style fit your project before you sign.
1. Have You Designed Projects Like Mine Before?
I'd ask this before getting too impressed by the portfolio. An architect can have a beautiful body of work and still not be the right person for your project. Someone who specializes in ground-up luxury homes, for example, may approach a 1950s renovation very differently from an architect who spends most of their time adapting existing houses.
So don't just ask, “How much experience do you have?” Ask: “Have you worked on projects similar to mine?” Then get specific. If you're planning a renovation, ask about renovations. If you're building on a steep lot, ask whether they've dealt with similar sites. If you're working with a tight budget, ask whether they've designed projects in that range. I'd also ask to see a few examples that are actually comparable, not just the firm's most impressive projects. Look beyond the portfolio. What you're really trying to find out is whether the architect has dealt with the kinds of problems your project is likely to create. For example, a complicated renovation can involve existing conditions that aren't obvious until walls come down. A difficult site can introduce drainage, grading, access, or structural issues. A historic property can come with a completely different set of constraints than a new build. An architect who has encountered those problems before isn't guaranteed to avoid them on your project. But they've at least had to solve something similar. I'd also pay attention to how they talk about those past projects.
If they can explain what made a project difficult, what changed during the process, and how they solved the problem, that's much more informative than simply showing you a finished house. The goal isn't to find an architect who has done your exact project before. It's to find one who has relevant experience with the problems your project is likely to present.
2. What Will You Actually Handle for Me?
This is one of those questions that sounds obvious until you realize how differently architects define their services. Ask an architect, “What do you handle?” and you might hear something like, “We take care of the entire design process.” That sounds reassuring. It also doesn't tell you much. Instead, walk through the project from beginning to end and ask what they are actually responsible for at each stage.
Will they handle the initial design? Construction drawings? Permit submissions? Engineering coordination? Contractor questions? Site visits? Construction administration? And, just as importantly, what aren't they responsible for? Don't assume “full service” means everything. An architect may be heavily involved during design but have little involvement once construction starts. Another may offer construction administration as part of the agreement. Another may provide it as an additional service. Those are very different arrangements. The same goes for permits. Saying “we handle permitting” could mean the architect prepares and submits the drawings. It could mean they communicate with the municipality throughout the review. Or it could simply mean they provide the documents you need to submit yourself. You want to know which one you're paying for.
Ask for the scope in plain English
I'd actually ask the architect to walk you through the entire process: “If I hire you today, what will you handle from our first meeting until construction is finished?” Then listen for specific responsibilities. You should come away knowing:
- ✓What happens during design
- ✓Who produces the construction documents
- ✓Who coordinates engineers and other consultants
- ✓Who handles permit-related work
- ✓Whether contractor selection is part of the service
- ✓Whether the architect visits the site during construction
- ✓Who answers contractor questions
- ✓What happens when something changes during construction
The important thing here isn't getting the longest list of services. It's getting a clear division of responsibility. Because when something goes wrong six months into a project, “I thought you were handling that” is not a particularly useful answer. Your contract should make clear who owns each major part of the process—and what happens when something falls outside the original scope.
3. Who Will Actually Be Working on My Project?
There's a small detail in the hiring process that can be easy to overlook: the person you meet isn't necessarily the person who will be doing the work. You might meet the principal architect, walk through your ideas together, see a few impressive projects, and feel confident that you've found the right fit. Then the project starts, and most of your day-to-day communication is with someone you've never met.
That's not necessarily a problem. Larger firms often have teams for a reason. But you should know how that team is structured before you sign. Ask: “Who will actually be working on my project day to day?” Then follow up. Who develops the design? Who produces the drawings? Who reviews the work? Who makes the major design decisions? And who do you contact when you have a question? The firm matters. The person matters too. There's nothing wrong with hiring a firm where the principal isn't involved in every drawing. In fact, having several people working on a project can be an advantage. You may get a senior architect's oversight along with the production capacity of a larger team. The issue is when you don't know what you're actually buying. If you hired the firm because you connected with a particular architect's design approach, find out how involved that person will remain once the contract is signed. I'd also ask what happens if the person assigned to your project leaves the firm or becomes unavailable.
It may sound like an uncomfortable question during an initial meeting. I'd still ask it.
Pay attention to the handoff A good transition from the initial sales conversation into the project should feel organized. You shouldn't have to explain your priorities from scratch to a new team member. The architect should have a process for transferring what was discussed during the initial meetings into the actual project. That includes things like your budget, priorities, must-haves, concerns, and decisions you've already made. Ultimately, you're not just hiring a firm's reputation. You're hiring a team that will spend months turning your ideas into a building. Know who that team is before you sign.
4. How Do You Approach the First Design?
I'd pay close attention to this answer because it tells you how the architect thinks, not just what they can draw. You probably already have ideas when you walk into the first meeting. Maybe you've saved a hundred photos, sketched a rough floor plan, or know exactly where you want the kitchen. That's useful. But those ideas aren't the design yet.
A good architect should be able to take what you've brought them and start figuring out why you want it. Maybe you say you want a bigger kitchen. What you actually need might be better circulation between the kitchen and dining room. Maybe you want more windows. What you're really after might be better morning light. Maybe you want an addition because you're running out of space. The better solution might involve changing the existing layout instead of adding another room. That's the kind of thinking you're paying for. Ask what happens after the first meeting I'd ask: “What does your design process look like after we give you our ideas?” You want to hear how they move from conversation to actual design decisions. Do they study the site first? Measure the existing house? Review zoning restrictions? Develop several concepts? Present options? Test the design against the budget? There's no single correct process. What matters is that there is a process.
Be careful if the answer jumps straight to drawings
Some homeowners love seeing sketches immediately. There's nothing wrong with that. But if an architect starts drawing before understanding the site, your priorities, your budget, and how you actually intend to use the house, you may end up refining the wrong idea. Early design should answer bigger questions before it gets buried in details. Where should the addition go? How should the rooms connect? What should happen to the existing structure? Where does the natural light come from? What are the major constraints? Once those decisions are right, the smaller decisions become much easier. The best first design conversation isn't necessarily the one where you leave with the most drawings. It's the one where you leave with a better understanding of what your project could actually become.
5. How Do You Keep the Design Within My Budget?
I'd ask this question early, not after the plans are finished. It's easy for an architect to create something you love when the budget isn't part of the conversation. The harder job is creating something you love that you can actually afford to build. And that's where you want to understand the architect's process.
Ask: “How do you keep the design aligned with my construction budget?” A good answer should go beyond “We'll keep an eye on it.”
Ask when the budget gets checked
Find out when construction costs enter the design process. Does the architect bring in a contractor early? Do they use cost estimates at different design stages? Do they work with a cost consultant? Or is the first serious pricing exercise done after the construction drawings are complete? That last approach can create an unpleasant surprise. You can spend months developing a design, only to discover that the project costs substantially more than expected. At that point, you're not making small adjustments. You may be removing rooms, changing materials, shrinking the footprint, or redesigning major parts of the house. The earlier you find out, the more options you have.
Ask what happens when the numbers don't work
This is the more revealing question: “What happens if the design comes in over budget?” You want to know whether the architect has a process for getting the project back on track. Maybe the answer involves changing materials. Maybe the floor plan gets simplified. Maybe the square footage comes down. Maybe a particular feature gets postponed. There isn't one right solution. What matters is that the architect is comfortable having the conversation before you've spent money building something on paper that you can't build in real life.
Don't confuse an estimate with a promise
One other thing I'd clarify: who is providing the cost estimate and what level of accuracy should you expect? Architects can design around a budget, but that doesn't mean an architect can guarantee what a contractor will ultimately charge. Labor rates change. Material prices change. Site conditions can reveal surprises. Contractors have different overhead and pricing structures.
The useful question isn't: “Can you guarantee this will cost $X?” It's: “How will you help me make design decisions that keep the project financially realistic?” That's a much more useful conversation—and one you want to have before the design gets too far down the road.
6. How Do You Charge, and What Isn't Included?
The fee is usually the first number homeowners compare. I wouldn't make it the first thing you judge. Two architects can quote very different fees for what appears to be the same project, but the difference may have less to do with what they charge and more to do with what they're actually agreeing to do. Start by asking: “How is your fee structured, and what services are included?”
Architects may charge a fixed fee, an hourly rate, a percentage of construction costs, or a combination of these. The structure matters, but the scope matters more.
Find the edges of the agreement
This is where I'd spend most of the conversation. Ask what happens if you need:
- ✓Additional design revisions
- ✓More meetings than expected
- ✓Changes after drawings are completed
- ✓Additional site visits
- ✓Permit resubmissions
- ✓Extra consultant coordination
- ✓Revisions requested by the contractor
- ✓Changes during construction
You don't need to assume these things will happen. You just want to know what happens financially if they do.
A proposal that says “architectural services: $X” doesn't tell you much if half the situations you're likely to encounter are treated as additional services.
Ask how additional work is billed
If something falls outside the original scope, is it billed hourly? Is there a separate fixed fee? Does the architect need your approval before doing the work? That last one is particularly useful. You don't want to discover a month later that several hours of work were added to your bill because everyone had a different understanding of what was included. I'd also ask for examples. “Can you give me a few examples of things that would normally fall outside this agreement?” It's a simple question, but it forces the scope to become concrete.
Don't automatically choose the lowest fee
A lower architectural fee can be a good deal. It can also mean you're comparing a limited scope against a much more comprehensive service. For example, one architect might include permit coordination and construction administration while another stops after producing the construction documents. Their fees shouldn't be compared as though they're selling the same thing.
The number matters. But the scope behind the number matters more. Before you sign, you should be able to explain—in plain English—what you're paying for, what you're not paying for, and what could cause the fee to increase.
7. How Many Design Changes Are Included?
At some point, you're going to change your mind. Maybe you see the first floor plan and realize the kitchen isn't where you want it. Maybe you decide that the home office should become a guest room. Or maybe you live with the design for a few weeks and discover that something that looks good on paper doesn't make sense for the way you actually use the house.
That's normal. The important question is what happens when you change your mind? Ask: “How many rounds of revisions are included in your fee?” And don't stop there. Ask what the architect actually considers a revision.
Not every change is the same
Moving a door a few feet is one thing. Deciding to move the kitchen to the other side of the house after the floor plan has already been developed is something else. That's why phrases like “reasonable revisions” aren't particularly helpful unless you understand what they mean. Ask the architect to give you examples: “What would be considered a normal revision, and what would be considered a change in scope?” That answer can tell you a lot about how they work with clients.
Find out when revisions become expensive
You should also ask at what point additional fees begin. Is there a certain number of design rounds included? Does the fee change once you move into construction documents? What happens if a revision requires the architect to redo work that has already been completed?
These details matter because design changes become more expensive as the project moves forward. Changing a floor plan during early concept development is relatively easy. Changing it after detailed drawings, structural coordination, and engineering are complete can affect several parts of the project at once. That's why a good architect should encourage decisions at the right time—not because they don't want you to make changes, but because late changes have consequences. These details matter because design changes become more expensive as the project moves forward. Changing a floor plan during early concept development is relatively easy. Changing it after detailed drawings, structural coordination, and engineering are complete can affect several parts of the project at once. That's why a good architect should encourage decisions at the right time—not because they don't want you to make changes, but because late changes have consequences.
Don't be afraid to ask about your own decision-making
I'd also ask: “What do you need from me, and when?” Architects aren't the only ones who can slow a project down. If you're taking three weeks to approve every design decision, the project can sit still regardless of how responsive the architect is. Understanding when you'll need to make decisions helps you plan for the process. The goal isn't to eliminate revisions. It's to understand how revisions work before you discover their cost after the fact.
8. Who Handles Permits and Code Issues?
Permitting is one of those parts of a project that sounds straightforward until the plans go in and someone at the municipality comes back with a list of comments. That's why I wouldn't settle for an answer like, “Yes, we handle permits.” I'd ask what that actually means. “Who prepares the permit submission, who communicates with the building department, and who handles revisions if the plans come back with comments?”
Those can be three different responsibilities.
Find out where the architect's responsibility ends
In some projects, the architect prepares the drawings and submits the permit package. In others, the architect may handle the submission and communicate with the municipality throughout the review. And in some arrangements, the homeowner or contractor may be responsible for parts of the process. None of these approaches is automatically wrong. The problem is not knowing which one you're signing up for. I'd also ask about zoning. Building-code compliance and zoning compliance aren't always the same thing. A project can have perfectly good construction drawings and still run into issues involving setbacks, lot coverage, height, parking, use, or other local requirements. If your project has unusual site or zoning conditions, you want to know how the architect deals with those issues before the design gets too far along.
Ask what happens when the city says no
This is the part people often forget to ask. “If the permit reviewer requires changes, is that work included in your fee?” You should know whether responding to ordinary plan-review comments is included, how many rounds are covered, and what happens if the municipality requires a substantial redesign.
Again, the goal isn't to predict every possible problem. It's to understand who owns the problem when one appears.
Don't assume the permit means the project is fully approved
I'd also clarify what the architect's permit work actually covers. A permit approval doesn't mean every construction issue has been eliminated. Contractors can still run into field conditions, questions, or discrepancies once work begins. That's why the permit conversation should connect back to the larger scope of services. Who answers questions during construction? Who updates drawings if something needs to change? Who communicates with the contractor? The more clearly those responsibilities are defined upfront, the fewer surprises you're likely to have later. You don't need your architect to promise that permitting will be painless. You need them to tell you exactly what they're responsible for when it isn't.
9. How Do You Work With the Contractor?
This is a question I'd ask even if you haven't chosen a contractor yet. The architect and contractor have different jobs, but the project works best when they can actually work together. Once construction starts, there will be questions. A dimension may need clarification. A material may not be available. The contractor may find something in the existing structure that wasn't visible in the drawings. You want to know what happens when that occurs.
Ask: “How involved are you once construction starts, and how do you handle questions from the contractor?”
Find out who answers when the drawings aren't enough
A contractor will inevitably have questions. Who answers them? Does the contractor contact the architect directly? Does everything go through you? Does the architect review requests for information? Are responses documented? The same applies to proposed substitutions. If a specified material isn't available, for example, the contractor may suggest an alternative. Someone needs to determine whether that alternative actually works with the design. That doesn't necessarily mean the architect makes every construction decision. It means you should understand where their responsibility begins and ends.
Ask about change orders
This is another area worth discussing before construction starts. Ask: “What is your role when the contractor proposes a change that affects the design or cost?” You want to know whether the architect reviews the change, helps evaluate alternatives, updates the drawings, or simply passes the information along to you. And if additional architectural work is required, ask whether that falls within your existing agreement.
Don't confuse coordination with supervision
There's an important distinction here. An architect can visit the site, review construction progress, and respond to contractor questions without being responsible for supervising the contractor's workforce. The contractor is generally responsible for actually managing construction means, methods, workers, and day-to-day site operations. Knowing that distinction matters.
If you assume the architect is watching every detail because they make periodic site visits, you may have expectations the architect never agreed to meet. So don't just ask whether they'll be involved during construction. Ask what that involvement actually looks like. The best arrangement is one where everyone knows who is responsible for what before the first wall is built.
10. How Often Will You Be on the Job Site?
This is one of those questions where the answer can sound better than it actually is. An architect might tell you, “We'll be involved throughout construction.” Great. But what does “involved” mean?, Ask: “How often do you typically visit the site during construction, and what are you looking for when you’re there?” The frequency matters, but the second part matters more.
A site visit isn't a construction inspection
An architect may visit the project to observe whether construction generally appears consistent with the design, answer questions, review details, or discuss issues with the contractor. That doesn't necessarily mean they're inspecting every piece of work. The contractor still has responsibility for construction, workmanship, job-site safety, and the means and methods used to build the project. That distinction is worth understanding before construction starts. Otherwise, you can end up assuming someone is checking something that was never part of their responsibility.
Ask what happens after the visit
I'd also ask what you actually receive from those visits. Does the architect send a site report? Are issues documented? Are questions from the contractor followed up in writing? Are drawings updated when necessary? You don't necessarily need a formal report after every visit. But you do want some way of knowing what was observed, what needs attention, and who is responsible for the next step.
Ask how construction issues are handled
This is where site involvement becomes particularly valuable. Imagine the contractor opens up a wall and discovers something that wasn't visible during design. Or a structural condition turns out to be different from what everyone expected. Or a detail in the drawings doesn't work once the materials are actually in front of the crew. Those situations aren't necessarily signs that someone did a bad job. Existing buildings hide things. Materials change. Construction rarely follows a perfectly straight line. What matters is how quickly and clearly the team responds. Ask your architect: “If something unexpected comes up on site, how do you typically handle it?” Their answer will tell you more than simply knowing whether they visit once a week or once a month. Because during construction, you're not really paying for someone to stand on the job site. You're paying for someone who knows when a problem needs attention, who needs to make the decision, and how that decision gets back into the project.
11. What Usually Goes Wrong on Projects Like This?
This might be my favorite question on the list because it takes the conversation somewhere most interviews don't. Instead of asking an architect to tell you why they're good, ask them to tell you what tends to go wrong. Try: “What are the most common problems you see on projects like mine?” Then follow it with: “How do you usually prevent those problems?” You may learn more from those two questions than from another 30 minutes of looking through finished projects.
Every project has friction
Even well-run projects run into problems. A client changes their mind. A permit takes longer than expected. The contractor discovers an unexpected condition. A material becomes unavailable. A project costs more than originally anticipated. The useful question isn't whether your architect can promise that none of these things will happen. They can't. What you want to understand is where they expect problems to appear and what they do when they do. An architect who immediately mentions budget changes, slow client decisions, permitting delays, or coordination issues is giving you something useful. They're showing you that they've actually thought about the messy parts of the job.
Listen for specifics
Compare these two answers. “Communication is really important to us. We try to stay on top of everything.” Versus: “On renovations, the biggest issue is usually discovering conditions we couldn't see during the initial survey. We try to reduce that risk by documenting the existing house carefully and identifying areas where we need to investigate further before finalizing the drawings.” The second answer tells you something. It identifies a real problem, explains why it happens, and describes a process for reducing the risk. That's the kind of answer I'd pay attention to.
Then turn the question back to your project
Once the architect gives you an answer, ask: “Do you see any of those risks in my project?” Now you're no longer having a generic interview. You're talking specifically about your house, your site, your budget, and your plans. And if the architect raises a concern you hadn't considered, that's not necessarily a reason to walk away. In fact, it can be a good sign. You want someone who can spot problems before you have to pay to fix them. The red flag isn't an architect who tells you things could go wrong. It's one who makes the project sound so easy that nothing apparently could.
12. Can I Speak With Recent Clients?
At this point, you should have a good sense of the architect's experience, process, fees, and involvement during construction. Now I'd ask for something you can't get from the architect themselves: Talk to someone who has actually been through the process with them., Ask: “Can you put me in touch with a few recent clients whose projects were similar to mine?” The word recent matters. A firm may have completed an impressive project five or ten years ago, but the people who worked on it may not represent the team, process, or experience you'll get today. I'd also look for projects that resemble yours. A homeowner who built a new $3 million house may have a very different experience from someone who hired the same architect for a renovation.
Don't ask clients whether they liked the architect
Ask better questions. For example:
- ✓Did the architect stay within the agreed scope?
- ✓Were additional fees clearly explained?
- ✓How responsive were they?
- ✓Did they listen when you disagreed with something?
- ✓How did they handle problems?
- ✓Were there any surprises during the project?
- ✓How involved were they during construction?
- ✓Did the project stay reasonably close to the original budget?
- ✓What do you wish you'd known before hiring them?
- ✓Would you hire the architect again?
That last question is useful, but I wouldn't make it the only one. Most people can tell you whether they liked someone. You're trying to understand what it was actually like to work with them.
Pay attention to what clients hesitate to say
You don't need every reference to give you a glowing review. In fact, a client who says, “The design was excellent, but we wish we'd understood the additional-service fees better,” may be giving you more useful information than someone who says everything was perfect. The point of references isn't to prove that the architect has never had a difficult project. That's unrealistic. You're looking for patterns. If several former clients independently mention that the architect communicates well, handles problems calmly, and is clear about fees, that's meaningful. If several mention slow communication, unexpected charges, or limited involvement during construction, pay attention to that too.
And ask why the architect gave you those references
If possible, ask the architect: “Why did you choose these clients as references for me?” Their answer can tell you how well they understand the similarities between your project and theirs. A good reference isn't just proof that someone was happy. It's evidence that the architect has successfully managed the kind of project you're about to undertake.
Conclusion
After asking all 12 questions, you should have more than a sense of whether you like the architect. You should understand how the project is going to work. That's the part I'd pay the most attention to. A great portfolio tells you what an architect can design. It doesn't tell you how clearly they communicate, how they handle budget pressure, what happens when you change your mind, or how involved they'll be once construction starts. Those things tend to matter a lot more once you're several months into the project. Look for clarity, not perfect answers You don't need an architect who tells you that everything will go smoothly. In fact, I'd be a little skeptical of that answer. Residential projects have too many moving parts for that. Existing conditions can surprise you. Permits can take longer than expected. Prices can change. Contractors can uncover problems. You may change your mind. What you want is an architect who can explain how they'll deal with those situations. Good answers tend to be specific. You should understand what the architect will do, what they'll charge, what they won't handle, who you'll work with, and what happens when something changes. If the answers stay vague, keep asking. The contract should confirm the conversation There's one final step I'd take before signing: go back through the agreement and make sure the important answers you received are actually reflected in it. If the architect told you that permit coordination is included, look for it in the scope. If they said they'll visit the site during construction, find out how that service is defined. If they explained that additional design work is billed separately, make sure you understand the rate and approval process. A good conversation is useful. A clear contract is what protects the understanding you reached during that conversation. And that's really what these 12 questions are designed to help you do. You're not trying to find the architect who gives the most impressive presentation. You're trying to find the one whose experience, process, communication style, scope, and expectations make sense for your project. Because you're going to spend a lot more time working with this person than you will looking at their portfolio. Make sure you know what that working relationship actually looks like before you sign.
