Recall / Safety Notice Coordinator

The problem this kills

A recall is one of the few moments where ops precision is not optional. Notify too few customers and you have an unreported safety gap. Notify too many and you spook people who were never affected, flood support, and erode trust. Most teams run this from a frantically filtered spreadsheet, a mail-merge, and a second spreadsheet to track who replied - with no record of who decided the list was right, what the notice actually said, or who is still unaccounted for.

When the auditor or regulator asks "show me exactly who you notified, when, what you told them, and who confirmed they got it," that pile of spreadsheets and sent-mail folders is not an answer. You need the recall to be auditable end to end, by design.

What you'll build

A small internal web app, built for how your business actually runs, that:

• Lets you define a recall scope - the affected SKUs, lots, or serial ranges - in plain terms.
• Pulls the affected-customer list straight from your sales or registration data, matching on exactly the SKU / lot / serial conventions you use.
• Holds that list and the notice wording at a compliance approval gate - nothing goes out until a lead reviews and approves both.
• Sends the safety notice to approved customers through Resend.
• Tracks acknowledgements and remediation - who confirmed, who still needs a reminder, what fix or return was completed.
• Produces a full audit export for compliance: who was on the list, who approved it, what was sent, and who responded.

What's inside the Implementation Plan

The plan is a single file you paste into Claude Code (an AI coding agent). It builds the whole tool with you, step by step, and each step ends with a ready-to-copy prompt.

The most important part: the plan opens by interviewing you about your business. Before it writes a line of code, it asks how your sales/registration data is shaped, how you write SKU / lot / serial codes, what your typical and peak recall volumes look like, who the compliance approver is, and the messy edge cases (refurbished units, resellers, lots that span date ranges, customers with several affected items). It reads a short tailored spec back to you, waits for your thumbs-up, and only then builds - so you get a tool fit to your data, not a generic template you have to fight.

You'll also get a complete CSV fallback: if you have no live connection to your system of record, the tool imports a Sheet/CSV and exports the affected list and acknowledgement log in clean columns - so it is fully buildable today.

The governance it includes (this is the point)

This tool is built to survive an audit:

• Login so only your team can use it.
• Row-level security so each organization only ever sees its own customers and recalls.
• A complete audit trail - who entered the scope, who approved the list, what was sent, and when.
• A hard human-in-the-loop approval gate - the tool drafts the affected list and the notice; a compliance lead reviews and approves both; only then does anything get sent. Precision is enforced, not hoped for.
• Duplicate guards so the same customer can't be double-notified for the same recall (dedupe key = customer + recall ID).

Who it's for

Quality and compliance leads, and support-operations people, who run product safety notices and recalls and need them to be precise, accountable, and fully documented - without waiting on engineering to build it.

You've got this - paste the first prompt and let the agent interview you.