Permit to work
Permits controlling hazardous work.
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.- Each record is
- An eventSomething that happened at a point in time.
- Status
- PlannedDefined ahead of the connector that will fill it.
- Data
- OrganisationPrivate to each organisation's own workspace.
- Version
- v1Current version.
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
21 fields: 6 required, 15 optional.
Required
Every record carries these fields.
- external_idText
The source system's own permit id.
Example:
ptw-8102-014- source_systemText
Which bound system emitted the row.
Example:
ASSIGNAR- projectText
The site or project the permit is for.
Example:
BWG-2025-002- referenceText
The permit's human reference.
Example:
PTW-8102-014- permit_typeText
The kind of hazardous work permitted.
Example:
Excavation- statusText
Where the permit is in its lifecycle.
Example:
Approved
Optional
Present when the source system records them.
- nameText
The permit's title.
- raised_atDate and time
When the permit was initiated.
Example:
2026-07-28T07:00:00Z- requesterText
Who asked for the permit.
- initiatorText
Who created the permit record.
- approverText
Who approved the permit.
Example:
Dean Whitfield- approved_atDate and time
When the permit was approved.
Example:
2026-07-28T08:30:00Z- employerText
The employer doing the permitted work.
- zoneText
The permit zone on site.
- locationText
Where the work is, as free text.
- proposed_startDate and time
When the work was planned to start.
- proposed_endDate and time
When the work was planned to finish.
- actual_startDate and time
When the work actually started.
- actual_endDate and time
When the work actually finished.
- closed_out_atDate and time
When the permit was closed out.
- 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 keep current from them, on your data, in a 30-minute call.