Site diary
Site diary is one of Demiton's published registers for Australian civil construction. Daily site diaries: delays, weather, productivity, variations. 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 Projects in the register catalog.
- Register ID
site_diaryUse 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.2)Current version.
Standards
This register's contract was designed against these standards and laws. Holding these records does not by itself certify compliance.
- AS 3798-2007Guidelines on earthworks for commercial and residential developments
- AS 4000General Conditions of Contract (construct only)
- ISO 45001Occupational health and safety management systems
- ISO 9001Quality management systems - Requirements
- Fair Work Act 2009Fair Work Act 2009
- WHS Act and RegulationsModel WHS Act Part 3 - notifiable incidents
- ISO 45001Occupational health and safety management systems
- ISO 9001Quality management systems - Requirements
- Health and Safety at Work Act 2015 (NZ)HSWA 2015 - records of notifiable events
- 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.
- HammerTech
- MittiPartial
- Oracle Aconex
- Procore
- SignOnSitePartial
- SitematePartial
Fields
24 fields: 3 required, 21 optional.
Required
Every record carries these fields.
- contentText
The composed Q&A narrative - the semantic-search payload.
Example:
Q: What progressed today? A: Pavement base course placed …- external_idWhole number
The source system's own identifier for this diary record; substrate source identity and idempotency key. Declared an INTEGER because that is what the source carries - the identity is a string concept but the adapter does not render it as one.
Example:
990211- occurred_onDate
The diary's project-day (ISO 8601 date), distinct from when it was filed. One diary is one project-day.
Example:
2026-06-15
Optional
Present when the source system records them.
- assetWhole number
The plant or vehicle the diary records. Declared an INTEGER because Assignar's asset_id is numeric where it is populated at all.
Example:
9301- tasksList of text
The task(s) selected for the day.
- delaysList
Delay reasons and their stated duration.
- delays[].commentText
No description yet.
- delays[].durationText
No description yet.
- workerWhole number
The worker who authored / is the subject of the diary. Declared an INTEGER because Assignar's worker_id is numeric.
Example:
5501- projectWhole number
The project the diary scopes. Optional because many live diaries carry no linked project. Declared an INTEGER because Assignar's project_id is numeric where populated.
Example:
8101- weatherText
Site weather conditions for the day.
Example:
Fine, 26C- progressText
What progressed, and where the crew worked.
Example:
Pavement base course placed and compacted, chainage 220-260- headcountWhole number
Number of people on site for the day.
Example:
8- hired_plantText
Hired plant/equipment on site for the day.
- legal_entityText
The contracting entity the diary belongs to.
Example:
Bridgeworks Group Pty Ltd- submitted_atDate and time
When the form was submitted, distinct from the diary day.
Example:
2026-06-15T16:20:00- subcontractorText
Subcontractor present on site.
- financial_periodText
The claim/accounting period the diary day falls in.
Example:
2026-06- form_template_idWhole number
Which form template produced the row. Declared an INTEGER because Assignar's form_id is numeric.
Example:
7701- odometer_readingNumber
Vehicle odometer at the diary. Unit unverified (km vs miles).
- tenant_questionsGroup of fields
The tenant's own form questions, keyed by the slugified question label. Tenant-specific by construction - the same question does not exist for another tenant.
- incident_reportedTrue or false
Whether an incident report was submitted for this day. The diary is evidence, not the incident record.
Example:
false- source_modified_atDate and time
Last modification at source; the incremental harvest cursor.
Example:
2026-06-15T16:20:00- estimated_completion_dateDate
Forecast completion for the linked project.
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 - Assetwhat the record is about, from
When known - Legal entitycontext for the record, from
When known - Financial periodcontext for the record, 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": 9301, "content": "Q: What progressed today? A: Pavement base course placed and compacted chainage 220-260. Q: Weather? A: Fine, 26C.", "delays": [], "external_id": 990211, "financial_period": "2026-06", "form_template_id": 7701, "headcount": 8, "incident_reported": false, "legal_entity": "Bridgeworks Group Pty Ltd", "occurred_on": "2026-06-15", "progress": "Pavement base course placed and compacted, chainage 220-260", "project": 8101, "source_modified_at": "2026-06-15T16:20:00", "submitted_at": "2026-06-15T16:20:00", "tasks": [ "Base course placement", "Compaction" ], "weather": "Fine, 26C", "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_diary/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.