Campaign launch process flowchart (brief to post-campaign review)
Marketing campaign launch flowchart template: brief and sign-off, parallel creative and channel builds, pre-launch QA, go/no-go gate, first-week monitoring and a review that feeds the next brief.
What the campaign launch process flowchart (brief to post-campaign review) process is
Most campaigns do not fail on the idea; they fail in the handovers. The brief is approved verbally, creative builds against one version of the audience while the channel specialist builds against another, tracking is added the night before, and the launch date is defended long after everyone knows the checks are not done. This chart puts those handovers on a swimlane so each has an owner: the Campaign manager writes and runs the brief, Creative and the Channel specialist build, Marketing ops owns tracking and the QA checklist, and an Approver, the head of marketing or finance in your company, signs the objective and makes the launch call.
The structure is specific to a launch with a date. After sign-off, 'Kick off the creative and channel builds' fans out into three builds that run side by side, and they converge on 'Run the pre-launch QA checklist'. The gate that follows, 'Go or no-go for launch?', has three outcomes rather than two: go, 'Not ready' (fix the failed checks and retest inside the same date), or 'Date must move' (the slip-the-date exception, which notifies everyone who planned around the original day). After launch, 'Performance on track?' and 'Pause or adjust the campaign?' give the first week a defined set of responses, and the review writes its lessons into the next brief so the loop closes. The numbers and thresholds on the chart are placeholders to adapt, and the legal checks are for your counsel to define.
This is a campaign-level process. Requests arriving from other teams are better handled first with /templates/marketing-request-intake-process, and the email-specific proofing, suppression and consent checks have their own chart at /templates/email-campaign-qa-process. Draw this one when you want the whole campaign, across channels, on one page.
What this flowchart covers
In this template
- Five swimlanes (Campaign manager, Creative, Channel specialist, Marketing ops and Approver) across five phases: Brief and sign-off, Build, QA and gate, Launch and monitor, and Review
- A sign-off decision, "Objective, audience and budget signed off?", with a changes-requested loop back to the brief
- Three parallel builds (creative, channel setup, and tracking and audience lists) that all feed "Run the pre-launch QA checklist"
- A three-way gate, "Go or no-go for launch?", with not-ready and date-must-move paths, the second drawn as the exception "Slip the launch date and notify stakeholders"
- First-week control: "Performance on track?" and "Pause or adjust the campaign?", ending in a pause exception or an adjust loop
- A review that records results and lessons and ends at "Lessons feed the next campaign brief"
When to use this template
- Campaigns launch late or on time with broken links, missing tracking or the wrong audience, and nobody can say who made the go call
- Creative and channel teams build from different versions of the brief and discover the mismatch at QA
- Stakeholders in sales, support or finance are surprised by dates moving and you want slipping the date to be a drawn, announced step
- There is no agreed response in the first week, so spend or a wrong offer runs on while people debate pausing
- Post-campaign reviews happen but the lessons never reach the next brief
How it works
Rename the lanes to your team
Replace Campaign manager, Creative, Channel specialist, Marketing ops and Approver with your own roles. In a small team one person holds several lanes; keep the lanes anyway, because the Approver must stay distinct from the person who wrote the brief.
Define what a signed-off brief contains
List the fields the Approver must see, such as objective, audience, offer, channels, budget, dates and the measure of success. The sign-off decision is only meaningful if the threshold is written down.
Write the QA checklist
Turn 'Run the pre-launch QA checklist' into a real list for your channels: links, tracking, audiences, proofing, approvals and any legal or consent wording. Have counsel define the legal items for your jurisdiction.
Decide who calls go or no-go
Name one person for 'Go or no-go for launch?' and state what forces 'Not ready' versus 'Date must move', such as whether the fix fits inside the launch date.
Set first-week triggers
Replace the placeholders behind 'Performance on track?' with your own signals, such as spend pacing, delivery errors or response against plan, and agree in advance what triggers a pause.
Add your tools and dates
Note where the brief, assets and tracking live, and add your real lead times for builds and QA. Mark any figure you have not validated as a placeholder.
Run it on the last campaign
Walk a recent launch through the chart and note where it waited. Adjust the lanes or the gate until the chart matches what actually happens, then use it as the standard.
Frequently asked questions
What are the steps in a campaign launch process?
A brief is written and signed off on objective, audience and budget. Creative, channel and tracking builds run in parallel, then a pre-launch QA checklist is run. One person makes the go or no-go call, with paths for fixing the failed checks or moving the date. After launch the team monitors results daily for the first week, decides whether to adjust or pause, and then holds a review that feeds the next brief.
What is the difference between 'Not ready' and 'Date must move'?
'Not ready' means the failed checks can be fixed and retested without moving the launch date. 'Date must move' is the exception path: the date is slipped, stakeholders who planned around it are told, and sends and ad flights are rebooked. Separating the two stops every problem becoming a delay.
Who should approve a marketing campaign before launch?
That depends on your company. A common split is the head of marketing signing objective and audience, and finance signing budget above a threshold. The chart shows one Approver lane; add a second if your budget approval is separate. Legal or privacy review for consent and claims should follow your own policy and counsel.
How does this relate to the email QA and intake charts?
The chart at /templates/email-campaign-qa-process goes deep on proofing, suppression and consent checks for email, and /templates/marketing-request-intake-process covers how requests enter marketing in the first place. This chart is the end-to-end launch that those feed.
Where this process fits
In most operations this process follows Marketing request intake process flowchart (form to backlog review) and hands off to Email campaign QA process flowchart (build to post-send report).
It is one step in Campaign delivery.
Step 1: Marketing request intake process flowchart (form to backlog review)
Marketing request intake flowchart template: request form, completeness check, triage against priorities and capacity, accept, defer or decline with a reason, estimate, scope change and acceptance.
Step 2: Campaign launch process flowchart (brief to post-campaign review) You are here
Marketing campaign launch flowchart template: brief and sign-off, parallel creative and channel builds, pre-launch QA, go/no-go gate, first-week monitoring and a review that feeds the next brief.
Step 3: Email campaign QA process flowchart (build to post-send report)
Email campaign QA flowchart template: ESP build, rendering and link test, audience check, consent and unsubscribe compliance, test send and sign-off, A/B or full send, stop-send monitoring and report.