Document Change Request (DCR) Intake & Routing

The problem this kills

Change requests for your controlled documents show up everywhere except where you can track them: a hallway conversation, a sticky note on a monitor, a "hey can you fix the SOP" email that gets buried, a comment scrawled in the margin of a printout. By the time an auditor asks "how do you handle requests to change documents?" you are reconstructing a paper trail that never really existed.

The result is predictable. The same problem gets reported three times because nobody knows it was already raised. A genuinely important change sits for weeks because it never reached the document owner. And when a document finally does get revised, there is no clean link back to why - no record of who asked, what was wrong, or who approved the work.

This tool replaces the sticky notes with one front door: a simple form anyone can fill in, that always reaches the right people, always gets a decision, and always leaves an audit trail.

What you'll build

A small, login-protected web app that does five things well:

• Intake. Anyone on your team picks the controlled document from your own document list and submits a change request - what's wrong, the proposed change, the reason, and how urgent it is.
• Routing. Each request is automatically routed to that document's owner and to document control for a decision.
• The decision gate. The owner or document control reviews each request and accepts, defers, or rejects it - with a required reason. Nothing moves to revision work until a human says so.
• Revision tracking. Accepted requests turn into a tracked revision item, tied to the document number, so you can see what changes are in flight.
• Closing the loop. The requester automatically gets an email with the decision, and you can export the entire DCR log as a CSV that matches the change-request log you already keep.

What's inside the Implementation Plan

The plan is a single file you paste into an AI coding assistant (Claude Code), and it builds the tool with you step by step - no prior coding needed.

It starts by interviewing you about your business. Before it writes a single line, the plan has the AI ask you about your real document-control process: how your document numbers are formatted, who owns what, how you currently log change requests, what "urgent" means to you, and the messy exceptions you deal with. It reads back a short tailored spec, you give it a thumbs-up, and only then does it build - so you get a tool shaped around your process, not a generic template you have to bend to fit.

From there the plan walks you through: setting up your accounts, loading your controlled-document list, building the intake form, wiring up routing and the approve/defer/reject gate, turning accepted requests into revision items, sending status emails through Resend, and exporting your DCR log as a CSV.

The governance it includes (this is the point)

This is not a toy form. The plan builds in the controls a quality or document-control team actually needs:

• Login so only your team can see or file requests.
• Row-level security so people only ever see your organization's data, enforced by the database itself.
• A complete audit trail - who submitted, who decided, what they decided, and when.
• A hard human-in-the-loop gate - the AI never authorizes a revision on its own; a person must accept it first.
• Duplicate guards so the same open issue can't be filed twice against the same document, and every request carries a unique DCR ID.

Who it's for

Document controllers and quality teams who are tired of chasing change requests across hallway conversations, sticky notes, and buried emails - and who want one auditable front door for "this document needs to change," without waiting on IT or a six-figure QMS module.

You've got this - paste the first prompt and let the interview tailor it to your shop.