How to Actually Brief an Agency: The Executive’s Guide to Getting Great Work in Half the Time

Why the brief is eighty percent of the outcome

We opened a project last quarter with a client who described the brief as “a rebrand, four weeks, keep it modern.” Nine sentences in an email. Four weeks later we shipped a rebrand that the CEO privately loved, the CFO privately hated, the head of sales did not understand, and the board deferred a decision on. It was, by any craft standard, good work. It was, by any commercial standard, a failure. The failure did not happen during the design phase; it happened before the design phase, in the eight sentences that never got written.

We started this article to save both sides a version of that story. On our side of the desk, we watch two teams of otherwise excellent people miss each other by a wide margin week after week — not because the client has bad taste or the agency has weak talent, but because the brief was the site of a decision-avoidance conspiracy neither party consciously agreed to. The client wanted to feel unconstrained. The agency wanted to feel trusted. What both got was three extra rounds of revision, a strained relationship, and an outcome no one signed up for.

Here is the uncomfortable truth from where we sit: the brief is not the front matter of the project. The brief is the project, expressed in the most consequential form it will ever take. Every downstream decision — strategy, concept, execution, revision, launch — is a compressed derivative of what the brief made possible or foreclosed. When the brief is sharp, the work moves at the pace of good judgment. When the brief is fuzzy, the work moves at the pace of internal debate, and internal debate is the most expensive material in a professional-services engagement.

The finding we return to over and over: outcome quality on our engagements correlates far more tightly with the quality of the brief than with the quality of the agency team assigned to it. Great teams cannot rescue vague briefs. Adequate teams can execute sharp briefs beautifully. If you have thirty hours to spend improving the odds of your next agency project, the first eight belong on the brief and nowhere else.

What actually goes wrong when briefs are weak

The problems the brief creates are not exotic. They fall into four buckets that appear so consistently we now diagnose an engagement’s health by which of the four the client is complaining about in month two.

Scope drift. The project changes shape every review because the outcome was never fixed in language everyone could point back to. When the client says “can we also add…” three times in the first two weeks, the correct question is not whether the additions are reasonable — they probably are — but why the brief did not force a decision about them earlier. Drift feels harmless in the moment; it compounds mercilessly by launch.

Late-stage rework. Concepts are delivered, admired, and then two weeks later someone senior looks at them and says “this is not for our real audience.” The audience was described in the brief as “professionals aged twenty-five to fifty-four,” which is another way of saying no one. If the brief does not force a specific and non-obvious answer to who the work is for, the rework tax gets paid at the most expensive possible moment.

Approval stalls. Reviews turn into meetings that turn into workshops that turn into memos that turn into rescheduled meetings. Somewhere in the org chart there is a person whose sign-off actually matters, and the brief did not name them, so their opinion arrives in month three when the concepts they finally see feel unrecognizable. This is not a communication failure. It is a governance failure that briefs are supposed to prevent.

Launched, but did not land. The work ships on time, on budget, exactly as approved, and the results are underwhelming. When we look back, the success criteria in the brief were either absent or wrong: the definition of success drifted with the work, so no one can now tell whether the project succeeded or failed. Launches that everyone agrees were “fine” are the most quietly damaging outcome in agency-client work, because they neither teach nor motivate a better next time.

Each of these failures has a specific paragraph in the brief that should have prevented it. That is the essential move of good briefing: identify the failure modes the project is prone to, and pre-empt them in language on the page before anyone starts drawing pixels.

The four non-negotiables in every brief

Everything else in a brief is optional decoration around four immovable pillars. If any of the four are missing, we push back before the engagement begins — not out of process fetish, but because the failure modes we described above map one-to-one onto missing pillars. If all four are present, the engagement has a fighting chance regardless of what else is or is not in the document. Here they are, in the order they should appear in your brief.

Outcome: the change you need in the world

The outcome is a sentence that describes the specific business change the project must produce. Not the deliverable. Not the activity. The change. “A new website” is a deliverable. “Double the volume of qualified demo requests from operations leaders at mid-market industrial companies by the end of Q3” is an outcome. The former can be answered by anything with pages; the latter demands strategic choices and rules out entire categories of approach on its own.

An outcome statement must satisfy three tests. It has to name a business change (something measurable moves). It has to name a timeframe (by when). And it has to be attributable to the work in question (a reasonable causal chain from what we make to what changes). “Improve brand perception” fails all three. “Increase unaided brand recall among enterprise buyers from twelve percent to twenty percent within twelve months of launch, as measured by our annual brand tracker” passes all three. The rule of thumb we use internally: if a competitor could steal your outcome statement without changing a word, it is not specific enough to yours.

Audience: the specific person, not a segment

