Write the campaign brief
the team can actually use.

Turn the client’s request into decisions about the result, audience, message, scope, spend and review. Use the nine-part guide and original worked example, compare eight tools, then export a complete draft with editable assumptions and exact budget arithmetic.

This is a practical editorial framework. A filled template is not a prediction, verified audience insight or recorded client approval.

Original illustration connecting a campaign brief’s scope, budget and review to the team’s production work

Collect the facts before polishing.

Find the evidence

Collect the client’s actual request, prior results, audience research and current brand guidance. Mark a missing baseline or untested audience belief as unresolved rather than filling it with confident prose.

Define the handoff

Ask what must be made, in which versions and languages, by whom and for which channel. Confirm whether quoted costs include production, distribution, coordination, tax and revisions.

Name the reviewers

Identify who comments, who resolves conflicting feedback and who records the final decision. Put review windows into the timeline rather than leaving only a launch date.

Nine useful parts of a client brief

Draft the measurable objective and scope before writing a long introduction. The headings below are a working checklist, not a universal standard; combine or expand them when the job requires it.

Context and reason to act

Explain the change this campaign responds to and the offer being promoted. Link the supporting material. A new producer should understand the problem without reading a complete company history.

Intake question: what changed, and what evidence shows that it matters?

Objective and measurement

Name the desired outcome, measurement source, current baseline if known and evaluation date. Separate a target from a forecast. If tracking is missing, make its setup a declared task.

Intake question: which observed result would make this campaign worth doing?

Audience and evidence

Describe who the campaign needs to help and what they currently do. Record the evidence behind that description. A plausible tension is still a hypothesis until you have supporting research.

Intake question: what do we know from customers, and what are we assuming?

Central message

Write the main idea in ordinary language, with the support needed to justify it. Keep message strategy separate from the finished headline: the creative team still needs room to find the expression.

Intake question: what should the audience understand after seeing the work?

Constraints and required material

List brand files, required wording, accessibility expectations, prohibited claims and any review needed before use. Give referenced assets a revision or date so the team knows which guidance is current.

Intake question: what would make an otherwise strong asset unusable?

Deliverables and boundaries

Specify counts, formats, duration or dimensions, variants, languages and included review rounds. State exclusions and what happens when new work is requested. “Social content” is too broad to schedule.

Intake question: could two producers read this list and quote the same scope?

Channels and their job

Explain what each channel contributes to the objective and which assets it needs. Separate planned paid spend from owned distribution. Do not mistake a channel list for a media-performance prediction.

Intake question: why is this channel in the plan, and who will operate it?

Budget and coverage

Make the total reconcile with production, distribution, coordination and any explicitly chosen reserve. Specify whether fees and tax are included or excluded. A reserve is an editable decision, not a hidden percentage.

Intake question: what exactly is inside the client’s stated figure?

Timeline and review responsibilities

Show the dates for decisions as well as production. Name the person responsible for consolidating feedback and the actual final reviewer. Retain the approved revision and source decision evidence in your chosen workflow; a name typed into a draft does not establish approval.

Intake question: what must be decided before the next person can start?

A worked example: LanternWay’s local walk

LanternWay is a fictional organiser. Its request is: “Help people discover the new guided walk; make a landing page and a couple of posters.” Every number below is a demonstration assumption, not a market price or measured result. The builder starts with this complete example.

Clarify the decision

The campaign promotes a new Saturday waterfront walk. The target is 40 completed registrations by the stated campaign end, measured in the organiser’s booking report. No reliable baseline is supplied, so the brief explicitly requests a tracking check. The audience is nearby residents seeking a manageable weekend activity; that description is labeled a hypothesis.

Make the scope and spend agree

The draft includes two print-ready poster variants at an assumed 120.00 each and one landing page at 480.00. Planned production is 720.00. A local paid-distribution line is 400.00; an existing email list has 0.00 planned media spend. Coordination is 180.00 and the chosen reserve is 100.00. Against a 1,500.00 budget, declared spend is 1,400.00 and the balance is 100.00.

