How to Communicate With Your Architect: A Practical Guide

Most problems on architectural projects don’t start with a bad design. They start with a misunderstanding — something that seemed clear in a meeting but was interpreted differently on paper.

As an investor building a home, you’re entering a professional relationship where the other side speaks a technical language you’re still learning. That asymmetry creates risk. Here’s how to manage it.

---

Start with a brief, not a mood board

Before your first meeting, write down what you need — not what you like.

A brief includes:

• Number of rooms and their required sizes
• How you actually live (morning person or night owl? work from home? host often?)
• Non-negotiables (ground-floor bedroom, south-facing garden, separate entrance)
• Budget — including contingency, not just the “aspirational” number
• Timeline constraints

A mood board of pretty houses is helpful context. But an architect can’t design to a mood board. They need requirements.

---

Distinguish between decisions and concerns

You’ll have moments where you’re not sure about something but don’t want to seem difficult. Push through that instinct.

Decisions are irreversible choices that need to be logged in writing: “We decided to extend the kitchen by 2m to the east.” If it’s a decision, email it. Don’t rely on a verbal agreement in a meeting.

Concerns are things you’re worried about but haven’t decided: “I’m not sure the bathroom will feel big enough.” Raise these as questions, not demands. Let the architect respond before you escalate.

The mistake most investors make: they turn a concern into a decision under stress, which creates a ripple of changes that takes weeks to resolve.

---

Ask for stage summaries in writing

After any significant meeting or milestone, ask your architect for a brief written summary of what was decided, what’s pending, and what’s next.

This doesn’t need to be formal — a short email is fine. But it creates a shared record that both sides can refer to.

If your architect uses a project management tool like ArchFlow, you may already have this: stage completion notes, files, and a message thread all in one place.

---

Understand what’s included in your contract

Revisions after a stage is approved are usually chargeable. Before you approve any design stage, understand:

1. What does “approval” mean? (Do you sign something?)
2. How many revision rounds are included?
3. What triggers an additional fee?

Some investors approve stage 2 verbally in a meeting, then come back two weeks later with major changes — and are surprised by the invoice. Read your contract before you sign off.

---

On site: let the architect do their job

During construction, your architect will make periodic site visits. Resist the urge to be there for every one of them and give instructions directly to the contractor.

Here’s why: the contractor works from the architect’s drawings and takes direction from the architect. If you instruct the contractor directly and it creates a conflict, you now own that conflict — and its cost.

If you see something on site that concerns you, call your architect. Don’t ask the foreman to fix it without the architect’s sign-off.

---

When things go wrong

If you have a concern — design, timeline, cost, quality — raise it early. The longer you wait, the fewer options you have.

A good structure for a difficult conversation:

1. State the specific issue (“The window position in the bedroom doesn’t match what we discussed”)
2. Share the impact (“It means no afternoon light, which was important to us”)
3. Ask what the options are (“How do we solve this?”)

Avoid accusations and generalisations. Specific, solution-oriented communication gets faster results.

---

Architectural projects run over time and over budget most often when communication fails. The good news: most of the fixes are simple. Write things down. Ask questions early. Let professionals do their job.