Plant risk assessment
Plant and equipment risk assessments.
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
- 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
- AS 2550Cranes, hoists and winches: safe use
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
21 fields: 5 required, 15 optional, 1 defined by each organisation.
Required
Every record carries these fields.
- external_idText
Stable identity of the source record (Assignar form-result id, cast to text).
Example:
ASGN-FR-52011- source_systemText
Originating system;
ASSIGNARtoday and the only system the frozen universe names.Example:
ASSIGNAR- 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- 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
Optional
Present when the source system records them.
- form_idNumber
The Assignar form-template id, the stable twin of
form_title.- assetText
The plant item the assessment is about, where the title's suffix resolves to exactly one registered asset.
Example:
9301- projectText
The project the assessment was recorded against, where the source gives one.
Example:
BWG-2025-001- financial_periodDate
The accounting period the record falls in, derived from
occurred_at.Example:
2026-06-01- assessment_dateDate
The date the form itself carries, distinct from submission time.
Example:
2026-06-09- reported_onDate
The date the hazard was reported, where the form states one.
- occurred_onDate
The date the hazard or occurrence happened, where the form states one.
- hazard_descriptionText
The hazard identified, and its details.
Example:
Ground instability adjacent to open trench- hazard_locationText
Where the hazard is.
Example:
Chainage 240-260, Emerald Street- risk_ratingText
The risk-matrix selection the form records.
Example:
medium- 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- actions_requiredText
Follow-up actions the assessment requires.
- reported_byText
The person who reported the hazard.
- reported_toText
The person the hazard was reported to.
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).
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 keep current from them, on your data, in a 30-minute call.