A one page campaign brief template

1. Make the page a decision contract

A campaign brief should let a writer, designer, channel owner and approver describe the same job without another discovery meeting. Its purpose is not to capture everything known about the business. It records the decisions that constrain execution, with links to supporting evidence.

Treat one page as a prioritisation discipline, not a typography challenge. If the offer, audience and approval rules cannot fit at readable size, remove background narrative before removing constraints. Complex campaigns still need specifications, research and channel plans, but those belong in linked documents.

Hypothetical example: a restaurant promoting Tuesday bookings needs the eligible dates, available sittings, offer conditions and booking destination on the page. Its complete brand history can remain elsewhere. A missing blackout date is more likely to cause rework than a missing paragraph about the founder.

• Ready means another owner can start without guessing.
• Separate verified facts, working assumptions and unresolved decisions.
• Give every unresolved decision an owner and deadline.

2. Copy this one page campaign brief template

Use the following as the working page. Replace bracketed prompts with short answers, usually one sentence per field. Link specifications rather than compressing them into unreadable notes. The brief owner maintains the current version; reviewers should not create competing copies.

• Campaign and control: [name], [brief owner], [version/date], [draft or approved], [launch and end dates, time zone].
• Business problem: [what needs to change], supported by [evidence link and reporting window].
• Objective: [one primary outcome], [target and rationale], [measurement period], [quality guardrail].
• Audience: [priority group], [buying situation], [main barrier], [exclusions].
• Offer and message: [offer], [single promise], [supporting proof], [CTA], [destination URL], [mandatory conditions].
• Deliverables: [asset quantities], [placements and formats], [versions], [linked specifications], [explicit exclusions].
• Resources: [media cap], [production allocation], [internal capacity], [dependencies and owners].
• Measurement: [primary metric definition], [source], [campaign identifier and UTM convention], [tracking QA owner], [review date].
• Approval and handoff: [decision-maker], [specialist reviewers], [review deadlines], [acceptance criteria], [launch owner].
• Change control: [open questions], [go/no-go blockers], [who can approve scope changes], [decision-log link].

3. Define success before choosing assets

Choose an outcome the campaign can plausibly influence, then distinguish it from diagnostic measures. For an enquiry campaign, clicks help diagnose delivery, but accepted enquiries may be the business outcome. Define what makes an enquiry accepted and who records that judgement.

Hypothetical example: an accounting firm seeks enquiries from businesses needing payroll support. The brief defines a qualified enquiry as a contactable business within its service area requesting an eligible service. A form submission alone does not meet that definition.

Name systems precisely. Google's guidance distinguishes GA4 key events from Google Ads conversions; do not label both simply 'conversions' and assume their reports are interchangeable. Record the event or conversion action, reporting window and quality source.

Set targets using relevant history, capacity and economics, with assumptions visible. There is no universal acceptable cost per acquisition. Include a review date rather than inviting daily target changes.

• State the primary outcome and its calculation.
• Assign tracking QA before launch.
• Record campaign identifiers consistently; Google's manual campaign guidance explains how UTM parameters populate traffic-source dimensions.

4. Connect audience, offer and proof

Demographics rarely provide enough direction for creative. Describe the buying situation, the audience's barrier and the evidence that could resolve it. Separate a customer insight supported by research from a hypothesis the campaign will test.

Hypothetical example: a furniture retailer targets renters furnishing a small dining area. The barrier is uncertainty about fit, not necessarily price. The brief requests dimension-led imagery and links to verified product measurements instead of defaulting to a discount.

Keep one main promise. Additional benefits can support it, but a list of unrelated selling points leaves the creative team to make strategic decisions. Specify what cannot be claimed, particularly delivery timings, availability and performance outcomes.

• Does the destination substantiate the headline?
• Are offer dates, eligibility and exclusions explicit?
• Is each proof point linked to an approved source?
• Would a different audience require a genuinely different brief?

5. Specify deliverables without prescribing every idea

