A useful campaign brief is not a long form filled with adjectives. It is a decision record that lets strategy, creative, review, publishing, community, and measurement teams work from the same promise and evidence.
Download the template
The CSV uses one row per campaign. Open it in a spreadsheet, Airtable, Notion, or a database workflow. Keep only fields your team will actually maintain, but do not remove ownership, evidence, risk, approval, or measurement merely because they require a decision.
What the campaign brief records
| Field group | Decision it protects |
|---|---|
| Identity | Stable campaign ID, name, owner, status, dates |
| Strategy | Business context, audience, problem, objective, promise |
| Evidence | Sources, proof, claim boundaries, assumptions |
| Offer | Product or action, value, destination, exclusions |
| Creative | Core idea, message hierarchy, tone, mandatory elements |
| Channel | Channel role, format, deliverable, adaptation requirement |
| Governance | Risk tier, rights, disclosure, approvers, deadline |
| Measurement | Primary metric, definition, window, baseline, target |
| Operations | Dependencies, publish owner, community owner, recovery plan |
The brief should define what must remain consistent across channels and what may adapt. The audience promise and evidence should remain stable. The opening, length, visual grammar, interaction, and call to action can change to fit each destination.
Write a usable strategic core
Name one primary audience and the situation in which the campaign matters to them. Describe the problem in observable terms. Replace “increase awareness” with a change the campaign can plausibly influence, such as qualified visits from a target segment or adoption of a newly released workflow.
Write the core promise as a sentence a creator can test against every asset. Then list the evidence and its limits. If a result applies only to a customer segment, time range, or study condition, preserve that condition instead of generalizing it into a universal claim.
Separate facts, approved positioning, hypotheses, and open questions. An unresolved assumption should have an owner and due date. Otherwise it will reappear as late-stage feedback.
Define channel roles and deliverables
Do not write “post on all channels.” Give each destination a job. One channel may introduce the problem, another demonstrate the workflow, another host the full explanation, and another support retargeting or community response.
For each channel, specify account, audience nuance, format, quantity, owner, due date, dependencies, and adaptation requirement. Link child content rows to the stable campaign ID in the content calendar template.
Estimate capacity before committing to volume. Include research, copy, design, video, review, revision, publishing, moderation, and reporting. A smaller set of finished channel-native assets is more useful than a large fictional deliverable list.
Make governance executable
Assign a risk tier based on claims, regulation, customer material, rights, offers, crisis context, and brand impact. Name required reviewers and one final decision owner. Set a decision deadline that leaves time for revision before the publish date.
Record rights and consent for every source asset. Define required disclosures. State which changes invalidate approval: a claim, price, date, destination, visual, audio track, customer quote, or channel identity may all matter.
Add a recovery owner and fallback. If a product page is unavailable, a spokesperson withdraws, or publishing fails, the team should know whether to pause, replace, reschedule, or cancel.
Define measurement before launch
Choose one primary metric and write its definition, numerator, denominator, data source, timezone, and measurement window. Add a baseline and target only when they are comparable and defensible. Secondary metrics can help explain the result but should not replace the original decision criterion after launch.
Schedule a review date and require one learning plus one next action. “Good engagement” is not a conclusion. “The proof-led carousel produced more qualified resource visits than the opinion-led text post; repeat the proof structure for the next audience objection” is operational.
Campaign brief checklist
- One audience, situation, objective, and core promise are clear
- Evidence, claim limits, assumptions, and open questions recorded
- Offer, destination, exclusions, and mandatory elements confirmed
- Every channel has a distinct role and owned deliverable
- Capacity, dependencies, approval path, and invalidation rules defined
- Rights, consent, commercial, and AI disclosures documented
- Primary metric, definition, baseline, window, and data source set
- Community response and publishing recovery have named owners
Use the approval workflow template and publishing checklist to carry the brief into execution.