Audience descriptions in briefs almost always describe segments (“mid-market IT decision-makers”) when they should describe people (“the VP of infrastructure at a two-thousand-person manufacturing company, sixteen months into her tenure, whose CIO is asking her every week what the cloud modernization plan is”). The segment is a filter; the person is a compass. When the design team is deciding whether a page is too dense or the copy team is choosing between two lines, they need the compass, not the filter.

The best audience descriptions we see combine three layers: a demographic sketch (age range, seniority, industry, geography); a situational sketch (what is on their calendar this week, what pressure is on them, what they just Googled); and a verbatim quote or two — either from real customer interviews or from a plausible reconstruction — that captures how they talk about the problem in their own words. If your brief cannot include a real quote from a real customer, that is a signal to spend the next week doing three customer interviews before you brief anyone.

Constraints: what is fixed and what is negotiable

Constraints are the geometry inside which the agency has to design. There are five categories worth naming explicitly: budget (with a range, not a hedge), timeline (with a launch date and any hard milestones), brand and voice (what you must not deviate from), technology (what has to integrate with what), and political (what you cannot say, do, or resemble because of internal or market realities). Naming these in the brief is not a limitation on creativity; it is a delegation of creativity to the places creativity actually helps.

The mistake we see most often is naming aspirational constraints instead of real ones. “Launch by end of quarter” when the real deadline is a board meeting six weeks later, or “budget flexible” when there is a hard number the CFO has already blessed. Aspirational constraints are worse than no constraints, because the agency plans against them and then has to replan when the truth surfaces. Tell us the real numbers on day one. We can work with hard truths. We cannot work with soft fictions.

Definition of success: how we will know it worked

The final pillar is the one most often missing entirely. What, specifically, will be measured to determine whether this project succeeded? By whom? On what timeframe? Against what baseline? Success has to be defined before the work starts, because success defined after the work starts is not success; it is retrospective justification. We have watched too many projects declared successes because no one could remember what would have counted as a failure.

Good success definitions have four properties: they are quantitative wherever possible; they name the measurement instrument (analytics platform, survey, sales report, CRM field); they identify the owner of the measurement (the person accountable for producing the number); and they specify the moment at which the measurement is made. “We will consider this successful if qualified pipeline attributable to organic search increases by thirty percent within six months of launch, as measured by our marketing operations team in HubSpot against the trailing six-month baseline.” That sentence rules out a hundred forms of drift on its own.

Brief versus RFP: when to use which

Executives ask us often whether the document they need is a brief or an RFP, and the answer matters more than the terminology suggests. The two instruments serve different purposes, and using the wrong one for a given situation adds months to the timeline and reduces the quality of the eventual output.

A brief is written for a chosen partner or a short shortlist you already trust. It assumes the strategic conversation will be co-created — that you have a clear enough view of the outcome to hand the work to a partner and let them help shape the approach. Briefs are faster, more collaborative, and typically produce better creative work because they invite dialogue rather than compliance. They are the right instrument for anyone who has already done the partner-selection work and is now doing the mandate-setting work.

An RFP is written for a competitive evaluation among vendors you do not yet know. It formalizes the requirements, defines the evaluation criteria, and asks each vendor to respond against a common framework so that comparisons are apples-to-apples. RFPs are slower, more bureaucratic, and often produce weaker strategic responses because vendors are optimizing for scorability rather than for the best strategy. They are appropriate when procurement or compliance rules require a formal process, when the engagement is large enough that structured competition is genuinely useful, or when you truly have no prior view of who should win.

The category error we see most often is executives writing an RFP because they think it is what serious buyers do, when in fact they already know which two or three agencies they would seriously consider. The result is that they spend three months running a formal process that could have been an eight-week brief-and-select cycle, they receive templated responses that hide each agency’s actual thinking, and the winning agency starts the real work later, poorer, and with less energy than if they had been briefed directly. Formality is not the same as rigor. Rigor lives in the four non-negotiables, not in the number of pages.

The rule we recommend to clients: use a brief when your shortlist is three or fewer agencies and you already have some directional view of what good would look like. Use an RFP when your shortlist is five or more, when procurement or public-sector rules genuinely require it, or when the engagement is large enough (typically well above a million dollars in total spend) that formal comparability is a meaningful part of the evaluation. Everywhere else, a brief is the faster and better instrument.

The C.L.E.A.R. brief framework

Once the four non-negotiables are settled, we recommend a five-section structure that clients find easy to reuse across project types. We call it C.L.E.A.R. because the acronym is memorable and because clarity is exactly what a brief is for. Each section maps to a specific question the agency will otherwise have to guess at, and each section is scoped to be short enough that a senior strategist can read the whole brief in ten minutes.

