Plant risk assessment
Plant risk assessment is one of Demiton's published registers for Australian civil construction. Plant and equipment risk assessments. 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
plant_risk_assessmentUse 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.4)Current version.
Standards
This register's contract was designed against these standards and laws. Holding these records does not by itself certify compliance.
- AS 2550Cranes, hoists and winches - Safe use - Mobile elevating work platforms
- WHS Act and RegulationsModel Work Health and Safety Act (Safe Work Australia)
- WHS Act and RegulationsModel Work Health and Safety Regulations (Safe Work Australia; given effect by each state/territory)
- ISO 45001Occupational health and safety management systems - Requirements with guidance for use
- ISO 55001Asset management - Asset management system - Requirements
- Health and Safety at Work Act 2015 (NZ)Health and Safety at Work Act 2015
- RIDDOR 2013 (SI 2013/1471)Reporting of Injuries, Diseases and Dangerous Occurrences Regulations 2013
- OSHAOSHA - Reporting fatalities, hospitalizations, amputations and losses of an eye
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.
- HammerTechPartial
- MittiPartial
- Sitemate
Fields
20 fields: 4 required, 15 optional, 1 defined by each organisation.
Required
Every record carries these fields.
- workerNumber
The worker who submitted or signed the record; the required subject anchor.
Example:
5502- form_titleText
The matched Assignar form's title — which instrument this fact is.
Example:
Plant Pre-Start Risk Assessment - Excavator- external_idText
Stable identity of the source record (Assignar form-result id, cast to text).
Example:
ASGN-FR-52011- occurred_atDate and time
When the assessment or hazard report was submitted; the event time and the retention clock start.
Example:
2026-06-09T06:50:00
Optional
Present when the source system records them.
- assetText
The plant item the assessment is about, where the title's suffix resolves to exactly one registered asset.
Example:
9301- form_idNumber
The Assignar form-template id, the stable twin of
form_title.- projectText
The project the assessment was recorded against, where the source gives one.
Example:
BWG-2025-001- occurred_onDate
The date the hazard or occurrence happened, where the form states one.
- reported_byText
The person who reported the hazard.
- reported_onDate
The date the hazard was reported, where the form states one.
- reported_toText
The person the hazard was reported to.
- risk_ratingText
The risk-matrix selection the form records.
Example:
medium- assessment_dateDate
The date the form itself carries, distinct from submission time.
Example:
2026-06-09- hazard_locationText
Where the hazard is.
Example:
Chainage 240-260, Emerald Street- actions_requiredText
Follow-up actions the assessment requires.
- financial_periodDate
The accounting period the record falls in, derived from
occurred_at.Example:
2026-06-01- hazard_descriptionText
The hazard identified, and its details.
Example:
Ground instability adjacent to open trench- controls_implementedText
Controls in place at the time of the assessment.
Example:
Trench boxed and spotter assigned- controls_recommendedText
Controls or actions recommended by the assessment.
Example:
Geotechnical inspection before deepening excavation
Defined by each organisation
Their contents come from the organisation's own forms or systems, so they differ between organisations.
- attributesGroup of fields
Every remaining form answer, keyed by the tenant's own question text, plus
_raw_metadataat rest. This is where the 270 person-name-like slugs (814 fact-field occurrences) and the 24 excluded tenant-authored keys (881 occurrences, longest 115 characters) live; both are counted, not named (SC002).
Filed against
Records are indexed along these dimensions, so they can be asked for by any of them.
- Assetwhat the record is about, from
When known - Projectwhat the record is about, from
When known - Financial periodcontext for the record, from
When known - Workerwhat the record is about, from
Always set
Example record
A sample from Bridgeworks Group, Demiton's demonstration company. The values are illustrative; the shape is exactly what the contract describes.
{ "assessment_date": "2026-06-09", "asset": "9301", "controls_implemented": "Trench boxed and spotter assigned", "controls_recommended": "Geotechnical inspection before deepening excavation", "external_id": "ASGN-FR-52011", "financial_period": "2026-06-01", "form_title": "Plant Pre-Start Risk Assessment - Excavator", "hazard_description": "Ground instability adjacent to open trench", "hazard_location": "Chainage 240-260, Emerald Street", "occurred_at": "2026-06-09T06:50:00", "project": "BWG-2025-001", "risk_rating": "medium", "source_system": "ASSIGNAR", "worker": 5502}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/plant_risk_assessment/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.