01
People and routines
Who uses the place, what they do, and how those patterns may change.
Cedar & Line journal
Preparing an architecture brief.
A useful brief records how a place should work, what must be protected, and where decisions still need to be made.
Describe the life around the project.
Room lists are useful, but they do not explain why spaces need to connect, separate, expand, or change. Daily routines reveal more: who arrives first, where people gather, what needs quiet, and which activities compete for the same space.
The brief should also identify fixed constraints. Budget range, planning conditions, existing structures, access, programme, and decision responsibilities influence the design from the beginning.
It should distinguish confirmed requirements from preferences and open questions. That distinction helps a design team protect essential outcomes while testing more than one way to achieve them.
Brief essentials
Four useful starting points.
02
Site and constraints
Access, orientation, neighbours, planning conditions, and existing structures.
03
Priorities and limits
Budget range, programme, essential outcomes, and areas of flexibility.
04
Decisions and timing
Who approves work, what information is missing, and when decisions are needed.
Turn aspirations into decisions.
Words such as calm, welcoming, flexible, or sustainable are useful beginnings, but they need practical interpretation. Ask what visitors should notice first, which rooms must adapt, what can be retained, and where energy or material use matters most.
Priorities become clearer when trade-offs are discussed early. More area, better materials, shorter programmes, and lower budgets cannot always move together. Recording which outcomes are essential gives later choices a consistent basis.
Useful reference images should explain a principle rather than prescribe a finished appearance. Note whether each reference is relevant for its light, proportion, material character, circulation, or relationship to the landscape.
Keep the brief alive as knowledge grows.
A brief is not complete simply because design has started. Surveys, planning advice, cost information, and conversations with users will add detail and sometimes expose conflicts. The document should record those changes rather than leaving important decisions scattered across messages and meetings.
A simple decision log can identify what changed, why it changed, who agreed, and what other parts of the project are affected. This keeps the original purpose visible while allowing the response to become more precise.
The strongest brief is concise enough to use and specific enough to guide. It gives the team a shared reference for evaluating options throughout the project.
Template demonstration
Give every service a clear educational pathway.
This fictional article demonstrates practical thought leadership and a focused next action within the template.