The genius of the structure is not the letters; it is the discipline of writing each section only long enough to answer its question. Briefs that mushroom to twenty pages usually contain the four non-negotiables buried inside a lot of context that the agency does not need. Briefs of six well-structured pages usually contain everything a senior team needs to start work with confidence. When you catch yourself writing a fifteenth paragraph, ask which of the five sections that paragraph belongs to and whether it is answering a question the agency actually needs answered.

How to write the outcome statement

Because the outcome is the single load-bearing sentence in the brief, it is worth writing several times before you commit. The best outcome statements are not composed; they are compressed. You start with a paragraph, argue about it, remove the parts that could belong to any project, and end up with a sentence that would only make sense for this project at this moment.

Here is the structure that works: verb, quantified change, specific audience, timeframe, measurement. “Increase [what is happening] by [how much] among [whom] within [when], as measured by [how].” Every element earns its place. Verbs that mean something (increase, reduce, launch, replace, position) beat verbs that mean nothing (support, enable, drive, deliver). Quantified change (from twelve to twenty percent, from four to eight per week, from thirty seconds to twelve seconds) beats directional language (“grow”). Specific audience (the operations lead at a mid-market industrial company) beats segmentation (“B2B buyers”).

Two examples of outcome statements we have improved together with clients recently, from a fuzzy first pass to a version that shaped every downstream choice.

Sharpening the outcome does not mean you have to commit to it publicly as a target the whole company will be measured on. It means the brief carries a specific enough hypothesis about what success looks like that every downstream design decision has a north star. If it turns out post-launch that the number moved from eighteen to twenty-eight rather than to thirty-six, the project is a partial success and everyone can have a substantive conversation about why. If the outcome was “build a new website,” there is nothing to talk about because the deliverable shipped and nothing was ever pegged to anything.

How to describe your customer: real people, not personas

The audience section of most briefs reads like a demographic form filled out by a lawyer. Age range. Job titles. Company size. Regions. It is accurate, unhelpful, and entirely disposable, because it tells the team who the audience is not without ever telling them who they are.

The alternative we recommend is to describe one specific person — either a real customer you interviewed, or a plausible composite of three or four — in three concentric layers.

The demographic layer is the standard set of filters: role, seniority, industry, company size, geography, tenure. This is the layer most briefs stop at. Include it, but keep it to one paragraph. It is the filter, not the compass.

The situational layer describes what is on the person’s calendar this week and what pressure is on them. Are they three months into a new role and trying to make a mark? Are they defending a project that just missed its numbers? Are they preparing a board update? This layer is what makes a design feel relevant instead of generic. It is the difference between copy that reads as marketing and copy that reads as an email from someone who understands what today is like.

The verbatim layer is a quote, or ideally three, from the actual person. Not a synthesized persona quote (“Sarah wants to improve efficiency”) but a real sentence you either heard or plausibly reconstructed (“Our finance team keeps asking me how I’m going to justify the license cost this year — if I can’t show them a clear number, this project stalls”). If your brief cannot supply three real quotes from three real customers, spend the week getting them before you write the brief. Three thirty-minute interviews will improve the resulting work more than any amount of secondary research.

Below is the template we ask clients to fill in, in the audience section of any brief. It looks trivially short and it takes surprisingly long to fill in well.

The last line matters as much as the first three. Buying decisions are almost never between your product and no product; they are between your product and a specific alternative, or between doing anything and doing nothing. Naming the alternatives in the brief prevents the team from writing copy that pretends the decision happens in a vacuum. It does not.

Sharing budget: why hiding it hurts you (with math)

The most common failure of nerve in briefs is the refusal to share budget. Executives worry that naming a number will cause the agency to charge exactly that number, no matter how much less the work could cost. It is a reasonable-sounding fear. It is also, in our experience of thousands of engagements, almost exactly backwards.

Here is the math. When you refuse to share a budget, the responding agency is forced to make one of three moves. They pitch what they would love to build (usually well above what you were prepared to spend, and it dies in the CFO’s inbox). They pitch what they think you can afford (usually below what you were prepared to spend, and now the work is under-scoped). Or they pitch a menu of options that puts the burden of trade-off decisions back on you at exactly the moment you were hoping to outsource that thinking. All three cost time. None of them save money.

Now compare to the world in which you shared a range: “Our budget for this project is between $180,000 and $250,000, with $250,000 requiring board approval.” The agency now knows exactly what shape of proposal to build. They can spend their creative energy on what to include rather than on how big to make the response. They can flag honestly, on day one, if the outcome you described will require more than the top of the range — a conversation you desperately want to have before you commit, not after. And the number you eventually pay is, empirically, closer to the middle of the range you shared, not the top of it, because agencies want to win the work and know you have a ceiling.

