Toolbox talk
Toolbox talks and pre-work safety meetings.
Part of Safety in the register catalog.
- Register ID
toolbox_talkUse 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.
- HammerTech
- MittiPartial
- ProcorePartial
- SignOnSitePartial
- SitematePartial
Fields
20 fields: 5 required, 14 optional, 1 defined by each organisation.
Required
Every record carries these fields.
- external_idText
Stable identity of the source submission, shelf-qualified
<shelf>:<source id>.Example:
tbt-2026-0198- source_systemText
Originating system; today always
ASSIGNAR.Example:
ASSIGNAR- occurred_atDate and time
Submission date/time; the event time and the retention clock.
Example:
2026-07-06T06:35:00+10:00- projectNumber
Project the talk was held on.
Example:
8101- titleText
Title of the form/record that produced the fact (observed source key
form_title), stamped by the pattern sweep.Example:
Pre-start Toolbox Talk - Traffic Control
Optional
Present when the source system records them.
- workerNumber
Worker the talk attaches to at form level (the WORKER anchor).
Example:
5501- financial_periodDate
The period the talk falls in, derived from
occurred_at.- occurred_onDate
Date-only form date captured by the reader's date-field detection (source key
diary_date).Example:
2026-07-06- topicText
Subject(s) discussed at the talk.
Example:
Traffic control set-up and pedestrian exclusion zones- attendees[]List
Normalized attendance list, replacing the per-person columns and the per-person absence columns of the wide record.
- attendee_countWhole number
Number of persons present.
Example:
3- absentee_countWhole number
Number of persons recorded absent.
Example:
0- follow_up_topicsText
Topics raised for future discussion.
- issues_raisedText
Issues or hazards raised at the meeting.
- duration_minutesWhole number
Duration of the meeting, derived from its start/finish times.
Example:
15- narrativeText
The Q&A prose composed once at ingress and stored as
Fact.content.- signature_refText
Reference to a signature captured on the form.
- attachment_refs[]List
Image/attachment answers on the form.
- source_refsGroup of fields
Originating system identifiers (
form_id,diary_id, rawproject_id/worker_id) kept for reconciliation instead of freezing vendor column names into the contract.
Defined by each organisation
Their contents come from the organisation's own forms or systems, so they differ between organisations.
- tenant_answersGroup of fields
The remaining tenant form-template columns, held verbatim. Tenant content, never part of the standard contract, never named outside the tenant.
Example record
A sample from Bridgeworks Group, Demiton's demonstration company. The values are illustrative; the shape is exactly what the contract describes.
{ "absentee_count": 0, "attendee_count": 3, "duration_minutes": 15, "external_id": "tbt-2026-0198", "occurred_at": "2026-07-06T06:35:00+10:00", "occurred_on": "2026-07-06", "project": 8101, "source_system": "ASSIGNAR", "title": "Pre-start Toolbox Talk - Traffic Control", "topic": "Traffic control set-up and pedestrian exclusion zones", "worker": 5501}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/toolbox_talk/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.