SOP Version Control & Change Log: Know What Changed, When, and Who Signed Off
Turn your SOP library into a real change-control system — draft to review to approved to published to superseded — with an AI-written summary of what changed between versions and a permanent record of every approval.
A web tool where you draft a new SOP revision, AI summarizes exactly what changed versus the current version, your reviewer and approver sign off in order, and only then does the version publish, become effective-dated, supersede the prior version, and update the change log — with full history kept forever and a CSV export of every version.
Before you start
- A Supabase account (free)
- A Vercel account (free)
- A Resend account (free)
- Your current SOPs (docs, PDFs, or a spreadsheet of revisions)
- Your review/approval roles and workflow
- Claude Code or any AI coding agent
The problem this kills
You have an SOP library, and you have no idea which copy is the real one. There's "Onboarding_SOP_v3_FINAL.docx," and "Onboarding_SOP_v3_FINAL_revised.docx," and the one in the shared drive that someone edited last Tuesday without telling anyone. When an auditor asks "what version was in effect on March 1st, and who approved it?" the honest answer is a shrug and forty-five minutes of digging through email.
Real change control on procedures isn't a nice-to-have for quality, ISO, and GxP shops — it's the whole game. You need every revision kept forever, a clear status for each (draft, in review, approved, published, superseded), a human-readable record of what actually changed between any two versions, and a signed-off approval on file for every release. Doing that by hand in Word and a tracking spreadsheet is how versions get lost and the wrong procedure ends up on the floor. You don't need a six-figure document-management system to fix this, and you don't need to be a developer.
What you'll build
A simple internal web tool that treats every SOP like a controlled document. You create a new draft of an SOP — paste or upload the revised content and the reason for the change. The tool pulls the current published version and asks the AI to write a plain-English "what changed" summary: added steps, removed steps, reworded responsibilities, changed forms. That draft enters its defined approval workflow — a reviewer signs off, then an approver signs off, in order. Only when the last sign-off lands does the version publish: it gets an effective date (today or future-dated), the prior version is automatically superseded and archived (never deleted), the version number ticks up in strict sequence, and the change log updates. You can compare any two versions side by side, and you can export the full version history to CSV any time.
What's inside the Implementation Plan
The downloadable plan is a step-by-step file you paste into an AI coding agent. It opens by interviewing you about your business — how you manage SOPs today, where they live, your exact version-numbering scheme, your review-then-approve roles and any second-approver rules, whether you future-date effective dates, your typical and peak revision volume, and the messy edge cases like emergency changes and parallel drafts — and then it tailors the data model, the workflow states, and every later step to your answers. This is not a generic template; the agent reads a short spec back to you and waits for your thumbs-up before it builds anything. From there it walks the agent through importing your existing SOPs, building the draft-and-diff flow, the AI change summary, the reviewer/approver sign-off gate, the publish-and-supersede logic, the change log, and the CSV export — each step with a ready-to-copy prompt. There's also a fallback so you can build and run the whole thing today, even with no integration to your document system.
The governance it includes (this is the point)
This is real change-control tooling, so it ships with the controls a quality team needs: login so only your team can use it, row-level security so you only ever see your own organization's SOPs, a complete audit trail of who drafted, reviewed, approved, and published each version and when, a hard human-approval gate so no version becomes effective until the reviewer and the approver have signed off in order, and duplicate guards keyed on SOP ID plus version number so you can never publish two of the same version or skip a number. Prior versions are superseded and archived, never lost, so the full lineage of every procedure is intact for any audit.
Who it's for
Quality managers, document-control owners, and operations leads who are accountable for procedures under ISO, GxP, or any audit regime — and anyone tired of guessing which SOP is current. If you can describe how a procedure gets reviewed and approved in your shop, you can build this.
You've got this — start with the plan, paste the first prompt, answer the interview, and you'll watch your first controlled SOP move from draft to published the same afternoon.