Agency brief

What an agency brief does

An agency brief explains the problem a client wants an agency to help solve, the audience involved, the outcome required, and the conditions under which the work must happen. It creates a shared starting point for decisions. A useful brief makes priorities visible without pretending that the client already knows every answer the agency should develop.

The brief can support a new project, an ongoing assignment, or an agency selection process. Its exact form depends on the work. A website improvement assignment needs different operational detail from a brand campaign, but both need a clear explanation of the challenge and a way to judge the response.

The document is only part of briefing. Discussion helps uncover assumptions, resolve contradictions, and confirm that both sides interpret the task consistently. Sending a file does not establish agreement if the agency reads it as a request for creative concepts while the client expects a fully costed implementation plan.

Start with the problem rather than a preferred execution

Describe the situation that makes the work necessary. Explain what is happening, who is affected, and why it matters now. Separate observations from interpretations. “Qualified prospects abandon the comparison page” describes a pattern; “we need a video” proposes a solution before the cause has been established.

A proposed execution may still be a genuine constraint. If a conference requires a printed guide, say so and explain the requirement. The problem comes from presenting an untested preference as though it were the only possible route to the desired outcome. Give the agency enough context to challenge the route constructively.

A useful problem statement is narrow enough to guide tradeoffs. “Improve our marketing” gives almost no direction. “Help operations managers understand whether our service supports their approval workflow before requesting a consultation” identifies an audience, an understanding gap, and a relevant decision. It still leaves room for the agency to determine the most effective response.

Connect business outcomes to communication objectives

State the commercial or organizational outcome that motivates the assignment, then explain the part communication can realistically play. A revenue objective may depend on pricing, availability, sales follow-up, and product quality as well as marketing. The agency should understand that wider context without being assigned responsibility for factors it cannot control.

Translate the challenge into an observable audience change. People might need to recognize a problem, understand a distinction, consider an alternative, complete a suitable enquiry, or use a service correctly. Choose the change that matters for this assignment rather than collecting every desirable outcome into one list.

Define success measures alongside the objective. Include the baseline where available, the reporting period, the population, and the measurement owner. If the baseline is unknown, identify the discovery work required to establish it. A target can be a planning aspiration, but it should not be presented as an evidence-backed forecast merely because it appears in a formal brief.

Describe the audience through its decisions

Give the agency enough audience context to understand what people are trying to accomplish. Roles, situations, motivations, barriers, and existing knowledge often matter more than a broad demographic label. Explain what decision the audience faces and what information would help it make that decision.

Use evidence carefully. Customer interviews, enquiry records, behavioral data, and sales observations can reveal different aspects of the problem. Identify the origin and limitations of important findings in the working materials. A small set of interviews can provide useful hypotheses without establishing how common every opinion is across the entire market.

Distinguish primary and secondary audiences. A campaign might need to persuade a user while reassuring a financial approver. The brief should explain whether both groups need dedicated communication or whether one is the main focus. Trying to address every possible stakeholder equally can produce work that feels relevant to nobody in particular.

Explain the offer and the evidence behind it

Describe what the organization can credibly promise and why the audience should believe it. Include the product or service details necessary to avoid misleading interpretations. If implementation requires specific conditions, or if an offer applies only to a defined customer group, make those boundaries visible early.

Provide proof that supports the intended message. This might include verified product capabilities, customer research, demonstrations, documented service processes, or appropriately supported case material. Explain what has been approved for public use and what is background information only. The agency should not have to guess whether an internal claim can become a headline.

Avoid substituting adjectives for a proposition. Words such as innovative, premium, and seamless do not explain a meaningful difference by themselves. Describe the practical advantage, the audience for whom it matters, and the evidence that makes it credible. If that strategic work remains unresolved, include it explicitly in the assignment instead of hiding the gap inside a list of brand attributes.

Set scope, deliverables, and exclusions

Specify what the agency is expected to produce or decide. Distinguish strategy, research, concepts, production, implementation, and ongoing optimization. A request for a campaign does not tell a supplier whether media planning, landing pages, measurement setup, or localization are included.

Use concrete deliverable descriptions where the output is already known. For a website assignment, identify the templates, key journeys, content responsibilities, integrations, and handover expectations. Where discovery should determine the final output, describe the discovery deliverables and the decision point that will establish implementation scope.

State important exclusions and dependencies without turning the brief into an exhaustive contract. If your internal team supplies photography, the agency needs to know when and in what form it will arrive. If translation is outside the assignment, identify who owns it. These boundaries protect the schedule and make competing proposals easier to compare because they reduce hidden differences in assumptions.

Share budget and timing as design inputs

Budget affects which approaches are feasible. Provide an approved amount or a realistic range, and explain what it must cover. Agency fees, production, technology, media, travel, research, and taxes may sit in different budgets. A proposal cannot be evaluated fairly if one party assumes a media budget is additional while another assumes it is included.

Give dates meaning. Distinguish a fixed external deadline from an internal preference, and explain which milestones must precede launch. Include time for client feedback, technical integration, legal or specialist checks where needed, and the agency's actual production process. An attractive launch date is not a workable schedule without those dependencies.

Invite explicit tradeoffs if time or money is constrained. The agency might propose a smaller initial scope, a staged release, or a different production approach. Evaluate these options against the objective rather than treating every adjustment as a failure to follow instructions. A transparent constraint can improve the solution; an undisclosed constraint often creates rework.

Clarify brand, technical, and accessibility requirements

Share the requirements that materially shape the work. Brand guidelines can define identity, tone, and approved assets. Technical requirements might cover the existing website stack, analytics environment, security review, integration points, or supported content formats. Accessibility requirements should identify the intended evaluation target and relevant user journeys.

