Architects, Chefs and Operators: How to Brief Each Other

A hospitality design brief fails in a familiar way. The architect hears "warm, lively, modern". The chef hears "a proper pass at last". The operator hears "it has to seat sixty". Everyone nods, and drawings begin on three different briefs.

Write one brief around a described service instead of around adjectives. A busy Saturday night can be argued about, tested and drawn. A mood cannot.

Why do hospitality briefs go wrong?

They go wrong because the three professions use the same words for different things. "Efficient" to an architect may mean a clean plan. To a chef it means too many steps from fridge to pan. To an operator it means fewer people on shift.

Design is also often treated as a relay, with designers handing over and operators carrying on. One designer interviewed by Architecture & Design rejects that sequence and calls the process "a very collaborative effort between the client, the chef, the branding consultants and the designers". She adds that the brand lives on after the designer leaves, so the design has to support it over time.

If you are earlier in the process, our guide to restaurant concept development helps you settle the idea the brief will serve.

What is the right order to brief in?

Start with the decision about whether to build, then the brief, then the design. In the RIBA Plan of Work, a UK model many architects use, Stage 0 is strategic definition and Stage 1 is preparation and briefing. Stage 0 weighs options, budget and risk. Stage 1 records requirements in a project brief, covering project outcomes, sustainability outcomes and quality aspirations, and gathers site information before concept design starts.

You do not need to follow that model to borrow its logic. Settle whether the project is the right answer and what it should cost. Write the brief. Only then ask for a concept.

Skipping ahead is how a beautiful dining room ends up attached to a kitchen nobody can cook in.

What is a scenario brief?

A scenario brief describes one demanding service in numbers and movements, and asks every drawing to survive it. It replaces adjectives with a night.

Write it in one page:

1. The peak. Covers per hour in the busiest hour, split between dine-in, bar and takeaway.
2. The team. How many cooks, servers and runners at that peak, and who is the weakest link.
3. The plate route. From the pass to the table, and the dirty plate from the table to the dish room.
4. The guest route. Entry, waiting, bar, table, toilet, exit. Where do people queue?
5. The menu's demands. Heat, cold storage, ventilation, prep space, deliveries.
6. The thing that must not fail. One non-negotiable, such as a wood fire, a bar of a certain length or step-free access.

A brief that cannot be tested on a busy night is a mood board.

What should the chef and operator ask the architect?

Ask how the plan behaves at the peak, not whether it looks right. Five questions do most of the work:

• Show the route of a plate at 8:30 on a full Saturday. Where does it cross another route?
• Where will the dish room sit, and how far is it for the team clearing tables?
• What are the noise and heat consequences of the kitchen's position, including an open kitchen?
• What happens to staffing if we change this wall?
• Which elements can be value engineered without hurting the guest or the cook?

These are drawn from how practitioners describe their own work. One restaurant builder interviewed by Construction Digital analyses how guests and staff will move to reach tables, keeps the bar, dining room and kitchen clearly separate, and warns that an open kitchen should not be a central focus because it can send unwanted noise into the dining area. He also describes value engineering: finding lower-cost materials that look nearly identical, guided by which elements the client cares about most.

What should the architect ask the chef and operator?

Ask what the menu and the team actually need, and what the operator will really afford. The kitchen cannot be designed from a square-metre figure.

A commercial kitchen design guide from Rapids Contract lists what to define early: whether the space can realise the vision, whether to use traditional hoods or ventless equipment, the skill level of the crew, the service style from disposable ware to fine china, and whether the kitchen is built for quick turnover or a slower pace. Its workflow runs from the client's vision to a preliminary layout, then a drawing with the equipment list, client feedback and detailed mechanical, electrical and plumbing plans to confirm compliance.

Add three questions of your own:

• Which dish defines the menu, and what does it need that nothing else does?
• Which station has a single person, and what happens when they are off?
• What would you remove first if the budget fell by ten per cent?

Who decides what?

Agree decision rights before the first concept meeting. Most late arguments are really arguments about who had the last word.

Our guides to commercial kitchen requirements and restaurant interior design go deeper on the two sides of that table.

How do you keep the brief alive after sign-off?

Treat it as a test, not a document. Each time a design changes, ask whether the Saturday night still works.

Walk the plan with the people who will use it. The Construction Digital builder describes refining layouts by walking through the space with the client to improve efficiency and fix problem areas. Do this with the head chef and a server, not only the person paying. Keep a short change log with the reason for each change and who agreed to it.

Where do briefs usually slip?

Four slips recur.

• Briefing the architect alone. The chef arrives at the second review and finds the pass in the wrong place. Put the chef in the first meeting.
• Fixing the budget last. A brief with no number invites a design that cannot be built. State the range and what can flex.
• Copying a photograph. A reference image shows an outcome and hides the operation behind it. Pair every image with the service it implies.
• Forgetting the dull rooms. Storage, deliveries, waste and staff areas decide whether a venue runs smoothly. Give each a line in the scenario.

Key takeaways

• Write one brief together, around a described service, not around adjectives.
• Decide first whether to build and what it should cost, then brief, then design.
• Use a one-page scenario: the peak, the team, the plate route, the guest route, the menu's demands and one thing that must not fail.
• Chefs and operators should ask how the plan behaves at the peak; architects should ask what the menu and team need.
• Agree who decides what before concepts begin, and test every change against the scenario.