Ask a designer what went wrong on a job that needed four rounds of amends and the answer is rarely the design. It is usually the brief. The brief said the client wanted something fresh, modern and premium, which describes almost everything, and the first round was the team guessing what those words meant to this particular client.
A good creative brief does not make the work good by itself. What it does is make the first round closer, the feedback easier to give, and the arguments shorter, because everyone is judging the work against the same page instead of against their own memory of a meeting.
Write it with the client, not for them
The most common way a brief fails is that the account manager writes it alone, from notes, after the client call. It then reflects what the account manager heard, which is not always what the client meant, and the client sees it for the first time when they see the work.
Draft it after the call, then send it back to the client and ask them to correct it. That step takes a day and saves a round. A client who has signed off a brief has agreed to the terms the work will be judged by. A client who has never seen it is free to judge the work by anything.
The background: why this, why now
Three or four sentences on what is happening that makes this work necessary. A product launch, a drop in sales in one city, a competitor who has moved into the same space, a rebrand that the old assets no longer fit. The creative team needs the reason, because the reason shapes a hundred small choices the brief will never mention.
Keep it short: if the background runs to a page, the useful sentence is buried in it.
One objective, one proposition
The objective is what should change as a result of the work. Make it specific enough that someone could tell, afterwards, whether it happened: more enquiries for the new service, a higher share of Arabic-speaking followers, sign-ups for an event. "Raise awareness" is a direction, not an objective. Push for what awareness should lead to.
The single-minded proposition is the one thing the work should say. One sentence, written in plain words, not a tagline. It is the hardest line in the brief to write and the most useful to have, because every piece of work can be checked against it. If the client has five things to say, the brief is where someone has to choose, and it is better that the choice is made in writing before production than in feedback after it.
If the brief cannot say what the work should say in one sentence, the work will try to say everything, and the client will notice what is missing.
Audience, proof and tone
Describe the audience as people, not as a demographic line. What do they think now, and what should they think or do after seeing the work? For work in the Gulf, say which languages the audience uses and whether the Arabic is a translation or written first. That single detail changes the schedule, the copy and often the layout.
Reasons to believe are the facts that make the proposition credible: a feature, a result, an award, a guarantee. List two or three. Tone is best given as three or four words and one example of a brand that sounds close, because tone words on their own mean different things to different people.
Mandatories, kept short
Mandatories are the things that are not open to interpretation. They should be easy to find and short enough to read in a minute.
- Logo use and the brand guidelines that actually apply to this job, not the whole brand book.
- Legal lines, disclaimers and any claims the client cannot make.
- Languages, and which one leads.
- Anything the client has rejected before and will reject again.
- Cultural and seasonal points, such as timing around Ramadan or national days, where they apply.
If the mandatories run past eight or nine lines, some of them are preferences. Move those into tone or background, so the true non-negotiables stand out.
Deliverables with dates and sizes
List every asset the team is expected to produce, each with its format, size, channel and due date. A key visual in 1080 by 1350 for the Instagram feed, a 15 second vertical video for Reels and TikTok, a banner set in named sizes. This is the part of the brief the production team reads most closely, and the part most often left vague.
Give two dates for anything the client approves: when the first version goes to the client, and when the final is due. The gap between them is the time for feedback, and naming it tells the client how long they have.
Approvals: who, how many rounds, how long
Name the person on the client side who approves, and anyone whose opinion they will seek before they do. Say how many rounds of amends are included and how long the client has to reply to each. The aim is to make sure the person who can say no has seen the brief before the work arrives, rather than after.
Agree the brief review internally as well. Before production starts, the creative lead should read the brief and be allowed to challenge it. A brief that the team does not believe will produce work the client does not believe either.
Use the brief when feedback arrives
The brief earns its keep when the first round comes back. Feedback that can be tied to a line in the brief is feedback on the work: the proposition is not clear, the Arabic headline is missing, the logo is too small for the guidelines. Feedback that cannot be tied to anything in the brief is often a new requirement.
New requirements are fine. Clients learn things, and markets move. The point is to notice them, agree whether they change the deliverables or the dates, and update the brief so the next round is judged against the right page. A brief that is never updated stops being the reference, and everyone goes back to remembering.
Keep the brief where the work is
A brief in an email attachment is out of date the moment someone replies with a change. Keep one version, attached to the project, and point everyone to it. The free creative brief template in the templates library follows the structure above on a single page. In Wiro, the brief sits on the project itself, beside the tasks, deliverables and the client's approval, so the page the work is judged against is the one the team is looking at.
