How to Write SOPs in Google Docs (with Template)
A step-by-step method for writing procedures people actually follow, a free SOP template to copy into Google Docs, and how to keep the library current.

A standard operating procedure (SOP) is a written, step-by-step description of how a recurring task is done, so it's done the same way no matter who does it. You need one when a task repeats, when mistakes are costly, or when only one person knows how to do it. Google Docs is a natural place to write SOPs: the people who do the work can write and update them, and everyone can comment.
This guide shows how to write an SOP people actually follow, gives you a template to copy, and explains how to keep a library of SOPs findable and current.
How to write an SOP, step by step
- Pick the right process. Start with tasks that repeat often, break easily or depend on one person: month-end close, customer refunds, publishing a release, onboarding a client.
- Write it with the person who does it. Watch them do the task once, or ask them to narrate it while you take notes. The best SOPs come from the people who do the work, not from a manager's memory.
- Define the scope. One sentence on what the procedure covers and when it starts and ends. If it branches into several cases, write one SOP per case.
- List what's needed before starting. Access, tools, inputs and approvals.
- Write numbered steps. One action per step, starting with a verb, with exact names of buttons, fields and files. Put decisions in the step itself: "If the amount is over 500 euros, ask Finance to approve."
- Show the tricky parts. A screenshot or a short video where people usually get stuck.
- Mark what can go wrong. Call out the steps that can't be undone, and say what to do when something fails.
- Test it. Hand the draft to someone who has never done the task and watch where they hesitate. Fix those spots.
- Name an owner and a review date. Every SOP gets one person responsible for it and a date to check it again.
The SOP template
Copy this into a new Google Doc and use real heading styles for each section, so the doc gets a table of contents.
# [Process name]: SOP Owner: [name] · Last reviewed: [date] · Next review: [date] ## Purpose One sentence: what this procedure achieves and why it matters. ## Scope When it applies, when it doesn't, where it starts and ends. ## Roles Who does what: the doer, the approver, who to tell. ## Before you start - Access or tools needed - Inputs: files, data, approvals ## Steps 1. [Verb] [exact action] 2. [Verb] [exact action] If [condition], then [action]. 3. ... ## If something goes wrong The most common problems and what to do. ## Related - Links to related SOPs and policies ## Change log [date]: [what changed], [who]
For the parts readers must not miss, use a callout. In Spaceli, a simple marker at the start of a paragraph in Google Docs turns it into a Note, Tip, Warning, Danger or Success callout on the page.
Keeping SOPs findable and current
An SOP nobody can find in the moment is an SOP nobody follows. Two habits fix most of it.
One home for all SOPs. Keep them in one folder in a shared drive, with a subfolder per team or area: Finance, Operations, Support, Engineering. Name each doc by the task ("Issue a customer refund"), not by a code number. Our Google Drive folder structure for teams shows where the folder fits.
A review rhythm. Review each SOP on its review date, and update it in the same week as any change to the process. An outdated SOP is worse than none, because people trust it. More habits in how to keep team documentation up to date.
To make the folder easy to use day to day, connect it to Spaceli. Every SOP becomes a clean page in a sidebar organized by team, with a table of contents and search across titles and full text, so the right procedure is a Cmd+K away. When a step changes, whoever does the work edits the SOP right inside Spaceli in the Google Docs editor, and the change syncs to Drive. Screen recordings in Loom or YouTube and process diagrams in Miro or Whimsical sit right on the page.
FAQ
What's the difference between an SOP and a policy?
A policy says what the rule is and why. An SOP says how to do the task, step by step. An expense policy sets the limits; the expense SOP explains how to submit a claim. Policies usually live in the employee handbook.
How detailed should an SOP be?
Detailed enough that someone who has never done the task can do it correctly on the first try, and no more. If a step needs a paragraph, it's probably two steps.
Should SOPs be in Google Docs or a dedicated tool?
Google Docs works well because the people who do the work already write there. Add a knowledge base layer like Spaceli when the library grows and finding the right SOP becomes the problem.
How often should SOPs be reviewed?
At least once a year, and right away when the process, the tools or the people involved change.

Writes about wikis, documentation and how teams keep their knowledge easy to find.
Keep reading
All articles →Employee Onboarding Checklist Template for Google Docs
A free onboarding checklist for Google Docs: before day one, day one, week one and the first 90 days, with an owner for every task.
Employee Handbook Template for Google Docs
A free employee handbook template for Google Docs: every section a growing company needs, what to write in each, and how to publish it.
Help Center Article Template: How to Write Docs Customers Actually Read
Three copy-ready help article templates (how-to, troubleshooting, explainer), style rules and a checklist for writing docs customers actually read.
Your knowledge base is already in Google Drive.
Give your team a better way to organize, find, and share knowledge. Keep your documents right where they are.
Start for FreeFree during the beta. Get started in about a minute.
Spaceli only accesses the folders you choose.