The concrete impact we have measured: engagements that share a budget range in the brief reach a signed statement of work an average of thirty to forty percent faster than engagements that hide it, and they experience roughly half the mid-project change orders. Both effects are compounding. The time you save moves the launch date earlier, and the change orders you avoid pay for themselves ten times over.

Two practical notes on how to share it. First, share a range, not a point number. “$180K to $250K” invites a strategic conversation; “$200K” invites a $200K response regardless of whether $180K would have worked. Second, share the shape of the money: how much is one-time versus ongoing, what is above versus below your discretionary threshold, and what triggers require additional approval. Shape is often more informative than the raw number.

Reference examples: doing them right

The reference section is where briefs most often waste their potential. Clients send us a list of eight URLs, no annotation, subject line “some inspo,” and expect us to reverse-engineer their taste. It cannot be done reliably. The reason we are looking at references at all is that words are a poor medium for conveying aesthetic preferences and strategic positioning — but references without annotation are almost as ambiguous as words, because we cannot tell what specifically resonates or grates.

Three principles turn references from decoration into decision-support.

Mix loves, hates, and near-misses. Three examples of things you love, two of things you dislike, and one or two that are directionally right but imperfect are far more informative than eight loves. Contrast is what teaches an agency team what your preferences actually are. Universal admiration is much harder to reverse-engineer than a specific pattern of “yes, no, almost.”

Annotate every reference with one to two sentences. Not “beautiful” or “clean” but “the confidence in the type hierarchy, the restraint of the color palette, and the way the case study text respects the reader’s intelligence” — or, for a negative example, “the animation is showy, the copy is buzzword-heavy, and the product benefits are impossible to find above the fold.” The annotation is the reference; the URL is the citation.

Separate the strategic references from the aesthetic references. Strategic references show us how a brand positions itself in the market (“we admire how Company X talks about their category”). Aesthetic references show us what visual language you gravitate toward (“we like the tonal restraint of Company Y’s art direction”). Mixing them causes teams to conflate positioning with design, which produces cargo-cult results: a website that looks like the reference without doing what the reference actually does.

A good reference set for a brand or website project might look like this: three brands whose overall positioning we admire, with a sentence each on what specifically we admire; two brands whose visual language we admire, with a sentence on the properties we want to inherit; two brands or sites that we want to be clearly distinct from, with a sentence on why; and one or two “so close, but not quite” references, with a sentence on what specifically is wrong. Ten references, ten sentences, one page. It changes what the agency can deliver.

Approval structure: who signs off on what

If we had to identify the single fastest way to save an agency engagement four to six weeks of drift, it would be to name the approvers before the work starts. Every engagement we have watched stall out has stalled at a specific approval that nobody had planned for. Every engagement that flew, flew because there was a named human at every gate and that human knew what they were being asked to decide.

The approval section of the brief should answer four questions for every major phase of the project.

Who is accountable? One name. Not a team, not a committee, not a role — a person. They may consult widely, but the decision is theirs and the agency talks to them. Committee approvals are how projects lose forty days.

Who must be consulted before that person decides? These are the stakeholders whose input the approver is required to gather. Naming them ensures they are looped in early rather than late, and it distinguishes their input from the decision itself, which belongs to the approver.

Who must be informed after the decision is made? These are the stakeholders who need to know the decision was made but do not have vote or veto. Informing them well prevents the “wait, why did we do that” conversation two months later that so often turns into rework.

What is the SLA on the approval? How many business days does the approver have to respond, and what happens if they miss the window? “Silence equals approval after five business days” is a legitimate and often necessary clause. Without an SLA, agencies experience approvals as an infinite queue, and the timeline drifts by however long the slowest response takes.

The best briefs we receive present this as a compact table at the end of the constraints section: phases across the top, roles down the side, one letter (A for accountable, C for consulted, I for informed) in each cell, and an SLA column. It is a page. It changes everything.

Timeline expectations: what is realistic

The other frequent gap in briefs is a timeline that does not survive first contact with reality. Executives arrive with a launch date pegged to an external event (board meeting, trade show, product release), the agency has to work backward from it, and the middle of the project turns into a squeeze because no one negotiated realistic milestones up front. Timeline in a brief needs to name both the fixed anchor (the immovable date) and the flexible milestones (everything else, subject to negotiation).

Here is the shape we recommend, with realistic ranges for common project types. These are total durations from brief acceptance to public launch, assuming the four non-negotiables are answered and the client’s side is staffed to move at agency pace. Halve the durations if you skimp on any of the non-negotiables and expect drift.

These are averages, not guarantees; the range moves depending on complexity and stakeholder density. What matters for the brief is that the timeline you write is the timeline you actually believe. Timelines chosen to sound impressive rather than to reflect reality are the single most reliable predictor of a stressed, over-budget, under-satisfying engagement. When the true timeline is longer than you would like it to be, the honest thing to do is either accept the honest timeline or narrow the scope until the shorter timeline is achievable. Neither of those conversations gets easier by postponing it.

