The difference between a media buying team that scales smoothly past $100k/month and one that constantly firefights usually isn't talent -- it's process. Without documented SOPs, every launch depends on one person remembering every step, every optimization decision is reinvented from scratch, and every mistake (a wrong pixel, an unapproved landing page, a budget typo) gets repeated by the next person who wasn't there for the last one. This article lays out the core SOP categories a serious media buying operation needs and what belongs in each.
Why SOPs matter more in media buying than they seem to
Media buying looks like a creative, judgment-heavy discipline, and strategically it is. But the operational mechanics underneath -- launching a campaign, QA-ing a pixel, requesting a budget increase, responding to an ad disapproval -- are highly repeatable and benefit enormously from being written down once and executed consistently after that.
The cost of skipping this shows up as expensive, avoidable mistakes: a campaign launched with the wrong conversion event, a budget change made without checking pacing first, a disapproved ad left down for two days because nobody owned the resolution process. At $100k+/month, a single one of these mistakes can cost more than the time it would have taken to write the SOP in the first place.
Pre-launch checklist SOP
Every new campaign, regardless of who is launching it, should pass through the same checklist before going live. This is the highest-value SOP to have in writing because launch mistakes are the most common and most preventable category of error.
- Correct pixel/dataset and conversion event selected and matched to campaign objective
- UTM parameters present and following the account's naming/tracking convention
- Budget and bid strategy confirmed against the approved media plan, not just 'looks about right'
- Landing page tested on both mobile and desktop, and checked for policy compliance (claims, required disclosures, functioning forms)
- Audience exclusions applied where needed (e.g., excluding existing customers from acquisition campaigns)
- Naming convention applied at campaign, ad set, and ad level before publishing, not after
Daily and weekly optimization cadence SOP
Define exactly what gets reviewed daily versus weekly, and what actions are pre-authorized at each level versus requiring lead sign-off. A workable structure: daily checks cover pacing, obvious underperformance (e.g., CPA more than 2x target with statistically meaningful spend), and any policy flags or disapprovals; weekly checks cover creative refresh decisions, audience expansion or consolidation, and budget reallocation across campaigns based on the prior week's trend.
Specify monetary or percentage thresholds for what a media buyer can act on independently (e.g., budget changes under 20% day-over-day) versus what needs a second set of eyes (larger budget moves, pausing a campaign that's a significant share of total account spend, or any change during a known high-stakes period like a launch week or holiday sale).
Incident response SOP: disapprovals, restrictions, and outages
Ad disapprovals, account restrictions, and Business Manager-level flags happen even to fully compliant advertisers, and how a team responds in the first hour matters. Document a clear escalation path: who checks Meta's Business Help Center and Account Quality status first, what information gets gathered before appealing (screenshot of the policy cited, the specific asset flagged, any relevant compliance documentation), and who has authority to submit an appeal versus who needs to loop in agency-level support.
For anything beyond a single ad disapproval -- an ad account-level restriction or a Business Manager flag -- have a documented decision tree for whether to pause all spend on that account, redirect budget to a backup account, or wait for appeal resolution, rather than deciding this under pressure in the moment. Teams operating through an agency structure with multiple available ad accounts have more flexibility here than teams dependent on a single account.
QA and handoff SOPs
Any time an account changes hands -- a new media buyer takes over, an agency transition happens, or someone returns from time off -- a documented handoff reduces the chance of dropped context. A handoff SOP should cover current campaign structure and rationale, any active tests and their status, known issues or pending appeals, and upcoming planned changes.
Separately, a lightweight QA SOP run weekly (or after any significant account change) catches drift before it compounds: verifying pixel firing is still correct after a website update, confirming naming conventions haven't slipped, and spot-checking that CRM feedback loop data (if in use) is still flowing correctly.
Keeping SOPs alive, not just written
The failure mode with SOPs isn't usually never writing them -- it's writing them once and never updating them as the account, the platform, or the team changes. Assign explicit ownership for each SOP document, review the full set on a quarterly cadence, and treat any repeated mistake as a trigger to update the relevant SOP immediately rather than relying on a verbal reminder to the team.
Power Ads runs its own internal SOPs across launch, optimization, and incident response for every managed account, which is part of how a 24/7 support model stays consistent regardless of which team member is handling a given account at any given time.
Key takeaways
- A written pre-launch checklist prevents the most common and most costly category of media buying mistakes
- Define pre-authorized action thresholds so media buyers can move fast on routine decisions while escalating larger ones
- Document an incident response process for disapprovals and account restrictions before you need it, not during the crisis
- Handoff and QA SOPs prevent context loss when accounts change hands or after significant account changes
- Assign ownership and review SOPs quarterly -- an SOP that's never updated after a repeated mistake isn't doing its job
FAQ
How detailed should an SOP be?
Detailed enough that someone unfamiliar with the specific account, but familiar with Meta Ads generally, could execute it correctly. If a step requires tribal knowledge to complete, it needs more detail, not less.
Who should own writing and maintaining SOPs on a small team?
Typically the account or team lead, but the best source material comes from whoever actually executes the task most often -- have that person draft it, then have the lead review and formalize it.
Do SOPs slow down a fast-moving media buying team?
Well-designed SOPs speed teams up because they remove repeated decision-making on routine tasks, freeing attention for the genuinely judgment-heavy calls like creative strategy and budget allocation.
