Can this result be checked?

A result check would confirm whether a shared report matches its recorded reference and method version. The verification endpoint is pending. The process below describes the intended service.

The register: how to check a result

A shared result is useful only if a recipient can check what it represents. The intended register would provide a short reference without exposing the underlying answers.

  1. 1
    A result gets a reference

    The intended service would associate a result with a reference and its method version.

  2. 2
    The company shares it

    The company would choose who receives its report and reference.

  3. 3
    The recipient checks it

    The recipient would submit the reference to the verification service.

  4. 4
    What the check returns

    The proposed response includes validity, method version, assessment date, current status and evidence level.

Proposed verification response

GET /verify/GS-4K2P-9QX7
{
  "valid": true,
  "method_version": "v1.5",
  "taken": "2026-06-14",
  "status": "current",
  "evidence_level": "self-assessed"
}

The endpoint and its operating rules remain subject to implementation and verification.

Checking a reference wouldn’t independently verify the business’s answers, establish a root cause or confirm the effectiveness of an intervention.

Two checks with different purposes

Checking a result

This page
Question it answers

Is this particular result authentic, current and associated with the stated method version?

Who uses it

A recipient shown a result, such as a funder, investor, auditor or procurement team

Conformance

Separate page
Question it answers

Does this implementation compute the published method correctly?

Who uses it

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.