BOM Revision Diff & Sign-Off
Upload two revisions of a bill of materials, get a plain-English change report (parts added, removed, quantity changed, designators moved), and route it through a reviewer-plus-approver sign-off before the new revision is marked released.
A private internal tool where engineering uploads rev A and rev B of the same assembly, sees a line-by-line diff with qty-only changes separated from structural changes, and a change owner plus an approver electronically sign off before the BOM is released - with a full audit trail.
Before you start
- A free Supabase account
- A free Vercel account
- A free Resend account
- Two BOM exports (old revision + new revision) as CSV or Google Sheet
The problem this kills
A bill of materials changes constantly: someone swaps a resistor, bumps a quantity, moves a part to a different reference designator, or drops a line item that turns out to be load-bearing. The change looks tiny in the engineering tool. Then the build floor uses it, and a "silent" change quietly breaks an assembly, scraps a run, or fails inspection - and nobody can say exactly what changed between revisions or who approved it.
Most teams "diff" two BOM revisions by eyeballing two spreadsheets side by side, or by trusting that whoever edited the file remembered to tell everyone. That is how a single wrong quantity ships.
What you'll build
A small, private web app where engineering uploads two exports of the same assembly - the old revision and the new revision - and instantly sees a clear, line-by-line change report: parts added, parts removed, quantity changed, and reference designators moved. Quantity-only changes are kept visually separate from structural changes (added/removed parts), because those carry very different build risk. The change owner reviews the diff, an approver signs off electronically, and only then is the new revision marked released - with a downloadable change record and released BOM.
What's inside the Implementation Plan
The plan opens by interviewing you about your business - your BOM exports, your SKU and reference-designator conventions, your revision scheme, your approval rules, and your messy edge cases - so the tool is tailored to how you actually work, not a generic template. It reads a short spec back to you for a thumbs-up before it builds anything.
Then it walks your AI agent through the whole build step by step: the data model for assemblies, revisions, and line items; the matching logic (match lines by child SKU + find number); the diff engine that classifies every line as added / removed / qty-changed / designator-moved; the plain-English summary; the reviewer-and-approver sign-off gate; and the change-record and released-BOM exports. Every step ends with a copy-ready prompt you paste into the agent.
The governance it includes (this is the point)
- Login so only your team can open the tool.
- Row-level security so people only ever see their own organization's assemblies and revisions.
- A human-in-the-loop sign-off gate: the diff is drafted automatically, but a change owner reviews it and an approver electronically signs off before the revision is marked released. Nothing releases itself.
- A complete audit trail: who uploaded, who reviewed, who approved, and exactly when.
- Duplicate guards: the same comparison can't be processed twice - the dedupe key is assembly + from-revision + to-revision.
Who it's for
Manufacturing engineers, document and change controllers, and quality engineers who own BOMs and need to prove what changed between two revisions - and that the right people signed off - before a build uses the new revision.
You've got this. Open the Implementation Plan and paste the first prompt into your AI agent.