SOP Freshness Auditor

The problem this kills

You suspect half your procedures are out of date - but you have no systematic way to prove it. SOPs reference systems you retired two years ago. Owners have left the company. Two slightly different versions of "Onboard a New Vendor" both float around. Nobody has looked at the "Quarterly Close" doc since the last reorg.

The result: people stop trusting the library, so they stop using it, so it rots faster. And every audit, every onboarding, every "wait, is this still how we do it?" moment costs you time and credibility.

You don't need a six-figure GRC platform to fix this. You need a tool that reads your SOP index, applies your freshness rules, and hands you a ranked cleanup list with one-click reminders to the people who own each doc.

What you'll build

A small, private web app - for your team only - that:

• Loads your SOP index (owner, effective date, review date, last-viewed date, tags, content).
• Applies freshness rules you choose: past review date, no owner, not viewed in a year, references a retired system or role, duplicate titles.
• Flags every problem and ranks the list by severity so you fix the worst first.
• Lets the library owner review each finding and approve a disposition - keep, revise, retire, or reassign - before anything changes. Nothing is ever auto-deleted.
• Emails reminders to the SOP owners who need to act, and lets owners snooze with a reason.
• Records every decision in an audit trail and exports the whole audit as a clean CSV.

What's inside the Implementation Plan

The plan is a single markdown file you paste into an AI coding agent (Claude Code). It builds the whole tool with you, step by step, in plain language.

It opens by interviewing you about your business - your current SOP process, where your index lives, how your docs are named and tagged, your real review cadences, and your messy exceptions. It then reflects a short tailored spec back to you and waits for your thumbs-up. That means you get a tool shaped around your library and your freshness rules - not a generic template you have to bend to fit.

From there it walks you through: setting up the database, building the login, importing your index, coding the freshness rules, the human review screen, owner reminders, the audit trail, and the CSV export - each step ending with a ready-to-paste prompt.

The governance it includes (this is the point)

This isn't a throwaway script. It's built like an internal tool that an auditor would respect:

• Login so only your team can open it.
• Row-level security so each organization only ever sees its own SOPs.
• A complete audit trail - who flagged what, who approved which disposition, and when.
• A hard human-in-the-loop gate - the tool drafts findings and proposed dispositions; a person reviews and approves before any SOP is marked retired or reassigned.
• Duplicate guards so the same SOP can't be double-counted and the same audit run can't be processed twice.

Who it's for

Ops and quality managers who own a growing SOP or playbook library and quietly suspect a big chunk of it is stale - but have no systematic, defensible way to find the rot and clean it up.

You've got this. Make a folder, start your agent, and paste the first prompt.