Permit to work
Permit to work is one of Demiton's published registers for Australian civil construction. Permits controlling hazardous work. 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
permit_to_workUse this name to ask for the register. The API calls it a shelf ID.- Status
- PlannedDefined ahead of the connector that will fill it.
- Data
- OrganisationPrivate to each organisation's own workspace.
- Version
- v1 (1.0.3)Current version.
Standards
This register's contract was designed against these standards and laws. Holding these records does not by itself certify compliance.
- ISO 45001Occupational health and safety management systems - Requirements with guidance for use
- ISO 45001Occupational health and safety management systems - Requirements with guidance for use
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.
None planned yet.
Fields
20 fields: 5 required, 15 optional.
Required
Every record carries these fields.
- statusText
Where the permit is in its lifecycle.
Example:
Approved- projectText
The site or project the permit is for.
Example:
BWG-2025-002- referenceText
The permit's human reference.
Example:
PTW-8102-014- external_idText
The source system's own permit id.
Example:
ptw-8102-014- permit_typeText
The kind of hazardous work permitted.
Example:
Excavation
Optional
Present when the source system records them.
- nameText
The permit's title.
- zoneText
The permit zone on site.
- approverText
Who approved the permit.
Example:
Dean Whitfield- employerText
The employer doing the permitted work.
- locationText
Where the work is, as free text.
- initiatorText
Who created the permit record.
- raised_atDate and time
When the permit was initiated.
Example:
2026-07-28T07:00:00Z- requesterText
Who asked for the permit.
- actual_endDate and time
When the work actually finished.
- approved_atDate and time
When the permit was approved.
Example:
2026-07-28T08:30:00Z- actual_startDate and time
When the work actually started.
- proposed_endDate and time
When the work was planned to finish.
- closed_out_atDate and time
When the permit was closed out.
- proposed_startDate and time
When the work was planned to start.
- closeout_checklist_completedTrue or false
Whether the closeout checklist was done.
Example record
A sample from Bridgeworks Group, Demiton's demonstration company. The values are illustrative; the shape is exactly what the contract describes.
{ "approved_at": "2026-07-28T08:30:00Z", "approver": "Dean Whitfield", "external_id": "ptw-8102-014", "permit_type": "Excavation", "project": "BWG-2025-002", "raised_at": "2026-07-28T07:00:00Z", "reference": "PTW-8102-014", "source_system": "ASSIGNAR", "status": "Approved"}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/permit_to_work/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.