Safety incident
Safety incidents and near misses on site.
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
- v1Current version.
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 systems
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.
- external_idText
Stable identity of the source incident record (Assignar form-result id, cast to text).
Example:
FR-91500- source_systemText
Originating system; today always
ASSIGNAR.Example:
ASSIGNAR- occurred_atDate and time
When the incident happened/was submitted; the notification and recording clock.
Example:
2026-07-22T13:40:00Z- financial_periodDate
The period the incident falls in, derived from
occurred_at; the axis retention is computed against.Example:
2026-07-01- 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)
Optional
Present when the source system records them.
- projectNumber
Project the incident attaches to.
Example:
8101- workerNumber
Worker involved or submitting; resolves to the worker spine.
Example:
5503- assetText
Plant/asset involved in the incident.
- 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…- modified_timeDate and time
Source last-modified time; the delta-harvest cursor.
- creator_nameText
Display name of the submitting Assignar user (free text, not a resolved identity).
Example:
Dean Whitfield- outcome_classText
Worst recorded outcome: none / first aid / medical treatment / restricted work / days away / death.
Example:
first_aid- jurisdictionText
The WHS regime whose notification and retention rules apply to this record.
Example:
QLD
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}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 keep current from them, on your data, in a 30-minute call.