Guide

How to write a design brief for a South African house

First written 30 September 2026

Most residential projects that go wrong go wrong before a line is drawn. The client remembers a bigger scullery; the architect remembers a smaller budget. A written design brief, agreed after the first meeting, is the cheapest insurance against that. This is a working format for South African residential studios, and it takes about an hour to complete properly.

What a brief is for

A design brief is a record of decisions, not a wish list. It states what the client needs, what the site allows, and what both sides will treat as success. It is also a scope document: when a change request arrives in month three, the brief is what you point to. SACAP's work stages start from a defined brief, and your professional indemnity exposure shrinks when the scope was written down before design started.

The client side: five things, in the client's words

Record five things from the first meeting and treat them as provisional until you have confirmed them in writing:

• Rooms. A room list with counts, including the ones the client is unsure about ('4 bedrooms, maybe 5 if the granny flat counts'). Ambiguity written down is a question; ambiguity left in the head is a dispute.
• Budget. A range, not a number, with what it excludes. 'R6,800,000 to R7,400,000, fit-out excluded' is honest; 'R7 million' is a trap.
• Style. Words and, better, references the client themselves picked. 'Contemporary, exposed brick, like the Boshof house' carries real information; 'modern' does not.
• Timeline. The date that actually matters, usually plan submission, not completion. Anchor it to municipal processes, not optimism.
• Priorities. What gets dropped first when the budget meets reality. The client should say this once, early, while everything is still possible.

The site side: facts, sourced

Site facts are different from client wishes in one way: a client can change their mind about a scullery, but the erf cannot negotiate. Record the erf number ('Erf 1042'), the zoning under the applicable town-planning scheme, the maximum coverage, the height restriction in storeys and metres, and the street, side and rear building lines. Mark each fact with where it came from: the title deed, the zoning certificate, the client's recollection. A coverage figure recalled over a kitchen table is not a fact; it is a lead. SANS 10400 compliance comes later, at design, but none of that work starts safely until the scheme controls are confirmed.

The trade-offs, honestly

A Word template reused from the last project costs nothing and produces a brief that reads like the last project. An InDesign pack produces a document clients admire, at the cost of half a day you cannot bill. A generic chat assistant is fast but knows nothing about erfs, schemes or coverage, and tends to invent site facts to fill the page. Whatever you use, the test is the same: every fact in the brief traces back to something the client said or a document you hold, and a principal signed it off before it left the studio.

A worked example

We put a complete pack online as a sample: rough meeting notes on one side, the formatted brief and site summary on the other, for a hypothetical Constantia house. Read the sample kickoff pack to see the format filled in end to end.

ArcStudio exists because this hour is exactly the wrong place for a principal's evening: paste in what you heard in the first meeting and ArcStudio drafts the whole pack, in your studio's name, with every site fact stated exactly as you entered it. Your first project is free, and the Studio plan is $199/month after that. This site, and the business behind it, are built and run by AI agents on NanoCorp, which is how a one-practice idea like this ships at all.