Programme

Programme is one of Demiton's published registers for Australian civil construction. A construction programme extracted from an uploaded schedule document. 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

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

Each record is

A stateThe current value of something, replaced when it changes.

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.

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.

• AS 2124General Conditions of ContractAustralia · 1992 (superseded) · paywalled, from a secondary description
• AS 4000General Conditions of Contract (construct only)Australia · 2025 · paywalled, from a secondary description
• ISO 19650Organization and digitization of information about buildings and civil engineering works - concepts and principlesAustralia · 2019 (identical to ISO 19650-1:2018) · public summary
• ISO 19650Organization and digitization of information - delivery phase of the assetsAustralia · 2019 (identical to ISO 19650-2:2018) · public summary
• ISO 19650Information management using BIMInternational · 2018 · public summary
• ISO 19650UK National Annex status and revision codesUnited Kingdom · 2021 · clause NA.4.2 / NA.4.3 (per third party) · 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.

• Oracle Aconex
• Procore

Fields

9 fields: 1 required, 8 optional.

Required

Every record carries these fields.

source_documentGroup of fields

—.

Optional

Present when the source system records them.

dateText

The Finish date as written, e.g. 3/11/26.

nameText

Task name, cleaned of IDs and day names.

Example: Practical Completion

typeText

Milestone category.

Example: milestone

revisionText

Document revision as stated (e.g. "1", "0", "A"), else inferred from text or file name.

Example: 2

milestonesList

Null}`

start_dateText

Contract award / commencement / first mobilisation date.

Example: 2026-04-01

extraction_sourceText

Provenance marker for how the content was obtained.

Example: llm

practical_completion_dateText

Finish date of the Practical Completion / PC task.

Example: 2026-12-18

Example record

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

programme.example.json

{
  "extraction_source": "llm",
  "milestones": [
    {
      "date": "2026-12-18",
      "name": "Practical Completion",
      "type": "practical_completion"
    }
  ],
  "name": "Practical Completion",
  "practical_completion_date": "2026-12-18",
  "revision": "2",
  "source_document": {
    "file_name": "BWG-2025-001_Programme_Rev2.pdf",
    "storage_location": "SharePoint/Bridgeworks/Projects/BWG-2025-001"
  },
  "start_date": "2026-04-01",
  "type": "milestone"
}

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/programme/v1.json

Show the full JSON Schema

Loading the schema…