How-To Guide

How to Create SOPs That People Actually Follow

Q: How many SOPs should I have?

Start with 5-7 covering your most repeated processes: email handling, client onboarding, meeting follow-ups, weekly review, end-of-day shutdown. Add more only when you catch yourself explaining the same process twice. Too many SOPs is almost as bad as none. People can't find the right one. Quality over quantity.

Q: Where should I store my SOPs?

Wherever your team already looks for information. If that's Notion, put them in Notion. If it's Google Drive, use Drive. If it's a project management tool, use that. The worst place is a standalone "SOP repository" that nobody visits. Embed SOPs where the work happens.

Q: How do I get my team to actually use the SOPs?

Three things: (1) Make them short enough to reference in 60 seconds, (2) Link to them from the places where work happens (task templates, onboarding checklists, pinned Slack messages), and (3) Use them yourself publicly. When someone asks how to do X, respond with "Here's our SOP for that: [link]" instead of explaining from scratch. Repetition builds habit.

Q: How often should I update SOPs?

Update within 48 hours of a process change. Review quarterly even if nothing seems different. You'll find outdated steps you missed. The quarterly review should take 5-10 minutes per SOP. If it takes longer, your SOP is too complex.

Q: What's the difference between an SOP and a checklist?

In practice? Not much. An SOP is a checklist with context: it includes the trigger (when to use it), the owner (who's responsible), and the steps (what to do). A checklist is just the steps. For most knowledge workers, the SOP format adds enough structure to be useful without being bureaucratic.

Q: How does alfred_ relate to SOPs?

alfred_ is essentially a pre-built SOP engine for your email, calendar, and tasks. It follows a consistent process: triage email by priority, draft routine replies, extract tasks and deadlines, surface follow-ups. You don't need to write an email processing SOP because alfred_ IS the email processing SOP. It just runs automatically instead of requiring manual execution.

You wrote the process doc. You spent 3 hours on it. It has screenshots and everything. Nobody reads it. When someone new joins, they ask you how to do the thing. You explain it for the 12th time and wonder why you bothered documenting it. The problem isn't that people don't want to follow SOPs. It's that most SOPs are written for the author, not the reader. Here's how to create ones that are actually used.

Why Your SOPs Failed (4 Common Attempts)

20-page onboarding manual

Nobody reads it. It sits in a shared drive collecting dust. When someone needs it, they ask you instead. — 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. — 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. — 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. — Not documented: lives in your head, dies when you're busy

The 5 Principles of SOPs That Stick

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

Client Onboarding SOP

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 — Account manager — Review quarterly

Email Processing SOP

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. — You (or your AI assistant) — Review monthly

Meeting Follow-Up SOP

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 — Meeting organizer — Review quarterly

Weekly Client Check-In SOP

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. — Account lead — Review monthly

End-of-Day Shutdown SOP

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.) — You — No updates needed: this one is timeless

Try alfred_

Automate Your #1 SOP

alfred_ runs your email processing SOP automatically: triage, replies, tasks, follow-ups. No manual execution needed.

Try alfred_ Free

Frequently Asked Questions

How many SOPs should I have?

Start with 5-7 covering your most repeated processes: email handling, client onboarding, meeting follow-ups, weekly review, end-of-day shutdown. Add more only when you catch yourself explaining the same process twice. Too many SOPs is almost as bad as none. People can't find the right one. Quality over quantity.

Where should I store my SOPs?

Wherever your team already looks for information. If that's Notion, put them in Notion. If it's Google Drive, use Drive. If it's a project management tool, use that. The worst place is a standalone "SOP repository" that nobody visits. Embed SOPs where the work happens.

How do I get my team to actually use the SOPs?

Three things: (1) Make them short enough to reference in 60 seconds, (2) Link to them from the places where work happens (task templates, onboarding checklists, pinned Slack messages), and (3) Use them yourself publicly. When someone asks how to do X, respond with "Here's our SOP for that: [link]" instead of explaining from scratch. Repetition builds habit.

How often should I update SOPs?

Update within 48 hours of a process change. Review quarterly even if nothing seems different. You'll find outdated steps you missed. The quarterly review should take 5-10 minutes per SOP. If it takes longer, your SOP is too complex.

What's the difference between an SOP and a checklist?

In practice? Not much. An SOP is a checklist with context: it includes the trigger (when to use it), the owner (who's responsible), and the steps (what to do). A checklist is just the steps. For most knowledge workers, the SOP format adds enough structure to be useful without being bureaucratic.

How does alfred_ relate to SOPs?

alfred_ is essentially a pre-built SOP engine for your email, calendar, and tasks. It follows a consistent process: triage email by priority, draft routine replies, extract tasks and deadlines, surface follow-ups. You don't need to write an email processing SOP because alfred_ IS the email processing SOP. It just runs automatically instead of requiring manual execution.