Audit readiness
Hand the Accredited Certification Body a link, not a folder
They open the register, open each file, and see the hash that proves it. No account, no onboarding.
By request
The audit room is shown live in a guided demo. The record, and how it reads, stays with the firms that use it.
Interactive demoThe alternative
A report ages. A register does not.
A law firm or a certification-body consultant can review your systems once and hand you a report. Regulation10 lets your Autonomous Systems Officer produce the same evidence, in a form the Accredited Certification Body reads directly, and keep producing it as your systems change.
| What matters to the ASO | Law firm or Accredited Certification Body consultant | Regulation10 |
|---|---|---|
| Who holds the evidence | Their file | Your workspace, sealed |
| What the Accredited Certification Body gets | A written report | The register, opened by link |
| How current it is | Correct on the review date | Re-run when a system changes |
| Runtime behaviour | Described | A decision record per call |
| Independence | Your adviser may also certify you | You prepare, the certifier stays independent |
| One more system | A new billable scope | One register entry inside your tier |
The handover
A stranger reads it with no account.
The external share room, zero onboarding, by design. What an Accredited Certification Body sees in the share room
The seal
What a hash proves, and what it does not
What it isA sha256 content hash of the locked file. A short code that changes if a single character changes.
What it provesThe file has not been altered since you locked it.
What it does not proveThat the content is correct, or that anyone approved it. It is tamper evidence, not a badge.