Compliance documents

Compliance documents is one of Demiton's published registers for Australian civil construction. Safety and compliance documents attached to projects or workers. Demiton keeps it current from the systems a contractor already runs and publishes the record's shape as a versioned JSON Schema, so the same question works whichever system produced the record.

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

v1 (1.0.3)Current version.

Download JSON SchemaSee an example record

Standards

This register's contract was designed against these standards and laws. Holding these records does not by itself certify compliance.

• ISO 19650Organization and digitization of information about buildings and civil engineering works, including BIM - Information management using building information modelling (Parts 1 and 2)Australia · 2019 (identical to ISO 19650-1:2018 and -2:2018) · public summary
• ISO 14001Environmental management systems - Requirements with guidance for useAustralia · 2016 · clause 10.2 · paywalled, from a secondary description
• ISO 45001Occupational health and safety management systems - Requirements with guidance for useAustralia · 2018 · clause 6.1.2, 8.1, 10.2 (per digest) · paywalled, from a secondary description
• ISO 9001Quality management systems - RequirementsAustralia · 2016 · clause 7.5 documented information · paywalled, from a secondary description
• WHS Act and RegulationsModel Work Health and Safety Regulations (safe work method statements)Australia · model regulations · clause reg 299 (SWMS required for high risk construction work); SWMS copy kept 2 years after a notifiable incident · public summary
• Occupational Health and Safety Act 2004 (Vic)Occupational Health and Safety Act 2004 (Vic)Australia · current · clause s 38 (written notification kept at least 5 years) · public summary
• ISO 19650Information management using building information modelling (Parts 1 and 2)International · 2018 · public summary
• ISO 45001Occupational health and safety management systems - Requirements with guidance for useInternational · 2018 (Amd 1:2024) · paywalled, from a secondary description
• ISO 9001Quality management systems - RequirementsInternational · 2015 (2026 expected) · clause 7.5 · paywalled, from a secondary description
• ISO 19650BS EN ISO 19650-2 UK National AnnexUnited Kingdom · 2021 revision · clause NA.4.2, NA.4.3 (unverified) · paywalled, from a secondary description

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

13 fields: 4 required, 9 optional.

Required

Every record carries these fields.

projectText

Project the compliance document is attached to.

Example: BWG-2025-001

external_idText

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

Example: compliance_documents:cd-8101-0142

occurred_atDate and timeISO 8601, with time zone

Submission date/time; the evidence and retention clock.

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

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.

assetText

Plant/asset the document attaches to.

workerText

Worker the document attaches to.

Example: 5501

summaryText

Composed prose description of the submission.

Example: Safe Work Method Statement submitted for traffic control …

revisionText

Document revision/version identifier.

expires_atDateYYYY-MM-DD

Document/credential expiry, where the document has one.

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.

status_codeText

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

document_typeText

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

Example: SWMS

financial_periodDateYYYY-MM-DDUnit: YYYY-MM

The period the submission falls in, derived from occurred_at.

Filed against

Records are indexed along these dimensions, so they can be asked for by any of them.

• Projectwhat the record is about, from Always set
• Workerwhat the record is about, from When known
• Financial periodcontext for the record, from When known

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…