How do you create SOPs that people actually follow?
- Most SOPs fail in 4 predictable forms: 20-page manuals nobody reads, overly complex flowcharts, unsearchable video walkthroughs, or verbal explanations that only live in your head.
- Follow 5 principles: keep it to one page, write for the common 80% case, use a numbered checklist format, assign a single owner, and test it on someone who didn't write it.
- Start with 5-7 SOPs covering your most repeated processes, like email handling, client onboarding, meeting follow-ups, weekly check-ins, and end-of-day shutdown.
- Update SOPs within 48 hours of a process change, and review each one quarterly, a check that should take just 5-10 minutes per SOP.
An SOP is essentially a checklist with added context, a trigger, an owner, and steps, not a substitute for judgment on edge cases.
Why Your SOPs Failed (4 Common Attempts)
If you've documented a process before and watched it die, it probably took one of these four forms. Each fails for a different, fixable reason.
20-page onboarding manual
Nobody reads it. It sits in a shared drive collecting dust. When someone needs it, they ask you instead.
Root cause: Too long: people need checklists, not textbooks
Detailed flowchart in Visio
Took 4 hours to create. Outdated within 2 weeks. Nobody updates it because the tool is annoying.
Root cause: Too complex: maintenance cost exceeds usage value
Video walkthrough (45 min)
Can't be skimmed or searched. When the process changes, you'd need to re-record the entire thing.
Root cause: Wrong format: video is great for training, terrible for reference
Verbal explanation ("just ask me")
Scales to exactly 1 person at a time. You become the bottleneck. And the explanation drifts every time.
Root cause: Not documented: lives in your head, dies when you're busy
The 5 Principles of SOPs That Stick
SOPs that get used share the same traits: short, checklist-shaped, written for the common case, owned by someone, and tested by a fresh pair of eyes.
One page max
If your SOP can't fit on one page, it's either too detailed or covering too many processes. Break it into multiple one-page SOPs. People will read a page. They won't read a document.
Written for the 80%
Cover the common path, not every edge case. "When X happens, do Y. For unusual situations, escalate to [person]." Trying to document every scenario makes the SOP unusable for the normal one.
Checklist format
Numbered steps. Action verbs. Specific enough that someone with context can follow without asking questions. Not paragraphs: steps.
Living document with an owner
Every SOP has one person responsible for keeping it current. When the process changes, they update it within 48 hours. No owner = no maintenance = outdated within a month.
Tested by someone who didn't write it
Have someone follow the SOP without your help. Where they get stuck = where the SOP is unclear. Fix those spots. If you wrote it, you have context they don't.
5 Ready-to-Use SOP Templates
Steal these. Each one follows the same format: a trigger that tells you when to run it, numbered steps, an owner, and an update cadence.
Client Onboarding SOP
Trigger: New client signs contract
- Send welcome email (use template: [link]) within 2 hours of signing
- Create client folder in shared drive using naming convention: [ClientName]_[Year]
- Add client to CRM with: company name, main contact, contract value, start date
- Schedule kick-off call within 5 business days (use scheduling link)
- Send intake questionnaire (template: [link]) 24 hours before kick-off
- After kick-off: add to weekly check-in list and set first milestone date
Email Processing SOP
Trigger: Start of each email processing session (3x/day)
- Open inbox. Sort by sender (VIP clients first, then team, then everyone else)
- For each email: Act (<2 min), Delegate (forward + instructions), Schedule (add to task list), or Delete (archive)
- Drafting replies: use templates for routine responses. Personalize the first and last sentence.
- Extract any commitments or deadlines → add to task tracker with due date
- Flag any email that needs >10 min of thought → schedule a block to handle it
- Goal: inbox at zero (or <10) by end of session. Target time: 20-30 minutes.
Meeting Follow-Up SOP
Trigger: Within 5 minutes of meeting ending
- Write 3-5 line summary: What was decided? What actions were assigned? What's the next check-in?
- Send summary to all attendees via email (not Slack: email creates a searchable record)
- Add each action item to your task tracker with owner and due date
- If you committed to something: block time on your calendar this week to do it
- If someone else committed: add a follow-up reminder for 2 days after their due date
Weekly Client Check-In SOP
Trigger: Every Monday at 10 AM
- Open client dashboard. Review each active client.
- For each client: When was last contact? Any overdue deliverables? Any upcoming milestones?
- Flag: Any client with 5+ days of no contact → send proactive check-in email today
- Flag: Any deliverable due this week → confirm it's on track or renegotiate now
- Send status update to your manager/team: "Here's where all clients stand this week."
- Total time target: 15-20 minutes for up to 10 active clients.
End-of-Day Shutdown SOP
Trigger: 30 minutes before planned shutdown time
- Process remaining inbox to zero (or flag anything that needs tomorrow's attention)
- Review task list: What did I complete today? Update statuses.
- Identify tomorrow's Top 3: Write them on a sticky note or digital equivalent
- Check calendar for tomorrow: Any meetings to prep for? Block prep time now.
- Close all apps. Close laptop. Say "Shutdown complete." (The phrase creates a psychological boundary.)