Retain what is still open

The message promises a clear route and a manageable outing, not an unsupported health benefit. Required material includes the confirmed route, booking link and current logo. The organiser reviews the concept before the finished files. The audience hypothesis and missing baseline remain questions for the brief-back; arithmetic does not validate either.

Choose the tool the client can review.

These eight documented workflows answer different needs. Recommendations are editorial judgments, not fabricated scores or authenticated vendor tests. Current subscriptions, exact account entitlements and AI output quality were not benchmarked.

Google Docs

Use it for a text brief with line-level review. Google documents suggesting edits without changing the original until accepted. Its separate Drive approval workflow has eligible-account requirements and configurable edit/reset behavior: confirm those settings for your account. Suggestions; Drive approvals.

Notion

Use it when briefs belong with a database of deliverables in the client’s workspace. A database row is itself a page; current Notion Agent can create and edit pages and databases using permitted workspace context. Confirm the actual sharing and agent scope rather than assuming unrestricted access. Pages and databases; Current Agent guide.

Canva Docs

Use it for a visual brief-back. Current Docs documentation includes collaboration, comments and Suggesting mode, so tracked suggestions should not be treated as exclusive to Google Docs. Magic Write drafts from prompts or existing text; the facts and decisions still need review. Current Docs workflow; Magic Write.

Storyflow

Use it when the brief, reference material and emerging production plan need to remain together on a canvas. Its campaign workflow structures a board from supplied material and keeps unresolved decisions visible. View-only reading and signed-in commenting are distinct access paths. Campaign brief workflow.

HubSpot

Use it when the campaign will be operated in HubSpot. Current Marketing Studio documentation describes updating a campaign brief as context for generated assets. Campaign Agent remains a beta-access workflow with permission/settings requirements; generated drafts are not automatically published. Studio brief and campaign; Current Campaign Agent requirements.

Asana

Use it to collect structured requests and carry agreed scope into project tasks. Its forms documentation describes submitted tasks, attachment questions and routing to project sections. Intake routing does not itself establish a complete approved brief; retain the actual reviewed document and decision. Forms and project routing.

Milanote

Use it for a reference-led visual brief. Its official template collection includes advertising, design, brand and video briefs with goals, audience, messaging and creative direction. Judge it on how clearly your actual references and scope can be reviewed, rather than importing an unsupported AI-feature absence from a comparison table. Brief templates.

Adobe Express

Use it to turn an agreed text brief into a designed document. Current document templates support linked text flow, replacing content, brand colors and sharing. Check the actual document workflow and any brand-control entitlement needed; polished layout does not verify the brief’s claims. Current document template workflow.

Before the intake

Ask for source files, prior results, scope expectations, budget coverage and the people who will review. Identify confidential material before placing it in any vendor account.

At the brief-back

Read the objective, message, scope and assumptions together. Resolve contradictions in the room and name the unanswered questions with an owner and a next action.

After a decision

Retain the agreed revision and the evidence behind the decision. Put changed scope beside its budget and date consequences; do not quietly rewrite the prior agreement.

A client request becomes useful when the decisions become explicit.

A request such as “we need a spring campaign” gives a team a starting point, but leaves the outcome, audience, work, and approval process open. A campaign brief turns those open questions into a shared working agreement. It connects the business problem to a specific audience response, then explains what the team will produce within the available money and time. The creative team can develop several executions from that agreement without repeatedly guessing what the client intended.

The client’s intake document, the campaign brief, and the production plan serve different purposes. Intake captures what the client knows and wants. The brief records the choices both sides accept. The production plan assigns tasks, dependencies, and review dates. Keep them connected, but do not make the brief an unreadable collection of every meeting note and task. A useful brief should let a new contributor understand the campaign’s purpose and boundaries before opening the supporting material.

Four gaps commonly create avoidable rework. An objective describes an output instead of a result; an audience contains several incompatible groups; deliverables omit versions or channel requirements; or the timeline assumes the client can approve work immediately. Resolve these gaps before treating a date or price as settled. A beautiful presentation cannot compensate for an unassigned decision.

