SOP Draft Generator from a Walkthrough

The problem this kills

Your most experienced people carry the real procedures in their heads. The "how we actually do it" lives in tribal knowledge - and it walks out the door when someone retires, quits, or moves teams. Writing it down is the part everyone dreads: it's slow, the formatting is inconsistent, and half-finished drafts rot in a shared drive.

So the knowledge never gets captured properly. New hires shadow whoever's free, every SOP looks different, and the steps that matter most - the safety warnings, the gotchas, the "don't ever do this" notes - are exactly the ones that get left out.

What you'll build

An internal web tool where an employee pastes or uploads a recording transcript, voice-to-text, or rough notes of how they do a task. The AI reads it and drafts a structured SOP in your house template: purpose, scope, materials/systems needed, numbered steps, warnings and cautions, and a revision block.

Then a human takes over. The process owner reviews the draft, edits anything that's wrong, and approves it. Only an approved SOP gets saved as a draft-of-record with an author and a version number, ready to hand to your library or approval flow. The original transcript stays linked to the SOP for provenance, so anyone can trace a step back to where it came from.

What's inside the Implementation Plan

The plan is a complete, paste-and-go runbook for an AI coding agent (Claude Code). You don't write code - you paste, answer questions, and review.

It opens by interviewing you about your business - your current process for capturing procedures, the SOP template and fields you already use, your role/department naming, your typical and peak volume of new SOPs, and your exact approval rules and edge cases. It reflects a short tailored spec back to you for a thumbs-up, then shapes the data model, the SOP template, and every later step around your answers. You get a tool fitted to how you actually work, not a generic template.

From there it walks the agent through building the database, the login, the draft-from-walkthrough screen, the AI drafting step, the human review-and-approve gate, versioning, and the Markdown/CSV export - each step ending in a ready-to-copy prompt.

The governance it includes (this is the point)

This isn't a toy. The plan builds in the controls that make a tool trustworthy enough for real procedures:

• Login so only your team can use it.
• Row-level security so people only ever see their own organization's SOPs.
• A complete audit trail - who drafted, who edited, who approved, and when.
• A hard human-in-the-loop approval gate - the AI only ever drafts; nothing becomes a draft-of-record or gets published until a process owner reviews and approves it.
• Duplicate guards so the same task can't quietly create two competing SOPs (deduped on task title + department + draft version).
• Quality flags - the AI marks steps that are vague or missing safety notes so the owner can fix them before approval.

Who it's for

Ops and BPM people who need to capture tribal knowledge from experienced staff before it walks out the door - and want every captured SOP to land in the same clean, reviewed, versioned shape.

You've got this. Paste the first prompt and let the agent interview you.