How detailed should an SOP be?

The Short Answer

One page per process. Step-by-step instructions with quality checkpoints at each step. Detailed enough that someone who's never done the task can follow it without asking questions. Simple enough that it fits on one page.

The Right Level of Detail

Most founders either overdocument (a 30-page manual nobody reads) or underdocument (a bullet list that leaves out the judgment calls). The sweet spot: a step-by-step checklist with three things at each step. What to do. How to know it's done right. What to do when something goes wrong.

Example for client onboarding: "Step 3: Send the welcome email. Template: [link]. Personalize the subject line with the client's name and project name. Send within 2 hours of contract signing. If the contract was signed after 5pm, send by 9am the next business day." That's detailed enough to execute. Short enough to follow. Specific enough to maintain quality.

The One-Page Test

If the SOP doesn't fit on one page, it's either too detailed or the process is too complex. Too detailed: you're documenting obvious steps ("open your laptop," "click the email icon"). Remove anything a reasonably competent person would figure out on their own. Too complex: the process has too many branches. Split it into two SOPs, each handling a simpler workflow.

The one-page constraint forces clarity. It forces you to decide what actually matters in the process versus what's nice-to-know. The team will follow a one-pager. They won't follow a 30-page manual.

Quality Checkpoints Are the Key

The difference between an SOP that works and one that doesn't is quality checkpoints. Without them, the team member completes the steps and declares it "done" without knowing whether "done" meets your standard. With them, they can self-assess at each step.

A quality checkpoint answers: "What does good look like at this step?" For a sales follow-up SOP: "Good: one-pager sent within 2 hours, personalized with the buyer's problem language from the conversation, investment amount included, one clear next step." The team member reads the checkpoint, compares their work against it, and knows whether to proceed or fix something. No founder review required.

Edge Cases

Every process has edge cases: the client who pushes back, the data that looks wrong, the timeline that shifts. Document the top three to five edge cases for each SOP. "If the client requests changes to the onboarding timeline, escalate to [name] before confirming." Edge cases are where unsupervised team members make the most mistakes, so they're the most valuable part of the document.

Where to Start

This guide covers the full SOP format with templates and real examples. The Rocket Fuel Sprint ($15,000) builds SOPs for your entire operation in 60 days. Start free.