Agency SOPs usually fail in one of two ways. Either they are never written, and every process lives in someone's head. Or they are written once as a forty-page document, become inaccurate within a quarter, and nobody opens them again.
Here is a version that survives contact with actual work.
Document decisions, not clicks
The most common SOP mistake is documenting the interface. "Click the blue button in the top right, then select Schedule from the dropdown."
Interfaces change. More importantly, that is not what people get stuck on. They get stuck on judgment: is this good enough to send, does this need approval, what do I do when the client says something unexpected.
Write down the decisions:
- What makes a post ready for client review
- When to publish versus when to escalate
- How to respond to a negative comment, and when to stop responding
- What to do when the client has not approved by the deadline
- Which changes require checking versus which are the coordinator's call
Screenshots for genuinely non-obvious mechanics are fine. But the value is in the judgment.
One SOP per recurring loop
Do not write one master document. Write short procedures for the loops that repeat:
Weekly content production. From pillar plan to drafts ready for review.
Approval cycle. Sending, reminder timing, default-approve handling, applying revisions.
Publishing and verification. Confirming posts went out, checking they rendered correctly, catching failed connections.
Comment and message management. Response timing, tone, escalation triggers.
Monthly reporting. Data pulled, document assembled, when it goes out.
New client onboarding. The day-by-day sequence.
Client offboarding. Access removal, content export, final handoff.
Each of these should be one page. If one runs longer, it is probably two procedures.
The structure that works
For each procedure:
Trigger. What causes this to start. "Every Monday at 9am" or "when a client submits revision feedback."
Steps. Numbered, in order, action-oriented.
Decision points. Where judgment is required and what the rule is. This is the section that makes an SOP useful. Format it as if-then: "If the comment is a complaint about a completed job, do not reply publicly — flag it to the account manager same day."
Definition of done. How the person knows they have finished. Specific: "All fourteen posts show status Scheduled and the client has received the review link."
Escalate when. The explicit list of situations to stop and ask. Include "you are unsure" as a legitimate entry.
Write the exceptions
The happy path is the easy part and rarely where people get stuck.
For each procedure, list the four or five things that actually go wrong and what to do:
- The social connection has expired and publishing failed
- The client approved, then asked for a change after it published
- A post is scheduled for a day that turns out to be inappropriate given local news
- The client sends feedback that contradicts their brand guidelines
- Two team members edited the same post
These are the moments where an undocumented process costs you an escalation. Writing them down is the highest-value part of the whole exercise.
Keep them current
An SOP nobody updates is worse than none, because people follow it into a wall.
Assign an owner per procedure. One name.
Update at the moment of failure. When someone hits a case the SOP does not cover, the fix is not just answering the question — it is adding it to the document that day.
Review quarterly. Thirty minutes, read them, delete what is stale.
Version them. A date at the top so people know whether they are reading something current.
Store them where the work happens
An SOP in a folder nobody opens does not exist.
Link procedures from wherever the work is triggered. If your team works from a task board, the recurring task should link to the procedure. The document should be one click from the moment of need, not two levels into a shared drive.
Test with someone new
The real test is handing a procedure to someone who has never done the task and watching without helping.
Every question they ask is a gap. Write the answer into the document immediately.
This is uncomfortable and it is the only reliable way to find what you assumed rather than stated.
What not to document
Anything changing more than quarterly. It will be wrong before it is read.
Genuine strategy. SOPs are for repeatable execution. Strategic judgment does not compress into a procedure and attempts to force it produce bad decisions made confidently.
Interface tours in exhaustive detail. Cover the non-obvious. Assume basic competence.
The realistic scope
Seven procedures, one page each, written over a few weeks rather than a heroic weekend. That covers most of an agency's recurring work.
The return is not the document. It is that new hires become useful in days rather than weeks, and that you can take a week off without the work stopping.