How to Build SOPs for Your Agency (With Templates)

Most agencies hate writing SOPs. They feel like bureaucracy. They take time.

They go out of date. By month three, nobody's reading them anymore.

But agencies without SOPs are chaos. Every project is managed differently. Every person does their job their own way.

Quality is inconsistent. New people take three months to get productive instead of four weeks.

Here's how to build SOPs that are actually useful instead of a binder collecting dust.

Start With Your Three Core Processes

Don't document everything. That's impossible and nobody wants to read it.

Document your three most important processes:

The thing you do most (usually client onboarding or project delivery)

The thing that goes wrong most (usually revision handling) 3. The thing that takes longest (usually client communication)

For a typical agency, this is:

Client onboarding and kickoff
Project delivery and handoff
Client feedback and revision handling

These three processes, if done well, solve 80% of your operational problems.

Write From the Perspective of Someone Who's Never Done This

Most people writing SOPs write for themselves. They include mental shortcuts that only the writer understands.

Write for a new hire on day three. Someone who's never done this before and is slightly overwhelmed.

Use the language they use, not industry jargon. Be explicit about decisions that seem obvious to you.

Example:

Bad: "Implement client feedback and track revisions."

Good: "When the client sends feedback:

Paste their exact words into the project management tool under 'Revisions' so the designer can see what changed

If it's outside our original scope, flag it with 'SCOPE CHANGE - discuss with PM before implementing' 3. Give the designer 2 business days to implement, then request feedback again"

Make Each SOP 2-3 Pages Max

Nobody reads 20-page documents. Make them scannable.

Format:

Title and objective (what is this about)
Inputs (what we need to start)
Steps (numbered, 5-10 steps max)
Outputs (what success looks like)
Common mistakes (what goes wrong if you skip steps)

That's it. One page of overview, one page of steps, one page of edge cases and mistakes.

Build in Decision Gates

The worst SOPs leave people confused when things are different.

Example: "Client requests more revisions than the contract allows."

Don't just say "tell them no." Include a decision gate:

If it's minor (one sentence change): implement it
If it's medium (one hour of work): flag to PM
If it's major (four+ hours of work): flag to PM and owner for pricing discussion

This prevents people from freezing up when the standard doesn't quite apply.

Use Your Actual Processes, Not Ideal Ones

The most common mistake is documenting how you wish you worked instead of how you actually work.

If you actually have clients who pay late, include that in your cash flow process. If you actually have certain clients who need extra hand-holding, include that in your client management SOP. If certain projects always go over budget, include that estimation adjustment in your delivery SOP.

Your SOPs should reflect reality, not aspiration.

Update SOPs When You Find A Better Way

Don't set it and forget it. Tag the SOP with a last-updated date. Every quarter, pull your three core SOPs and ask:

Is this still accurate?
Where did we struggle with this process this quarter? - What changed that we need to document?

If you update it, tell the team. "We changed how we handle revisions. Here's the new process."

Processes that improve continuously are processes people actually follow.

Create a System for Onboarding New People

The real value of SOPs is in onboarding. When someone new starts, they should be able to read the SOP and execute it reasonably well by day three.

Create an onboarding checklist:

Day 1: Read SOPs 1 (onboarding), review past onboarding projects
Day 2: Shadow someone doing an onboarding, read SOP 2 (delivery)
Day 3: Do an onboarding with supervision, read SOP 3 (revisions)
Day 4-5: Execute SOPs independently, check in daily

By end of week one, they should be productive on the easy stuff. By week three, they're handling projects solo.

Agencies without this onboarding process take three months to get people productive. With it, you hit four weeks.

Version Control Your SOPs

Use Google Docs or Notion with version history. When you change a process, note what changed and why.

Example:

v1.0 (Jan 2025): Initial onboarding process
v1.1 (Feb 2025): Added decision gate for scope questions
v1.2 (Mar 2025): Changed kickoff meeting time from 1 hour to 30 minutes

This helps new people understand the process wasn't random. It evolved. And it helps you avoid reverting to old processes when you're busy.

Template: Basic Client Onboarding SOP

Here's a template you can steal:

OBJECTIVE: Ensure every new client understands scope, timeline, deliverables, and communication process before work begins.

INPUTS:

Signed contract or email confirmation
Client project brief or requirements document

STEPS:

Schedule kickoff call within 3 business days (calendar invite + confirmation)
Send pre-kickoff email with agenda and prep questions
Run kickoff meeting (30 minutes):
- Introductions (client team, your team)
- Goals and success metrics
- Deliverables and timeline
- Communication process (weekly standups every Tuesday)
- Revision rounds (included, what happens after)
Send post-kickoff summary within 24 hours (what we discussed, next steps, timeline)
Get client confirmation on summary within 2 days (email reply is fine)
Create project in management tool
Assign team members
Schedule first deliverable review

OUTPUTS:

Client understands scope and timeline
Team is assigned and has context
Project is tracked in management tool

COMMON MISTAKES:

Skipping the pre-kickoff email (clients come unprepared)
Letting kickoff go over 30 minutes (time expands, clarity decreases)
Not sending post-kickoff summary (client forgets what was agreed)
Waiting for confirmation to create project (delays start by days)

FAQ

Do I need to document everything?

No. Document the three processes that happen most frequently and cause most issues. Everything else can be learned on the job or in one-on-ones.

What tool should I use to document?

Google Docs, Notion, or a wiki. Pick whichever your team already uses. The tool matters less than whether people actually read it.

How do I get my team to follow the SOP?

Start by following it yourself. Show up 15 minutes late to client calls and suddenly everyone's timing changes. Follow the process, make it the standard, and people follow.

What if a client requests something that breaks our SOP?

That's a decision for you or your PM. Document it as a "variation" that required approval. If it happens repeatedly, update the SOP to reflect the new reality.