Begin with an ordinary day
A project often begins with an image: the atmosphere of a restaurant, the warmth of a café, the quiet confidence of a workplace. Images are useful. They give a conversation somewhere to start. A project brief takes that first impression further by describing the people, activities and decisions behind it.
Before discussing finishes, describe an ordinary day in the future space. Who arrives first? Where do deliveries go? What happens when several people need the same counter, meeting room or entrance? Follow the day through to cleaning and closing. These small observations give a beautiful reference image a practical context.
Separate the essential from the preferred
Write down what the project must support, then distinguish it from what would be welcome. A restaurant may need a clear route between preparation and service before it needs a particular decorative feature. A café might value flexible seating more than a fixed arrangement that photographs well. The brief should make those priorities visible.
A short list is easier to use than a catalogue of aspirations. Give each priority a reason: seating that can change because group sizes vary; a durable counter edge because bags and equipment regularly pass it; a quieter room because private conversations are part of the working day. Reasons help the team assess alternatives without losing the original intent.
Give references a caption
Choose a few images and explain what matters in each. Is it the light, the relationship between materials, the spacing of furniture or the feeling of arrival? A picture without a caption can carry several different interpretations. Naming the quality you want makes it easier to discuss how that quality could belong in your own project.
Include observations about the existing site alongside these references. Record what is already known, what needs measuring and what remains uncertain. Separate confirmed information from assumptions. A question clearly marked for investigation is more useful than an untested assumption presented as a requirement.
Make decisions visible
A useful brief also names who will review the work, who will make decisions and how comments will be gathered. Several separate streams of feedback can pull a project in different directions. Agree on one consolidated response at each review so the next step begins from a shared position.
Record timing, spending priorities and any dates that are genuinely fixed. Where something is flexible, say so. Avoid presenting every wish as equally urgent. Keep a simple decision record with the choice, its reason and the people who confirmed it; update the brief when the project changes.
Leave with a document people can use
The first brief does not need to answer every technical question. It needs to describe the intended experience, the everyday operation, the priorities and the open questions well enough for the next conversation to be productive.
Before sharing it, ask someone unfamiliar with the project to read it. Can they explain what the space is for and what matters most? If they can, the brief is beginning to do its job: giving everyone a clear point of reference before the first detail is drawn, selected or built.
A clear brief connects every preference to a purpose.
Ideas from Constructive Method.
From an idea to your project
Which of these decisions belongs in your next brief? Bring your questions, references and requirements into the conversation.
Discuss your project