SOP generation and upkeep
Turn how your team actually works into clear, version-controlled standard operating procedures, and keep them current with an agentic tool that drafts, reviews, and flags stale docs against real source files.
Tools you'll use
A standard operating procedure (SOP) is the written version of how a job gets done: who does what, in what order, with what tools. Operations teams live or die by these. Good SOPs make onboarding faster, cut "how do I do this again?" interruptions, and give auditors something to check. The catch is that writing them is tedious and nobody updates them. Processes change, people swap tools, responsibilities move, and the doc quietly stops matching reality.
That gap is expensive. When the written process is missing or wrong, people fall back to hunting for answers. McKinsey's "The Social Economy" report found that interaction workers spend nearly 20% of the workweek searching for internal information, roughly a full day a week lost to "where's the right way to do this?" On top of that, auditors expect to see an SOP reviewed within the last 12 months; an 18-month-old review date is a finding. New hires follow broken steps, the team stops trusting the docs, and the whole library rots.
This is a strong fit for an agentic AI tool. The boring parts (turning a recorded walkthrough or a messy folder of notes into a clean, structured SOP, then re-checking it against the current process) are exactly what these tools do well. The point is not to replace your people's judgment. It is to give an operations lead a way to draft and maintain a real SOP library in hours instead of weeks, and to own that process going forward without hiring anyone.
Moriva's take
Gate 1 (Real work): SOP upkeep is a recurring chore every ops team owns and most neglect, so it attaches cleanly to weekly work. Gate 2 (Owned): an operations lead can run this with Claude Cowork on day one, no engineer required, and the SOPs live in your own files so you can edit and extend them forever. Gate 3 (Measured): you can count hours saved per SOP drafted and track how many docs you pulled back inside the 12-month review window. Risk is low because this is internal, reversible, and always reviewed by a human before publishing. This is a clear start-here.
How do you sOP generation and upkeep?
- 1
Pick one painful process and gather raw material
Start with a single process that breaks often or causes the most onboarding questions (a returns flow, a monthly close, a vendor onboarding). Collect whatever already exists: old SOP drafts, Slack threads, a recorded screen walkthrough with a transcript, the relevant spreadsheet or checklist. You are not writing yet; you are pointing the tool at the truth of how the work is done today.
- 2
Draft the SOP with Claude Cowork
Open Claude Cowork, hand it the raw material, and ask it to produce a structured SOP: title, owner role, purpose, prerequisites, numbered steps, and decision points. Cowork is built for this kind of multi-document synthesis and needs no code, so an ops lead runs it directly. Tell it to flag any step where the source material is vague or contradictory rather than guessing.
- 3
Review with the person who actually does the job
Sit the SOP next to the person who runs the process and walk it line by line. Fix the spots Cowork flagged as uncertain and any step that does not match reality. This human pass is non-negotiable; the tool drafts, your people decide what is correct. Capture the named owner and approver before you call it done.
- 4
Set a standard format and store SOPs as plain files
Agree on one template (Markdown files in a shared repo or folder work well, and keep version history for free). Save each SOP with its owner, approver, effective date, and last-reviewed date in a header. Storing SOPs as plain text files means you own them outright and any tool can read and update them later, with no platform lock-in.
- 5
Batch-generate the rest of the library
Once the format is proven, repeat for your other core processes. Feed Cowork a batch of source materials and your approved template so each new SOP comes out in the same shape. Keep the same review-with-the-doer step for every one; speed comes from drafting, trust comes from the human check.
- 6
Stand up a staleness check with Claude Code
If your processes are tied to files that change (a pricing sheet, a config, a tool's settings), point Claude Code at both the SOPs and those source files and ask it to flag SOPs whose steps no longer match. Describe the check in plain English; Claude Code builds a small script your team owns and can re-run. This turns 'we should update the docs someday' into a list of specific docs to review.
- 7
Schedule the review cadence and keep an audit trail
Run the staleness check monthly or quarterly, and run a full review of each SOP at least once every 12 months so you stay inside the window auditors expect. Because SOPs are version-controlled files, you automatically keep a dated history of what the process was on any given day. Assign each flagged SOP back to its owner to update and its approver to sign off.
What could go wrong (and how to handle it)
The AI invents a step that nobody actually performs, or smooths over a contradiction in the source material.
Require the drafting tool to flag uncertain steps instead of guessing, and never publish an SOP without a line-by-line review by the person who does the job.
Sensitive data (customer records, credentials, internal pricing) ends up in source material fed to the tool.
Strip secrets and customer PII from inputs before drafting; keep credentials in steps as references ('use the shared vault'), never as literal values. Treat the SOP library as medium-sensitivity internal content.
The library is generated once and then rots again, recreating the original problem.
Treat the scheduled staleness check and 12-month review as the actual deliverable, not the first batch of docs. Assign a named owner to every SOP so review has somewhere to land.
Over-automation: a process changes and the SOP auto-updates without anyone confirming the new way is correct or safe.
Keep a human approver in the loop. The tool flags and drafts changes; a person verifies and signs off before the SOP is considered current.
SOPs drift out of sync with the systems they describe because the doc lives far from the work.
Store SOPs close to where the work happens and version them, so the staleness check can compare docs directly against the source files that drive the process.
For regulated processes, an SOP that is wrong creates compliance exposure, not just confusion.
Route regulated SOPs through your existing quality or compliance approval before publishing, and rely on version history to prove what the procedure was on any given date.
Prompts to get started
FAQ
Won't the AI just make up steps that sound plausible but are wrong?
It can, which is why the workflow never publishes a draft unsupervised. You instruct the tool to flag uncertain or contradictory steps rather than guess, and the person who actually runs the process reviews every SOP before it goes live. The tool saves you the typing; your people still own correctness.
Do I need a developer to set this up?
No, not for the core of it. An operations lead can draft and maintain the whole library with Claude Cowork, which is built for non-coders doing research and document work. Claude Code only comes in if you want an automated staleness check against files that change, and even then it builds a small script your team can run and edit itself.
Where do the SOPs actually live, and do we own them?
You own them completely. We recommend storing them as plain Markdown files in a shared folder or repo you control, which gives you free version history and an audit trail. There is no proprietary platform holding your procedures hostage, and any tool can read or update them later.
How does this help with audits and compliance?
Auditors expect each SOP to have a named owner and a review within the last 12 months, plus a history of past versions. Storing SOPs as version-controlled files gives you the dated history automatically, and the scheduled review cadence keeps every doc inside the window auditors look for. For regulated processes, route the SOP through your existing quality sign-off before publishing.
How do we know it's actually saving time?
Track two numbers. First, drafting time per SOP, which typically drops from hours of writing to a draft-plus-review in well under an hour. Second, the share of your library reviewed within the last 12 months, which should climb from 'who knows' to near 100% once the cadence runs. Both are easy to point at.
Sources
- The average interaction worker spends an estimated 28 percent of the workweek managing e-mail and nearly 20 percent looking for internal information or tracking down colleagues who can help with specific tasks. — McKinsey Global Institute, The Social Economy, 2012
More from Operations
Meeting notes to action items and tickets
Turn raw meeting transcripts into clean action items and properly formatted tickets in your tracker, with a human approving before anything gets created. An owned automation your ops team runs every week and can fix itself.
Executive briefings from many sources
Build an agent that reads your scattered sources every morning and writes one short, sourced briefing for leadership, so an operator stops spending an hour stitching updates together by hand.
Prep renewals and spot upsell openings
Build a repeatable agent that pulls usage, support, and account data into a per-customer renewal brief flagging churn risk and concrete upsell openings, 90 days ahead of each renewal date.
Want help shipping this?
We'll build it with your team on your real work — and leave you owning it, not renting it.