Eastern Ontario Residential Design · Preparing for Concept Design

Design Brief Primer

How to describe what, why, and who, leave the how to us

You have an idea for your home. Maybe it's a new room, a renovation, or a way to make your house work better for how your family actually lives. The Design Brief is how you get that idea out of your head and into a form your design team can work with.

This page shows you exactly how to do it - no construction experience required.

What is a Design Brief, and why should you be excited about writing one?

Here's something most people outside the construction industry don't know: the reason some renovation projects feel smooth (and most don't) often comes down to a single document that gets skipped. It's called a Design Brief.

A Design Brief is a short document (typically three to five pages) that describes your project's who, what, where, and why. Not the how. The how is what your architect, engineers, and contractors will figure out once the concept is agreed upon. Right now, your job is to describe the problem you're solving and the life you want to live in your own words.

Think of it the way you'd think about planning a family trip. Before you book anything, you need to know: Where are we going? How long are we staying? What's the budget? Who's coming? What does everyone want to do? You wouldn't book flights, hotels, and activities without answering those questions first, because you'd end up somewhere nobody wanted to be, spending money nobody agreed to spend.

A Design Brief is that planning conversation, written down. Without it, the workflow between start and finish begins to resemble a tangled mess of string rather than an orderly progression marked by clear milestones. With it, every person on your project (designer, builder, engineer) is reading from the same page you are.

The exciting part? This is the stage where your project stops being a daydream and starts becoming real. Every decision that follows, from the layouts, the materials, the construction documents, the permit, they all build on what you write here. You're not filling out paperwork. You're laying the foundation for your project's success.

You don't need to get it perfect. A Design Brief is a living document. You'll start it, your design team will help you refine it, and it will evolve as the project develops. What matters right now is getting your ideas out of your head and onto paper so the conversation can move from imagination to action. Start with what you know. The concept design process will fill in the rest.

Check out the free Design Brief Workbook for you to download.

Seven conversations that build your Design Brief

Below is a template you can use, not as a rigid form, but as a guided conversation with yourself and your family. Some sections will feel easy. Some might need a kitchen-table discussion with your partner. That's not a problem; that's the process working. Getting everyone aligned now is far cheaper than discovering disagreements three rounds of revisions into concept design.

There may be sections that don't apply to your project, and you might think of things that aren't covered here. If so, add them. The more context your design team has, the better the concept options will be.

1

The big picture: what is this project, and why?

Start with a plain-English summary: what you're hoping to do, where it is, and the key features or outcomes that matter to you. If you can describe it to a friend over coffee, you can write this section.

Then, and this is the part most people skip, describe the problem this project will solve. Not "we want a renovation" (that's a solution, not a problem). The problem is the thing that made you pick up the phone in the first place. Maybe it's that your parent can't safely manage the stairs. Maybe it's that your kitchen was designed for a couple, and you're now a family of five. Maybe it's that your backyard space is unusable half the year.

Name the problem in one or two sentences. This becomes the anchor for every design decision that follows, and when the project gets complicated (it will), you'll come back to this sentence to make sure you're still solving the right problem.

Questions to start with

  • In one paragraph, what are we doing and where?
  • What triggered us to start thinking about this project?
  • What isn't working about how we live in this house right now?
  • If we do nothing, what happens in one year? In five?
  • If we could fix only one thing, what would it be?

Involve the whole household

Get everyone who lives in the house involved. Your teenager's frustration about sharing a bathroom is just as valid a design input as your concern about the heating bill. The best briefs capture the whole household's reality, not just the person filling out the form. Think of it like planning a family holiday; everyone's needs should be on the table.

2

How do you want to live in this space?

This is the heart of the brief, and the part that matters most to your designer. Your architect can figure out beam sizes, insulation values, and code requirements. What they can't figure out without your help is that you want to see the kids in the backyard while you're cooking dinner, or that your partner needs a quiet space to work from home that isn't the bedroom, or that your aging parent values dignity and independence more than square footage.

Describe your daily routines. Describe your weekends. Describe what drives you crazy about the current layout. Describe how you entertain. This isn't fluff, it's the raw material that concept design is built from. Your designer is creative, but they're not telepathic. The more clearly you can describe how you actually live, the better the concepts will fit.

Questions to ask yourselves

  • Walk through a typical weekday morning; where does it get crowded or frustrating?
  • Where does the family naturally gather? Where do people go to be alone?
  • How do you entertain: formal dinners, casual barbecues, rarely, constantly?
  • What do you love about this house? What made you buy it in the first place?
  • What rooms or spaces in other people's homes have you envied, and why?
  • Are there accessibility needs now, or ones you should plan for in the future?

Start a visual folder

Start a shared photo folder (Google Drive, Pinterest) or even a group text thread. When you see a room, a material, or a detail you love, save it with a one-line note about why you like it. "I like this because the kitchen feels open to the living room" gives your designer more to work with than the photo alone. A brief with good pictures is much easier for any design professional to interpret, especially when each image comes with a reason for why you selected it.

3

What must the project include? What would be nice to have?

Now we get practical. List the rooms, spaces, and features you need. Then separate them into two categories: must-haves (the project fails without them) and nice-to-haves (you'd love them, but you'd give them up if the budget required it).

This distinction saves enormous time during concept design. It tells your designer where to protect scope and where there's room to flex. Without it, every feature looks equally important, and when the budget forces a trade-off (it usually does), nobody knows what to cut. Include design preferences here too: materials you love, styles you're drawn to, things you know you don't want.

Questions to ask yourselves

  • How many bedrooms, bathrooms, and living areas do you need?
  • Do you need dedicated space: home office, laundry, mudroom, studio, workshop?
  • What about outdoor connections: a deck, patio, screened room, or three-season space?
  • Are there storage requirements your current home doesn't meet?
  • For each item: is it a must-have or a nice-to-have?
  • Are there materials, architectural styles, or finishes you know you want (or don't)?

Describe the need, not the solution

Resist the urge to design it yourself. Write "a space for two people to work from home simultaneously," not "convert the dining room into an office." When you prescribe the solution too early, you close doors your designer might have opened. Your job is the what and the why. The how is what concept design is for, let the design team bring you options you haven't imagined yet.

4

What's your budget range, and when do you need the project completed?

This is the conversation most people avoid, and it's the one that matters most. The budget constrains the design, not the other way around. If your design team doesn't know what you can spend, they'll produce concepts that may be beautiful but unbuildable within your means. That wastes their time and yours.

You don't need an exact number. A range is fine: "We're comfortable between $120,000 and $160,000" gives your designer enough to realistically calibrate your options. What doesn't work is "we'll worry about the budget later", because by the time "later" arrives, design decisions have already been made and changing them costs real money.

For timelines: share any hard deadlines, such as a lease expiring, a school year starting, or an aging parent's needs accelerating. But understand this: a realistic completion date can only be projected after the concept phase is complete, the scope is defined, and no more changes are being introduced. Before that, any date is an estimate at best.

Questions to ask yourselves

  • What's our comfortable budget range, and what's our absolute ceiling?
  • Have we spoken with our bank or mortgage broker about what's available?
  • Are there hard deadlines: a lease, a family event, a seasonal constraint?
  • Are we prepared for the project to take longer than we expect? (Most do.)

Get budget clarity early

If your budget range feels uncertain, the Project Preparedness Tool can help you calibrate expectations before concept design begins. Knowing how much you can realistically spend is not a limitation, it's a design parameter. The best designs are shaped by honest constraints, not unlimited imagination.

5

What do you know about your property?

Your property has a history, and that history shapes what you can build. If you've already completed a Feasibility & Risk Review (Gap 1), most of this is documented. If not, gather what you can. Anything you bring to the table saves time and prevents surprises downstream.

Don't worry if you can't answer every question below. Just gather what's available. Your design team will help you fill in the gaps. and knowing what's missing is just as useful as knowing what's there.

Things to gather if you have them

  • An up-to-date property survey (lot boundaries, setbacks, grades)
  • Previous building permits and associated drawings for your property
  • Site photos, especially of the area where the project will happen
  • Any floor plans, estate agent plans, or sketches you already have
  • Known issues: flooding, drainage, underground utilities, shared driveways
  • Your property's title and any legal descriptions attached to it

Call your municipal building and planning departments

Your local building and planning departments can provide zoning information, setback requirements, and a history of permits issued (and if you're lucky), copies of the original drawings for the building(s) on your lot. This is public information, and you're entitled to it. Ask specifically about: zoning by-law provisions for your property, floodplain or wetland designations, easements, and any subdivision covenants. If you find something you don't understand, include it in your brief and flag it with a question mark. Your design team would rather have a confusing document than no document at all.

6

Who else is part of this project?

Design decisions slow down when the decision-makers aren't identified. If your partner, your parents, your contractor, or your friend-who-is-an-engineer will have opinions that influence the outcome, name them now. Not because their input is unwelcome, because your design team needs to know who's at the table, so surprises don't surface as contradictions after the work has started.

A project where one partner loves modern design and the other loves traditional can produce a beautiful result, if the designer knows about the tension from the start. A project where that tension surfaces after three rounds of revisions results in frustration and increased costs.

Questions to ask yourselves

  • Who makes the final decisions? Both partners equally? One person?
  • Is there a builder or contractor already involved who will have input?
  • Are there family members, friends, or advisors whose opinions will influence your choices?
  • If there's a friend who is a contractor, architect, or engineer who will be whispering into your ear, are they acknowledged as part of the team?
  • If you disagree on a direction, how will you resolve it?

Acknowledged input is productive

If you regularly consult someone with construction experience, bring them into the conversation openly. If you already have a builder, invite them to review the brief before concept design starts. A builder's early input on costs driven by material selections and construction processes prevents scope surprises later. What doesn't work is when outside advice surfaces mid-project as a surprise contradiction. That creates confusion and rework.

7

How will you know the project succeeded?

This is the section most briefs leave out, and it's the one that keeps the whole project honest. If you can describe what "done" looks like, your design team can measure their work against your expectations at every stage. If success is never defined, the project drifts toward the designer's idea of good rather than yours.

Think about this from two angles: what would make you say "this is exactly what we needed," and what would make you say "this isn't what we asked for." Both answers are useful.

Questions to ask yourselves

  • When this is finished, what will be different about how we live?
  • What will tell us the money was well spent?
  • What would make us say "this is exactly what we needed"?
  • What would make us say "this isn't what we asked for"?

What a real first draft looks like

Below is a Design Brief for a project you might recognize: an enclosed three-season room between a house and an outdoor pool area. Notice that it's written in plain language, no code references, no assembly specifications, no construction jargon. Just a clear, honest description of what the homeowner wants and why.

This is exactly the level of detail your design team needs to start developing concept options. Most of the time, what designers actually receive is "Here's a photo of something we found online. Make it work." This is better than that. This gives your team something to design from.

Sample Design Brief — First Draft

Three-Season Enclosed Outdoor Space

1. Project Overview & Problem

We want to renovate the existing outdoor area between the house and the pool to create an enclosed, low-maintenance space we can use for three seasons. The room should connect the indoor eating area to the outdoor pool area while keeping the bugs out.

The problem: we use the pool from May to September, but the outdoor space is unusable most evenings because of mosquitoes. We end up eating all summer indoors when we'd rather be outside.

2. How We Want to Live

We entertain frequently, mostly casual dinners with friends and family on summer weekends. The grandkids go back and forth between the pool and the house constantly. We want to be able to relax and eat dinner without being driven indoors by 7 PM. On cooler spring and fall evenings, we'd love to use the space and enjoy some quiet time, sharing a glass of wine with our adult children after the grandkids are in bed.

3. Must-Haves

  • Large windows or panels that open in good weather
  • Bug-free when panels are closed or open
  • Smooth connection between the kitchen/dining area and the pool so food and grandkids can move easily
  • Space for a dining table for six plus a separate seating area
  • Durable, easy-to-clean materials (this is a pool-adjacent space, not a formal room)
  • Adequate ventilation so it's comfortable without needing air conditioning during summer

3. Nice-to-Haves

  • Ceiling fans for air circulation
  • Some form of heating for cooler evenings (infrared heaters?)
  • Ambient and task lighting for evening use
  • Retractable panels with screens, rather than fixed windows, if the budget allows
  • A small counter or prep area so we don't have to go back inside for everything

4. Budget & Timeline

We're comfortable in the $60,000–$85,000 range, including design fees. We've talked to our bank and have access to a home equity line. We'd love to use the space next summer, but we're flexible on timing if the design is right.

5. Property & Site

Single-storey home, built in 1998. Property survey on file (2019). No known easements or drainage issues. The area between the house and pool is currently a concrete pad with a pergola that we'd remove. South-facing exposure.

We'll need to check setback and lot coverage requirements with the municipality if we attach the new room to the house. We can make it a separate building, if that helps with the zoning. We're flexible.

6. Decision-Makers & Team

Both of us (Mark and Lisa). No builder selected yet. Mark's brother is a general contractor and will have opinions and we'd like to include him in the concept review so his input comes early rather than late.

7. What Success Looks Like

We're eating dinner by the pool on a July evening with the windows wide open and no bugs. The space doesn't feel like an afterthought or a cheap add-on — it feels like it's always been part of the house. The materials are holding up after two winters without us having to baby them. Friends say, "This changes everything about your backyard."

What this first draft provides

It's missing some detail — regulatory requirements, detailed design preferences, full site documentation, but that's fine. The design team will help fill in those gaps during the concept phase. What this draft provides is the essential context: why the project exists, what it needs to include, who is involved, and how much is available. That's enough to start developing concept options that actually fit this family's life.

Four traps that slow projects down, and how your Design Brief prevents them

These aren't criticisms, they're patterns that show up on project after project. Every one of them creates rework, delays, or cost surprises later. Every one of them can be prevented at the Design Brief stage. Knowing them now means you can sidestep them before they become expensive.

1

The Undisclosed Budget

"Let us worry about the budget. You just do your job."

The budget constrains the design, not the other way around. When the budget isn't shared until after concept options are developed, those concepts often don't fit the available funds. Redesign costs time and money, yours and your designer's. Even a rough range gives your team the guardrails they need to produce options that are realistic from day one.

Your brief's Section 4 prevents this.

2

The Undefined Need (Disguised as a Design Change)

"We love this design. But can you split the house into a duplex somehow? A buddy of mine said it could be done…"

When actual needs aren't defined before design begins, what looks like a small design change is often a fundamental scope change, requiring the plan to be abandoned and restarted from scratch. The brief prevents this by getting your real requirements on paper before drawing starts. If the need genuinely changes mid-project, the brief provides a reference point for an honest evaluation of the impact.

Your brief's Sections 1 and 2 prevent this.

3

The Rolling Change Request

"It's not really a change, it's just a continuation of the design process, right?"

One or two adjustments during concept design are normal. But continuous additions, without acknowledging their impact on timeline and cost, turn the design process into a moving target. The must-have / nice-to-have list and the success criteria you defined in your brief provide the anchor. Changes are measured against defined priorities, so refinements stay refinements rather than becoming restarts.

Your brief's Sections 3 and 7 prevent this.

4

The Premature Deadline

"We need it done by April." (Before the scope is even defined.)

A completion date without a defined scope is a promise built on a guess. The timeline becomes realistic only after the concept phase is complete, the scope is agreed upon, and the decision-makers have signed off. Before that, locking a date traps everyone, and if multiple changes are introduced without adjusting the timeline, quality is the first thing to get compromised.

Your brief separates hard deadlines (a lease expiring) from hopeful targets (wanting to use it next summer), so planning can be honest.

Your brief's Section 4 prevents this.

A note about drawings and ownership

This surprises most first-time-project homeowners, so it's worth knowing upfront: when your design team produces drawings, sketches, plans, or digital models, those documents remain the intellectual property of the designer. As the client, you receive a licence to use the work for your specific project to build from, to submit for permits, to share with your builder. But you don't own the design itself, and you can't reuse or resell it without permission.

This is standard practice across the architecture and design industry. It protects both parties: you get the right to build your project, and the designer retains ownership of the creative and technical work they produced. It's not something to worry about, just something to understand before the process begins, so there are no surprises when deliverables are shared or ownership questioned.

What happens after you finish your brief

Your Design Brief is the starting point, not the finish line. Once we receive it, here's what happens:

  1. We read it carefully. Not to judge your writing, but to understand your priorities, your constraints, and the way you think about your home. We'll have follow-up questions. That's a good sign. It means we're taking your input seriously and building the concept on the foundation you've provided.
  2. We develop two to three concept options. Each one responds to your brief differently, testing different layouts, different trade-offs, and different ways to solve the problem you identified in Section 1. You'll see them side by side, with enough detail to compare and enough flexibility to combine the best elements of each.
  3. You choose a direction. Not a final design — a direction. The concept you choose moves into schematic design (Gap 2B), where dimensions lock, assemblies are defined, and the project becomes quotable. The brief stays with us throughout the entire process, and we refer back to it at every decision point to make sure we're still solving the problem you started with.

This is collaborative, not a test

The brief doesn't need to be complete or polished before you share it. Start with what you know. If you can write three sentences per section, that's enough to begin. The best briefs are honest, not perfect, and the best design work comes from clients who describe what they actually need, not what they think their designer wants to hear.