SOP Library with Search & Ownership

The problem this kills

Your procedures live in seventeen places. There's a shared drive with SOP_final_v2_REALfinal.docx, a folder someone made in 2021, a few PDFs in email, and a wiki nobody updates. When a new hire asks "what's the current way to do this?" the honest answer is "let me ask around." Auditors love that. So do mistakes.

The real pain isn't that the documents don't exist - it's that nobody can tell which version is current, who owns it, or when it was last reviewed. Duplicates pile up. Out-of-date steps get followed. The one person who knew the answer left.

This Implementation Plan kills that. You build a single, searchable home for every SOP, where exactly one version is ever marked "current," every procedure has a named owner and a next-review date, and finding the right one takes a keyword - not a scavenger hunt.

What you'll build

A private web app for your team where:

• Every SOP has an owner, department, tags, effective date, and next-review date.
• Staff search by keyword or browse by category and instantly open the current version.
• An SOP only becomes "current" after its owner reviews and approves it - the AI can draft and tag, but a person signs off.
• Superseding an SOP requires owner approval and automatically archives the old version - you keep the full history but only ever show one current copy.
• Every view is logged (who opened what, and when) and review dates are tracked so nothing silently goes stale.
• You can export the whole SOP index to CSV any time.

What's inside the Implementation Plan

The plan is a single file you paste into Claude Code (a free AI coding assistant that writes and runs the software for you). It walks the AI through building the whole app, step by step, ending each step with a ready-to-copy prompt.

Crucially, the plan opens by interviewing you about your business - your departments, how you name and number SOPs, who approves what, your review cadence, and your messy edge cases. It uses your answers to shape the data model and the rules, so you get a library tailored to how you actually work, not a generic template you have to bend yourself into.

Inside you'll find: the discovery interview, the database design with row-level security, the owner-approval workflow, full-text search across titles, bodies, and tags, the version/supersede logic, view logging, review-date tracking, the CSV export, and a "no API yet?" path that imports your SOPs from a Google Sheet or Drive so you can build this today.

The governance it includes (this is the point)

This isn't a toy. The plan bakes in the controls that make a tool safe to run a real operation on:

• Login so only your team can get in.
• Row-level security so people only ever see their own organization's SOPs.
• A complete audit trail - who approved, who superseded, who viewed, and when.
• A hard human approval gate before any SOP is marked "current" - the AI drafts and tags, the owner reviews and approves, and only then does it publish.
• Duplicate guards so the same SOP ID + version can't be published twice, and only one version per SOP ID is ever "current."

Who it's for

Ops and quality managers, team leads, and enablement folks who are drowning in scattered, duplicate, out-of-date procedure docs and want a single source of truth they - and their auditors - can trust. You don't need to know how to code. You need to know your process; the AI handles the building.

You've got this - paste the first prompt and let the interview tailor the rest.