Standard Operating Procedure Template: Free SOP + Step-by-Step Guide
A standard operating procedure (SOP) is a documented, step-by-step process for completing a recurring task the same way every time. This guide explains what goes into a good SOP, includes a free copy-and-use template, and shows three filled-in examples for client onboarding, content publishing, and monthly bookkeeping.
A standard operating procedure (SOP) is a documented, step-by-step process for completing a recurring task the same way every time. A good SOP has a title, a purpose, a scope, a list of responsibilities, numbered steps with expected outcomes, and a decision branch for edge cases. The free SOP template in this guide is ready to copy and adapt for any workflow in your business. Document five recurring tasks and you will save hours of rework each month, eliminate variation errors, and have something real to hand off to a future hire or virtual assistant.
Most early-stage founders think documentation is something you do when you have a team to hand things off to. It is not. It is something you do so that you can have a team to hand things off to. The sequence matters. The SOP is not the output of having a functioning business. It is one of the inputs.
This guide gives you a complete SOP template you can use immediately, the anatomy of what makes a procedure document actually useful, and three filled-in examples for the processes founders most commonly need to systematize.
What Is an SOP
A standard operating procedure is a document that describes how to complete a specific recurring task or process. It exists so that anyone doing that task produces the same result, every time, regardless of how their day is going, how much context they carry in their head, or whether the usual person is available.
The term comes from the military and manufacturing industries, where process consistency is not a productivity preference but a safety requirement. In those environments, an SOP is not supplementary documentation. It is the procedure itself, captured in a repeatable form that can be followed, audited, and improved.
For founders and solopreneurs, the concept transfers directly. You are not trying to coordinate hundreds of people on an assembly line. You are trying to make sure that the client onboarding you did perfectly for client three still happens consistently for clients thirteen and thirty. That you do not spend 20 minutes every Tuesday reinventing your invoicing routine. That a virtual assistant can pick up any recurring task in your business without needing you to walk them through it from scratch.
An SOP is different from a checklist. A checklist confirms that steps happened. An SOP explains what the steps are, in what order, and what to do when something unexpected comes up. Checklists are tools for working from a known process. SOPs are the source of that known process.
Why Solo Founders Need SOPs More Than Anyone
The common objection is this: SOPs are for large companies with teams to manage. A one-person business does not need documentation because there is only one person doing the work.
That objection has the logic exactly backwards.
Large organizations implement SOPs to coordinate many people around a single standard. Solo founders need SOPs for a completely different reason: to coordinate one person against the distraction, context-switching, and accumulated variation that any growing business produces. When you run a business alone, you are the accountant, the marketer, the customer support team, and the operations manager. Without documented processes, each role competes for your attention in a slightly different way every week, and the inconsistency compounds into real problems.
Aziz's take
The most common objection I hear from solo founders is that their business is too small for SOPs. Every time I have heard that, it turned out the real issue was that the business was too disorganized for SOPs. Those are opposite problems. When you cannot document a process, it usually means the process does not fully exist yet. Writing the SOP is actually the forcing function that makes the process real. Start with whatever you do most often, and write it down the next time you do it. You will find gaps you did not know were there.
McDonald's operates over 40,000 locations across more than 100 countries. The product is consistent across all of them not because every employee is exceptional, but because the procedures are documented to a level that makes exceptionalism unnecessary. The SOP is the system. The system is the business.
For a solo founder, every recurring task is a candidate for a documented procedure: client onboarding, content publishing, bookkeeping, vendor payment, customer support responses, monthly reporting. Each one you document is one fewer thing you re-decide or re-explain every time you do it.
SOPs also have a compounding value that is easy to miss when you are working alone: they are the mechanism that makes delegation possible. The most common reason founders cannot hand work to a virtual assistant or a contractor is that the work only exists in their heads. An SOP externalizes it. Before you can hand something off, you have to be able to describe it. The SOP is that description.
For a broader perspective on why systematizing early is so critical, read our guide on why most businesses fail before they start and the role systems play in the ones that do not.
What Goes Into a Good SOP
A useful SOP has seven components. The more complex the process, the more detail each section needs. For a simple task, several sections can be a single sentence.
1. Title
The exact name of the procedure, specific enough that anyone can tell at a glance what this document covers. "Client Onboarding SOP" or "Monthly Bookkeeping Close" works. "The Process" does not.
2. Metadata
Version number, effective date, owner (who is responsible for keeping this accurate), and the next review date. This is what separates a document you trust from one you have to second-guess.
3. Purpose
One sentence explaining why this procedure exists. "To ensure every new client receives their welcome package within 24 hours of contract signing." The purpose tells someone following the SOP what success looks like before they even start.
4. Scope
Who does this apply to, and what triggers it. "This SOP is followed whenever a new client signs a contract, starting from the moment the signed agreement is received." Scope prevents ambiguity about when the procedure starts and who is responsible.
5. Prerequisites
What needs to be in place before step 1. Tools, accounts, template files, system access, or information that must be ready before the procedure can begin. Missing prerequisites are the most common source of stalls in a documented process.
6. Procedure
The numbered steps. Each step should have an action (what to do) and an expected result (what you should see or have when it is done correctly). Decision points and if/then branches go here, clearly marked, so the person following the SOP knows what to do at forks in the process.
7. Revision history
A log of when the SOP was updated, who changed it, and what changed. This is what lets you trust an SOP that has been in use for a year. Without revision history, you cannot tell whether the current version reflects how the process actually works today.
The Free SOP Template
Copy the template below into a Google Doc, Notion page, or any document tool you already use. Fill in the brackets. The template works for any recurring process in your business.
For the procedure section, write every step at the level of detail where someone competent but new to your business could follow it without asking a clarifying question. That is the standard. Not beginner-level hand-holding. Competent but new.
How to Write Your First SOP in 5 Steps
The most common failure mode for first-time SOP writers is trying to document everything at once. Pick one process and document it completely before moving to the next.
The 5-step SOP writing process
Pick one recurring task
The task you do most often, or the one that costs you the most time when it goes wrong. Start there, not with the most complex process in your business.
Do the task while writing down every step
Actually do it, and record each action as you take it. Do not reconstruct it from memory afterward. Observing the process as it happens catches steps that memory skips.
Mark every decision point
Go back through your steps and find every point where the next action depends on a condition. "If the client has not responded in 48 hours, go to step 7." These are the places where undocumented processes most often break down.
Add the prerequisites section
Look at step 1 and ask what must already be true before that step is possible. Work backward and add those items to the Prerequisites section. Prerequisites are what prevent someone from getting three steps in and realizing they cannot continue.
Set a review date before you file it
Write the date when you will check whether this SOP still accurately reflects the process. 90 days is a reasonable starting interval. Without a review date, SOPs drift silently out of sync with how the work actually gets done.
Once the SOP is written, hand it to someone unfamiliar with the task and have them follow it without assistance. Every question they ask, every moment they stall, is a gap in the document. Fix those before calling it done.
If you are working alone and do not have someone to test it with, wait two weeks and then follow your own SOP as if you have never seen it before. You will catch gaps you missed the first time.
Three SOP Examples for Common Founder Workflows
The fastest way to understand what a filled-in SOP looks like is to see one. Here are three examples for the processes founders most commonly need to systematize.
Example 1: New Client Onboarding SOP
Client Onboarding SOP | OPS-001 | v1.0
Purpose: Ensure every new client receives their onboarding materials within 24 hours of signing, and has a confirmed kickoff call within 5 business days.
Triggered when: Signed contract is received in inbox.
Steps:
- Reply to the client within 2 hours confirming receipt and next steps. Use the welcome email template in /templates/client-welcome.txt.
- Create a new client folder in /clients/[client-name]-[year] with the four standard subfolders: contracts, briefs, deliverables, invoices.
- Copy the signed contract into /contracts and rename to [client-name]-contract-[date].pdf.
- Send the onboarding questionnaire link via the Tally form at [link]. Log the send date in the CRM.
- Schedule the kickoff call using Calendly and send the invite. Target: within 5 business days.
- Decision point: If the questionnaire is not returned within 48 hours, send one follow-up. If no response after 72 hours, call the client directly.
- After the kickoff call, send a written summary of agreed scope, timeline, and next action. File the summary in /briefs.
Quality check: Kickoff call completed, scope summary sent and acknowledged, first invoice issued within 7 days of contract signing.
Example 2: Content Publishing SOP
Content Publishing SOP | OPS-002 | v1.0
Purpose: Publish each article with consistent formatting, SEO metadata, and internal linking before any content goes live.
Triggered when: A draft article is marked "approved" in the content calendar.
Steps:
- Final scan: zero em dashes, zero uncited statistics, all internal links verified live.
- Upload the PHP article file to /articles/content/[slug].php.
- Add the article entry to data/articles.json at position 0 (newest first).
- Run image-pipeline.py to generate WebP variants from hero.jpg.
- Run og-image-articles.py to generate the 1200x630 social sharing image.
- Submit the new URL to Google Search Console for indexing.
- Update 2-3 existing articles to add inbound links to the new article.
Quality check: Article visible on site, GSC index request submitted, og.png file present in assets folder, inbound links added to existing articles.
Example 3: Monthly Bookkeeping Close SOP
Monthly Bookkeeping Close SOP | FIN-001 | v1.0
Purpose: Close the books for each calendar month within 5 business days of month end, so financial reports are always current.
Triggered when: The first business day of the new month.
Steps:
- Download and reconcile the bank statement. Match every transaction to a record in your accounting software.
- Review all open invoices. Follow up on any invoice more than 14 days past due.
- Categorize any uncategorized expenses from the previous month.
- Review the profit and loss statement for the month. Flag any line item that is more than 20% above or below the prior month without a clear explanation.
- Decision point: If a significant unexplained variance is found, investigate before closing. Do not close the month with unexplained line items.
- Export the finalized P&L and balance sheet to /financials/[year]/[month-name].
- Update the monthly KPI tracker with revenue, expenses, and net profit figures.
Quality check: Bank reconciliation at zero discrepancy, all invoices current or in follow-up, P&L exported and filed, KPI tracker updated.
Notice the pattern across all three examples: the steps are specific enough to be followed without interpretation, the decision points are explicit rather than implied, and the quality check gives a concrete test for whether the procedure was completed correctly.
You can use ChatGPT to write the first draft of almost any SOP. Describe the process in plain English and ask it to format the output as a standard operating procedure with purpose, scope, prerequisites, numbered steps, decision points, and a quality check. You will still need to verify and refine the output, but the first draft takes minutes instead of an hour.
Why SOPs Fail (And How to Avoid It)
Most SOPs fail for one of three reasons. Each has a direct fix.
They are written for someone who does not exist. The person writing the SOP has deep context, and they skip steps that feel obvious to them but are not obvious to anyone else. The fix: write every step as if it will be followed by a capable person who has never done this task before. Not a beginner who needs everything explained from first principles. A skilled person who is new to your specific process and context.
They are never updated. A process documented in January can be obsolete by April if tools change, clients change, or the workflow evolves. An SOP that does not match the real process is worse than no SOP at all, because it produces confident mistakes. The fix: the review date. Make reviewing SOPs part of a scheduled quarterly routine, not a reaction to something going wrong.
They live somewhere nobody opens. An SOP in a Google Drive folder nobody bookmarks gets the same use as an SOP nobody wrote. Keep your SOPs somewhere you actually go: a pinned Notion page, a shared folder bookmarked in your browser, a #sops channel in Slack. Accessibility is not a formatting decision. It is a discipline decision.
Aziz's take
The first SOP I wrote for Groundwork was the content publishing checklist. It took about two hours. It saved me roughly 20 minutes every single week after that. In a year, that is 17 hours recovered from a task that was eating time in small, invisible pieces. The thing nobody tells you about documentation is that the time you spend writing it is front-loaded and obvious, but the time you get back is distributed and invisible. You will not feel yourself saving 20 minutes on a Tuesday. You will just eventually realize you are getting more done with less friction.
The last thing to say about SOPs is that they change how you see your business. When you sit down to document a process and realize you cannot explain steps 3 and 4 clearly, that is not a documentation problem. That is a process problem that was hiding in your head. Writing the SOP reveals the gaps. Fixing the gaps improves the business. The document is almost a side effect.
A lean canvas documents the business model. A lean canvas template gives you the structure to fill in. SOPs do the same thing for the operations layer: they give you the structure to capture how the business actually runs, not just how it is supposed to run in theory. Use both.
For an overview of the tools that can help you automate recurring steps inside your SOPs, see our guide on business automation for solo founders.
Frequently Asked Questions
