Every architectural project begins with a conversation – between client and architect, idea and execution, vision and reality. That conversation is shaped, refined, and recorded in the form of a design brief.
An architectural brief is more than just a list of rooms or requirements. It’s a foundational document that outlines the project’s objectives, constraints, and aspirations.
Whether you’re designing a house, a public building, or preparing a student project, the brief sets the tone and direction for everything that follows.
Do you find design projects difficult?
...Remove the guesswork, and start designing award winning projects.
But writing a good brief one that’s clear, structured, and genuinely useful – isn’t always straightforward. What should it include? Who writes it? And how detailed does it need to be?
In this guide, we’ll answer all of that and more. You’ll learn:
- What an architectural brief is (and isn’t)
- What to include, step by step
- How to write one for your own project
- And we’ll give you a free downloadable checklist to help get started
Whether you’re a client, student, or practising architect, this is your complete reference for creating a meaningful and effective architectural brief.
What is an Architectural Brief?
At its core, an architectural brief is a structured outline of what a project needs to achieve. It brings together the client’s vision, the project’s practical requirements, and any technical, financial, or site-related constraints. It forms the foundation of the design process.
It’s not a fixed document either – at least, not at the start. The brief is typically developed and refined through early conversations, sketches, and research. As the project takes shape, so does the brief.
A Working Document, Not a Final Statement
In the early stages, the brief acts as a point of reference – a shared understanding between client and architect. It sets the scope of work, defines success, and establishes the key parameters that will guide every design decision.
And while it may start with the client, it’s almost always a collaborative effort. As site conditions are analysed, planning requirements reviewed, and ideas tested, the brief evolves alongside the design.
What a Brief Isn’t
- It’s not a detailed specification – that comes later.
- It’s not a list of solutions or pre-determined answers.
- And it’s not a one-size-fits-all template.
Instead, it’s a framework for exploration – a clear but flexible outline that balances what a client wants, what a site allows, and what the architecture can offer.
The Concept Kit
Discover the core components, principles, and processes to form the foundations of award winning work.
Have confidence in your design process.
Types of Briefs in Architecture
Not all briefs are created equal. Depending on the project stage, who’s writing it, and what it’s for, an architectural brief can take several forms. While the terminology varies, most can be grouped into two broad categories: the project brief and the design brief.
Understanding the distinction between the two is key to structuring your process – and communicating clearly.
Project Brief
The project brief sets out the overall aims, constraints, and deliverables of the project. It’s typically written early on – often before a designer is appointed – and serves as a strategic document for everyone involved.
It might include:
- The client’s goals and priorities
- The overall budget and timeframe
- Site location and ownership
- Statutory or planning requirements
- Procurement and delivery methods
- Key stakeholders and responsibilities
It answers the “what, why, and when” of the project. It doesn’t prescribe solutions – it defines the problem to be solved.
Design Brief
The design brief is usually more detailed, and focuses specifically on the requirements of the building or space itself.
It’s often developed with or by the architect – either from the original project brief, or through a separate client interview process. At this stage, broader ambitions are translated into spatial, technical, and functional requirements.
This might include:
- Room types and their relationships
- Performance requirements (acoustics, sustainability, accessibility)
- Aesthetic preferences and materiality
- Flexibility or future-proofing
- User experience goals
Where the project brief outlines intent, the design brief begins to define form.
Other Types
Depending on context, you may also encounter:
- Client brief – written by or on behalf of the client, outlining needs in their own words
- Internal/studio brief – used within architecture firms to guide concept development
- Academic brief – set by tutors or institutions for design studio projects
- Creative brief – occasionally used in marketing or branding-heavy projects to align vision
A strong project starts with a clear brief – but it’s rarely written in one go. The best briefs are shaped through conversation, research, and iteration.
What Should an Architectural Brief Include?
A well-structured brief doesn’t just describe what you want – it builds a foundation for clear communication, focused design, and smooth delivery.
Whether you’re writing it yourself or refining it with an architect, the following elements form the core of any effective architectural brief.
You don’t need to include every detail from day one – but the clearer you are from the outset, the more useful your brief will be.
1. Project Objectives and Vision
What is the purpose of the project? What’s driving it?
This might include:
- The core aims (e.g. more living space, a new studio, improved flow)
- Personal or business motivations
- Your long-term aspirations for the site or property
This section sets the tone – it helps keep decisions aligned with the bigger picture.
2. Site Information and Constraints
Describe the physical context of the project. This may include:
- Location and access
- Site boundaries
- Orientation and topography
- Trees, views, neighbouring properties
- Planning history or constraints (e.g. conservation area, listed status)
If you have a site survey or existing drawings, mention them here.
3. Spatial Requirements and Adjacencies
List the spaces you need – grouped by function, use, or level – and describe how they should relate to one another.
Examples:
- Bedrooms and bathrooms
- Kitchen, dining, utility
- Workspaces, studios, communal areas
- Storage, circulation, outdoor space
You don’t need to draw it – just describe the relationships. Adjacency diagrams and bubble diagrams can come later.
4. Budget and Cost Expectations
Outline your total budget (if known), including:
- Build cost
- Design and professional fees
- Contingency
- Planning and regulatory costs
- VAT and other taxes
If you’re unsure, be honest – but include something. It’s essential context for design decisions.
5. Programme and Key Dates
When do you want to start? And when do you need to finish?
This section could include:
- Key deadlines or events (e.g. move-in date, school term)
- Flexibility in timing
- Constraints like holidays or planning periods
6. Stakeholders and Decision-Makers
List everyone involved and what role they’ll play:
- Client(s)
- End users (e.g. staff, family, tenants)
- Funders or developers
- Planning consultants or technical advisors
It helps define who needs to be consulted – and who can sign off.
7. Regulatory and Planning Considerations
Include anything known at this stage:
- Planning status and relevant policies
- Access or sustainability requirements (e.g. Part M, BREEAM, Passivhaus)
- Party wall, rights of light, or restrictive covenants
This might be developed further after a site analysis or pre-app meeting.
8. Aesthetic and Material Preferences
Describe the look and feel you’re aiming for:
- Architectural style (modern, vernacular, minimal, etc.)
- Material choices (e.g. timber cladding, exposed brick, zinc roofing)
- Inspirational projects or reference images
- Likes and dislikes (even if vague)
If you’ve started a moodboard or Pinterest board, link to it here.
9. Sustainability and Performance Goals
Are there any specific sustainability targets?
This might include:
- Low-energy systems
- Renewable materials
- Lifecycle performance
- Energy efficiency, thermal comfort, or passive design principles
Even a simple statement here helps define design direction early.
10. Deliverables and Scope of Work
What are you expecting from your architect or designer?
Be clear about:
- Concept design
- Planning drawings and submissions
- Tender packages
- Site supervision and delivery
- Visualisations, models, or presentations
If you’re not sure, list what you think you’ll need – and ask your architect to help clarify.
How to Write an Architecture Brief (Step-by-Step)
Writing an architectural brief can feel daunting, especially if it’s your first time working with an architect. But it doesn’t need to be overly formal or complicated.
What matters most is clarity – expressing what you want to achieve, what you need from the space, and any constraints you’re working within.
Here’s a straightforward process you can follow, whether you’re a client writing it yourself, or an architect preparing it in collaboration with others:
1. Start with a Conversation
Begin by talking through the project goals. This might happen informally between client and architect, or as part of an internal team discussion. Ask questions like:
- Why is this project happening now?
- What problem are we solving?
- What would a successful outcome look like?
The answers to these questions will shape the rest of the brief.
2. Define the Key Parameters
Next, collect the hard facts. These form the skeleton of the brief:
- Site location and existing conditions
- Budget range (even if approximate)
- Key dates and programme constraints
- Planning or legal limitations
This section doesn’t need to be long, but it should be accurate and easy to reference.
3. Describe the Required Spaces and Uses
List out all the spaces you need, including:
- Room types and sizes (if known)
- How spaces should relate to one another
- Access, privacy, and natural light considerations
- Outdoor or circulation needs
Don’t worry about exact layouts at this stage – just focus on intent and relationships.
4. Add Design Preferences and Reference Projects
If you have strong views on materials, aesthetics, or inspiration, include them here. That might be:
- Photos of other buildings you like
- A rough Pinterest board
- Notes on what you want to avoid
The aim isn’t to dictate the design, but to provide useful context.
5. Outline Who’s Involved
Clarify roles and responsibilities. Who are the decision-makers? Who needs to be consulted? Who’s handling planning or approvals? Including this early helps prevent delays and miscommunication.
6. Draft, Review, Refine
A good brief is rarely written in one go. It often evolves over the first few weeks of a project, and sometimes longer. Don’t be afraid to review and update it as the design develops.
Tip: Use version numbers or dates so it’s clear what the latest version is.
7. Turn It Into a Working Document
Once agreed, the brief becomes a reference point for the whole team. It should be easily accessible, clearly formatted, and ideally included in any project documentation going forward.
Ready to put this into practice? In the next section, we’ll share a sample brief and a downloadable template to get you started. Let me know if you want that next.
Example Architecture Brief (Downloadable)
To help you get started, we’ve put together a sample architectural brief based on a typical small residential project. It’s written in clear, practical language and follows the same structure outlined above.
This example is designed to show you how the key elements of a brief come together in real terms – not just as a checklist, but as a working document that can be adapted to suit different types of projects.
Sample Brief – Residential Extension
Project Overview
The client is seeking to extend their existing 3-bedroom semi-detached house in South London to create additional space for a growing family. The key objectives are to provide a larger kitchen/dining area, a dedicated workspace, and improved access to the garden.
Site Details
- Location: South-facing rear garden in a suburban residential street
- Access: Through side gate; limited vehicular access
- Site constraints: Mature tree at boundary; neighbouring extensions on both sides
- Planning: Within a conservation area; single-storey rear extensions typical
Required Spaces
- Open-plan kitchen, dining, and informal living area
- Ground floor WC and utility cupboard
- Small home office with natural light
- Garden access via large sliding or folding doors
- Integration with existing layout and circulation
Design Preferences
- Contemporary aesthetic with clean lines and natural materials
- High-quality but durable finishes
- Timber cladding or brick to match surroundings
- Rooflights to bring daylight deep into the plan
- Strong visual connection to garden
Budget
£120,000 including VAT and contingency, excluding furniture and landscaping
Timeline
- Brief finalisation: March
- Planning submission: May
- Construction start: Ideally by October
- Completion: Spring the following year
Stakeholders
- Client: Homeowners (2 adults, 2 children)
- Architect: To be appointed
- Planning consultant: To be engaged if required
- Structural engineer: Required for load-bearing changes
- Party wall surveyor: May be needed depending on scope
👉 Click here to download it (PDF)
Common Mistakes to Avoid When Writing an Architectural Brief
Even with the best intentions, it’s easy to overlook key details or miscommunicate priorities when writing a brief – especially if it’s your first time.
Below are some of the most common pitfalls to avoid. Getting these right from the start can prevent frustration and costly delays further down the line.
Being Too Vague
Saying you want “more space” or “better light” is a useful starting point, but it won’t be enough to guide the design. Try to describe what that means in practical terms. More space for what? Better light in which room, at what time of day, and for what purpose?
Specifics lead to better design responses.
Jumping to Solutions
It’s tempting to suggest layouts, materials, or features you’ve seen elsewhere – but avoid getting too attached to early ideas. Your job in the brief is to describe the problem; the architect’s job is to explore solutions.
Instead of saying “we want a skylight here,” try: “we’d like more natural light in this part of the plan.”
Not Acknowledging Constraints
Every project has limits – budget, planning, access, existing structures. Being upfront about them early avoids disappointment and allows your architect to work with, rather than against, the conditions.
Constraints can lead to more creative outcomes if they’re clearly defined.
Forgetting Stakeholders
Who else will use the space? Who needs to approve decisions? Overlooking the needs or opinions of other users (family members, business partners, building managers) can result in changes mid-process – or worse, a design that doesn’t work for everyone.
Get these voices involved early, even informally.
Treating It as Final
A brief isn’t a fixed document. It should grow with the project, especially in the early stages. If new constraints or opportunities arise, the brief should reflect them.
Keep it accessible, editable, and referenced as part of the design process – not something written and then forgotten.
Conclusion
A well-written architectural brief doesn’t guarantee a great project – but it gives you the best possible chance of getting there.
It brings clarity to the process, aligns everyone involved, and helps ensure that what’s delivered matches what was needed. Whether you’re a client commissioning a home, a student starting a studio project, or a designer preparing for a new commission, the time spent crafting a good brief is never wasted.
If you’re not sure where to start, begin with what you do know: your goals, your constraints, and the spaces you need. Let the rest take shape as the conversation develops.
To help, we’ve created a free checklist you can download below. Use it as a starting point, adapt it to your project, and refine it as the design evolves.
Ready to write your brief?
Download the checklist, look through the example, and take it from there.
👉 Click here to download it (PDF)
Frequently Asked Questions
What should be included in an architectural brief?
At a minimum, it should include the project’s objectives, site information, space requirements, budget, timeline, aesthetic preferences, stakeholder roles, and expected deliverables.
What is the difference between a project brief and a design brief?
A project brief sets the scope and goals of the project. A design brief translates those goals into architectural requirements such as space planning, performance targets, and materials.
Can I write my own architectural brief?
Yes, especially on smaller projects. Many clients create their own brief or develop it with their architect. The key is clarity and being open to collaboration.
How long should an architectural brief be?
It depends. A small residential brief might be 2–3 pages. Larger or more technical briefs can be 20+ pages. Focus on usefulness, not length.
Who is responsible for writing the brief?
The client typically starts it, but it’s often refined with the architect during early design stages. On student projects, it may be set by the tutor.