Start with the business problem, not a preferred execution.

“Make six videos” is a production request. “Help qualified prospects understand the installation process before booking a consultation” is a communication problem. The six videos might be appropriate, but the team should first establish what prospects misunderstand, which evidence supports that diagnosis, and where the audience will encounter the explanation. That distinction makes it possible to evaluate creative alternatives without arguing over personal taste.

A brief can be concise without pretending every answer is known. Write “baseline unavailable; client to confirm booking-report access before concept approval” when that is the truth. Mark a proposed audience insight as a hypothesis. An unresolved item should have an owner and a decision date. Otherwise a question disappears from the document while its consequences remain in the project.

Collect the inputs that change the work.

Before the intake conversation, ask for five practical inputs: the business objective and reason for launching now; existing audience or customer evidence; current brand and product reference material; the expected deliverables and distribution channels; and the available budget, launch date, and approval contacts. Ask for links or files people can actually access. “Use our latest logo” is incomplete when the folder contains several competing versions.

During the conversation, turn broad statements into decisions. If the client wants awareness, ask what audience should recognize or understand and how that change could be observed. If they want conversions, clarify the conversion event and who owns its reporting. If they want a premium tone, request examples and ask which characteristics matter: restrained language, imagery, production finish, or pricing position. Reference examples are useful when the client explains what to retain and what to avoid.

Separate fixed constraints from preferences. A confirmed event date, approved product claim, accessibility requirement, or contracted media placement may constrain the plan. A suggested color treatment or first-draft headline usually belongs in creative exploration. Put evidence beside claims, and ask who can confirm them. For regulated or sensitive statements, identify the actual authorized reviewer rather than assuming the account contact can approve everything.

At the end, read the major decisions back in plain language. Confirm what is included, which unknowns remain, and who will provide the missing information. Send the written brief for review before expanding the execution. When the client changes the objective after approving direction, the team needs a new decision about scope and timing; silently treating that change as a small copy edit conceals its real cost.

Useful questions when the answers are vague

Write the decisions in an order that exposes contradictions.

Begin with the objective and measurement. Then write the audience, the evidence behind its problem, and the single central proposition. Add the constraints, deliverable and channel tables, budget coverage, and review milestones. Write the background last, when you can explain the context that actually matters. This order helps reveal a campaign with a conversion target but no usable conversion route, or an audience promise unsupported by the product.

Connect the nine sections instead of filling nine boxes.

The background should explain why the objective matters. The objective should describe the audience response and how it will be observed. The audience section should distinguish a specific group and its barrier. The proposition should answer that barrier with a supported message. The constraints should identify what the work must respect. Deliverables should express the executions needed for the channel roles. Budget coverage should pay for those executions and their distribution. The timeline should include the client decisions that make delivery possible.

For example, a campaign intended to generate event registrations needs a confirmed event offer, a functioning registration destination, and a way to count registrations. A poster can introduce the event, a landing page can resolve practical questions, and a paid placement can reach nearby people. Describing these different roles prevents the team from expecting every asset to accomplish the entire campaign alone.

Use a deliverable table when ambiguity affects effort. Include asset, format, quantity, versions or variants, owner, review requirements, and exclusions. A “social video” without duration, aspect ratio, language, caption needs, or version count invites disagreement. The scope builder below calculates only the quantities and prices actually entered. Additional variants, usage rights, localization, or licensed material need explicit scope and cost decisions.

Use a milestone table for decisions rather than listing only the launch day. Identify when the brief is accepted, when direction is reviewed, when the client provides consolidated draft feedback, and when final files are approved. Include the person responsible for each decision. Work backward from genuine dependencies and available review time. A target date does not become feasible merely because it appears in a table.

Brief back, approve, and preserve the version.

Share the completed brief with the client and explain the interpretation of their request. Invite corrections to the objective, audience, deliverables, money, and review route. Record written acceptance of a named revision before production depends on it. A comment saying “looks good” should identify what was reviewed; acceptance of the brief is different from approval of the final creative assets.

