The architect's brief, in five minutes

Most architect’s briefs are written for the planning officer, not the kitchen designer. They describe the proposal in the language of policy compliance — the scale, the materials, the heritage context. The kitchen, when it’s mentioned at all, gets a sentence. Sometimes a fragment. The trick is reading what’s not said.

Here’s how to read a brief in five minutes and walk away knowing whether the project is worth a conversation, what the architect actually wants, and what you’d be expected to bring.

What the planning officer needs vs. what you need

The Design and Access Statement, the Heritage Statement, and the Planning Statement are written to a specific audience: the validation officer, the case officer, the conservation officer. They argue the proposal complies with local plan policy, NPPF paragraphs, and any relevant Article 4 direction. The kitchen is rarely the subject of that argument — it’s a consequence of the new space.

For the kitchen designer, the useful brief is buried inside the planning narrative. Look for: the relationship between the new kitchen and the existing rooms (open-plan, broken-plan, back-to-back), the orientation (south-facing glazing changes the appliance plan), the floor level (a step down to a new extension changes the entire layout), and the structural moves (new opening, retained chimney, removed wall).

The five lines that matter

Ninety per cent of what a kitchen designer needs from the brief lives in five recurring lines. They almost always appear, sometimes verbatim:

1. The principal use. Is the new space a kitchen, a kitchen-dining, a kitchen-living, or a kitchen-family room? The brief usually pairs “new kitchen” with one or two other functions. That pairing tells you the layout intent.

2. The connection. The brief describes how the new space connects to the existing house — through a structural opening, a glazed corridor, a retained wall with a doorway, an internal level change. Each option pushes the kitchen layout in a different direction.

3. The orientation and glazing. “Bifolds to the rear”, “sliding doors to the south elevation”, “steel-look glazing on three sides”. These tell you the run lengths and where the appliances can’t go.

4. The materials register. Heritage briefs name materials explicitly: stone, timber, lime render, lead, slate. Contemporary briefs usually say “steel-look frames” or “polished concrete floors”. The register tells you whether the homeowner is in the bespoke-joinery or the slab-island bracket.

5. The retained features. “The original chimney breast is retained”, “the existing cornice is to be made good”, “the herringbone parquet is to be lifted, repaired, and re-laid”. These are constraints. They shape what the kitchen can and can’t do.

Read those five lines, then close the document. The rest of the brief is planning-policy argument. It won’t change your kitchen specification.

What the brief almost never says

Three things you have to infer because the brief won’t tell you:

The budget. The brief never quotes a budget. The architect won’t share it on a first email either. You triangulate from the materials register, the heritage premium implied by the listing grade, and the floor area of the new build.

The timeline. Briefs say “subject to consent”. They don’t say when consent is expected, when the contractor is on site, or when the kitchen needs to be on order. You’ll get a date from the architect on the first call, and it usually moves twice before the install.

The decision-making. The brief is written by the architect, but the kitchen is chosen by the homeowner. The architect introduces. The homeowner decides. The brief gives you no signal about the homeowner’s appetite — you only get that by talking to the architect.

A working five-minute checklist

Open the Design and Access Statement. Find “principal use”. Find “connection”. Find “glazing”. Find “materials”. Find “retained”. Open the proposed plan drawing. Eyeball the kitchen footprint. Note the wall lengths.

That’s the kitchen brief. It takes five minutes once you know where to look, and it gives you everything you need to write the architect a one-paragraph note that demonstrates you actually read the application.