If you’ve ever sat down to finally document how your team does things and found yourself wondering whether you’re writing a “procedure,” a “process,” an “SOP,” or just… instructions — you’re not alone. These terms get used interchangeably in most small organizations, and that’s fine right up until the day it isn’t: a new hire follows the wrong document, an auditor asks for something you can’t produce, or the one person who knew the whole routine retires.
The good news: the distinction is simple, and once you see it, everything you document gets easier to organize.
An SOP is one task, done right
A Standard Operating Procedure answers a single question: how do we do this one thing, correctly, every time?
Resetting a password. Creating an email account for a new employee. Backing up the front-desk computer. Closing out the register. Each of these is one task with a clear start, a clear finish, and a set of steps in between. That’s an SOP.
A good SOP is specific enough that someone unfamiliar with the task can follow it without asking for help. Screenshots of each step, in order, with short plain-language instructions — that’s the gold standard, because it removes guesswork.
A process is the bigger picture
A process answers a different question: what has to happen, in what order, to get a larger outcome?
Take onboarding a new hire. That’s not one task — it’s a chain of them. Someone creates the email account. Someone sets up the workstation. Someone adds them to payroll, orders a badge, walks them through safety training. Each link in that chain is its own SOP. The chain itself — the sequence, the handoffs, the “this must happen before that” — is the process.
Here’s an easy way to hold onto it: an SOP is a recipe; a process is the whole dinner. You can hand anyone a recipe and get a reliable dish. But putting dinner on the table means knowing which dishes to make, in what order, and how they come together.
Why the distinction matters
It might sound like bookkeeping, but separating tasks from workflows pays off in three places:
Consistency. When each task lives in its own SOP, updating “how we reset passwords” means changing one document — and every process that includes that step is automatically current. No hunting through five different binders for the same instructions written five different ways.
Training. New people learn faster when they can zoom in and out. The process view tells them where their work fits; the SOP view tells them exactly what to do right now. Neither one alone gets them there.
Audit-readiness. Whether it’s a compliance review, an insurance question, or a board member asking “how do we handle this?”, being able to produce both the workflow and the step-by-step detail behind each stage is the difference between a scramble and a shrug-and-print.
Most teams have pieces of both — scattered
If your documentation lives in a mix of Word files, sticky notes, and one veteran employee’s memory, you already have SOPs and processes. They’re just not written down in a way anyone else can use. The goal isn’t to create something new — it’s to capture what your team already knows before it walks out the door.
How Notavi handles both
This distinction is built into how Notavi works.
When you perform a task on your computer, Notavi captures it as you go — each step recorded with a screenshot and turned into a clean, standardized SOP you can hand to anyone. No writing from memory, no formatting battles. Do the task once, and the documentation writes itself.
And with Processes, you can now link those SOPs into complete workflows. Build your “New Hire Onboarding” process out of the SOPs your team already captured — email setup, workstation prep, payroll — and everyone sees both the big picture and the exact steps behind every stage. Update an SOP once, and every process that uses it stays current.
Everything stays in files you control, stored where you choose — not locked in someone else’s cloud.
Start with one recipe
Don’t try to document everything at once. Pick one task your team does weekly — the one that always generates questions — and capture it as an SOP. Then pick the workflow it belongs to and sketch the process around it. In an afternoon you’ll have more usable documentation than most small organizations build in a year.
See how it works on the Notavi product page — available for Mac and Windows — and capture your first SOP today.