Separate mandatory conditions from preferences and examples. A reference website may illustrate a useful interaction without authorizing a copy of its visual design. Explain what you like about the reference and what should be different. Otherwise, the agency may imitate a surface treatment when you actually wanted the underlying clarity or functionality.

Keep requirements usable. Link working teams to the current source of truth and name someone who can resolve questions. A large archive of conflicting documents is not a clear specification. If a requirement is uncertain, mark it as unresolved and explain when it will be confirmed. Silent uncertainty tends to reappear later as an unexpected revision.

Assign decision rights and a feedback process

Identify the person who can approve the direction, the specialists who must be consulted, and the people who provide input. These roles can differ. A stakeholder may have valuable expertise without having authority to change the assignment independently. The agency needs to understand how conflicting comments will become one client decision.

Agree on feedback format and timing. Consolidated feedback should explain the issue against the brief, distinguish mandatory corrections from suggestions, and identify the desired outcome. “This does not yet explain the eligibility condition” is more actionable than a collection of unrelated personal preferences about the design.

Plan for absences and escalation. If the main approver is unavailable, identify who can keep the project moving. If feedback changes the agreed scope or objective, route it through a visible change decision. A clear process reduces the risk that an agency spends time satisfying one stakeholder only to discover that another had a different, unstated definition of success.

Work through an example website assignment

Consider a fictional B2B service whose comparison page receives 2,000 eligible visits each month and produces 40 suitable consultation requests. The observed request rate is two percent. Customer conversations suggest that visitors struggle to understand which service configuration fits their approval process. This is a hypothesis to investigate, not a proven explanation for every abandonment.

A useful brief asks the agency to clarify the comparison journey, test comprehension with representative users, and deliver an accessible page implementation within the existing site. It includes the product differences, existing analytics definitions, enquiry qualification rules, approved claims, technical constraints, and the internal owner of sales follow-up.

The client might set a planning target of a three percent suitable-request rate. At the same 2,000 eligible visits, that would be 60 requests, an increase of 20. Moving from two to three percent is one percentage point, or a 50% relative increase. The brief should label the target as an aspiration and specify how seasonality, traffic mix, and qualification consistency will be considered when evaluating results.

The assignment also needs quality guardrails: visitors should understand exclusions, unsuitable requests should not increase merely because the form becomes more aggressive, and the implemented page should work with keyboard navigation. These conditions connect the desired business result to an experience worth delivering.

Evaluate proposals against agreed criteria

Tell the agency how its response will be assessed. Criteria can include understanding of the problem, relevance of the proposed approach, evidence of suitable capability, delivery feasibility, collaboration process, and commercial clarity. Match the criteria to the assignment instead of defaulting to whichever presentation is most polished.

Request a proportionate response. An early conversation may need a proposed method and relevant experience rather than extensive unpaid speculative production. If several agencies are involved, provide consistent information and clarify how questions will be answered. Compare like with like by identifying differences in scope, assumptions, and responsibilities.

Separate confidence in the team from enthusiasm for one initial idea. A concept can be promising while its implementation plan is unrealistic. Conversely, a thoughtful discovery approach may be more appropriate than a finished-looking solution when important audience questions remain unanswered. Evaluate whether the proposed working process can resolve the uncertainty the brief actually contains.

Use a briefing conversation to expose assumptions

Schedule time for the agency to interrogate the brief. Ask the team to explain the challenge back in its own words, identify missing information, and describe which assumptions most affect its approach. This can reveal a mismatch before expensive production begins.

Use the meeting to discuss tradeoffs, not merely to read the document aloud. Explore tensions such as a broad audience with a narrow budget, a fixed launch date with unresolved product details, or a conversion target that depends on sales operations. Record decisions and distinguish them from questions that still need investigation.

After the discussion, issue a version that reflects the shared understanding. Both sides should know which brief governs the assignment and where supporting materials live. An informal conversation can improve clarity, but unrecorded changes can also produce conflicting memories. Keep the written record concise enough to use throughout the project rather than treating it as a file that matters only on the first day.

Maintain the brief when the assignment changes

A brief should remain a decision reference as work progresses. When new evidence changes the audience, objective, scope, or constraints, update the relevant parts and explain the implications. Do not quietly replace the original target and then evaluate completed work against a standard the agency never received.

Use a simple change record: what changed, why, who approved it, and what happens to cost, timing, or deliverables. Small clarifications may require no commercial adjustment, while a new audience or integration can materially affect effort. The distinction should be discussed rather than assumed.

At the end, compare the delivered work and observed outcomes with the agreed brief. Record which assumptions proved useful, what remained uncertain, and what the next assignment should do differently. This turns briefing into an improving organizational practice. A reusable template helps, but the real value comes from making clearer decisions about each specific problem.

Related terms

• Creative brief: A document that gives direction to creative development. It can translate the broader agency assignment into a focused communication challenge, audience insight, proposition, and execution considerations.
• Content brief: Guidance for producing a particular content asset. It specifies the reader's need and practical requirements within the wider objectives established for the agency's work.
• Marketing objective: The outcome marketing activity is intended to achieve. A clear objective gives the brief a basis for prioritizing work and evaluating whether the response addresses the right problem.
• Key performance indicator: A selected measure used to assess progress toward an objective. The brief should explain its definition, baseline, reporting period, and limitations rather than naming a metric without context.
• Brand guidelines: The documented rules and principles for presenting a brand consistently. They help an agency work within the identity while making original decisions appropriate to the assignment.
• Stakeholder communications: The information and conversations used to keep relevant people aligned. Clear decision rights and consolidated feedback help prevent competing stakeholder interpretations from disrupting an agency project.