7 min read
28 questions · Lahav Meiri, licensed renovation contractor · Published 2 August 2026
The questions to ask an architect fall into five groups: choosing a practice, the process and the site, budget, the build itself, and the questions your architect will ask you. That last group is the one most people aren't ready for, because the answers have to come from you.
One thing worth knowing before you start: the last section isn't questions you ask. It's the questions your architect will ask you. That's the part most people aren't ready for.
Not just "residential" - homes at your scale, your budget, your kind of site. A practice that does mostly commercial work can still be excellent, but you want to know what you're getting.
In some practices the person who wins the project isn't the person who runs it. Worth knowing before you sign.
Structural engineer, surveyor, planning submissions, revisions past a certain point - these are often separate. Ask for the boundary in writing.
A good answer names the exclusions in writing. "We'll sort that out later" is not an answer.
Everyone has references from projects that went well. The useful one is where something went wrong, because it tells you how they handle pressure - and every build has a moment like that.
The useful one is where something went wrong
Most will answer with a list: survey, budget, references, and your brief. Worth asking early, because it's the one item on that list that only you can produce.
Concept, planning, technical drawings, tender, construction. You want to know what you'll be asked to approve and when.
Everyone knows late changes cost more. What's less obvious is the order - which decisions lock other decisions behind them. Ask which choices open doors and which close them.
Revisions are normal. Unlimited revisions are not. Find out where the meter starts.
Some architects supervise construction, some hand over and step back. These are very different services and they cost differently.
A good answer tells you exactly which service you're buying, and what it costs. Vagueness here shows up on site.
Height limits, setbacks, coverage, access. Before you fall in love with a shape, find out what's permitted - and who decides.
This decides where you'll want to eat breakfast and where you'll never sit. It's also one of the hardest things to fix later.
Slope, drainage, access for machinery, ground conditions. A difficult site can add a great deal before anything is built.
Ask it directly, early, and be ready for an uncomfortable answer. An architect who tells you the number doesn't work is doing you a favour.
A good answer gives you a number or a range, even an uncomfortable one. "It depends" means they haven't thought about your project yet.
Ask specifically whether it includes site works, foundations, fees, and finishes. The gap between a "build cost" and a "total project cost" is where most surprises live.
Ground conditions, utilities, code requirements. Ask what a sensible contingency looks like for a site like yours.
This question separates the decisions you can make later from the ones you can't. Most people find they've never ranked their own priorities - and the ranking is what makes the cut possible.
Some choices can wait until the walls are up. Others block everything behind them.
A good answer separates the two lists for you. If everything is urgent, nothing has been prioritised.
There's a difference between a weekly walkthrough and a phone call when something goes wrong.
Something always comes up. What matters is who decides, how fast, and whether it costs you.
Get the process in writing before you need it. A change agreed verbally on site is a dispute waiting to happen.
Snag lists, certificates, handover. Know what the last week looks like before you're in it.
Coming up: the questions they'll ask you.
The next section is the other half of that first meeting, and it's the half most people haven't prepared for. It matters more than it sounds: in a survey of a thousand people who built a new home, 88% wished they'd made different decisions, and the most common regret wasn't budget or quality. It was conflict over decisions.
Everything above is what you ask them. This is the part most people don't expect: the first meeting is mostly them asking you. And these are harder than they look.
Where do you eat on a normal Tuesday? Where does the mail pile up? Which room do you walk through and never stop in?
Easier to answer than what you want, and more useful. But "not enough space" isn't something anyone can design from - the question is what specifically fails, and when it fails.
A kitchen for hosting is a different room than a kitchen where two people cook together. Same request, two different designs.
A kitchen for hosting is a different room than a kitchen where two people cook together
Kids leaving. A parent moving in. Working from home. Getting older. You know your own life - the question is what it looks like as rooms.
This is the one that catches couples out. Not because they argue, but because the disagreement was never put into words - so it surfaces halfway through the build instead.
When was the last time you actually ranked them? The order is what survives a budget cut - and almost nobody has one before they're asked for it.
There usually is.
Can you answer these? Nestbrief works through them with you.
See how it works →Three quarters of these questions have answers someone else can give you - the architect, the builder, the planning office. The rest don't. They're yours, and they're the ones that decide what the house actually is.
Nestbrief asks you those questions one at a time, at home, at your own pace. When you say you want a bigger kitchen, it asks what for. When you're not sure, it helps you think it through instead of moving on. Nothing to prepare, nothing to fill in - you just talk.
This is what comes out of it:
One conversation, in your own time, and you arrive knowing what you want and why. On a project this size, it's the cheapest hour you'll spend.