SOP Templates for Marketing Agencies
Ask for “sop templates for agencies” and most of what comes back is somebody else’s blank document with your logo pasted over theirs: the same eight headers, the same generic steps, none of it built from your actual delivery week. I think the real question behind that search is more useful than give me a file. It is show me the shapes, so I can build mine correctly. That is what this piece does, and there is no template attached to it. That is deliberate. A template copied without deciding its own fields is the reason most SOP libraries sit in a folder nobody opens. The fields are the actual decision, and a downloaded document has already made that decision for someone else’s agency, not yours. What follows instead is the catalogue: eight procedure shapes I see in almost every marketing agency between five and fifty people, and what each one specifically needs to not go quiet.
I am not re-teaching how to write a step here. That is a separate piece, and I cover the mechanics of it in the craft of writing one, which walks through imperative steps, naming exceptions, and testing a draft on a stranger. This piece sits one layer above that. It pairs with the agency SOP guide, which covers why the library matters and how to keep it maintained once it exists. What you are reading now answers a narrower question: which shapes exist, and what each one specifically needs so it does not go quiet.
What does every shape below actually need?
Every shape in this catalogue breaks into the same five parts, in the same order, on purpose: what starts it, who owns it, what information it needs to actually run, what state counts as finished, and the one way I have watched that specific shape go quiet. The first four are structure, and structure is roughly the same everywhere. The fifth is the reason a copied template fails where a built one does not. A reporting procedure rots differently than an offboarding one rots, and a generic template has no way of knowing that in advance. Deciding the five parts correctly, for your own delivery week, is the actual work. Writing the resulting steps down is the easy part, and it is the part the piece linked above already covers.
What are the eight shapes an agency actually runs?
These are the eight I see most often, roughly in the order client-facing work touches them. Each gets a trigger, an owner, the fields it needs, and the state that counts as done, plus the specific way I have watched it rot.
1. Client onboarding
Client onboarding is the shape most agencies write first, and it deserves the full treatment I have given it separately on this site, so here it earns one line. Trigger: a signed contract lands in the CRM. Owner: the account lead. The rot risk: the document gets built for one typical client and nobody edits it for the account that does not fit the template, so it becomes a checklist people quietly route around.
2. Brief or work intake
Trigger: a request for work lands, whether that is a client email, a Slack message, or an intake form. Owner: the producer or ops coordinator who turns a request into a scoped job, not whoever happened to see the message first. The mistake that rots this shape: most intake tools let you submit a brief with the objective field left blank, so half the briefs in the system are missing the one line that would have prevented the rework two weeks later.
| Required fields | Objective, deliverable type, deadline, available assets, approver name |
|---|---|
| Definition of done | Brief lives in the project tool with every field filled and assigned before anyone starts the work |
3. Production handoff
Trigger: work is marked ready to move from whoever scoped or sold it to whoever builds it. Owner: the person handing off, not the person receiving, because handoff quality is the sender’s problem to solve, not the receiver’s problem to survive. The mistake that rots this shape: handoff gets treated as a notification instead of an acceptance. The sender assumes silence means it landed, the receiver assumes they will be told if anything is missing, and the gap between those two assumptions is where scope quietly disappears.
| Required fields | Scope as sold, what is explicitly out of scope, assets and prior approvals, deadline |
|---|---|
| Definition of done | Receiving person confirms acceptance in writing or by moving the task status themselves, not by the sender assuming so |
4. QA before a client sees it
Trigger: a deliverable is marked complete by whoever built it. Owner: a named reviewer, not whoever is free, because a QA step with no fixed owner defaults to whoever is least busy, which in a bad week is nobody. The mistake that rots this shape: QA becomes optional exactly when it matters most, the week everyone is behind, which is also the week a client is most likely to notice something wrong.
| Required fields | Checklist specific to the deliverable type, reviewer name, date reviewed |
|---|---|
| Definition of done | Checklist signed off and the task moved to an approved status before it goes to the client |
5. Client reporting
Trigger: a recurring date on the calendar, or a campaign milestone, not whenever it gets done. Owner: the account lead. The mistake that rots this shape: the report gets built correctly once and then never adjusted when the client’s actual priorities shift, so six months later it is answering a question the client stopped asking a quarter ago.
| Required fields | Data pull date, template, who writes the commentary, send date |
|---|---|
| Definition of done | Report sent, logged in the client record, next send date set |
6. Change or scope request
Trigger: a client asks for something outside what was sold. Owner: the account lead, with pricing authority escalating beyond them once the number is large enough to need it. The mistake that rots this shape: the team says yes out loud to keep the client happy and starts the work before pricing it, so the procedure only ever gets used afterward, to justify scope creep that already happened rather than to prevent it.
| Required fields | What is being asked, hours estimate, timeline impact, client’s written agreement to new terms |
|---|---|
| Definition of done | Change documented and priced before work starts, not reconstructed after |
7. Offboarding
Trigger: a cancellation notice, or a contract’s natural end date. Owner: the account lead. The mistake that rots this shape: it only gets used for the ugly departures, so it quietly becomes a damage-control document instead of the thing that turns even a lost account into a reference, or at minimum a clean exit.
| Required fields | Access removal list, final file and documentation handover, exit conversation date, referral ask |
|---|---|
| Definition of done | Access confirmed removed, files delivered, exit conversation held |
8. New-hire ramp
Trigger: a start date confirmed after a signed offer. Owner: the new hire’s manager, not HR, because HR was not in the room for the actual work. The mistake that rots this shape: it gets written for the first person hired into a role and never touched again, so the fifth hire is being ramped on tools and steps the agency stopped using two hires ago.
| Required fields | Tool access list, which procedures to read and in what order, first shadowed task, 30-day check-in date |
|---|---|
| Definition of done | New hire completes one full instance of a core task without being walked through it |
Which of the eight is your agency actually missing?
Of the eight, the two I see missing most often are not the ones you would guess. Client onboarding and reporting get written early because a client notices immediately when either one is absent. Production handoff and change requests get skipped because they read as communication, a Slack message and a verbal yes, rather than as procedure, and an agency will document a client-facing process years before it documents an internal one that no client will ever see. That is backwards. Handoff and change requests are where rework and scope creep actually originate, not in the parts a client can see. If onboarding and QA are already covered on your team, the next two worth writing are handoff and change requests, not new-hire ramp, however overdue those onboarding docs for staff feel.
Where to start
None of these eight are hard to write once you have decided the five parts for your own delivery week. What is hard is finding the time to do it for all eight while a client’s actual account still needs running today. If you want them built into whatever tool your team already runs on, ClickUp, Asana, Monday.com, Airtable, or Notion, with the genuinely repeatable triggers connected through n8n, that is the work I do as SOP consulting, backed by twelve years running delivery operations for marketing agencies and 92 completed engagements. If you are not sure which of the eight is actually costing you the most right now, that is exactly what the Agency Ops Audit answers: $1,500 fixed, two weeks, a written 90-day roadmap, and a 60-minute readout call, before anyone writes a single field.
