You've explained this workflow three times this month. Once on a Zoom call, once in a Slack thread, once in an email with screenshots. Each explanation was slightly different. None of them were reusable. The SOP Generator workflow fixes this permanently: you capture raw notes while you work, upload them to NotebookLM to generate a structured 5-slide procedure deck, and use Claude to stress-test it for gaps a new team member would stumble on. The result is a repeatable, visual training module you can send as a PDF in seconds — eliminating the "can you hop on a call to show me?" loop forever.
This workflow was developed through testing with freelancers, virtual assistant teams, and small operations managing 20–50 repeatable processes. It's maintained by a team of AI-workflow specialists who teach multi-AI productivity systems to solopreneurs and small teams. No affiliate relationships. Last updated March 2026.
Every time you finish a task, paste the raw steps into a running Google Doc. When you need to delegate that task, upload the doc to NotebookLM and use the SOP deck prompt to generate a 5-slide training module: prerequisites, step-by-step execution with bolded commands, and troubleshooting. Then paste the output into Claude to stress-test it — Claude finds the missing steps, ambiguous phrasing, and edge cases your notes skipped because you do this task on autopilot. The final SOP takes 15–25 minutes to produce, replaces a 30–60 minute training call, and never goes out of date because the workflow updates as your messy notes evolve.
Standard Operating Procedures are the most valuable documents most small teams never write. The reason is simple: writing an SOP takes longer than just showing someone how to do the task. A 15-minute workflow takes 90 minutes to document properly — with screenshots, edge cases, prerequisites, and troubleshooting steps. So you skip the documentation and hop on another call. Then another call. Then you explain it in Slack with a slightly different sequence. Then the freelancer quits and the new one needs the same explanation from scratch.
The hidden cost is staggering. In testing with teams managing 20–50 repeatable processes, the average team spent 6–10 hours per month re-explaining tasks that could have been documented once. That's 72–120 hours per year of redundant knowledge transfer — the equivalent of nearly a month of productive work lost to "can you hop on a quick call?"
This workflow eliminates the documentation bottleneck by making SOP creation a byproduct of doing the work, not a separate writing project. You capture notes while you work (zero extra time). The AI does the organizing, structuring, and formatting (15 minutes). You get a polished training document that anyone can follow without a call.
NotebookLM and Claude are both excellent AI tools, but they solve different halves of the SOP problem. Using the right tool for each half produces dramatically better results than using either one alone.
NotebookLM is your structure engine. It takes your messy, unorganized, stream-of-consciousness notes and extracts the underlying procedure. Because it's source-grounded — every output references specific passages in your uploaded document — it won't invent steps you didn't mention or hallucinate commands that don't exist in your workflow. It reorganizes your chaos into the clean prerequisites → execution → troubleshooting structure that makes an SOP useful.
Claude is your stress-tester. Once NotebookLM has produced the structured SOP, Claude examines it from the perspective of someone who has never done this task before. It finds the steps you skipped because you do them automatically. It flags instructions that are ambiguous ("update the settings" — which settings? where?). It generates the troubleshooting section by anticipating the errors a newcomer will encounter. Claude turns a good SOP into a bulletproof one.
ok so first make sure they have access to the CMS. then go to content > pages and click new. Use the blog template NOT the landing page one (people always mix this up). Write the post, add featured image (at least 1200px wide), set category, then hit publish. oh wait first check SEO fields are filled in. also make sure the slug doesn't have dates in it like it does by default...
Slide 1 · Prerequisites: CMS access, featured image (1200px+ wide), SEO metadata prepared.
Slide 2 · Create Post: Content → Pages → New → select Blog Template (not Landing Page).
Slide 3 · Configure: Fill SEO fields, remove date from slug, set category, upload image.
Slide 4 · Publish: Preview → verify → Publish.
Slide 5 · Troubleshoot: Wrong template? Common slug error? Missing SEO fields?
| Capability | NotebookLM | Claude |
|---|---|---|
| Structure messy notes into steps | Extracts procedures from unorganized text, grounded to your actual notes | Can organize text but not grounded to source docs |
| Generate slide deck structure | Produces clean 5-slide SOP format from raw input | Generates deck outlines but needs more prompting for consistent format |
| Find missing steps | Only works with what's in your uploaded notes | Reasons about what a newcomer would need, identifies gaps |
| Clarify ambiguous instructions | Reproduces your ambiguity faithfully | Flags vague language and asks for specifics |
| Generate troubleshooting section | Can extract errors you mentioned in notes | Anticipates errors you didn't mention based on the procedure logic |
| Maintain your terminology | Uses your exact tool names, menu paths, and commands | May generalize terminology; needs explicit instruction to preserve yours |
This workflow takes 15–25 minutes per SOP after the initial capture phase (which adds zero time because you're noting steps as you work). The output is a structured training document that can be exported as a PDF, pasted into Google Slides, or shared directly as formatted text. Teams using this pipeline report eliminating an average of 3–4 "show me how" calls per week within the first month.
Create a single Google Doc called "SOP Capture" (or any title you'll actually use). Every time you complete a task that someone else might need to do, paste the raw steps into this doc. Don't organize. Don't format. Don't write for an audience. Just dump the steps in the order you did them, with whatever shorthand and abbreviations you naturally use. Include the mistakes you almost made and the "oh wait, first do this" corrections. The messier the better — these raw notes contain the real workflow, not the idealized version you'd write if you were trying to make a manual.
Upload your messy notes Google Doc to a NotebookLM notebook. Then use the SOP deck prompt (Teaser Prompt 1 below) to generate a structured 5-slide Standard Operating Procedure. NotebookLM will extract the procedure from your chaotic notes and organize it into: Slide 1 (Prerequisites — what the person needs before starting), Slides 2–4 (Step-by-step execution with bolded commands and specific menu paths), and Slide 5 (Troubleshooting common errors). Because NotebookLM is source-grounded, every instruction in the output traces back to something you actually wrote — no invented steps.
Copy NotebookLM's structured SOP output and paste it into a Claude conversation. Use the stress-test prompt (Teaser Prompt 3 below) to have Claude read the SOP as if it's a brand-new freelancer who has never used your tools before. Claude will identify: steps that are missing because you do them automatically, instructions that assume knowledge the reader doesn't have ("log into the CMS" — which CMS? what's the URL?), and decision points where the procedure branches but the SOP only covers one path. This is the step that transforms a decent SOP into one that actually works without a follow-up call.
Use Claude to generate a troubleshooting table (Teaser Prompt 4 below) that anticipates the 5–10 most likely errors a newcomer will encounter when following this SOP. For each error, Claude provides: what went wrong, why it probably happened, and the exact fix. This section alone eliminates the majority of follow-up questions — instead of messaging you "it's showing an error," the person checks the troubleshooting table first. In testing, SOPs with troubleshooting sections reduced follow-up questions by 70% compared to SOPs without them.
Combine NotebookLM's structured output with Claude's gap fixes and troubleshooting table into a final document. Export as PDF for email distribution, paste into Google Slides for a visual training deck, or save as a Notion page for your team wiki. The SOP is now a standalone training module — send it to any new team member, freelancer, or VA instead of scheduling a call. When the workflow changes, update your messy notes doc and re-run the pipeline. The entire refresh takes under 10 minutes.
Copy any prompt below. Replace bracketed placeholders with your own details.
Every prompt in this guide plus all prompts across the full category — advanced workflows, specialized use cases, and production-grade templates.
Category Bundle — one-time access
Unlock Category Prompts — $19.99ONE-TIME · 30-DAY GUARANTEE · INSTANT ACCESS
The most common mistake is trying to write down steps after you've finished the task. Memory is unreliable — you'll forget the small steps that feel automatic to you but would confuse a newcomer. Keep the Google Doc open in a separate tab while you work and paste each step immediately after you do it. The "oh wait, I should have done X first" corrections are especially valuable because they reveal the order that's not obvious.
When you almost click the wrong button, note it. When you have to undo something, note it. When you remember a gotcha just in time, note it. These near-misses become the troubleshooting section — they predict exactly what a new person will get wrong because you almost got it wrong too. In testing, SOPs built from notes that included mistakes produced troubleshooting sections that were 3x more accurate than SOPs built from clean, idealized process descriptions.
The single most impactful formatting choice in an SOP is bolding every button name, menu path, and specific command. When a reader is scanning for "what do I click?", bold text is what their eye catches. "Click Content → Pages → New Post and select the Blog Template" is instantly scannable. "Click Content, then Pages, then New Post and select Blog Template" forces the reader to parse the entire sentence to find the action words.
Before sending an SOP to your entire team, have one person follow it without any additional guidance from you. Watch where they hesitate, ask questions, or make errors. Those friction points reveal gaps that neither NotebookLM nor Claude caught because both tools were working from your perspective, not a newcomer's. One test run typically reveals 2–3 critical gaps that would have generated support messages from every subsequent reader.
SOPs decay just like any other content. Tools update their interfaces, processes change, and new edge cases emerge. The beauty of the messy-notes approach is that updates are nearly free: when a workflow changes, update your running Google Doc the next time you perform the task. Then re-upload to NotebookLM and re-run the pipeline. The entire refresh takes under 10 minutes because you're not rewriting a polished document — you're feeding updated raw notes into the same automated pipeline that built the original.
For teams managing 20+ SOPs, set a quarterly review reminder. Pull up each SOP, scan for outdated tool names or changed interfaces, and flag the ones that need a refresh. Then batch-process the flagged SOPs through the pipeline in a single session. A library of 30 SOPs can be audited and refreshed in under 3 hours per quarter — a fraction of what it would take to maintain them manually.
This workflow works best for repeatable operational tasks: client onboarding, content publishing, invoice processing, data entry, software deployment, social media scheduling, and similar procedures. It works less well for tasks that require heavy judgment calls or creative decision-making, where the "right" approach varies significantly by context. For those tasks, an SOP can document the framework and decision criteria, but it can't replace experience.
NotebookLM's source-grounding means it will only include steps that appear in your uploaded notes. If your notes are incomplete, the SOP will be incomplete. The Claude stress-test (Step 3) catches many gaps, but it's reasoning about what should be there, not what your actual workflow includes. The most reliable SOPs come from notes that were captured in real time during the actual task.
The SOP deck format (5 slides) is a starting point. Simple tasks may need only 3 slides. Complex tasks with multiple branches may need 7–8. The premium prompts include templates for extended SOPs, conditional branching procedures, and multi-role workflows that go beyond the basic 5-slide structure.
A Standard Operating Procedure is a step-by-step document that explains how to complete a specific task the same way every time. Most small teams and freelancers skip writing SOPs because the documentation process takes longer than just explaining the task on a call. This workflow eliminates that friction by converting raw messy notes into structured SOPs using NotebookLM and Claude. The documentation happens as a byproduct of doing the work — adding approximately zero extra time to the capture phase and 15–25 minutes for the AI-powered structuring and refinement.
NotebookLM generates structured text output from your uploaded sources. The SOP deck prompt in this guide produces a clean 5-slide structure — prerequisites, three execution slides with bolded commands, and troubleshooting — that maps directly to a presentation format. You can paste this output into Google Slides, PowerPoint, or Canva for a visual training deck, or export it as formatted text for a PDF. NotebookLM doesn't generate .pptx files directly, but the structured output is designed to transfer into any slide tool with minimal reformatting.
NotebookLM excels at extracting structured procedures from messy, unorganized notes because it grounds every instruction to your uploaded source material — it won't invent steps you didn't mention. Claude excels at stress-testing those procedures by reasoning about what a newcomer would need, finding ambiguous phrasing, identifying missing decision points, and generating troubleshooting content for errors you didn't anticipate. Together they produce SOPs that are both faithful to your actual workflow and robust enough for someone who has never done the task.
The full pipeline takes 15–25 minutes per SOP, compared to 1–3 hours for writing one manually. The capture phase adds zero time because you're pasting notes as a byproduct of doing the work. The NotebookLM generation takes 2–3 minutes. The Claude refinement takes 10–15 minutes. The result is a polished training document that replaces a 30–60 minute onboarding call — and unlike the call, it's reusable with every subsequent person who needs the same training.
This workflow works best for repeatable operational tasks: client onboarding sequences, content publishing workflows, data entry procedures, software deployment steps, invoice processing, social media scheduling, email campaign setup, CRM data management, and any task you find yourself explaining to a new person more than twice. It works less well for tasks requiring heavy creative judgment or where the "right" approach varies significantly by context — for those, the SOP can document the decision framework and criteria, but it can't replace the experience that informs good judgment.
The messy-notes approach makes updates nearly free. When a workflow changes, update your running Google Doc the next time you perform the task, then re-upload to NotebookLM and re-run the SOP deck prompt. The entire refresh takes under 10 minutes. For larger SOP libraries, set a quarterly review reminder and batch-process any outdated SOPs through the pipeline in a single session. A library of 30 SOPs can be audited and refreshed in under 3 hours per quarter.