How to Write a Creative Brief: A Template for Getting Sharper Work from Agencies and Studios
Published:
Last Updated:
Category:
Published:
Last Updated:
Category:
Authors: Shusaku Yosa
You hand work to an agency or a production studio, and what comes back is not what you had in mind. That gap usually has less to do with the agency's ability than with the quantity and quality of information you gave them. The document that prevents it is the creative brief, known in Japan as an orientation sheet. This article covers what a brief is, how it differs from an RFP or a proposal, the ten items to include, a template you can copy, and the writing habits that raise the quality of what you get back.
A creative brief is a document that gathers the background, objective, audience, budget, schedule, and other prerequisites you need to pass to an advertising agency or production studio when commissioning work. The Japanese term comes from "orientation," in the sense of establishing which way to face, and in daily practice it is shortened to orie, orientation materials, or simply the brief.
The important thing is that a brief is not a specification for the thing you want built. What you need to convey is not what to make but why you are doing this and what success would look like. Prescribe the method in too much detail and you shut out the partner's expertise and any better alternative they might have offered, which largely defeats the point of going outside in the first place.
Several similar documents exist, so it helps to sort them by who writes them and why.
In practice the line between an RFP and a brief is blurry, and some organizations use the terms interchangeably. Do not get attached to the label. Judge instead by whether the document gives the proposing side enough to work with.
Briefing verbally tends to produce four recurring problems.
Writing a brief takes a day or two. Set against the rework it prevents, that is time well spent.
Whatever your industry or the type of campaign, covering these ten items produces a brief that works.
Put the project name, a one-line summary of the request, the briefing date, and the proposal deadline at the very top, so a reader can grasp what this is about in seconds.
Your business, flagship products, position in the market, and the values the brand holds to, kept brief. Skip this with a new partner and the proposals will come back generic. Attach existing brand guidelines if you have them.
Explain why you are doing this now, using facts and numbers. Specifics such as "inquiries down 30 percent year on year" or "first-month retention among new users is low" let the proposing side narrow their options. Share what you have on hand, whether that is analytics, sales data, or customer feedback.
State what you want to achieve in measurable form. Not "raise awareness" but "1.5 times more branded search volume within six months." Not "get more inquiries" but "from 30 to 60 per month." Where numbers are genuinely unavailable, at least describe in words the state that would count as success.
Go beyond demographics to the situation these people are in, what troubles them, and where they look for information. In B2B, the user and the decision maker are often different, so say which one the work is aimed at to keep the proposals from drifting.
Describe what you do better than competitors and what customers actually praise. What the makers believe and what customers value often diverge, so evidence such as reviews or the content of inbound questions sharpens the proposals considerably.
Say where the engagement starts and stops. Planning only, or production, execution, and ongoing operation as well? Also state what falls outside the scope, such as copy supplied in-house or photography commissioned separately, so that quotes rest on the same assumptions.
Give a ceiling or a range. Splitting production cost from media spend, and initial from ongoing cost, gets you quotes that are easier to compare. Hide the budget and you receive a mix of unworkable and overreaching proposals, and your comparison workload grows for nothing.
List the proposal deadline, selection period, contracting date, and target launch or campaign date in order. Where a constraint cannot move, such as a trade show date or a product release, say so plainly.
Specify what the proposal should contain, such as the approach, team structure, cost breakdown, and comparable work, along with the format and deadline, how you will weight each criterion, and who fields questions during what window. Publishing the criteria up front sharpens the focus of what you receive.
Use the following as your section headings and fill each one in. Around ten to twenty slides, or three to five pages as a document, is a reasonable length.
Write "customers do not understand how to use the product, and post-purchase support volume is high" rather than "we want a video." The first version gets you a quote for a video. The second may surface stronger answers, such as rebuilding the FAQ or revising the in-box guide. Even when the method is already settled, include the reasoning that led you there.
"Stylish" and "a trustworthy tone" mean completely different things to different people. Show a handful of reference examples and annotate them, noting what works in each and which direction is wrong. That alone cuts design rework dramatically.
Campaigns you have already tried without success, and the numbers behind them, are extremely valuable to the proposing side. Withhold them and the same idea will simply come back wearing different clothes. Set pride aside and share it as fact.
Industry association rules, regulatory limits on claims, phrasing you cannot use, assets you cannot license, directions previously rejected internally. Raising these after proposals arrive wastes everyone's time. Stating them at the outset is a kindness.
Saying who makes the final call and how each factor is weighted focuses the proposals. A scoring scheme such as 40 points for understanding of the problem, 30 for creative, 20 for team and track record, and 10 for cost also carries over directly into building internal consensus.
A brief gains value when you walk people through it rather than simply sending it. Allow about an hour and run it in this order.
When several vendors are involved, sharing questions and answers with all of them is the fair approach. If one party holds information the others lack, the basis for comparison collapses.
Three to five pages as a document, or ten to twenty slides. Length matters less than whether the proposing side has what it needs to make judgments. Keep detailed analytics and brand guidelines out of the main body and attach them as appendices to keep it readable.
Yes. Without a budget, proposals arrive at wildly different scales and you spend your time on comparisons that go nowhere. Asking for the strongest plan achievable within a stated range means the way each vendor sets priorities becomes visible, which is useful selection input in itself.
Anything the proposal depends on should be shared under an NDA. Revenue mix, customer retention, and the cost effectiveness of past campaigns all change the accuracy of a proposal substantially. For anything you truly cannot release, communicating the range or the direction still helps.
Yes. A brief is not only a comparison device; it is how the request itself gets pinned down. The longer the relationship, the more easily "they will know what I mean" creeps in, and that is precisely what causes rework. A simplified version is fine, but make writing it down a habit.
A creative brief communicates the problem you want solved and the conditions that must be met, so that the proposals you receive are sharper. Cover the skeleton, background and problem, objective and KPI, audience, scope, budget, constraints, and evaluation criteria, and it will do its job regardless of format.
What matters most is describing the problem rather than dictating the method, replacing adjectives with numbers and examples, and not holding information back. Start by using the template above as a base and adding or removing items to fit the project in front of you.
How to write a requirements definition document, with a seven-chapter template you can use as-is. Covers turning vague w...
Why web development and advertising estimates are so hard to compare. Which fields to check first, how man-month pricing...
What vendor management means, why a hands-off approach fails, the four areas to manage, five things to settle before eng...
