Overview
A lightweight campaign planning SOP for marketing teams, covering stages, roles, notes, review rhythm, and workspace ownership. It turns the campaign planning workflow into a repeatable operating habit without forcing marketing teams into a heavyweight process.
Page-specific fit
Why this resource exists
SOP audience: content, demand generation, brand, and marketing operations teams.
Workflow object: campaign execution.
Operating cadence: weekly planning, midweek review, and a monthly refresh sweep.
Trust signal: draft age, approval blockers, publish consistency, refresh completion, and reporting follow-through.
Purpose of the SOP
This SOP exists to make campaign planning work repeatable for marketing teams. The goal is not to document everything. The goal is to reduce the specific failure mode where strategy, creative, channel operations, deadlines, and post-campaign reporting are planned in separate surfaces.
The SOP should help a teammate understand what stage the work is in, who owns the next move, which note explains the context, and when the next review happens.
Roles and ownership
The workspace needs a production rhythm where intent, channel, owner, review state, launch date, and refresh notes stay close to the work. That means every SOP needs clear role boundaries without creating a governance layer nobody wants to maintain.
Use one accountable owner for each active item. Collaborators can contribute, but the workflow should never depend on a vague group owner.
- Workflow owner: maintains stages and review rhythm.
- Card owner: owns the next action and status accuracy.
- Reviewer: approves or requests changes by a visible date.
- Context owner: keeps notes, decisions, and references current.
Procedure
Start with Strategy, Creative, Build, Review, Launch, Report. These stages are enough to describe the work without turning the board into an admin project.
The SOP should state what must be true before work enters each stage and what must be true before it leaves. If the rule cannot be explained in one sentence, simplify it.
- Strategy: define the owner, input, output, and review signal for this stage.
- Creative: define the owner, input, output, and review signal for this stage.
- Build: define the owner, input, output, and review signal for this stage.
- Review: define the owner, input, output, and review signal for this stage.
- Launch: define the owner, input, output, and review signal for this stage.
- Report: define the owner, input, output, and review signal for this stage.
Workspace setup
In Kanvly, the board handles movement and the note layer handles durable context. Audience, message, channel, asset owner, launch date, measurement, and learning need to stay connected.
For marketing teams, this is especially useful because campaign ideas, briefs, approvals, publishing dates, distribution tasks, and reporting notes live in different places. The SOP should tell people where to update status, where to write context, and where to review blockers.
Review and improvement
Review the SOP during weekly planning, midweek review, and a monthly refresh sweep. Use the review to inspect stale work, owner gaps, blocked items, and repeated exceptions.
Measure draft age, approval blockers, publish consistency, refresh completion, and reporting follow-through. If the SOP reduces those issues, keep it. If it creates extra admin without better decisions, shorten it.
- Name the workflow owner.
- Define stage entry and exit rules.
- Clarify one owner per active item.
- Link the notes that explain decisions.
- Set a review cadence and improvement rule.