Skip to content
ToolDeck

Productivity & Team Ops

SOP Generator

Process demos and docs become a written SOP your team can actually follow.

Saves about ~2 hrs per week

What it does

  • Takes process notes or short recordings of how you do things
  • Drafts a step-by-step SOP with owners and tools
  • Adds the 'gotchas' only you know
  • Outputs a review-ready SOP document

How it works

  1. Process source provided
  2. Steps extracted and ordered
  3. Gotchas and owners added
  4. SOP doc generated for review

What's included

  • Process capture
  • SOP drafting prompt
  • Review + library

Set it up yourself

Follow these 4 steps in order. You will need accounts for: Claude.

Step 1: Capture the process

  1. Provide the source: paste your notes, or upload a screen recording / Loom transcript of the process.
  2. For recordings, transcribe first.
  3. Add the tools used at each step if known.
  4. Upload to the workflow.
  5. Test the source ingestion.

Watch out: A clear recording is worth a thousand notes — the transcription + AI can turn a 3-minute recording into the skeleton of a solid SOP.

Step 2: Add the SOP prompt

  1. Build: 'Turn this into a step-by-step SOP. Structure: title, purpose, when to use, prerequisites, numbered steps (with tools), owners, and a 'gotchas' section for edge cases. Under 500 words.'
  2. Instruct to note where judgment is needed.
  3. Paste with API key.
  4. Test on one real process.
  5. Check the gotchas match reality.

Watch out: The gotchas section is where SOPs gain their weight — 'step 4 fails if done on a Friday' is the kind of thing that turns a document into the team's actual reference.

Step 3: Add owners and checks

  1. Assign a reviewer per SOP (who knows the process).
  2. Have the draft flag 'verify with the owner' sections.
  3. Create the doc in your knowledge base on approval.
  4. Test the review loop.
  5. Keep review fast (a 'strongly agree' form is enough).

Watch out: The review step is non-negotiable — an SOP generated and auto-published without owner review is how wrong processes get institutionalized.

Step 4: Maintain the library

  1. Keep SOPs in one KB location.
  2. Version them (date + owner).
  3. Schedule 6-month reviews of the SOP list.
  4. When a process changes, regenerate from the new recording.
  5. Track which SOPs get referenced.

Watch out: Track which SOPs are actually opened — an SOP library nobody reads is a museum; the usage data tells you what needs rewriting in shorter form.

Frequently asked questions

What does the SOP Generator automation do?

Process demos and docs become a written SOP your team can actually follow. Takes process notes or short recordings of how you do things

How much time does SOP Generator save?

It is estimated to save ~2 hrs per week. Actual savings depend on your volume.

Which tools does SOP Generator use?

It works with Claude.

What does SOP Generator include?

Process capture, SOP drafting prompt, Review + library.

Can I set up SOP Generator myself?

Yes. The do-it-yourself guide on this page walks through 4 steps, from getting access to testing the finished automation.