Describe outputs in quantities and placements, not loose labels such as 'social assets'. Separate concepts from adaptations: two concepts in three ratios means six adaptations, before copy or language variants. This distinction makes workload and quotes easier to assess.

Hypothetical example: a workshop campaign needs two visual concepts, each adapted for a square feed placement and a vertical story placement, plus one registration email. A landing-page redesign is explicitly out of scope.

State acceptance criteria while leaving creative room. Require legible dates, an accurate venue address and approved terms; avoid prescribing every composition unless there is a genuine constraint. Include accessibility in the specification, not as an optional final check. W3C guidance says captions convey relevant speech and non-speech audio, so dialogue-only transcription may be insufficient.

• List formats, quantities, copy limits and editable-file requirements.
• Identify supplied assets and who clears usage rights.
• Specify caption review and placement-safe text checks.

6. Expose resource limits and launch dependencies

Separate media spend from production costs and internal effort. A modest media campaign can still consume substantial design and review capacity. Record limits, who may authorise changes and what gets reduced if time runs short.

Hypothetical example: a retailer plans to promote a seasonal bundle, but final stock confirmation arrives after the proposed artwork deadline. The brief names the merchandising owner and makes confirmation a blocker. The team can prepare layouts without approving availability claims.

Plan backwards from launch through trafficking, tracking QA, approval and production. Avoid deadlines that assume instantaneous feedback. For every external dependency, record the fallback: postpone, narrow the offer or remove a placement. A fallback is a decision rule, not permission to publish unverified material.

• Check destination readiness, account access, inventory and permissions.
• Confirm reviewer availability before committing the schedule.
• Distinguish hard blockers from improvements that can wait.

7. Make approval and scope changes unambiguous

Name one final decision-maker and specialist reviewers with bounded responsibilities. Legal review, brand review and channel QA answer different questions. Collect feedback into one resolved instruction set rather than sending contradictory comments to the creator.

Hypothetical example: after approving a webinar campaign, a stakeholder requests a second industry audience. That may require new proof, copy, targeting and registration questions. Record the change and its effect on dates and effort before treating it as a minor amendment.

Approval should identify the version, destinations and budget covered. Silence is not approval. Reopen approval when a material claim, offer or spend limit changes, rather than allowing the original sign-off to cover a different campaign.

• Handoff includes final files, destination, tracking values and approved version.
• Launch owner verifies blockers are closed.
• Late requests require an explicit keep, replace, defer or decline decision.

8. Measure whether the brief reduces avoidable work

Evaluate briefing quality through workflow evidence, not confidence alone. Track clarification rounds, active production time, approval waiting time and rework caused by missing information. Separate waiting from working: fewer meetings may coexist with a longer approval queue.

Hypothetical calculation: if comparable campaigns previously needed five hours of clarification and rework, and a pilot needs three, the observed difference is two hours per campaign. Subtract additional briefing and maintenance effort before estimating net time saved.

Do not infer causation from a before-and-after comparison. Campaign complexity, staffing and reviewer availability may also change. Compare similar work, record exceptions and ask the delivery team which fields prevented specific mistakes.

• Net observed time difference = downstream effort reduction minus additional briefing effort.
• Pair speed with quality checks, including corrections after launch.
• Use a small pilot before adding mandatory fields across every campaign.

9. Keep the brief connected to accountable work

Its described workflow includes Oppo drafting briefs for human review, RiseProjects holding tasks with owners and due dates, and RiseChat keeping discussions beside the relevant work. These support the process; they do not replace strategic decisions or approval.

Explore RiseProjects and RiseCampaigns through the product links, or see /the-solution for the broader workflow. RiseCampaigns describes campaign creation paused, with explicit human approval and no spend without team approval.

Connected actions depend on provider permissions and integration status. TikTok Ads and LinkedIn are approval pending; Microsoft Advertising is planned. Confirm current availability before making a provider-dependent launch commitment. Keep the approved brief usable even when a channel requires a manual handoff.