Write the SOP right after doing the task. Use a 3-part format. Keep it under one page. Store it where the work happens.
Every SOP answers: what starts this? what are the exact steps? how do I know it's complete?
Document the task the day you do it, not a month later. Accuracy drops fast from memory.
If it's longer, split into two SOPs or use a checklist. Unread SOPs are worse than no SOPs.
Google Docs, Notion, or even a shared drive folder. The tool doesn't matter — proximity to the workflow does.
Don't write SOPs for tasks you do once a year or tasks that require judgment each time. SOPs are for repeatable, rule-based tasks.
Standard Operating Procedure — a documented method for completing a repeatable task consistently, regardless of who does it.
One page or less for most tasks. If your SOP needs 3 pages, it's either two processes or it needs to be condensed into a checklist.
Notion, Google Docs, Confluence, and simple shared drives are all common. The most important factor is that it's where your team naturally looks — not a separate 'documentation system' nobody opens.
Want a quick operator take on your situation?
💬 Text PJ · 773-544-1231Updated: 2026-03-04T19:46:03Z · SideGuy Solutions
Not finding what you need? Text PJ · 773-544-1231
See Also — Related Clusters