Risk-banded watchlist
Low / medium / high. Sorted by risk_score desc. Open findings + expiring soon visible at a glance.
Per-supplier scorecards, expiring-cert dashboards, and predictive recall risk scoring - built on the same row-level-secure database as your document repository.

Every supplier gets a risk score: open findings, expiring certs, fraud signals, prior reject rate. The watchlist sorts the red band to the top so your Monday morning starts at the right supplier instead of the most recent email.
When a supplier slides from low to medium risk, you generate a tokenised link, the supplier renews, the validation engine cites the BRCGS clause that failed, and the score recovers - all without leaving the platform.
Low / medium / high. Sorted by risk_score desc. Open findings + expiring soon visible at a glance.
Predictive scoring of which docs are most likely to lapse. Probability per doc, days remaining.
Combines fraud score, validation findings, supplier history. Sortable, exportable, action-driven.
Time-boxed read-only invites. Auditors see only the docs in their engagement window. Citations on every NL answer.

Your repository, sortable by risk ยท expiring soon ยท supplier ยท folder. Filtering is instant - Postgres does the work.
Every supplier ranked low / medium / high. Open findings, expiring soon, last upload date - all on one dashboard. Sorted by score, descending.
Predictive scoring of which documents are most likely to lapse before renewal. Probability per doc, days remaining, and the supplier responsible.
ML model combines document signals (fraud score, validation findings, supplier history) into a per-document recall risk. Sortable, exportable.
Time-boxed read-only invites. Auditors see only the documents in their engagement window. NL queries answered with citations to the source documents.
Rule-engine check that every raw material has a current CoA from an approved supplier. Lapses raise a finding, not a silent miss.
Send a single email - supplier clicks, drops the requested documents, never sees a login screen. Tokens are race-safe and use-bounded.
Toggle Broken CoA โ hit Validate. Every failing rule cites the BRCGS or SQF clause and the offending field. That is what your supplier sees in their rejection email.
Hit Validate to run the rule engine.
Supplier watchlist sorted by risk_score desc. Three suppliers in the red band. One has 4 open findings, one expires in 7 days.
/suppliersGenerate tokenized upload links for the two suppliers needing renewal. Token URL emailed with the expiring document type pre-selected.
POST /supplier-upload-linksNew CoAs land in the queue. Auto-validated against BRCGS rules - 2 pass, 1 fails on signed=false. Supplier notified with the failing clause.
apps/validation/External auditor pings on the Tracegence portal: "Show me CoAs from Supplier X with allergen findings in 2026." NL query, answered with citations.
POST /auditor/queriesCompliance score recomputed nightly. Export this week's history to CSV. Ship the score to your buyer.
GET /score/historySend one tokenized link and watch the validation engine cite every BRCGS clause that fails.