Checking a result
Can this result be checked?
A report can be copied and a number can be changed. Every result carries a reference, so a recipient can check its authenticity without seeing information the company has not chosen to share. The register and verification endpoint are live; results issued before launch have been given references retroactively.
The register: how to check a result
A shared result is useful only if a recipient can check what it represents. The register provides a short reference, similar to a certificate number, without exposing the underlying answers.
| Step | What happens |
|---|---|
| 1. A result gets a reference | Every assessment completed through a conforming implementation is recorded with a short reference, printed on the report. For example GS-4K2P-9QX7 |
| 2. The company shares it | The company decides who sees the report and who gets the reference. Nothing is shared by us without them choosing it |
| 3. The recipient checks it | A funder, investor or procurement team enters the reference, or their system calls the endpoint, and gets an answer in a second |
| 4. They learn only four things | Whether it is real, which method version produced it, when it was taken and whether it is still current, and its evidence level |
It does not return the score, company name or any response. Verification confirms that the shared document is authentic and associated with the stated method version. It does not disclose information the company has not chosen to share.
This is similar to checking a certificate number on a certification body’s site. The recipient is checking the document shown, not looking up a private result. The check covers authenticity, method version and current status.
When the endpoint is live, a recipient can check a shared result without seeing the score, company name or answers. The response returns the validity, method version, date taken, current status and evidence level.
Example response from a verification request
GET /verify/GS-4K2P-9QX7 { "valid": true, "method_version": "v1.4", "taken": "2026-06-14", "status": "current", "evidence_level": "self-assessed" }
No score, no company name, no answers. The register is how a published method stays trustworthy, and it is the part that is not published.
Status: the register and the verification endpoint are live. Every result is recorded at creation, results issued before launch carry retroactive references, and a result stays current until a newer result for the same company supersedes it.
Two checks with different purposes
| Check | Question it answers | Who uses it |
|---|---|---|
| Checking a result this page | Is this particular result authentic, current and associated with the stated method version? | A recipient shown a result, such as a funder, investor, auditor or procurement team |
| Conformance separate page | Does this implementation compute the published method correctly? | An implementer, reviewer or risk function assessing the implementation |
A useful analogy: conformance checks whether an implementation follows the published test procedure. Checking a result checks one reported result against its reference.