Training records
Training logs and training requests, by worker.
Part of Workforce in the register catalog.
- Register ID
training_recordsUse 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
- ISO 9001Quality management systems
- ISO 30414Human capital reporting
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.
- MittiPartial
- SignOnSitePartial
- SitematePartial
Fields
15 fields: 6 required, 8 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:
FR-92011- source_systemText
Originating system;
ASSIGNARtoday.Example:
ASSIGNAR- occurred_atDate and time
When the training was logged/requested (source
submitted_time); the event time and the period key.Example:
2026-07-09T08:00:00Z- workerNumber
The worker trained or requesting training; the record's subject and its accountability anchor.
Example:
5502- training_titleText
What the training was — the course/programme name as recorded (log) or requested (request form).
Example:
White Card - General Construction Induction- training_kindText
Whether the activity is a completed log entry or a request, and whether it is statutory/licence training, a scheme card, or internal.
Example:
completed_statutory
Optional
Present when the source system records them.
- completed_atDate
Date the training was completed (or the log date), where the source records one.
Example:
2026-07-09- total_hoursNumber
Hours of training delivered/attended.
Example:
6- estimated_hours_requiredNumber
Hours the source says are required before a VOC assessment; a planning figure, not delivery.
- training_locationText
Where the training was delivered.
- provider_nameText
Training provider / registered training organisation (RTO) named on the record.
Example:
QLD Safety Training Group- training_costNumber
Cost of external training, where stated.
- form_idNumber
Source form template identity, where the source is form-backed; distinguishes log from request without parsing answers.
- financial_periodDate
The accounting/reporting period the record falls in, derived from
occurred_at.Example:
2026-07-01
Defined by each organisation
Their contents come from the organisation's own forms or systems, so they differ between organisations.
- record_kind_noteText
Free-text comments/notes the tenant attaches to the record.
Example record
A sample from Bridgeworks Group, Demiton's demonstration company. The values are illustrative; the shape is exactly what the contract describes.
{ "completed_at": "2026-07-09", "external_id": "FR-92011", "financial_period": "2026-07-01", "occurred_at": "2026-07-09T08:00:00Z", "provider_name": "QLD Safety Training Group", "source_system": "ASSIGNAR", "total_hours": 6, "training_kind": "completed_statutory", "training_title": "White Card - General Construction Induction", "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/training_records/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.