A client brief is the short written statement of what a piece of work has to achieve, for whom, and under which fixed constraints, agreed before either side commits to a solution.
Assessment. The brief is your document, not the client's. Very few people buying creative or technical work can write one, so drafting it on their behalf and holding out for a written yes is part of the job you are charging for, not a favour you do before the job starts.
Write it so a stranger could mark it
Name the reader, not the market. One person: the shopper who abandoned a half-filled form last Tuesday, the finance manager who has to approve a supplier. Work aimed at everybody gets judged by whoever speaks loudest in the review meeting.
Say which behaviour should change. Something a real reader currently does, or avoids doing, that the finished thing should shift. Taste arguments hide inside this line and asking the question forces them into the open.
Attach an observation to every goal. If you cannot describe what somebody would watch, count or read to settle whether the goal was met, you have recorded a preference rather than an objective.
List the constraints nobody may negotiate away. File formats, accessibility duties, the elderly system it has to plug into, the regulated wording that cannot be improved.
Record what exists already and whether replacing it is permitted. A large share of all rework is a supplier upgrading something the client was contractually stuck with.
Log the previous attempts and why each was dropped. That history is usually where the genuine constraint is hiding, and clients rarely volunteer it unprompted.
Almost nothing arrives in this shape. What lands in your inbox is a paragraph of adjectives and a link to a competitor, which is raw material rather than an instruction. Interrogate it in one call, write your version in under a page, send it back, and refuse to start until somebody answers yes in writing. That confirmation is the whole object of the exercise: it moves the picture out of one person's head into a record you can both quote, and a buyer who will not confirm six lines is telling you, cheaply and early, how sign-off on the finished work is going to feel.
When the buyer does not know what they want, the brief becomes the deliverable. Sell it as a bounded paid piece carrying a price of its own and a defined ending, producing a written problem statement that either side may act on afterwards, including with somebody else. Unpaid briefing is an education you are funding for a stranger. Then hold the line on vagueness: make it feel more professional carries no observation at all, so any result can be rejected and none can be defended. Ask what a more professional version would let the reader do that the current one does not, and keep asking until the answer contains a verb. Two further habits repay the awkwardness. Put the name of the single person who approves at the top, because briefs with three approvers become negotiations. And write down what is explicitly out of bounds while goodwill is high, since the lines you will wish you had written are always the ones that felt too obvious to type, and they transfer straight into the statement of work. Where the brief sits in the wider run of an engagement is set out in freelance work.
In practice
A charity asked for a homepage that looks more trustworthy. Nothing in that sentence can be delivered or refused, so it was rewritten as a line the client could test without the supplier present: “a first-time visitor can find the registered charity number, a named contact and where the money goes, without leaving the homepage or opening a menu”. Same ambition, now markable. The redesign that followed could be checked by handing a laptop to somebody who had never seen the site and watching.
Note what the rewrite refuses to decide. It says nothing about typefaces, photography or layout, because those are the judgement being bought. A useful brief tightens the walls of the box and leaves the inside of it alone.
The brief argues for the work and may stay open in places; it is written before anyone prices anything. The statement of work closes those open places and attaches money and dates to the closure.
Creep is the bill that arrives later for a briefing failure: where nobody wrote down what the work was for, each stakeholder's private version turns up one small request at a time.
Key takeaways
→Expect to write the brief yourself, then get it confirmed in writing before any work begins.
→Every goal needs an attached observation, or it is a preference that can be rejected forever.
→When the client cannot say what they need, sell the brief as a paid piece with its own ending.
Detail on constraints, readers and tests; restraint on execution. Naming the typeface, the layout and the wording removes the judgement they are hiring you to exercise and leaves you delivering a specification rather than an opinion. Leaving out the accessibility duty or the antique system it must feed guarantees rework instead.
The client sent a brief. Do I still write my own?
Write a short restatement anyway. Not a rival document, a summary in your words of what you believe you are being asked for, sent back for a yes. Disagreements surface in the reply, which costs an email at this point and a renegotiation later.
Can a brief be a phone call?
The conversation can be; the brief cannot. Memory diverges, and always in the direction of whoever is paying. If formality feels heavy for a small job, write six bullet points into an email and ask for a one-word reply. That is a brief in every respect that will matter if it goes wrong.
Sources
The primary text this definition rests on. Read it before relying on this one.
