Compliance state

Compliance state is one of Demiton's published registers for Australian civil construction. Current compliance status for one area of a legal entity: a scheme, obligation or requirement. 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_stateUse 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

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 14001Environmental management systems - Requirements with guidance for useAustralia · 2016 (international 2015 superseded; 2026 adoption unverified) · paywalled, from a secondary description
• ISO 45001Occupational health and safety management systems - Requirements with guidance for useAustralia · 2018 incorporating Amd 1:2024 (listing) · clause 6.1.2, 7.2, 8.1, 10.2 (per digest) · paywalled, from a secondary description
• ISO 9001Quality management systems - RequirementsAustralia · 2016 · clause 7.5, 7.1.5, 7.2, 8.7, 10.2 · paywalled, from a secondary description
• NPSNational Prequalification System for Civil (Road and Bridge) ConstructionAustralia · 2025 Edition · public summary
• CAL (NT)Contractor Accreditation Limited accreditationAustralia · current · public summary
• JAS-ANZ accreditationJoint Accreditation System of Australia and New ZealandAustralia · current · public summary
• Occupational Health and Safety Act 2004 (Vic)Occupational Health and Safety Act 2004 (Vic)Australia · current · public summary
• ISO 14001Environmental management systems - Requirements with guidance for useInternational · 2026 · paywalled, from a secondary description
• 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) · paywalled, from a secondary description

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.

• HammerTechPartial
• MittiPartial
• SignOnSitePartial
• SitematePartial

Fields

27 fields: 15 required, 12 optional.

Required

Every record carries these fields.

as_ofDate and timeISO 8601, with time zone

When the standing was last asserted by the org — the read-time clock for every derived status.

Example: 2026-07-01T00:00:00Z

titleText

The human name of the obligation/requirement (for a scheme, its catalog label)

Example: NPS annual financial accounts

statusText

The standing's own state; today scheme.status defaults "active" (:245) and requirement.status is free-ish with not_assessed expressed as absence (:1523-1528)

Example: current

cadenceTextUnit: biennial \

triennial \.

Example: annual

declaredTrue or false

Self-declared by the org, as opposed to evidenced.

Example: true

fact_keyText

The per-record key inside the kind: profile, scheme:{scheme_key}, obligation:{obligation_key}, the requirement key.

Example: obligation:nps_annual_financial_accounts

is_activeTrue or false

Whether the org still carries the obligation (inactive rows are kept visible, never retired)

Example: true

scheme_keyText

The catalog scheme/panel this row belongs to (nps, iso45001, …, or panel:{key})

Example: nps

shelf_typeText

The concrete pattern instance compliance_state:{record_kind}:{fact_key}; today the only carrier of the record kind and the per-record key.

Example: compliance_state:obligation:obligation:nps_annual_financi…

record_kindTextUnit: scheme \

obligation \.

Example: obligation

jurisdictionsList

The jurisdictions the org declares it operates/contracts in.

obligation_keyText

Stable key for a recurring obligation: catalog id for a template, custom:{slug} for a user-added one.

Example: nps_annual_financial_accounts

requirement_idText

The clause/scheme-requirement identifier being adhered to.

Example: nps-financial-accounts

subject_entity_idWhole number

The org the standing belongs to; the shared subject of all four kinds.

Example: 4210

max_contract_valueText

The largest contract value the org declares it can take.

Example: 100

Optional

Present when the source system records them.

noteText

Free-text assessor note.

sourceText

Provenance of the obligation row (template today)

next_dueDateYYYY-MM-DD

When the obligation next falls due.

Example: 2027-07-01

expires_atDateYYYY-MM-DD

When the holding or the next evidence obligation lapses.

descriptionText

What the obligation requires.

Example: Submit audited annual financial accounts to maintain NPS …

evidence_idWhole number

The evidence artefact backing the adherence claim.

valid_untilDate and timeISO 8601, with time zone

Supersession stamp; the live row is valid_until IS NULL

completed_atDate and timeISO 8601, with time zone

When the org finished the standing wizard.

effective_fromDateYYYY-MM-DD

The date the declared standing took effect.

classificationsGroup of fields

The declared levels on one scheme, e.g. the NPS A/B/F/R level set.

last_completed_atDateYYYY-MM-DD

When it was last satisfied.

contract_value_rangeText

The org's declared typical contract value range.

Filed against

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

• Legal entitycontext 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_state.example.json

{
  "as_of": "2026-07-01T00:00:00Z",
  "cadence": "annual",
  "declared": true,
  "description": "Submit audited annual financial accounts to maintain NPS financial-capacity classification F100.",
  "fact_key": "obligation:nps_annual_financial_accounts",
  "is_active": true,
  "jurisdictions": [
    "qld"
  ],
  "max_contract_value": "100",
  "next_due": "2027-07-01",
  "obligation_key": "nps_annual_financial_accounts",
  "record_kind": "obligation",
  "requirement_id": "nps-financial-accounts",
  "scheme_key": "nps",
  "shelf_type": "compliance_state:obligation:obligation:nps_annual_financial_accounts",
  "source_id": "compliance_state:obligation:nps_annual_financial_accounts:2026-07-01",
  "source_system": "DEMITON",
  "status": "current",
  "subject_entity_id": 4210,
  "title": "NPS annual financial accounts"
}

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_state/v1.json

Show the full JSON Schema

Loading the schema…