Risk and score
The trust score is a Beta surface. The page shows the score recorded for your company when one exists. On a new account it shows "Trust score not computed yet". Nothing on this page needs action from you yet.
The Risk & Score page is where your supplier trust score appears. The trust score is a single rating, with supporting sub-scores, that summarises how a customer views your compliance and responsiveness as a supplier.

Risk and score.
What you see today
- Trust score not computed yet. On a new account, the page explains that a score has not been calculated for your organisation yet.
- Where a score is present, it shows an overall score with a rating badge, plus sub-scores for compliance, responsiveness, and verification rate.
- Score trend. A dedicated section plots your score over time as a sparkline, with a total-delta readout of how far it has moved. Until at least two scoring cycles have been recorded there is nothing to plot, and the section says so: "No score history yet, your monthly trend appears here once your customers have run a couple of scoring cycles." Nothing is wrong with your account if you see that.
- Roadmap describing what is coming next, including an AI risk explainer and remediation playbook, and peer benchmarking.
Score drivers and risk factors
The page says your trust posture is computed by your customers from responsiveness, completeness, evidence coverage and verifier attestations.
When a score exists, the page also shows Score drivers (Timeliness, Completeness, Evidence coverage, Geographic risk and Verifier attestation, each with a value and a weight) and a Risk factors list with severity and status. When there is no data, the Risk factors card reads "No active risk factors."
What you can do now
While the score is in Beta, you can keep your compliance data current:
- Respond to data requests promptly. See Respond to a request.
- Keep certificates up to date. See Certificates.
- Maintain your evidence vault and materials. See Evidence vault.
We will announce changes to this page in the changelog.