Compliance documents

Safety and compliance documents attached to projects or workers.

Part of Safety in the register catalog.

Register ID

compliance_documentsUse this name to ask for the register. The API calls it a shelf ID.

Each record is

An eventSomething that happened at a point in time.

Status

AvailableFilled today from connected systems, uploads or public data.

Data

OrganisationPrivate to each organisation's own workspace.

Version

v1Current version.

Download JSON SchemaSee an example record

Standards

This register holds records these standards and laws ask for. Holding them does not by itself certify compliance.

• ISO 45001Occupational health and safety management systemsInternational
• ISO 9001Quality management systemsInternational · Clause 7.5
• ISO 19650Information management using building information modellingInternational

Connectors

Connected today

Demiton keeps this register current from these systems now.

• Assignar
• Azure AI Search
• Dropbox
• SharePoint

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
• Mitti
• Oracle Aconex
• ProcorePartial
• SitematePartial

Fields

14 fields: 5 required, 9 optional.

Required

Every record carries these fields.

external_idText

Stable identity of the source submission, shelf-qualified as compliance_documents:<id>.

Example: compliance_documents:cd-8101-0142

source_systemText

Originating system; today always ASSIGNAR.

Example: ASSIGNAR

occurred_atDate and timeISO 8601, with time zone

Submission date/time; the evidence and retention clock.

Example: 2026-07-14T07:45:00Z

projectText

Project the compliance document is attached to.

Example: BWG-2025-001

document_titleText

Name of the form/document as submitted (observed source key form_title).

Example: SWMS - Traffic Control Emerald Street

Optional

Present when the source system records them.

workerText

Worker the document attaches to.

Example: 5501

assetText

Plant/asset the document attaches to.

financial_periodDateYYYY-MM-DDUnit: YYYY-MM

The period the submission falls in, derived from occurred_at.

document_typeText

Class of compliance document (SWMS / ITP / inspection / diary).

Example: SWMS

expires_atDateYYYY-MM-DD

Document/credential expiry, where the document has one.

revisionText

Document revision/version identifier.

status_codeText

Document status/suitability, stored with the code set it comes from.

summaryText

Composed prose description of the submission.

Example: Safe Work Method Statement submitted for traffic control …

source_refsGroup of fields

The originating system's own identifiers (assignar_project_id, assignar_worker_id, assignar_asset_id) kept for reconciliation, rather than freezing one vendor's column names into the contract.

Example record

A sample from Bridgeworks Group, Demiton's demonstration company. The values are illustrative; the shape is exactly what the contract describes.

compliance_documents.example.json

{
  "document_title": "SWMS - Traffic Control Emerald Street",
  "document_type": "SWMS",
  "external_id": "compliance_documents:cd-8101-0142",
  "occurred_at": "2026-07-14T07:45:00Z",
  "project": "BWG-2025-001",
  "source_system": "ASSIGNAR",
  "summary": "Safe Work Method Statement submitted for traffic control activities on Emerald Street.",
  "worker": "5501"
}

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.

Schema URL

https://docs.demiton.io/registers/compliance_documents/v1.json

Show the full JSON Schema

Loading the schema…