Good brief vs. vague brief: side by side

The abstract advice above is easier to internalize with a concrete comparison. Below is the same website project, described first as it typically arrives in our inbox and then as it looks after we have worked with the client to sharpen it. The difference is not that one is prettier; the difference is that one is buildable.

The vague version above generated four rounds of concept revision and slipped by seven weeks in the version of this story we lived. The sharp version, on a comparable project, generated one round of concept refinement and launched on the anchor date. The clients had similar budgets, similar constraints, and similar ambition. The only meaningful difference was the brief.

Category-specific brief: rebrand

Different project types put different pressures on the brief. The four non-negotiables and the C.L.E.A.R. framework apply universally, but the emphasis shifts. Here are the five categories that account for most of our engagement work and what the brief needs to emphasize for each. We recommend using this section as a checklist when you next write a brief in one of these categories.

A rebrand is not a logo project. It is a strategic decision to reposition the company for a next phase, expressed through the visual and verbal identity system. Rebrand briefs that treat the deliverable as “a new logo and some brand guidelines” almost always produce a new logo and some brand guidelines that fail to move the underlying market perception. The brief needs to carry the strategic weight the deliverable will otherwise silently invent for itself.

What a rebrand brief has to answer beyond the non-negotiables:

• What has changed in the business that requires a rebrand now? New leadership, category expansion, a market repositioning, a merger, an IPO track, a loss of relevance? The trigger is not decorative — it shapes what the rebrand must accomplish and what it must not touch.
• Which equities of the current brand must survive? The customers who love the current brand are not confused; they chose you for reasons. Name the reasons. A rebrand that strips out the equities the customers valued is a rebrand that loses the customers who loved the old one and does not immediately gain the ones who might love the new one.
• What is the rollout plan and who bears the cost? A rebrand touches every artifact the company produces — site, sales deck, packaging, signage, invoices, email signatures, uniforms, business cards, product UI, retail environments. Naming the scope of rollout and the budget attached to it separates a rebrand from a logo redesign.
• What are the sacred cows? The colors the founder loves. The typeface the CMO refuses to give up. The tagline the sales team has finally learned to say. Naming these up front lets us either work within them or negotiate them explicitly. Discovering them by accident in a concept review is expensive.

Category-specific brief: website

Website briefs fail because clients describe features (pages, sections, integrations) instead of behaviors (what visitors should do, believe, feel, and then act on). A good website brief starts from the visitor’s journey and works backward to the pages that journey requires. It also acknowledges that a modern marketing site is a product, not an artifact: it has to be measured, iterated, and maintained, and the brief has to name who owns each of those functions post-launch.

What a website brief has to answer beyond the non-negotiables:

• What is the top action the visitor should take, ranked? If a visitor does exactly one thing on the site, what should it be? If two, what is the second? A ranked list of desired behaviors is the tightest constraint you can give a design team. Un-ranked lists (“we want them to demo, sign up, subscribe, or contact us”) get treated as four coequal priorities and result in a site where no action stands out.
• What is the visitor arriving from? A visitor arriving from a paid ad has different context than one arriving from a partner co-marketing email or an organic search. The brief should identify the top three arrival contexts and what each visitor needs to see first to convert.
• What is the technology posture? CMS choice, framework, hosting, integrations, analytics, personalization, internationalization — these are decisions the brief either makes or delegates. Delegating is fine; obscuring the decision is not.
• Who owns the site after launch? Content updates, technical maintenance, analytics review, iteration decisions, ownership of the CMS. A site with no named post-launch owner is a site that will be six months out of date within a year of launch.

Category-specific brief: campaign

Campaign briefs are the ones we most often see written with real craft, and also the ones most often derailed by the absence of legal, regulatory, or media-buying constraints that surface at the last minute. Campaign work happens on tight timelines, and every day lost to a surprised legal review or a missed media flight is a day the campaign is dark. The brief needs to surface every party whose approval will be needed and every dependency the campaign has on external calendars.

What a campaign brief has to answer beyond the non-negotiables:

• What is the single insight the campaign is built around? Campaigns without an insight are executions of tactics. A good campaign brief includes one sentence describing the truth about the audience that the campaign has discovered and will speak to. Everything downstream flows from that sentence.
• What are the channels and their weights? Not just where the campaign runs, but how much of the budget lives in each channel and why. Weighting decisions belong in the brief because they shape creative decisions — a campaign designed for out-of-home is not the same campaign designed for LinkedIn.
• What are the regulatory or legal review requirements? Financial services, healthcare, alcohol, cannabis, children’s products, comparative advertising, endorsements — each has approval overhead that must be scheduled into the timeline, not discovered mid-flight.
• What is the media flight and what does the calendar require? Publications close for issues on specific dates. Broadcast has hard flight windows. Digital has creative-refresh cadences. The brief should surface every calendar dependency.

