Marketing campaign planning template — and a process that survives the launch date moving

Campaign plans rarely fail at the strategy stage. They fail in the week before launch, when a date slips and nobody is sure which asset version is current, who approved what, and whether the copy in the ad platform matches the copy the client saw. This template covers the plan and the versioning discipline around it.

The plan itself: eight stages

1. Objective: one measurable outcome and the date you'll judge it.
2. Audience: who, and what they currently believe about the category.
3. Insight: the tension or truth the campaign plays on. One sentence.
4. Proposition: the one thing the campaign says.
5. Channel plan: where it runs, and what's native to each channel — not one asset resized.
6. Creative assets: a list per channel, with the owner and the due date for each.
7. Dependencies: what must exist before launch (landing page, tracking, legal sign-off, stock). Dependencies are where plans actually die.
8. Timeline with a buffer: the real launch date plus the slip you can absorb. If the buffer is zero, say so out loud.

The spreadsheet version

For a small campaign, a spreadsheet with these columns works fine:

Asset | Channel | Owner | Draft due | Approver | Approved on | Version | Status

The columns that people skip — Approver, Approved on, Version — are precisely the ones you'll need when the launch date moves and two people disagree about which headline was final.

Why campaign plans break: the version gap

Here's the failure mode we've watched repeat across agencies and in-house teams:

1. The plan lives in a spreadsheet; the assets live in a shared drive; the feedback lives in email and WhatsApp.
2. The date moves. The copywriter updates "final" copy — but the designer worked from the previous file.
3. Approval history is reconstructive: someone scrolls email trying to establish which version the client signed off.
4. Launch slips again, partly because of the archaeology itself.

The plan wasn't wrong. The system around the plan had no memory. The fix is unglamorous: every asset version tied to its brief, its approver and its approval date — in one place, visible to the whole team.

That's the specific problem CreativeBoard was built for: brief, versions and approvals as one object per campaign item, so when the date moves, everything that depends on it moves together — visibly. Early access is free:

Using the template with a team of two

You don't need process overhead at small scale — you need the three columns that prevent disputes: approver, approved-on, version. Everything else can stay loose. As the team or client count grows, add the dependency column before you add anything else; dependencies are the first thing that silently breaks when two campaigns share a designer.