I need to write SOPs and have no idea where to start. Where do I begin?

This page may contain affiliate links from which Blur Studio earns commissions.

The hardest part of writing an SOP is rarely the content, it's starting. A blank page makes you decide on structure, tone and level of detail all at once, before you've even gotten to the actual steps. The fix is simple: never start from blank.

Free ways to get a starting structure

• Google or Notion template galleries (free): both have public template libraries with SOP, onboarding and handbook templates you can copy directly. The content is generic, but the structure (sections, headers, a logical flow) saves real time.
• ChatGPT or Claude drafts (free to low-cost): describe the process in a sentence or two and ask for a numbered SOP structure. This is genuinely useful for the skeleton, but treat every generated step as a guess until you've personally verified it matches how the work actually gets done; AI will confidently invent a plausible-sounding step that isn't how you actually do it.

Either way, the actual work is the same: take the structure, and replace every generic line with the real step, in your own words, checked against someone who actually does the job.

Where a built-in template library earns its cost

Trainual, a platform for writing up and assigning company process documentation, includes a library of 500+ templates across process, policy and role documentation on every plan, meaning the starting-structure problem above is solved once inside the platform rather than needing a separate trip to a free gallery each time. As of 29 October 2026 Trainual is quote-only (Core, Pro, Premium, Enterprise, no published monthly price) with a $1,000 one-time setup fee on new accounts; its paid courses library is a separate add-on on top of that.

That cost only makes sense if you're writing SOPs often enough, or across enough roles, that saved time per template adds up to real money. If you need three or four SOPs total, a free Google template plus an afternoon of editing gets you most of the way there for nothing. To see what the library holds, read Trainual templates: what is included.

The mistake almost everyone makes with templates

A generic template describes the shape of a process, not your process. Using it word for word without replacing the steps with your own real workflow produces an SOP that looks professional and is subtly wrong, which is worse than no SOP at all, because people trust it. Treat any template, free or paid, as a skeleton to fill in, never a finished document.

A worked example: turning a generic template into a real one

Say you pull a free "customer onboarding" template from a Notion gallery. It arrives with sections like "Welcome Call," "Send Contract," "Schedule Kickoff," each with a generic one-line description. The template is useful exactly because it tells you what sections an onboarding SOP typically has, but every one of those lines needs replacing with your actual practice: what you specifically say on the welcome call, which contract template you actually send and from where, who specifically schedules the kickoff and how far out from signing. A good test for whether you've actually done this work rather than just renamed the template: hand the filled-in version to someone who's never onboarded a client at your business and see if they can do it without asking you anything. If they can't, a section still reads as generic rather than as your real process, and that's exactly the section to go back and rewrite with more specific detail.

A practical note on AI drafts specifically

Asking ChatGPT or Claude for an SOP draft works best when you give it real detail up front rather than a one-line description. "Write an SOP for onboarding a new client" produces a generic skeleton. "Write an SOP for onboarding a new landscaping client: we send a contract through our invoicing tool, schedule a site visit within a week, and assign a crew lead who calls the client the day before" produces something much closer to usable, because the model has actual facts to work from instead of guessing at a plausible-sounding process. Either way, read every step out loud to yourself and ask "is this actually what I do," not "does this sound reasonable," since AI-generated steps are specifically good at sounding reasonable while being wrong about your specific business. A fuller set of prompts and a review checklist is in how to write SOPs with AI.

A simple structure that works for almost any process

If you don't want to hunt for a template at all, this basic shape covers most operational SOPs: a one-line purpose statement (what this process accomplishes and why it matters), a numbered list of steps in the order they actually happen, a short "common mistakes" section for anything that trips people up repeatedly, and a named owner responsible for keeping it current. That's four sections, not forty, and it's enough structure to be genuinely useful without taking longer to build than the process itself takes to do.

A worked example: writing your first SOP in under an hour

Say you've never written an SOP and you're starting with "how we onboard a new client," which currently lives entirely in your head. Pull a free template from Notion's gallery for structure, fifteen minutes. Then narrate the process out loud to yourself or a colleague exactly as you'd actually do it this week, including the small things you don't usually think to mention, like checking a specific field in your CRM before sending the welcome email, twenty minutes to talk through and type up roughly. Hand the draft to the newest person on your team and watch them try to follow it without asking you anything, fifteen minutes. The questions they ask in that fifteen minutes are the exact gaps worth fixing, and fixing three or four specific gaps takes another ten minutes. Under an hour total, and you have a real, tested SOP rather than a template that merely looks finished.

A practical note on building a habit, not a one-time project

The businesses that end up with genuinely useful SOPs rarely wrote them all in one big push. They built a small habit: whenever something goes wrong twice, write down the correct version once so it doesn't go wrong a third time. That habit, applied consistently over a few months, produces a more useful set of documentation than a single ambitious weekend trying to document everything the business does, because each SOP exists specifically because it was needed, not because a checklist said you should have one. Once a few exist, you can turn your SOPs into audio training for staff who prefer listening.

How I'd approach this

If you've genuinely never written one before, start with a free Google template today, pick your single most repeated task, and get a rough draft done this week rather than researching the perfect tool. Once you've written three or four SOPs by hand and know roughly how much time that costs you, that's the point where a template library or AI drafting tool's value becomes obvious, rather than something you're guessing at. When a folder of docs stops working is covered in Trainual vs Google Docs.