Category-specific brief: product launch

Product launches are the highest-coordination briefs we work on because they touch every function of the client organization simultaneously. The brief has to align product, engineering, marketing, sales, customer success, support, and often finance and legal. When it does not, the launch splits into two launches happening in parallel — a product launch and a marketing launch that reference different audiences, different messages, and different timelines — and the market notices.

What a product launch brief has to answer beyond the non-negotiables:

• What is the launch tier? Not every release deserves a full launch. Categorize the launch (tier 1: strategic company-defining launch; tier 2: significant new capability; tier 3: notable enhancement; tier 4: incremental update) and align the investment level accordingly.
• What is the moment being created? Launches are conversations you are trying to start with the market. The brief should describe the conversation, not just the release. “We want CIOs to say to their teams: ‘we should be looking at X.’” is a launch outcome. “We want people to know we shipped a new feature” is not.
• What is the internal launch? The people who most need to internalize the launch are the sales, success, and support teams who will talk about it every day. The brief should identify the internal launch deliverables (enablement, talk tracks, FAQ documents) as first-class artifacts, not afterthoughts.
• What is the analyst and press strategy? Named analysts to brief in advance, press embargoes, exclusive interviews, third-party validation. Coordination with external voices is often the difference between a launch that lands with editorial context and one that lands as a company announcement.

Category-specific brief: ongoing retainer

Retainer briefs are the most different from the others because they describe a way of working, not a deliverable. A retainer that operates on a project-brief mindset (each month is a mini-project) never accumulates the compounding advantage a good retainer produces. A retainer built on an operating-pattern mindset (standing objectives, recurring rituals, decision rights) gets sharper every quarter.

What a retainer brief has to answer beyond the non-negotiables:

• What are the standing objectives? Retainers earn their keep by producing consistent progress against three to five long-horizon objectives, not by generating discrete deliverables. Name the objectives, state how they will be measured, and name the person accountable for each.
• What are the recurring rituals? Weekly standups, biweekly strategy reviews, monthly retros, quarterly planning — the cadence of the relationship is the operating system it runs on. Missing rituals are the single most common reason retainers atrophy.
• What are the decision rights? In a retainer, small decisions get made every week and cannot all escalate to the CMO. The brief should describe which categories of decision are the agency’s to make, which are the client’s, and which require joint review.
• What is the escalation path? When something goes sideways, who gets called, in what order, by what medium? Escalation paths written before they are needed prevent the panicked ambiguity that follows the first real problem.
• What is the quarterly re-planning cadence? Retainers stale without regular re-planning. A named quarterly review that revisits objectives, reallocates budget across work areas, and prunes what is no longer producing value keeps the relationship fresh.

Red flags agencies watch for in briefs

Since the whole point of a good brief is to start an engagement healthy, it is worth stating openly what we look for — and quietly worry about — when a brief lands in our inbox. If you find your own brief carrying any of these patterns, treat them as invitations to sharpen before you send.

“Please propose a budget.” Almost always means no internal alignment has happened yet, which means whatever we propose will land in a debate we cannot participate in. We flag it, we ask for a range, and if none exists we suggest scoping a small paid discovery first.

An approver list of five or more people. Almost always means no single accountable owner. Committees produce mush. We look for the one name and we ask who it is if the brief doesn’t say.

“It’s just a logo” / “It’s just a landing page.” Almost always means the strategy conversation has not happened yet and will surface at exactly the wrong moment, usually in concept review. We push back gently in scoping.

A three-week timeline for substantive creative work. Almost always means something external is broken (a board meeting, a launch date, a funding pitch) and the brief is a way to push the mess downstream to us. We prefer to talk about whether the mess is fixable.

No success metric at all. The scariest one. It means the engagement will end when the deliverable ships and nobody will ever know whether it worked, which means the client will not be able to justify continuing the relationship or scoping the next phase. Both of us lose.

A thirty-page brief with a thousand appendices. Signals indecision dressed as rigor. Long briefs are usually short briefs buried under everything the writer was afraid to leave out. We would rather have four sharp pages than thirty comprehensive ones.

A tone of “wow us.” The invitation to surprise the client with brilliance in the first meeting is almost always followed by the disappointment that the surprise did not match the taste the client had not articulated. Wowing is not a substitute for briefing; it is a symptom of underbriefing.

None of these are fatal. Every one of them can be surfaced early, discussed openly, and fixed before the engagement is scoped. The reason we mention them at all is that most clients would prefer to know what we are reading for — and we would prefer to work with clients who write the brief we secretly wish everyone wrote.

