Checking a result
Is this result genuine?
A report can be screenshotted and a number can be edited. Every Growth Score result carries a reference, and anyone shown one can confirm it is real without seeing anything the company did not choose to share.
The register, and how anyone checks a result
A report can be screenshotted and a number can be edited. The register is what makes a shared result checkable, and it works like a certificate number.
| 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 |
What it does not return: the score, the company name, or any answer. Verification confirms that what the company showed you is authentic. It does not disclose anything the company did not choose to disclose.
Same idea as checking a certificate number on a certification body’s site. You are not looking up their result. You are confirming the document in front of you is genuine, current, and produced by the method it claims.
When a company shares a result with an investor or a programme, the recipient can confirm it’s real without seeing anything private. The endpoint returns whether it’s valid, which version produced it, when it was taken, whether it’s current, and its evidence level. Nothing else.
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 specified and not yet live. Results taken today are recorded; verification opens with the next release.
Two different checks, often confused
| Question it answers | Who asks it | |
|---|---|---|
| Checking a result this page | Is this particular result genuine, current, and produced by the method it claims? | A funder, investor, auditor or procurement team who has been shown a result |
| Conformance separate page | Does this implementation compute the method correctly? | Anyone running the method themselves, and any risk function assessing the instrument |
The nearest analogy: conformance is a laboratory being accredited to run a test. Checking a result is the certificate number on one specific test.