Punch list
Punch list is one of Demiton's published registers for Australian civil construction. Completion defects to close out before handover. 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
punch_listUse 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.1.1)Current version.
Standards
This register's contract was designed against these standards and laws. Holding these records does not by itself certify compliance.
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: 4 required, 16 optional.
Required
Every record carries these fields.
- nameText
The defect's short title.
Example:
Kerb alignment defect - Ch 220- statusText
The item's lifecycle state.
Example:
open- projectText
The project the defect is on.
Example:
BWG-2025-001- external_idText
The source system's own item id.
Example:
PL-2026-0142
Optional
Present when the source system records them.
- tradeText
The trade responsible for the fix.
Example:
Civil- managerText
Who manages the item.
Example:
Aaron Patel- assigneeText
Who must fix it.
Example:
Sofia Reyes- categoryText
The kind of defect.
Example:
civil- currencycurrency
The currency of
cost_impact_amount, an ISO 4217 alpha-3 code as the source states it. A record with no currency has no usable amount.- due_dateDate
When the fix is due.
Example:
2026-07-28- locationText
Where on site the defect is.
Example:
Chainage 220, northbound- priorityText
How urgent the fix is.
Example:
medium- closed_atDate and time
When the item was closed.
- closed_byText
Who closed it.
- cost_codeText
The cost code the fix is charged to.
Example:
CIV-220- raised_byText
Who recorded the defect.
Example:
Liam Castellano- descriptionText
What is wrong.
Example:
Kerb line deviates more than 20mm from design at chainage…- final_approverText
Who signs the fix off.
- cost_impact_amountMoney amount
The cost the defect adds.
- schedule_impact_daysWhole number
The programme slip the defect causes.
Example:
0
Example record
A sample from Bridgeworks Group, Demiton's demonstration company. The values are illustrative; the shape is exactly what the contract describes.
{ "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.
https://docs.demiton.io/registers/punch_list/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.