Workflow Automation
Most small businesses run on undocumented knowledge. When the person who knows how to do something is out sick, everything stops. A standard operating procedure — a SOP — is how you fix that. This guide walks through documenting one process from scratch in under 30 minutes.
Pick the right first process
Not every process needs a SOP on day one. Start with the one that causes the most friction when the person who owns it is unavailable.
Common first candidates: client onboarding, invoice processing, weekly reporting, content publishing, vendor payments.
The four-part structure
Every useful SOP has four parts: trigger (what starts this process), steps (numbered, one action per step), decision points (if X then Y), and output (what the finished state looks like). Anything more complicated than this usually means the process itself needs simplification before documentation.
Write it while you do it
The fastest way to document a process is to run it once while narrating. Open a doc, set a timer for 30 minutes, and do the actual work while writing each step in plain language. Do not reconstruct from memory — memory compresses steps and skips the parts that only become obvious when something goes wrong.
The one-sentence test
Read each step aloud as a single sentence. If it takes more than one breath to say, it contains more than one action. Split it. The goal is that someone unfamiliar with the process could follow these steps without asking a question.
What to do with it
A SOP that lives in a doc no one can find is not a SOP — it is a liability. The moment you write it, it belongs in your shared workspace with a clear owner and a review date. Set a calendar reminder to review it quarterly. Processes change; documentation that does not change with them becomes dangerous.
Ready to build your full workflow documentation library? The Workflow Automation guided workflow walks you through documenting your team's processes systematically and produces a complete operations reference.