Keep supporting research, production tasks, and reference links beside the brief. When a decision changes, update the brief revision and explain the consequence. A new audience may require a new proposition. A new placement may require another format. An earlier launch may require removing optional work. Preserve the previous agreement so contributors can understand the change without relying on memory.

A complete brief for a fictional local event.

Lantern Way is a fictional organizer offering a Saturday waterfront walk. The example below extends the same sample loaded in the builder, so its scope and arithmetic can be checked. Its registration target is an invented planning objective, not a forecast or evidence of campaign performance.

Brief decisionExample agreementWhat still needs checking
BackgroundIntroduce a new guided weekend activity and explain the route, booking process, and practical requirements.Confirm the event details and the source of the client’s demand assumption.
ObjectiveSeek 40 completed registrations by the campaign end, using the organizer’s booking report.Baseline and reporting access are unavailable; verify tracking before approving direction.
Audience and insightNearby people considering a weekend activity; assume uncertainty about the route and effort prevents some bookings.The audience insight is a hypothesis, not supplied customer research.
PropositionA clearly explained waterfront outing with a confirmed route and straightforward booking.Avoid health or accessibility promises that the organizer has not substantiated.
ConstraintsUse the approved logo, verified event information, confirmed booking link, and agreed language.Owner confirms the reference version and any required claim review.
DeliverablesTwo poster executions at 120 each, plus a landing page at 480: production total 720.State formats, review rounds, language, and whether additional variants are excluded.
ChannelsPaid placement introduces the event; the landing page answers questions; the organizer’s email points subscribers to booking.Client confirms the placements, audience access, and destination functionality.
BudgetProduction 720, distribution 400, coordination 180, reserve 100: declared allocation 1,400 against a budget of 1,500.The remaining 100 is unallocated. Confirm taxes, fees, rights, and any direct client costs.
Timeline and approvalReview the concept before draft execution, collect one consolidated client response, and approve final materials before launch.Assign actual dates and a named final reviewer rather than assuming immediate responses.

The useful feature of this example is the connection between message, assets, and decisions. The poster cannot compensate for an unclear landing page. A paid budget does not establish likely registration volume. The arithmetic confirms the declared allocation, but says nothing about commercial viability. Change the inputs to your real scope and keep the unknowns visible.

What a mid-project change looks like

If the organizer adds a second event date, first determine whether the landing page can present both dates within the approved scope. Then identify whether the poster needs an additional execution or merely a permitted revision. Confirm changes to distribution, tracking, and approval. Record the new scope, price, and review date in a revised brief. This avoids delivering an extra campaign while the original agreement still describes one event.

Choose the document around the review process.

The eight tools discussed earlier solve different parts of this workflow. The right choice depends on where clients can review the brief, how references connect to tasks, and how much account administration the studio can maintain. A template is useful only when its fields capture the real decisions; an AI-generated first draft still needs evidence, scope, and human acceptance.

ToolUseful roleDecision before adoption
Google DocsA text-first brief with comments and suggested edits that clients can review in a familiar document.Check sharing permissions. Google Drive’s formal approval workflow has account and configuration requirements; ordinary comments are not that workflow.
NotionConnect the brief to references, project pages, and structured records in an existing workspace.Test the actual client’s guest access and page relationships. Review inherited permissions before including internal notes.
Canva DocsCombine a readable brief with visual references and collaborative document review.Confirm the current sharing and suggesting experience for the intended client. Visual polish should support a complete scope table.
StoryflowKeep a campaign brief alongside visual references and other creative planning material.Verify the current distinction between viewing and authenticated commenting, and test the handoff route before inviting stakeholders.
HubSpotConnect campaign planning to the marketing environment where campaign assets and reporting already live.Campaign creation requires the relevant Marketing Hub Professional or Enterprise access and permissions. Campaign Agent availability and beta settings need separate checking.
AsanaTurn structured intake into project work and assign follow-up actions to owners.Check the required forms and project capabilities on the actual account; keep an accepted narrative brief accessible beside the task list.
MilanoteExplain a creative brief through visual references, notes, and boards.Test how the client reviews detailed deliverables, budget, and decisions. A moodboard alone does not establish production scope.
Adobe ExpressProduce a designed document connected to a team’s existing brand material.Current shared-brand roles include Editor and Consumer. Choose the appropriate role and test document access; brand access does not itself accept a campaign brief.

