Turning an early requirement into a buildable scope
A useful brief clarifies outcomes, constraints, interfaces, responsibilities, and the evidence needed to proceed.

An early project conversation rarely starts with every answer. A client may know the problem, the site or the intended use while the exact solution is still open. A useful brief turns that starting point into a shared understanding of what the project must achieve and what needs to be established next.
Describe the outcome before the solution
Start with the change the project should make possible. Is the aim to improve access, accommodate a new use, connect infrastructure or complete an existing building? Describe who will use the result and what successful operation would look like. This gives the team something to evaluate proposals against, rather than treating the first suggested solution as the only option.
Separate facts from assumptions
Collect the available plans, site information and known requirements, then identify the gaps. Distinguish a confirmed boundary from an approximate sketch, and an agreed deadline from a preferred date. An assumption is useful when it is visible and assigned for checking. It becomes a problem when it quietly turns into the basis for a price, design or commitment.
Define the boundaries of the work
Write down what is included, what is excluded and what depends on another party. Discuss the budget parameters, access restrictions, decision makers and any approvals that need to be established. These points do not all need final answers at the first meeting. They do need a place in the brief so the next proposal can state its basis clearly.
Agree the next decision, then develop the detail
The next step might be a site visit, a survey, a feasibility review or the development of a defined work package. Agree what that step must answer, who is responsible and what information it should produce. Revisit the brief as the project develops, recording changes and their implications. A buildable scope emerges through this process of clarification; an early wish list alone is not a construction instruction.
Questions to take into the next conversation
- What must the project enable, and for whom?
- Which information is confirmed, missing or assumed?
- What is the next decision, and what evidence will support it?
Further reading
RIBA — Briefing Template and Tracker