Common failure modes in briefing

Beyond the red flags themselves, there are patterns of failure that emerge only after briefs are written. These are the ones we watch clients repeat across engagements, and they are worth calling out explicitly.

Writing the brief after the internal debate rather than as the internal debate. Some clients write the brief as a way of documenting a decision that was already made. Others use the brief as the forcing function that produces the decision. The second use is the better one. Writing the brief together, as a leadership team, forces the disagreements about outcome, audience, and success to surface at the cheapest possible moment.

Under-investing in the outcome sentence. Because the outcome is the shortest thing in the brief, it gets the least drafting time. That is exactly backwards. The outcome sentence should be redrafted five to ten times, argued about with your co-approvers, and stress-tested against your competitors’ possible versions of the same sentence. It is the load-bearing beam.

Describing the deliverable in too much detail. Well-intentioned clients try to be helpful by specifying features (“must have a testimonial carousel, an interactive product tour, an ROI calculator”). This forecloses better solutions the agency might have proposed. The rule of thumb: describe the outcome, not the means; describe the constraints, not the solution. If a specific feature is genuinely non-negotiable, mark it as a constraint. If it is a preference, leave the door open.

Using the brief to relitigate past disagreements. Occasionally briefs contain sentences that are clearly the result of a compromise inside the client team — language that satisfies competing internal factions rather than describing what the project should be. Agencies feel this immediately, and it produces work that does not fully commit to any direction. Resolve the internal debate before you write the brief; use the brief to describe the resolution, not the debate.

Overlooking legal, brand, and technical governance early. The teams whose approval matters most at the end are often the teams least included at the beginning. Bringing legal, brand governance, and technical architecture into the briefing conversation early — even in a brief consultation — prevents the late-stage discovery that a critical constraint was missed.

Confusing formality with clarity. A twenty-page RFP-style document with sections numbered to three decimal places is often less clear than a six-page brief written in complete sentences. Formality is a defense mechanism against ambiguity that does not actually reduce ambiguity. Clarity does. Trust the shorter document.

Failing to socialize the brief internally. The brief must be read and approved by the people who will approve the work. If the CEO signs off on the brief but the head of sales, who will be presented with the work in month three, has never seen the brief, the head of sales’s opinion arrives as a surprise. Socializing the brief with all major stakeholders before it is sent to the agency prevents a large class of late-stage rework.

The revision process: how to give feedback that lands

A brief that starts a project well can still be undone by a feedback process that operates poorly. Because feedback is where the client’s influence on the work is most concentrated, it deserves as much thought as the brief itself. Below are the five moves we ask clients to internalize before revisions begin.

Consolidate feedback through one voice. The single most damaging pattern in agency-client feedback is the arrival of five separate emails from five separate stakeholders, each with different priorities, some contradicting each other. It is not a communication problem — it is a governance problem. Consolidate the stakeholder feedback internally, resolve internal contradictions before they reach the agency, and send one voice with one prioritized list.

Prioritize using a P1 / P2 / P3 tier. Not all feedback is equal. P1 items are must-fix (they violate the brief or block launch); P2 items are should-fix (they meaningfully improve the outcome); P3 items are nice-to-fix (they are preferences that would be considered if time allows). When every note is treated as equal weight, teams either fix everything (blowing the timeline) or fix arbitrarily (frustrating everyone). Explicit tiers let the team allocate revision effort where it will most move the outcome.

Respond within an agreed SLA. Every review round should have a stated response window (typically three to five business days for concepts, one to two for later stages). Late feedback compounds worse than late anything else, because it forces the team to context-switch back to earlier phases just as they are engaged with later ones. If the SLA cannot be met, the honest move is to renegotiate the timeline, not to slip feedback and pretend the timeline still works.

Separate observations from prescriptions. An observation names a problem (“the hero doesn’t convey the right emotional register”). A prescription names a solution (“change the hero image to a photograph of our office”). Observations invite the agency to solve the problem with the full range of options they have available; prescriptions foreclose better solutions the agency might have proposed. Prescriptions are appropriate for things that must be a certain way for legal, technical, or brand reasons. Otherwise, prefer the observation.

Cite the brief when rejecting a direction. When you push back on a direction the agency has proposed, connect the pushback to the brief. “This doesn’t fit — the audience section describes buyers who explicitly want restraint, and this feels performative” is a redirect the team can act on cleanly. “I just don’t like it” is a redirect that will produce another round with no meaningful improvement, because the team has no idea what direction to move in. The brief is your ally in these moments; use it.

