The creative brief: how to write one that prevents rework

A brief turns a request into a solvable problem. It does not describe the deliverable; it describes what that deliverable has to achieve, for whom, and within which limits. A creative team starting without one is not working without information. It is working with whatever each person remembers from a call, which is worse: nobody knows a fact is missing until the client contradicts it.

This is where an agency wins or loses hours before anyone opens a design tool. The process that comes afterwards is covered in the guide to project management for creative agencies.

What is a creative brief, and what is it not?

A creative brief is a written agreement between the person commissioning the work and the people doing it, covering the objective, the audience, the message, the deliverables and the constraints. It is written before work starts and confirmed by both sides. That confirmation is half of its value.

It is worth separating it from four documents that often stand in for it:

• It is not the request. "We need three social posts" is a request. A brief starts one question earlier: what problem needs solving, and why anyone believes three social posts will solve it.
• It is not the proposal. The proposal sells the work; the brief defines it. They share facts, but one is written to persuade and the other is written to leave no room for interpretation.
• It is not the internal job sheet. Task allocation comes afterwards and depends on the brief, not the other way round.
• It is not meeting minutes. Minutes record what was said. A brief records what was decided, which is far less text and far more useful.

Why does rework come from the brief rather than the execution?

When a client rejects creative work, they rarely say it is badly made. They say it is not what they expected, that it lacks impact, that they cannot see themselves in it, or that they tried this before. None of those is a craft criticism. All four describe the gap between what the client had in their head and what they never wrote down.

An incomplete brief does not remove that conversation, it postpones it. Instead of arguing about a paragraph, the team argues about a finished piece, with the hours already spent and somebody defending their own work. Challenging an assumption takes minutes. Challenging an assumption once it has been turned into a design costs a full round and leaves a mark on the relationship.

There is a simple test for whether a round of rework was avoidable. Take the change the client asked for and look for the brief field that would have anticipated it. It almost always exists, and it is almost always empty or written in a sentence that allowed two readings.

Which fields does a working brief need?

A brief does not need to be long. It needs to be complete. These are the fields that do real work; most of the rest is decoration.

The business problem, not the deliverable requested

This is the most commonly skipped field and the only one that lets anyone judge the work by something other than personal taste. A client asks for a catalogue; the actual problem may be that the sales team has nothing to leave behind after a visit. With the problem written down, the creative team can propose something better than a catalogue. Without it, all it can do is make a good-looking catalogue.

Write it as one sentence with a subject and a verb: what happens today, what should happen instead, and how anyone will know it happened. If the client cannot answer, that is the first finding of the project and it should be said out loud.

The audience

Not generic demographics, but what that person already knows about the brand, what holds them back, and the context in which they will see the work. Someone glancing at a phone in a queue does not read what someone opening a document at a desk reads.

The single message

If the audience retains one sentence, which one is it. One. A brief with five priority messages produces work that says five things and is remembered for none, and it also produces the revision round where the client asks for all five to be made bigger.

Tone of voice

Tone is where vagueness hides. It gets pinned down with references: two or three brands the client wants to sound like, and, more importantly, one they do not. Negative examples discriminate better than positive ones, because most people admire the same work but each one rejects something different.

Deliverables, with formats and dimensions

How many pieces, in which file formats, at which exact dimensions, in how many versions and in which languages. The field looks clerical and it prevents the most avoidable rework of all: delivering something correct in a format that has to be rebuilt before it can be published.

Channels

Where each piece gets published and who uploads it. The same message is not built the same way for a vertical format as for a footer, and when the channel is decided after the design exists, the agency absorbs the adjustment.

Brand constraints

Guidelines, licensed typefaces, mandatory colours, anything explicitly off limits, and legal sign-off if the sector requires it. A typeface without a digital licence, discovered at the end, is a full round lost to a fact that fitted on one line.

Dates

Two dates, not one: the real date, when something happens in the world, and the preferred date, when the client would like to have it. Confusing them makes everything urgent and therefore makes nothing urgent. If the project chains several dependent pieces together, map them before promising anything; that is what a Gantt chart is for.

Which two fields does almost nobody write?

