Skip to content
Demiton

Punch list

Completion defects to close out before handover.

Part of Projects in the register catalog.

Register ID
punch_listUse 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.

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

20 fields: 5 required, 15 optional.

Required

Every record carries these fields.

external_idText

The source system's own item id.

Example: PL-2026-0142

source_systemText

Which bound system emitted the row.

Example: ASSIGNAR

projectText

The project the defect is on.

Example: BWG-2025-001

nameText

The defect's short title.

Example: Kerb alignment defect - Ch 220

statusText

The item's lifecycle state.

Example: open

Optional

Present when the source system records them.

descriptionText

What is wrong.

Example: Kerb line deviates more than 20mm from design at chainage…

priorityText

How urgent the fix is.

Example: medium

categoryText

The kind of defect.

Example: civil

tradeText

The trade responsible for the fix.

Example: Civil

locationText

Where on site the defect is.

Example: Chainage 220, northbound

due_dateDateYYYY-MM-DD

When the fix is due.

Example: 2026-07-28

closed_atDate and timeISO 8601, with time zone

When the item was closed.

assigneeText

Who must fix it.

Example: Sofia Reyes

managerText

Who manages the item.

Example: Aaron Patel

final_approverText

Who signs the fix off.

raised_byText

Who recorded the defect.

Example: Liam Castellano

closed_byText

Who closed it.

cost_impact_amountMoney amountUnit: AUD

The cost the defect adds.

schedule_impact_daysWhole numberUnit: days

The programme slip the defect causes.

Example: 0

cost_codeText

The cost code the fix is charged to.

Example: CIV-220

Example record

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

punch_list.example.json
{
"assignee": "Sofia Reyes",
"category": "civil",
"cost_code": "CIV-220",
"description": "Kerb line deviates more than 20mm from design at chainage 220",
"due_date": "2026-07-28",
"external_id": "PL-2026-0142",
"location": "Chainage 220, northbound",
"manager": "Aaron Patel",
"name": "Kerb alignment defect - Ch 220",
"priority": "medium",
"project": "BWG-2025-001",
"raised_by": "Liam Castellano",
"schedule_impact_days": 0,
"source_system": "ASSIGNAR",
"status": "open",
"trade": "Civil"
}

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/punch_list/v1.json
Show 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 keep current from them, on your data, in a 30-minute call.

Book a 30-minute callStart free