Feedback given this way compresses revision cycles by roughly a third in our experience, and it dramatically improves the quality of the eventual work — because the team can spend energy on solutions rather than on parsing conflicting or ambiguous feedback. It also protects the relationship, because the client’s reactions arrive as considered judgments rather than as impulses.

International and remote brief considerations

An increasing share of our engagements are cross-border or fully remote, and both patterns put additional pressure on the brief. When the client team, the agency team, or the target audience live across time zones or languages, the brief has to carry weight that in-person context would otherwise supply. It has to be a more durable and self-explanatory document, because there is less chance for casual clarification.

Three practical additions for international briefs. First, name the languages the work must live in and identify one native speaker per language as the linguistic approver — not the translator, but the person who will sign off that the tone lands in that market. Machine-translated brand work reads as machine-translated to every native speaker. Second, name the cultural sensitivities relevant to the geographies in play. Colors, gestures, humor conventions, religious or political references, and even numeric conventions can carry meanings the originating team is not aware of. The brief should surface these explicitly rather than trusting the team to catch them retrospectively. Third, specify the local regulatory and legal landscape that the work must respect. Data protection, advertising standards, competitive-claim rules, and platform policies vary significantly by jurisdiction, and the review overhead varies with them.

For fully remote engagements, the brief also has to substitute for the ambient information exchange that happens in shared workspaces. Two additions here: an explicit communication protocol (which channels are for what — async writing, synchronous review, urgent escalation), and a documented ritual cadence (weekly synchronous review, biweekly strategy discussion, monthly retrospective, quarterly re-planning). Both of these prevent the ambient drift that fully remote teams experience by default when nothing forces them together at regular intervals.

The best remote-first briefs we receive are essentially self-contained operating manuals for the engagement. They read as if the writer had assumed the reader would never have the chance to ask a follow-up question. That posture — write it as if you cannot iterate — produces the sharpest briefs we see, regardless of whether the work is remote or co-located.

Long-term partnership implications

The best client-agency relationships we have — the ones that stretch across five, eight, twelve years — are built by clients who briefed well from the start and got better at it over time. Not because they optimized for extracting the maximum value from the agency, but because they took seriously the idea that the brief is the seat of the client’s craft. Great clients are great partly because they are great briefers, and great briefers become great clients because their agencies can do their best work for them.

There are three dynamics worth naming here. The first is compounding trust: each engagement where the brief was sharp and the outcome landed builds credibility that allows the next brief to be slightly higher-stakes, slightly more ambitious, slightly more delegated. Over time the client and agency develop a shared shorthand that lets briefs get shorter without losing precision, because the accumulated context does the work that the words used to have to do. This is the version of a mature retainer where the biweekly brief is a two-line Slack message and both sides understand it perfectly.

The second is portfolio thinking. Great long-term clients treat the sequence of briefs as a portfolio rather than as isolated projects. They know that the rebrand brief this quarter has implications for the website brief in six months, that the campaign brief this fall assumes the messaging framework from last spring, and that the retainer they run in parallel is the connective tissue that keeps everything consistent. The individual briefs get better because they are written with the whole in mind.

The third is agency respect for the process. When clients invest in the brief the way we have described, agencies respond by investing more of their best people in the response. Senior strategists join engagements they would otherwise have delegated. Creative directors get personally involved. Timelines get treated as commitments rather than as aspirations. This is not a formal exchange — no one wrote it down — but it is remarkably reliable. The clients who brief well get the best work agencies can do, in part because they have proven that they can hold up their end of the bargain.

None of this happens in the first engagement. It happens over the course of two or three well-briefed projects that leave both sides feeling more trust than they started with. The brief is where that trust either accumulates or gets spent. Choose accumulation.

Bringing it all together: the brief checklist

If you take one artifact from this article, take this: a checklist you can hold your next brief up against before you send it. If every line is a “yes,” the engagement it starts has a very high probability of landing well. If more than two lines are “no,” the brief is not yet ready to send.

Ten checkpoints. A well-run leadership team can walk through this list in an hour and either send the brief with confidence or identify exactly what needs another day of thought. That hour is the highest-leverage hour you will spend on the project. Spend it.

The brief is where clients most often underinvest and where the return on additional investment is highest. It is also, from our side of the desk, the artifact that most predicts whether the engagement will produce work we are proud of. When the brief is sharp, our best people bring their best thinking, the timeline holds, the revisions stay focused, and the launch lands. When the brief is fuzzy, we spend the first third of the engagement writing the brief the client should have written, and the whole engagement stays in catch-up mode. Neither of us wants that.

Write the brief you would want to receive. If you would like a partner to help you write it — either as a paid discovery preceding a larger engagement or as a standalone artifact you can then take to a shortlist — that is work we do regularly and enjoy. Either way, treat the brief as the most important piece of writing in the project. Because that is exactly what it is.