What these SOPs are for
Marketing teams lose more time to inconsistency than to ignorance. Most people know how to tag a link or publish a page; the trouble is that five people do it five slightly different ways, and the differences surface weeks later as a broken report or an unindexed page. An SOP removes that variation. It names one owner, one trigger and one sequence, so the work comes out the same whoever is on shift.
An SOP sits between two other formats on this site. A playbook, collected in the playbooks library, describes a whole programme of work that runs over weeks with several roles and phases. A checklist is a short list of things to confirm at a single moment. An SOP is narrower than a playbook and longer than a checklist: it describes one task from trigger to hand-off, including the decisions inside it, and usually tells you which checklist to run at the QA step. Where a job needs judging rather than doing, such as scoring an account or a site, the audits library holds the scoring frameworks instead.
Every SOP here follows the same shape: owner, trigger and scope; what to have before you start; the numbered procedure; the QA checks; the hand-offs and records; and the mistakes people make running it. Nothing in a procedure states a KPIA metric tied directly to an objective. target or a threshold, because those belong to your plan, not to the procedure.
How to adopt and version an SOP
Treat each page as a starting draft, not a finished policy. Copy it into wherever your team keeps working documents, replace the generic role names with real people, swap the tool names for your own stack and delete any step that genuinely does not apply. The guide to writing a marketing SOP covers how to draft, test and approve a procedure from scratch; use it when nothing here fits.
Give every adopted SOP a version number, an owner and a review date at the top. When a step changes, change the version, note what changed and why, and tell the people who run it. An SOP nobody has reviewed for a long time is usually describing a tool screen that no longer exists. The simplest test of whether an SOP is real is to hand it to someone new and watch them run it without help: every question they ask is a missing line.
Keep procedures short. If an SOP grows a long appendix of exceptions, the exceptions probably deserve their own procedure, or the task is really a programme that belongs in a playbook. The wider marketing operations hub covers how procedures fit with governance, systems and team structure.
A retailer adopting two SOPs in one quarter
Hollin & Pike, an invented homeware retailer with a marketing team of 6, kept finding campaign traffic reported as "unassigned". An audit of the previous 3 months showed 41 distinct spellings of the same handful of campaign sources. The team adopted the UTM link request SOP first, named one marketing operations owner and versioned the procedure as v1.0. Six weeks later they added the monthly reporting pack SOP, which now includes a step to check the UTM register against the month's traffic. By the end of the quarter, unassigned sessions had fallen from roughly 18% of campaign traffic to under 4%, and the monthly pack was signed off two working days earlier than before.
Which SOP when
Start from the trigger in front of you. Several tasks chain together: a campaign launch depends on tagged links and approved creative, and a tracking outage usually ends with an annotation in the next monthly pack. The table routes common situations to the procedure to run first and the one that usually follows.
| Situation | Run first | Usually followed by |
|---|---|---|
| An approved draft page is ready to go live | Publishing a web page | Search Console error triage if the page later shows an issue |
| A paid campaign is built and needs to go live | Paid campaign launch | Pausing underperforming ads at the first optimisation review |
| An ad, keyword or ad set looks like it is wasting budget | Pausing underperforming ads | Monthly reporting pack to record the change |
| The month has closed and stakeholders expect numbers | Monthly reporting pack | Tracking outage response if a source looks broken |
| Someone needs a tagged link for a campaign or post | UTM link request | Paid campaign launch if the link feeds an ad |
| Conversions or events have stopped recording | Tracking outage response | Monthly reporting pack to annotate the gap |
| A new marketing tool has been bought or upgraded | Marketing tool onboarding | Tracking outage response if the new tag breaks something |
| Creative is ready and waiting for sign-off | Creative approval | Paid campaign launch once assets are released |
| A send has just gone out, or the month's hygiene pass is due | Email list hygiene | Monthly reporting pack for list health |
| Search Console has emailed an alert | Search Console error triage | Publishing a web page if a fix needs a republish |
| A live page's address has to change (a page with no true equivalent at a new address goes to Removing a web page instead) | Changing a page URL | Search Console error triage if the old address starts showing an error |
| A live page is being retired and nothing replaces it | Removing a web page | Search Console error triage if the address later shows as a soft not-found |
| Someone joins, moves or leaves, or a supplier starts or ends | Marketing tool access requests | Compromised marketing account response if anything looks wrong |
| An error is found in a live ad, landing page or post | Live ad and page error response | Creative approval for the correction |
| A campaign email or newsletter issue is due | Email campaign send | Email list hygiene for any list problems the send turns up |
| A shift on the brand's social inbox begins | Social media inbox triage | Live ad and page error response for an error in something the brand published, or the social media crisis plan if a problem outgrows the routine |
| Someone asks, by any route, to stop receiving marketing | Marketing opt-out requests | Email list hygiene to keep the suppression list synced across sending tools |
| A partner, creator, campaign, insert or the service team asks for a discount code | Discount code request | Ending a sale or promotion when the code's end time arrives |
| A sale or promotion reaches its end time | Ending a sale or promotion | Monthly reporting pack for the month the promotion ended |
| Offline outcomes are waiting in the CRM for the ad platforms | Offline conversion upload | Tracking outage response if counts collapse |
| A holiday, special day or new opening hours are coming | Opening hours change | Live ad and page error response if the wrong hours already went out |
| A social, ad or email account is in the wrong hands | Compromised marketing account response | Marketing tool access requests for any new access and to close the gap the intruder used |
| A wave of a repeated customer survey is due | Customer survey wave | Monthly reporting pack for the chart and the themes |
The procedures beneath this introduction are listed automatically, so a new SOP appears here as soon as it is published.
SOPs and the guides behind them
An SOP tells you what to do and in which order; it deliberately does not teach the method. Each step that needs judgement links to the guide that owns it. The link request procedure points to the naming and UTMURL tags identifying traffic source. conventions guide rather than restating the parameters. The reporting procedure points to the guides on data quality and on why platforms and GA4Google's event-based analytics platform. disagree. The publishing procedure points to the on-page and structured data guides. When a step fails and you need to understand why, follow that link; when you simply need to get the task done, stay on the SOP.
The relationship also runs the other way. Most SOPs name a checklist from the checklists library at their QA step, because a checklist is the fastest way to confirm a finished piece of work at the moment of sign-off. Use the SOP to run the task, the checklist to check it, and the guide to fix whatever the checklist finds. That loop, repeated, is what keeps a small team's output consistent without anyone having to remember everything.
