Daily log

Daily log is one of Demiton's published registers for Australian civil construction. A structured daily log, distinct from a form-shaped site diary. 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

daily_logUse this name to ask for the register. The API calls it a shelf ID.

Status

PlannedDefined ahead of the connector that will fill it.

Data

OrganisationPrivate to each organisation's own workspace.

Version

v1 (1.0.3)Current version.

Download JSON SchemaSee an example record

Standards

This register's contract was designed against these standards and laws. Holding these records does not by itself certify compliance.

• ISO 9001Quality management systems - RequirementsAustralia · 2016 (adopts ISO 9001:2015) · clause 7.5 · paywalled, from a secondary description
• ISO 9001Quality management systems - RequirementsInternational · 2015 (ISO 9001:2026 successor expected; unverified) · clause 7.5 · paywalled, from a secondary description

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

14 fields: 3 required, 11 optional.

Required

Every record carries these fields.

projectText

The project the log is for.

Example: BWG-2025-001

log_dateDateYYYY-MM-DD

The day the log covers.

Example: 2026-07-01

external_idText

The source system's own log id.

Example: dl-2026-0701-8101

Optional

Present when the source system records them.

notesText

The day's free-text notes.

Example: Kerb and channel pours on schedule; minor delay from a la…

ended_atTextUnit: local time of day

When work ended that day.

Example: 16:45

completedTrue or false

Whether the day's log was completed.

Example: true

started_atTextUnit: local time of day

When work started that day.

Example: 06:30

distributedTrue or false

Whether the log was sent out.

Example: true

entry_countWhole number

How many individual entries the day holds.

Example: 6

completed_atDate and timeISO 8601, with time zone

When the log was completed.

Example: 2026-07-01T16:52:00+10:00

completed_byText

Who completed the log.

Example: Aaron Patel

distributed_atDate and timeISO 8601, with time zone

When the log was sent out.

Example: 2026-07-01T17:05:00+10:00

interrupted_hoursDecimal numberUnit: hours

Hours lost to interruptions.

Example: 0.5

subcontractors_submittedWhole number

How many subcontractors submitted entries.

Example: 1

Example record

A sample from Bridgeworks Group, Demiton's demonstration company. The values are illustrative; the shape is exactly what the contract describes.

daily_log.example.json

{
  "completed": true,
  "completed_at": "2026-07-01T16:52:00+10:00",
  "completed_by": "Aaron Patel",
  "distributed": true,
  "distributed_at": "2026-07-01T17:05:00+10:00",
  "ended_at": "16:45",
  "entry_count": 6,
  "external_id": "dl-2026-0701-8101",
  "interrupted_hours": 0.5,
  "log_date": "2026-07-01",
  "notes": "Kerb and channel pours on schedule; minor delay from a late concrete delivery.",
  "project": "BWG-2025-001",
  "source_system": "ASSIGNAR",
  "started_at": "06:30",
  "subcontractors_submitted": 1
}

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.

Schema URL

https://docs.demiton.io/registers/daily_log/v1.json

Show the full JSON Schema

Loading the schema…