Site inspection
Site inspection is one of Demiton's published registers for Australian civil construction. Vehicle and plant inspection checklists. 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
site_inspectionUse 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
- v1 (1.0.4)Current version.
Standards
This register's contract was designed against these standards and laws. Holding these records does not by itself certify compliance.
- AS 1742.3:2019Manual of uniform traffic control devices - Traffic control for works on roads
- AS 2550Cranes, hoists and winches - Safe use - Mobile elevating work platforms
- ISO 14001Environmental management systems - Requirements with guidance for use
- ISO 45001Occupational health and safety management systems - Requirements with guidance for use
- ISO 9001Quality management systems - Requirements
- WHS Act and RegulationsModel Work Health and Safety Act
- WHS Act and RegulationsModel Work Health and Safety Regulations
- ISO 45001Occupational health and safety management systems - Requirements with guidance for use
- ISO 9001Quality management systems - Requirements
- LOLER 1998Lifting Operations and Lifting Equipment Regulations 1998
- RIDDOR 2013Reporting of Injuries, Diseases and Dangerous Occurrences Regulations 2013
- OSHAOverhead and gantry cranes
- OSHAOSHA Recording and Reporting Occupational Injuries and Illnesses
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.
- EROADPartial
- HammerTech
- Mitti
- Oracle Aconex
- Procore
- SignOnSitePartial
- SitematePartial
Fields
14 fields: 4 required, 9 optional, 1 defined by each organisation.
Required
Every record carries these fields.
- assetNumber
The vehicle or plant item the checklist is about; the required subject anchor.
Example:
9302- form_titleText
The matched Assignar form's title — which inspection instrument this fact is.
Example:
Pre-Start Plant Inspection (QF-018)- external_idText
Stable identity of the source record (Assignar form-result id, cast to text).
Example:
FR-90112- occurred_atDate and time
When the inspection was submitted; the event time and the retention clock start.
Example:
2026-07-11T05:50:00Z
Optional
Present when the source system records them.
- workerNumber
The worker who submitted or signed the inspection.
Example:
5501- form_idNumber
The Assignar form-template id, the stable twin of
form_title.Example:
501- projectNumber
The project the inspection is recorded against.
Example:
8101- commentsText
Free-text remarks on the inspection.
Example:
All checks satisfactory, machine released for shift.- odometerText
The odometer or meter reading the inspection captured.
Example:
98120- inspection_dateDate
The date the form itself carries, distinct from submission time.
Example:
2026-07-11- financial_periodDate
The accounting period the inspection falls in, derived from
occurred_at.Example:
2026-07-01- flagged_item_countWhole number
Number of checklist answers whose value names a fault, derived from the response vocabulary by
form_measures.Example:
0- unanswered_item_countWhole number
Number of answerable checklist questions left blank.
Example:
0
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 82 checklist answer slugs, the 152 tenant-derived identity/vehicle slugs and the 15 excluded tenant-authored keys live; all are counted, not named (SC002).
Filed against
Records are indexed along these dimensions, so they can be asked for by any of them.
- Projectwhat the record is about, from
When known - Workerwhat the record is about, from
When known - Financial periodcontext for the record, from
When known - Assetwhat the record is about, from
Always set
Example record
A sample from Bridgeworks Group, Demiton's demonstration company. The values are illustrative; the shape is exactly what the contract describes.
{ "asset": 9302, "comments": "All checks satisfactory, machine released for shift.", "external_id": "FR-90112", "financial_period": "2026-07-01", "flagged_item_count": 0, "form_id": 501, "form_title": "Pre-Start Plant Inspection (QF-018)", "inspection_date": "2026-07-11", "occurred_at": "2026-07-11T05:50:00Z", "odometer": "98120", "project": 8101, "source_system": "ASSIGNAR", "unanswered_item_count": 0, "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/site_inspection/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.