Supplier Diversity & Classification Tracker: Diverse-Spend Numbers You Can Trust

The problem this kills

Someone up the chain asks for your diverse spend — what percentage went to minority-, women-, and veteran-owned businesses, or to small businesses — and your honest answer is a spreadsheet you don't trust. Classifications were typed in years ago by whoever onboarded the supplier. Half the certificates have expired. A few suppliers self-claimed a status no one ever checked. The certifying bodies are a jumble of acronyms, and at least one "certificate" is a screenshot that could be anything.

So you spend a week reconstructing the number, hedge it when you report it, and quietly worry that an auditor or a customer could pick it apart. Diverse-spend reporting fails when nothing connects a verified, in-date certificate to actual spend. You don't need a six-figure compliance platform to fix that, and you don't need to be a developer.

What you'll build

A simple internal web tool. Suppliers (or your team on their behalf) submit classification claims — the diversity type, the certifying body, the certificate number, the expiry date — and upload the certificate file. A program owner opens a verification queue and checks each one: is the certifying body legitimate, is the certificate in date, does the name and number on it actually match the supplier? Only when they click Approve does that classification become trusted.

Then you import your spend-by-supplier export, the tool joins it to the approved, in-date classifications, and out comes a diverse-spend report by category and period — total spend, diverse spend, and the percentage, broken down by classification type. Certificates nearing expiry trigger email alerts so your numbers don't quietly rot, and everything exports to CSV in the columns your reporting needs.

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 classification types and certifying bodies you recognize, exactly how your spend export is shaped and how suppliers are keyed in it, your typical and peak supplier counts, who is allowed to verify a certificate, and the messy edge cases (expired certs, self-claims with no document, one supplier holding several classifications) — and then it tailors the data model, the validations, and every later step to your answers. This is not a generic template; the agent reads a short spec back to you and waits for your thumbs-up before it builds anything. From there it walks the agent through certificate capture and Storage, the verification-and-approve queue, the spend join, the diverse-spend report, expiry alerts, and the 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 API to your ERP.

The governance it includes (this is the point)

This is reportable, sometimes audited data, so it ships with the controls a procurement team needs: login so only your team can use it, row-level security so you only ever see your own organization's suppliers and certificates, a complete audit trail of who verified and approved which classification and when, a hard human-verification gate so a classification never counts toward diverse spend until a program owner has checked the certificate and signed off, and duplicate guards keyed on supplier + classification type + certifying body so the same status can't be entered twice. Self-claims with no valid in-date certificate simply don't count — which is exactly what makes the final number defensible.

Who it's for

Procurement leads and supplier-diversity program owners who get asked for diverse-spend numbers and have nothing reliable to hand over. If you can describe which classifications you track and how your spend export is laid out, you can build this.

You've got this — start with the plan, paste the first prompt, answer the interview, and you'll watch your first trustworthy diverse-spend report come together the same afternoon.