These are workflow comparisons, not a ranking based on independent product testing. Verify current account entitlements, external-user access, export options, and the approval route with a small sample brief. The official sources linked in the tool descriptions explain the specific features; marketing claims about speed do not prove that a tool will prevent scope changes.

Budget for collaboration, not just the first seat.

A solo studio may need a simple document, a reliable export, and one clear client reviewer. A four-person team may also need shared templates, revision ownership, internal working notes, and permissions that separate those notes from the client-facing agreement. Count the accounts actually needed, including collaborators and any feature-dependent plan requirements. Compare the current billing terms rather than assuming a free viewing link includes editing or formal approval.

Include setup and maintenance effort in the decision. A comprehensive workspace that nobody updates creates conflicting versions. A simple document can work well when one owner keeps it current and the client knows where to review. Select the smallest arrangement that reliably captures decisions, keeps references accessible, and hands approved scope to production.

Current feature references: HubSpot campaign access and permissions; Adobe Express shared-brand roles; Canva Docs review features.

A reusable outline with a clear acceptance point.

Copy the headings below into your preferred document or use the builder. Add enough detail to make each decision usable; delete instructions that do not apply instead of leaving an empty template masquerading as a completed brief.

  1. Campaign name, brief revision, client owner, and document owner.
  2. Background: the business problem, relevant context, and reason for launching now.
  3. Objective: intended audience response, measurement source, baseline status, and evaluation date.
  4. Audience: specific group, barrier or insight, and evidence or hypothesis status.
  5. Proposition: one supported message and the facts that make it credible.
  6. Constraints: approved references, required claims, language, rights, accessibility, and review requirements.
  7. Deliverables: quantities, formats, variants, ownership, review scope, and exclusions.
  8. Channels: each channel’s role, distribution ownership, and declared spend.
  9. Budget: production, distribution, coordination, reserve, coverage assumptions, and unallocated balance.
  10. Timeline: dependencies, review milestones, final approver, launch date, and unresolved decisions.

For acceptance, record the brief revision, reviewer, decision date, accepted scope, and any conditions still outstanding. Identify who can authorize a change. The local builder records source information and exports a draft; it does not authenticate an approver, send the document, or create a legally binding approval process.

Common mistakes to catch before production

Do not use deliverables as the objective, inflate a hypothesis into established research, or list every possible audience. Do not hide media spend inside an unexplained total. Do not promise a launch date while ignoring client review. Do not let one stakeholder approve work that another has authority to reject later. And do not treat generated copy as substantiated product evidence. Each mistake shifts an unresolved decision into execution, where correction usually affects more work.

The builder helps with the declared arithmetic, structured source data, and exportable draft. It cannot establish whether the audience is right, whether a claim is lawful, whether a placement is effective, or whether a reviewer has authority. Those are real project decisions that belong in the brief and its review process.

Questions clients and creative teams actually face.

How long should a campaign brief be?

Long enough to make the objective, audience, scope, constraints, money, and decision route clear. Keep the core readable and link supporting research. A short brief with missing deliverables is incomplete; a long brief repeating meeting notes can still leave the same decision unresolved.

Is a campaign brief the same as a creative brief?

They overlap. A campaign brief typically connects creative direction to channels, distribution, budget, and timing. A creative brief can focus more closely on the communication idea and execution. State what your document covers instead of assuming everyone uses the terms identically.

Who writes it when the client supplies a brief?

The client supplies business context and requirements; the team responsible for execution checks that those inputs form a usable agreement. Brief back your interpretation, ask about gaps, and obtain acceptance of the revision that production will use.