The fields above appear, in better or worse shape, in most briefs in the industry. The next two almost never do, and they are exactly the two that prevent conflict.

Who decides

Not who has an opinion: who signs. At a mid-sized client several people have a view on creative work and normally one has the authority to approve it. If the brief does not name that person, the project discovers the hierarchy the expensive way: someone new turns up at the final review, sees the work for the first time and asks for a fundamental change.

Write it with a full name, first and last, and add a second line that matters just as much: who else will see the work, and in what capacity. "Marketing and the store manager review and comment; the brand director approves" is a sentence that stands on its own when people disagree.

How many revision rounds the price covers

A round is a full cycle: the agency delivers, the client gathers all its comments into a single response, and the agency applies them. The brief has to say how many rounds there are, what counts as a round, and what happens once they are used up.

Without that field, revisions have no floor. The extra work does not arrive as a new job that can be invoiced; it arrives as small emails nobody feels comfortable charging for, and the project margin disappears without ever showing up on an invoice. It is one of the three margin leaks described in the guide to project profitability in agencies, and the easiest to close: one line of text agreed before work starts.

What should you ask for each field?

The table below is the whole conversation: what to ask, and what it costs when the field is left blank.

How do you actually collect a brief?

In two moves, and neither is optional.

1. A meeting. Briefs are not filled in cold, because half the useful information only appears when you ask the follow-up question. That is what the meeting is for: to hear the quick answer and then ask again, which is where the constraints the client assumed were obvious finally surface.
2. A written document, drafted by the agency and confirmed by the client. The people who will do the work write it, not the person commissioning it. Send it with an explicit request for confirmation, and do not start production until that confirmation arrives in writing.

Having the agency draft it is not administrative overhead, it is quality control: writing it is what exposes the gaps. And having the client confirm it turns the document into the shared reference for the moment when two people remember the same meeting differently.

A single email does not work as a brief for three specific reasons. It has no structure, so nobody notices the missing fields. It is unconfirmed, so it remains one side's version. And it sinks into the thread: two weeks later the good version sits alongside four later corrections and nobody knows which one governs.

When should you stop and ask again?

Some signals mean the brief is not ready even though the document looks complete. When they show up, stopping costs less than starting:

• The objective field says "awareness", "refresh the image", or anything else nobody can check afterwards.
• Nobody can name the final approver, or the name changes depending on who you ask.
• The client describes the solution in detail and cannot explain the problem.
• More than three messages are flagged as priorities.
• There is a delivery date, but the materials the client owes have no date at all.
• The tone reference is a brand from another sector working at a budget nothing like this one.
• Someone on the client side has been in none of the conversations but will review the work.

Stopping here is uncomfortable for ten minutes. Carrying on is uncomfortable for three weeks.

Where does the brief live once it is approved?

Somewhere single, shared and readable by everyone touching the project, not in an email attachment or on the desktop of whoever drafted it. In Tasuki that place is notes, where the workspace's internal documentation lives and where it can be linked to the work in progress.

An approved brief has a second life: it becomes the referee. When a request lands mid-project, the question is not whether people like it but whether it was in the brief. If it was, do it. If it was not, it is a scope change and gets treated as one, with its own conversation about timing and cost. Making that distinction calmly, with the document in front of you, is what keeps the relationship intact.

It also helps to separate where things get discussed from where they get decided. Day-to-day conversation belongs in a team chat; decisions do not. A decision that exists only in a message thread is lost, because nobody will scroll back through four hundred messages to find it. If something changes the brief, edit the brief.

Key takeaways

• The brief describes the business problem, not the deliverable requested. Without that field there is no way to judge the work except by the taste of whoever is looking.
• Rework is usually a framing failure rather than a craft failure: the change the client asks for almost always maps to a brief field that was left blank.
• The two fields that prevent conflict are who signs off and how many revision rounds the price covers. They are the two almost nobody writes.
• Collect it in a meeting, close it in writing, drafted by the agency and confirmed by the client. A single email has no structure, no confirmation and no permanence.
• Vague looks like "modern", "impactful" and "awareness". Specific looks like a negative reference, one message and exact dimensions.
• Once approved, the brief is the referee: anything outside it is a scope change, with its own timeline and its own cost.