Writing a Design Brief Your Architect Can Actually Use

A brief describing how you live produces a better house than one describing what you like. How to write one.

Most design briefs are collections of images and adjectives. An architect can work with those, but they produce a house shaped by references rather than by your life. A brief built from how the household actually functions produces a different and better result.

Before stage one

Before writing anything, spend a week noticing how your current home works and fails: where people gather, what is always cluttered, which rooms are unused and when the house feels too small.

• Observations of how your current home functions, not just what annoys you about it.
• The household composition now and as you expect it in ten years.
• A budget ceiling you are prepared to state.
• The plot constraints from the engineering office.

Stage 1: Describe the household

Set out who lives here, their ages, their routines, who visits and how often, and how that may change.

• Deliverable: A written description of the people the house serves.
• Owner: Owner.
• Approval gate: The description is specific enough that a stranger could picture the daily pattern.

Stage 2: Define spaces by function

List the spaces needed by what happens in them rather than by name, including how many people and what activities each must support.

• Deliverable: A functional space list with approximate sizes.
• Owner: Owner with the architect.
• Approval gate: Every space has a stated purpose rather than appearing because houses usually have one.

Stage 3: Set privacy and reception requirements

Define how guest reception separates from family life, which is one of the most consequential decisions in a Saudi home.

• Deliverable: A statement of separation requirements and circulation.
• Owner: Owner.
• Approval gate: Requirements stated before layout begins, since they shape the whole plan.

Stage 4: State what you do not want

List what should be avoided, from spaces you would never use to features you dislike, since exclusion directs design as strongly as requirement.

• Deliverable: A list of exclusions with brief reasons.
• Owner: Owner.
• Approval gate: Exclusions recorded, because they prevent effort spent on directions you will reject.

Stage 5: Set the budget and priorities

State the ceiling and rank what matters most, so the architect knows what to protect when reconciliation is needed.

• Deliverable: A budget with a priority order.
• Owner: Owner.
• Approval gate: Priorities stated before design, not during value engineering.

Stage 6: Review and approve the brief

Go through the brief with the architect, resolve ambiguities and approve it as the reference for design.

• Deliverable: An approved brief signed by both parties.
• Owner: Owner with the architect.
• Approval gate: Design begins from an approved document rather than from a conversation.

Handovers between stages

The weak point is between the brief and the first concept. Owners often approve a brief and then respond to the concept with requirements that were never stated, which is how the design process becomes circular.

How you know it is finished

The brief is complete when it describes the household, the functions required, the privacy structure, the exclusions and the budget priorities, and when both parties have agreed it as the basis for design.

If you are starting a design, Domira can help you write the brief, review the drawings and keep the design aligned with the budget before it reaches a contractor.