Safety incident (v1)
Safety incident is one of Demiton's published registers for Australian civil construction. Safety incidents and near misses on site. 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
safety_incidentUse 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.1)Superseded by v2.
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 use
- ISO 45001Occupational health and safety management systems - Requirements with guidance for use
- ISO 9001Quality management systems - Requirements
- WHS Act and RegulationsModel Work Health and Safety Act (Cth enactment: Work Health and Safety Act 2011)
- Occupational Health and Safety Act 2004 (Vic)Occupational Health and Safety Act 2004 (Vic)
- Privacy Act 1988Privacy Act 1988 (Cth)
- GDPRRegulation (EU) 2016/679 (General Data Protection Regulation)
- ISO 45001Occupational health and safety management systems - Requirements with guidance for use
- Health and Safety at Work Act 2015 (NZ)Health and Safety at Work Act 2015
- RIDDOR 2013Reporting of Injuries, Diseases and Dangerous Occurrences Regulations 2013 (SI 2013/1471)
- Social Security (Claims and Payments) Regulations 1979Social Security (Claims and Payments) Regulations 1979 (accident book)
- OSHAOSHA Recording and Reporting Occupational Injuries and Illnesses
Connectors
On the roadmap
Systems in the planned connector rollout that can fill this register. Partial means the system holds only some of its fields.
- Mitti
- Oracle Aconex
- Procore
- SignOnSitePartial
- SitematePartial
Fields
14 fields: 6 required, 8 optional.
Required
Every record carries these fields.
- form_idNumber
The source form template the incident was captured on.
Example:
490- form_titleText
The source form template's title, i.e. which tenant incident template this is.
Example:
Incident/Injury Report (QF-030)- external_idText
Stable identity of the source incident record (Assignar form-result id, cast to text).
Example:
FR-91500- occurred_atDate and time
When the incident happened/was submitted; the notification and recording clock.
Example:
2026-07-22T13:40:00Z- source_systemText
Originating system; today always
ASSIGNAR.Example:
ASSIGNAR- financial_periodDate
The period the incident falls in, derived from
occurred_at; the axis retention is computed against.Example:
2026-07-01
Optional
Present when the source system records them.
- assetText
Plant/asset involved in the incident.
- workerNumber
Worker involved or submitting; resolves to the worker spine.
Example:
5503- projectNumber
Project the incident attaches to.
Example:
8101- narrativeText
The incident description, composed from the source responses Q&A; may be null when nothing is renderable.
Example:
Labourer sustained a minor laceration to forearm while ha…- creator_nameText
Display name of the submitting Assignar user (free text, not a resolved identity).
Example:
Dean Whitfield- jurisdictionText
The WHS regime whose notification and retention rules apply to this record.
Example:
QLD- modified_timeDate and time
Source last-modified time; the delta-harvest cursor.
- outcome_classText
Worst recorded outcome: none / first aid / medical treatment / restricted work / days away / death.
Example:
first_aid
Example record
A sample from Bridgeworks Group, Demiton's demonstration company. The values are illustrative; the shape is exactly what the contract describes.
{ "creator_name": "Dean Whitfield", "external_id": "FR-91500", "financial_period": "2026-07-01", "form_id": 490, "form_title": "Incident/Injury Report (QF-030)", "jurisdiction": "QLD", "narrative": "Labourer sustained a minor laceration to forearm while handling formwork; first aid applied on site, returned to duties.", "occurred_at": "2026-07-22T13:40:00Z", "outcome_class": "first_aid", "project": 8101, "source_system": "ASSIGNAR", "worker": 5503}Version history
- v2 (current)
- v1
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/safety_incident/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 fill from them, on your data, in a 30-minute call.