Compliance evidence
Evidence backing a compliance record: certificates, audit reports, licences.
Part of Safety in the register catalog.
- Register ID
compliance_evidenceUse this name to ask for the register. The API calls it a shelf ID.- Each record is
- A stateThe current value of something, replaced when it changes.
- Status
- DeclaredDefined, and fills when a source produces its first record.
- Data
- OrganisationPrivate to each organisation's own workspace.
- Version
- v1Current version.
Standards
This register holds records these standards and laws ask for. Holding them does not by itself certify compliance.
- ISO 9001Quality management systems
- ISO 14001Environmental management systems
- NPSNational Prequalification System for civil construction
Connectors
Connected today
Demiton keeps this register current from these systems now.
No system fills this register yet.
On the roadmap
Systems in the planned connector rollout that can fill this register. Partial means the system holds only some of its fields.
- HammerTech
- MittiPartial
- SitematePartial
Fields
19 fields: 3 required, 16 optional.
Required
Every record carries these fields.
- subject_entity_idWhole number
The org spine node the evidence supports (the fact subject)
Example:
5502- source_systemText
The producing system (today always
DEMITON)Example:
SHAREPOINT- source_external_idText
The raw evidence record's id in the producing system.
Example:
shp-doc-4471
Optional
Present when the source system records them.
- scheme_keyText
Scheme/panel the evidence supports (catalog key)
- obligation_keyText
Recurring obligation the evidence completes.
- requirement_idText
Requirement clause the evidence covers.
- evidence_typeText
register\.Example:
licence- certificate_numberText
Certificate identifier.
Example:
QLD-WC-884213- certifying_bodyText
Issuing body (certification body, insurer)
Example:
Site Safe QLD- standard_editionText
Edition of the certified standard (e.g.
ISO 14001:2015,ISO 14001:2026)- scopeText
Certified/insured scope statement.
Example:
worker- issued_atDate
Issue date.
Example:
2024-03-11- expires_atDate
Expiry date; readers derive lapsed/current from it.
Example:
2029-03-11- verified_atDate and time
When Demiton verified the evidence row.
- titleText
Display title of the artefact.
Example:
General Construction Induction (White Card)- source_pathText
Document path in the org's IMS store — the upsert key across re-crawls.
Example:
/Compliance/Workers/5502/WhiteCard.pdf- classificationsGroup of fields
Scheme classification levels (today NPS
R/B/F/A), only whenscheme_keyis a classified scheme.- noteText
Free-text note on the evidence.
- summaryText
Rendered prose summary of the evidence.
Example:
Current White Card on file for Mia Okafor
Example record
A sample from Bridgeworks Group, Demiton's demonstration company. The values are illustrative; the shape is exactly what the contract describes.
{ "certificate_number": "QLD-WC-884213", "certifying_body": "Site Safe QLD", "evidence_type": "licence", "expires_at": "2029-03-11", "issued_at": "2024-03-11", "scope": "worker", "source_external_id": "shp-doc-4471", "source_path": "/Compliance/Workers/5502/WhiteCard.pdf", "source_system": "SHAREPOINT", "subject_entity_id": 5502, "summary": "Current White Card on file for Mia Okafor", "title": "General Construction Induction (White Card)"}Use this contract
The contract is a standard JSON Schema (draft 2020-12) document, so any JSON Schema validator can check a record against it. Keywords starting with x-demiton- add Demiton's own meaning, such as units and requiredness, and validators ignore them.
https://docs.demiton.io/registers/compliance_evidence/v1.jsonShow the full JSON Schema
Loading the schema…
Talk to the team
Tell us what you run - your ERP, field, payroll and document systems - and we will show you the registers Demiton would keep current from them, on your data, in a 30-minute call.