SOPs that actually get used: writing procedures with AI

Open your documentation system and look at the last-viewed dates on your procedures. Go ahead, we'll wait.

If your team is like most, there's a folder of SOPs written during an audit push or an onboarding sprint two years ago, viewed a handful of times since, quietly rotting while the actual procedure lives in the head of whoever has done the task most recently. When that person is on holiday, the task is done wrong or not at all. Everyone agrees documentation matters. The folder stays dead anyway.

Here's the uncomfortable explanation: those SOPs were written for the auditor, not the person doing the work. Documents written to prove a process exists read very differently from documents written to help someone at 16:45 on a Friday do a task they half remember. The first kind fills folders. Only the second kind gets opened.

What makes an SOP get used

It's shaped like the task, not like the org chart. "Employee offboarding and access revocation" gets used. "HR-IT interface procedures, section 4.2" does not. Someone with a task should find the document by searching the words in their head at that moment.

It fits on roughly a page. If the procedure is longer, it's usually two procedures stapled together, or it's padded with background that belongs in a policy. The person mid-task needs steps, not history. Anything you have to scroll past to start working is a tax on every single use.

Every step is checkable. "Ensure the account is properly secured" is not a step, it's a wish. "Disable the account in the identity provider, then confirm the user shows as blocked in the admin portal" is a step. The reader should never have to decide what a sentence means while doing it.

It says how you know it worked. The most commonly missing section in real-world SOPs is verification. What should be true when you're done? A procedure without a verification step produces confident mistakes, and those are the expensive kind.

It has an owner and a review date. Not a committee, one name. And a date, because "we review documentation regularly" means never, while "review due March" means March. Most SOP decay is nobody's fault because keeping it current was nobody's job.

Where AI changes the economics

The honest reason documentation debt exists is that writing procedures is slow and it always loses to a ringing phone. AI changes the cost side of that equation dramatically, if you feed it the right raw material.

The workflow that works: have the person who knows the task talk through it once, roughly. A voice memo while doing the task is ideal, a rambling explanation in chat also works. Feed that raw brain-dump to your AI assistant with instructions to structure it as a task-shaped SOP with numbered steps, decision points, and a verification section. Then, and this is the step that separates real documentation from plausible fiction, the expert reviews the draft against reality.

That review matters because AI will confidently fill gaps with what usually happens at other companies rather than what happens at yours. The expert isn't checking grammar. They're checking that step 4 doesn't skip the approval your company actually requires.

Total cost per SOP with this workflow: about twenty minutes of expert time instead of an afternoon. At that price you can afford to document the long tail of tasks that were never worth an afternoon.

Consistency is what makes a library

One good SOP is nice. Thirty SOPs that all follow the same skeleton is an operating asset. Same sections in the same order, same style of step, verification at the end, owner and date in the header. When every procedure looks the same, people stop reading defensively. They know where the steps live, where the exceptions are, and where to look when it goes sideways.

Getting to that consistency is mostly a template problem. We ship fifty pre-structured SOP templates in the Opstimio library, covering the usual suspects from onboarding to access revocation to backup verification, exactly so teams don't have to invent the skeleton fifty times. But even if you build your own template from scratch, build one, write it down, and let AI fill it per task from expert brain-dumps. That combination is what turns documentation from a project that never finishes into a habit that doesn't hurt.

Start with the scariest gap

Don't start a documentation programme. Start with one question at Monday's standup: "Which task would hurt most if the only person who knows it won leave next month?"

That answer is your first SOP. Twenty minutes of that person talking, one AI-structured draft, one review. Ship it, put a name and a review date on it, and do the next one next week. Ten weeks later you have the ten documents that actually matter, and a folder people open on purpose.