How the SOP generator works
This tool turns a few quick choices into a complete standard operating procedure. You pick the process you want to document, name the person accountable for it and the person who runs it, set how often it runs, and toggle off any sections that do not apply. The generator lays out the document in the standard SOP format: purpose, scope, tools and access, numbered steps, a quality checklist, edge cases with escalation rules, and handoff expectations. The copy button drops the whole thing into your clipboard as clean plain text that pastes into a Google Doc, Notion, or any project tool.
The eight built-in templates cover the processes business owners delegate first: inbox management, calendar scheduling, social media publishing, invoicing, CRM updates, customer support, weekly reporting, and research. Each one is grounded in the work Cherry assistants run for clients every day, which is why the steps name real checks and real escalation rules instead of filler. For anything else, the blank framework gives you the same structure with prompts for what to write in each section. If the process is documented but you have no one to run it, you can request vetted candidates and hand over the SOP on day one.
What a standard operating procedure should include
Most SOP templates fail in the same way: they capture the happy path and skip everything that makes the document usable by someone new. A procedure your assistant can actually run needs eight parts, and the two that get skipped most often, the quality checklist and the edge cases, are the ones that save you the most interruptions.
| Section | What it is for |
|---|---|
| Purpose | One or two sentences on why the process exists and what a good outcome looks like |
| Scope & boundaries | Who runs it, what it covers, and the decisions that always need the owner |
| Tools & access | Every account and template needed, with the access level, before the first run |
| Step-by-step procedure | Numbered actions, each starting with a verb, specific enough to follow without asking |
| Quality checklist | Pass/fail checks the person runs before calling the work done |
| Edge cases & escalation | If-this-then-that rules for the situations outside the happy path |
| Handoff & reporting | What gets reported when the process finishes, to whom, and in which channel |
| Revision history | Version, date, and a review cadence so the document stays true over time |
The test of a good SOP is simple: could a capable person you have never met produce an acceptable result from the document alone? If they would have to ask what a tool is, where a template lives, or what to do when a customer gets angry, the document is not finished yet.
How to write an SOP step by step
If you are documenting a process by hand, or turning the generated draft into the real thing, work in this order. First do the task yourself once while recording your screen, because the recording catches the steps you do on autopilot and would never think to write down. Turn each action into a numbered step that starts with a verb and names the exact button, field, or template where it matters. Add the trigger that starts the process, the tools and access needed before the first run, and what done looks like in checkable terms. Then write the section most people skip: the situations where the person should stop and ask instead of pushing through, and exactly who to contact for each one. Finally, have the person who will run the process walk through the document once while you watch, and fix every step where they hesitated. That single walkthrough catches more problems than any amount of editing.
SOPs slot into a larger delegation workflow, and the other pieces are here too. The job description generator scopes the role before you hire, the interview questions generator builds the screening script, the contract template generator handles the paperwork, and the onboarding checklist generator plans the first 90 days, during which your assistant documents each process they learn and your SOP library builds itself. To size the budget for the person who will run these procedures, the cost calculator compares a dedicated assistant against an in-house hire.
SOP templates by process
The generator ships with templates for the eight processes owners hand off first, each mapped to a role we source. Inbox management and calendar scheduling are usually run by a general virtual assistant or an executive assistant. Invoicing and payment follow-up belong to a bookkeeper, customer support replies to a customer support representative, and social publishing to a social media manager. CRM updates map to a CRM specialist, and research briefs to a research assistant.
If your process library has outgrown what you can maintain yourself, there is a role for that too: an SOP specialist who documents, organizes, and keeps procedures current as the business changes. Browse the full list of roles we source and the use cases clients hire for to see where a documented process could become a delegated one.
Why SOPs are the unlock for delegation
The reason most delegation fails is not the hire, it is the handoff. A process that lives in your head cannot be delegated, only demonstrated, which means every question comes back to you and the assistant can never be more consistent than your availability. A written SOP breaks that dependency. The assistant ramps in days instead of weeks, output is checkable against the document instead of your memory, and quality stops depending on who happened to do the task that day. The library compounds too: your second hire inherits every procedure the first one helped write, and getting more from the whole team gets easier with each document added.
There is a second-order benefit owners rarely expect: writing the procedure down exposes the process. Steps that exist for no reason, approvals nobody remembers instituting, and workarounds that became habits all surface the moment you try to explain them to someone else. Many clients tell us the documentation exercise improved the process before an assistant ever touched it. If you want a partner who works this way by default, read how Cherry works and see transparent pricing for a dedicated assistant who runs your procedures and keeps them current.
Document the process, then hand it off
An SOP is most valuable the day someone else runs it. If you have the documents but not the person, tell us which processes you want off your plate and we will match you with vetted candidates, primarily in South Africa, who are used to working from procedures and documenting new ones as they learn. Build your SOP above, then request candidates or book a meeting to hand it off.
