CAPA Intake & Triage Hub: One On-Ramp for Every Quality Problem
Capture potential CAPAs from any source — audit findings, customer complaints, incidents, internal ideas — and triage each one (full CAPA or quick correction?) with risk, owner, and CAPA number, while your quality manager approves before any record is opened.
A web tool where anyone can log a quality problem from any source, AI proposes whether it needs a full CAPA or just a correction plus a risk level and an owner, your quality manager reviews and approves, and only then does the tool open a numbered CAPA record, email the assignment via Resend, and export a clean CAPA intake log CSV.
Before you start
- A Supabase account (free)
- A Vercel account (free)
- A Resend account (free)
- Your existing problem sources (complaints, audit findings, incident reports) as a CSV/Sheet or manual entry
- Your triage rules (when a full CAPA is required vs a correction)
- Claude Code or any AI coding agent
The problem this kills
Quality problems arrive from everywhere — an auditor's finding, a customer complaint, a near-miss on the floor, a "hey, we should fix this" email — and they land in different places: one spreadsheet, three inboxes, a sticky note, the back of someone's mind. There's no single front door. So things slip. The same root issue gets two CAPAs opened by two people who didn't know about each other. A real problem gets logged as a "quick fix" because nobody applied the risk rule consistently. An auditor asks "show me how you triage" and you have no clean answer.
The triage decision itself is the hard part: is this a full CAPA (investigate the root cause, fix it, prove it stays fixed) or just a correction (clean it up and move on)? Who owns it? How risky is it? Today that judgment lives in one person's head and a tangle of spreadsheets. You don't need to live like this, and you don't need to be a developer to fix it.
What you'll build
A single internal web tool that is the one on-ramp for every quality problem. Anyone on your team logs a problem — picking the source (audit finding, complaint, incident, internal idea) and pasting the source reference — or you bulk-import a backlog from a CSV/Sheet. For each one the tool proposes a triage decision: full CAPA vs correction, a risk level, and a suggested owner, all driven by the rules you give it. It checks for duplicates so the same root issue can't spawn two CAPAs. Your quality manager opens the triage queue, reviews each proposed decision, adjusts it, and clicks Approve. Only then does the tool open a CAPA record with a real CAPA number, link it back to its source, email the assignment to the owner via Resend, and add the decision (with rationale) to an exportable CAPA intake log.
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 — which sources your problems come from, how you reference them, exactly what your CAPA numbering looks like, your real risk levels and the rules that drive them, when a full CAPA is required versus a correction, who can own a CAPA, your typical and peak volumes, and your messy edge cases — and then it tailors the data model, the triage logic, and every later step to your answers. This is not a generic template; the agent reflects a short spec back to you and waits for your thumbs-up before it builds anything. From there it walks the agent through intake from every source, the dedupe guard, the AI triage proposal, the quality-manager review-and-approve queue, CAPA-number assignment, the Resend assignment email, and the intake-log CSV export — each step with a ready-to-copy prompt. There's also a fallback so you can build the whole thing today even with no integration to your existing QMS.
The governance it includes (this is the point)
This is real quality-system tooling, so it ships with the controls an audited team needs: login so only your team can use it, row-level security so you only ever see your own organization's records, a complete audit trail of who logged, triaged, approved, and assigned each problem and when, a hard human-approval gate so no CAPA is ever opened until the quality manager signs off on the triage decision, and duplicate guards keyed on the source reference plus the issue so the same root problem can't be opened twice. Every triage decision stores its rationale, so when an auditor asks how you decided, the answer is right there.
Who it's for
Quality managers and compliance leads who own CAPA and are tired of chasing problems across scattered spreadsheets and inboxes. If you can describe how you decide what becomes a CAPA versus a quick correction, you can build this.
You've got this — start with the plan, paste the first prompt, answer the interview, and you'll see your triage queue take shape the same afternoon.