What if there is no audience research?

Label the proposed insight as a hypothesis and explain the available basis. Assign validation if it is necessary before execution. Do not invent customer quotes, demographic certainty, or research findings to make a template look finished.

Should the brief include final headlines and designs?

It should establish the proposition and constraints needed to judge those executions. Include approved copy or supplied assets when they are actual requirements. Otherwise allow the creative work to develop within the brief rather than prematurely treating a first idea as the final solution.

Can an AI tool write the brief?

It can help organize supplied information or draft questions. The client and project owner still need to verify evidence, choices, scope, costs, and acceptance. Never present generated estimates or product claims as confirmed facts without an appropriate source.

How do we handle feedback from several stakeholders?

Name a client contact who consolidates comments and a person authorized to make the final decision. Identify specialist reviewers where needed. Resolve contradictory feedback before assigning production changes, and record which version the decision applies to.

What happens when budget and scope do not match?

Make the mismatch visible and choose a real tradeoff: remove optional deliverables, change formats or quantities, revise distribution, adjust the budget, or move timing. The builder flags a declared over-allocation, but cannot choose the commercially appropriate compromise.

Can the local builder sign off the campaign?

No. It produces a reviewable draft and complete source exports. Use your real client review route to record acceptance of a named revision, including any conditions. Restoring a JSON file recomputes the draft; it does not prove that anyone approved it.

Build the brief and reconcile the scope.

Edit the fictional example or enter your own material. The builder creates a complete draft, computes declared spend exactly to two decimal places and lists open fields. It structures what you provide; it performs no AI inference or audience verification.

Columns: asset, format, quantity, unit_cost, owner. Quantity is the number of priced units. Variants, translations, revisions and dimensions must be included explicitly in the format/constraints; they are not silently multiplied.

Columns: channel, role, budget. These are declared planned amounts, not recommended media allocations or performance forecasts.

Columns: milestone, date, owner. Dates use YYYY-MM-DD and are treated as calendar dates, not timed events. The draft sorts them chronologically. Milestones after launch are flagged for review, not automatically removed.

Fictional example loaded. Build to compute the draft.
No computed draft yet.

    JSON includes your text and settings. Restore recomputes the scope, totals and document; it does not trust saved output.

    The complete document will appear here.

    Decimal.js 10.6.0 performs the actual budget arithmetic. PapaParse 5.5.3 reads and writes quoted scope data. markdown-it 14.1.0 renders the actual document preview and standalone HTML with raw HTML disabled. All amounts use the same supplied currency label and exactly two decimal places; no exchange rates, taxes or hidden reserve percentages are added. Costs must be entered as plain nonnegative decimal amounts. An over-budget draft remains exportable with its warning so the client can review the mismatch. Text and files are processed in this worksheet’s browser operations; this does not claim a blanket audit of unrelated site telemetry. Exported HTML is a standalone document you can open and print in your browser, not an electronically signed approval or a promise of identical formatting in every document editor.

    Review the decisions behind the document.

    A complete draft should still distinguish supplied facts, assumptions and questions. Reconcile the budget with the actual scope, read the message against the evidence and check that review dates leave enough time for the people involved. A clean export is a useful handoff; it does not establish that the client has read or accepted it.

    What should a client campaign brief include?

    Include the context, objective and measurement, audience and evidence, central message, constraints, exact deliverables, channel roles, budget coverage, and dates with review responsibilities. Keep unanswered questions visible. The number of headings is a working structure, not an industry certification.

    Does the builder approve the brief or predict campaign results?

    No. It structures your supplied text and tables, computes declared spend using decimal arithmetic, flags missing fields and exports a draft document. It does not validate your audience research, forecast results, authenticate a reviewer or record client approval. Review the draft and retain the actual decision in your chosen workflow.

    Make the next handoff easier to understand.

    Keep the objective, scope, spend and open questions in the same draft.

    Prepare your campaign brief
    Plan client campaigns, briefs and creative deliverables with Super