Agency Standard Operating Procedures: How to Document What Your Business Knows

The Knowledge in Someone's Head Problem

Your best account manager runs client onboarding perfectly. Every client has a smooth start. Relationships begin well.

Then she leaves.

The next person onboards clients their way. Things that were always done fall through the cracks. Client experience becomes inconsistent. Some starts go well; others do not.

The knowledge has left the building.

This is the most common scaling problem agencies face. The solution is SOPs — standard operating procedures that capture how things are done so anyone on the team can replicate them.

What SOPs Are (and Are Not)

A good SOP:

• Describes how to complete a specific, recurring process
• Is actionable enough to follow without prior experience
• Lives where the work happens (not in a shared drive nobody opens)
• Is updated when the process changes

A bad SOP:

• Vague high-level principles that do not tell you what to do step by step
• Last updated 18 months ago
• So long nobody finishes reading it
• Exists only for the purpose of existing

The Processes Worth Documenting First

Not everything needs an SOP. Prioritize:

High-frequency: Happens more than once per month High-stakes: An error here significantly impacts the client or the business High people-dependency: Only one person knows how to do this well

Top priority SOP list for most agencies:

1. Client onboarding (new client to first deliverable)
2. Monthly reporting (data collection, template, review, delivery)
3. Content production workflow (brief to published post)
4. New project setup (folder structure, tool access, kickoff prep)
5. Invoice creation and payment follow-up
6. Social media scheduling workflow
7. Quality review process (how deliverables are reviewed before client)
8. Offboarding process (contract end to final handover)

Start with the one that would cause the most disruption if the person who runs it left tomorrow.

How to Write a Good SOP

The Structure

Title: Specific and searchable. "Monthly Client Report — SEO" not "Report Process."

Purpose: One sentence. Why does this process exist?

Scope: What is included and what is not.

Who it applies to: Which role(s) is responsible for this process.

When it is triggered: What event or schedule kicks off this process?

Step-by-step instructions:

• Numbered, not bulleted (sequence matters)
• One action per step
• Written for someone doing it for the first time
• Include screenshots for tool-based steps
• Note where to find resources needed
• Flag common mistakes or edge cases

Output / done criteria: How do you know the process is complete?

Last reviewed: Date and who reviewed it.

Tone and Length

Write for a capable person who has never done this before, not for an expert who already knows most of it.

If you are writing "as usual, then do X" — you have lost your audience. Be explicit.

Keep each SOP to one page if possible. For complex processes, break them into sub-procedures.

Where to Store SOPs

SOPs only work if people can find and trust them.

Two requirements:

1. Searchable: can you find "onboarding SOP" in under 10 seconds?
2. Current: last-updated date visible; old SOPs worse than no SOP

Good homes:

• Notion (highly flexible, easy to embed Looms and screenshots)
• Confluence (better for larger teams with structured knowledge bases)
• Google Sites (free, simple, shareable)
• Your project management tool's documentation section

Avoid: Email chains, shared Google Docs in random folders, Word docs on local drives.

Getting Your Team to Actually Use Them

The best SOPs fail if the culture is "ask a person instead of checking the doc."

Build the habit:

• New hire onboarding: every process learned by following the SOP, not by shadowing
• When someone asks a process question: "Have you checked the SOP? Let me know if it is missing something."
• Weekly review: account managers refer to checklists embedded in SOPs rather than creating their own lists

The key question: After following this SOP, would someone new produce the same quality output as our best team member?

If not, the SOP is incomplete.

Maintaining SOPs

SOPs become liabilities if they are outdated. Build maintenance into your rhythm:

SOP owner: Every SOP has one person responsible for keeping it current.

Review trigger: Anytime a process changes, the SOP changes the same day.

Quarterly audit: Review top-10 SOPs. Flag any that are outdated or unclear.

Team contribution: Let team members suggest edits. They spot the gaps between the written process and what actually works.

The Compounding Value

Every SOP written today pays dividends for years:

• New hire onboarding drops from 4 weeks to 2
• Process quality becomes consistent regardless of who is on vacation
• Delegation becomes possible without explaining everything from scratch
• You can sell your agency one day and the buyer sees a business, not a set of people

SOPs are not paperwork. They are infrastructure. Build them now, while the pain is manageable — not when you are scaling fast and cannot slow down to write them.