Daily log

A structured daily log, distinct from a form-shaped site diary.

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.

Each record is

An eventSomething that happened at a point in time.

Status

PlannedDefined ahead of the connector that will fill it.

Data

OrganisationPrivate to each organisation's own workspace.

Version

v1Current version.

Download JSON SchemaSee an example record

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

15 fields: 4 required, 11 optional.

Required

Every record carries these fields.

external_idText

The source system's own log id.

Example: dl-2026-0701-8101

source_systemText

Which bound system emitted the row.

Example: ASSIGNAR

projectText

The project the log is for.

Example: BWG-2025-001

log_dateDateYYYY-MM-DD

The day the log covers.

Example: 2026-07-01

Optional

Present when the source system records them.

started_atTextUnit: local time of day

When work started that day.

Example: 06:30

ended_atTextUnit: local time of day

When work ended that day.

Example: 16:45

interrupted_hoursDecimal numberUnit: hours

Hours lost to interruptions.

Example: 0.5

notesText

The day's free-text notes.

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

completedTrue or false

Whether the day's log was completed.

Example: true

completed_byText

Who completed the log.

Example: Aaron Patel

completed_atDate and timeISO 8601, with time zone

When the log was completed.

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

distributedTrue or false

Whether the log was sent out.

Example: true

distributed_atDate and timeISO 8601, with time zone

When the log was sent out.

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

subcontractors_submittedWhole number

How many subcontractors submitted entries.

Example: 1

entry_countWhole number

How many individual entries the day holds.

Example: 6

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…