Before you brief an architect: what actually needs to be in a design brief

I have sat in enough first design meetings to notice a pattern. The client has a folder of images, a rough budget, and a strong sense of what they don't like. What they usually don't have is a written account of how they actually intend to live in the building — and that gap is where the first draft goes wrong, not because the architect misunderstood the brief, but because there wasn't really one.

A brief is not a style exercise. It's a decision document. Its job is to force the trade-offs you'll eventually have to make anyway — budget against area, view against overlooking, open-plan against noise — to happen on paper, in an afternoon, rather than on site, in month nine.

Start with how you live, not how it looks

Before any image gets pinned, write down how the household actually functions. Who cooks, and do they want to be sociable while doing it or left alone. Where does post pile up. Where do muddy boots and school bags land. Does anyone work from home, and do they need a door that closes during a call. Is there a dog, and does it need a route to the garden that doesn't cross the kitchen.

None of this is glamorous, and none of it will appear on a mood board, but it drives room adjacencies far more than the finishes do. An architect working from a genuine account of daily life will produce a plan that survives contact with actually living in it. One working from a Pinterest board will produce something that photographs well.

Non-negotiables versus nice-to-haves

Separate the brief into two honest lists. Non-negotiables are the things you will not compromise on even if it costs more or takes longer — a downstairs bedroom for an ageing parent, a specific number of car spaces, a south-facing garden. Nice-to-haves are everything else, however much you want them.

The value of this split isn't philosophical. It's practical: when the budget doesn't fit the brief — and on a first pass it very often doesn't — the architect needs to know which items to protect and which to trim. Without the split, everything looks equally important, and the thing that gets cut is whatever is easiest to cut, not whatever matters least to you.

Say the budget number, and say it early

Clients sometimes hold the number back, worried that stating it invites a design that spends all of it. The more common outcome of holding it back is a design that has no relationship to it at all, and a much more painful conversation at tender stage when the two finally meet.

Give a real construction budget, not the headline figure that includes the plot, fees, furniture and a holiday afterwards. If you don't yet know what a realistic construction cost looks like for your project type and area, that's worth establishing before the brief, not during design — it's a much cheaper question to answer on paper than by redesigning a scheme that's already been drawn.

What gives first, if something has to

Most projects eventually face a moment where area, quality and budget don't all fit together, and one of them has to move. Decide the order of preference now, while it's an abstract question, rather than later, while it's an argument. Would you rather build smaller to the specification you want, or build the size you want and simplify the specification? Would you phase a garage or outbuilding to a later date rather than compromise the main house?

Writing this down doesn't bind you to it forever. It gives the architect a default to work to instead of guessing, and gives you something to refer back to when a decision has to be made quickly.

Site constraints you already know

If you've done proper due diligence on the plot, you already hold information the brief should carry forward rather than leave the architect to rediscover: designations, access and visibility splay requirements, tree root protection areas, known services runs, a sloping site's fall, flood zone status. A brief that states these up front saves a design iteration that would otherwise be spent finding out the hard way.

Use precedent images for feeling, not for literal copying

Reference images are useful for conveying atmosphere — light, material warmth, a sense of scale — but taken literally they can pull a design toward a house that doesn't suit your site, your orientation or your budget. Annotate what you actually like about each image rather than presenting it as "this, please": is it the ceiling height, the material, the way the light falls, or just that it looks finished in the photograph.

What a written brief should actually contain

• A room-by-room account of function, not just a room list — who uses it, when, and for what
• Non-negotiables, stated as non-negotiables, separately from preferences
• A real construction budget, stated as a number
• The order in which area, specification and budget give way if they conflict
• Site constraints already known from due diligence
• Precedent images annotated with what specifically is being referenced
• Anything already agreed with planners informally, or any pre-application feedback received
• A target timescale, including any hard deadlines (a tenancy ending, a school year)

What happens without one

Not disaster, usually — most architects will draw something and iterate. But every iteration costs a design fee and a chunk of the programme, and the iterations that come from an absent brief tend to be structural ones — room count, footprint, storey height — which are the expensive kind to change once drawn, and very expensive once built.