Day works docket (v1)
Day works docket is one of Demiton's published registers for Australian civil construction. Day works dockets for extra or variation work. 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 Contracts in the register catalog.
- Register ID
day_works_docketUse 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
- AvailableFilled today from connected systems, uploads or public data.
- Data
- OrganisationPrivate to each organisation's own workspace.
- Version
- v1 (1.0.1)Superseded by v2.
Standards
This register's contract was designed against these standards and laws. Holding these records does not by itself certify compliance.
- AS 4000General Conditions of Contract (superseded edition, still in use)
- AS 4000General Conditions of Contract (construct only)
- AS 4902General Conditions of Contract for Design and Construct
- Security of paymentAustralian state and territory Security of Payment Acts (NSW 1999, QLD 2017, VIC 2002, WA 2021, SA 2009, TAS 2009, ACT 2009, NT 2004)
- Privacy Act 1988Privacy Act 1988 (Cth)
- Security of paymentBuilding and Construction Industry Security of Payment Act 2009 (Tas)
- GDPRGeneral Data Protection Regulation
- NZ CCA 2002Construction Contracts Act 2002 (NZ), 2002 No 46, as amended 2015 and 2023
- Privacy Act 2020 (NZ)Privacy Act 2020 (NZ)
- HGCRA 1996 Part IIHousing Grants, Construction and Regeneration Act 1996, Part II (as amended by LDEDCA 2009)
- SI 1998/649Scheme for Construction Contracts (England and Wales) Regulations 1998
- UK GDPRUK GDPR and Data Protection Act 2018
- AIA G702/G703Application and Certificate for Payment; Continuation Sheet
Connectors
On the roadmap
Systems in the planned connector rollout that can fill this register. Partial means the system holds only some of its fields.
- SitematePartial
Fields
26 fields: 6 required, 20 optional.
Required
Every record carries these fields.
- projectNumber
The project or job the extra work was done on.
Example:
8101- work_dateDate
The calendar day the dayworks were performed, falling back to the diary date.
Example:
2026-07-14- descriptionText
The works performed.
Example:
Additional kerb and channel removal due to unforeseen uti…- external_idText
The source row's own identifier.
Example:
DWD-2026-0031- occurred_atDate and time
When the docket was submitted.
Example:
2026-07-14T16:30:00Z- source_systemText
Which bound system emitted the row.
Example:
ASSIGNAR
Optional
Present when the source system records them.
- rateText
The agreed dayworks rate.
Example:
62.00- assetText
The plant or equipment used.
Example:
9302- hoursDecimal number
Hours of extra work.
Example:
8.5- amountDecimal number
The docket total.
Example:
4820- workerNumber
The worker the docket is attributed to.
Example:
5503- currencyText
The currency of
rate/amountExample:
AUD- narrativeGroup of fields
The source form responses.
- signatureText
The client sign-off on the docket.
Example:
T. Aldous- tax_basisText
Whether
rate/amountinclude GST/VAT.Example:
GST exclusive- delay_daysDecimal number
Estimated delay, in days, attributable to the extra work.
Example:
0.5- attachmentsText
Photo evidence attached to the docket.
- creator_nameText
Who filled the docket in.
Example:
Aaron Patel- project_numberText
The human project number quoted on the docket.
- source_form_idNumber
The id of the form template that produced the row.
Example:
4410- client_referenceText
The client's own docket or PO reference.
Example:
CHRC-DW-014- financial_periodText
The period the work is attributed to.
Example:
2026-07- source_form_titleText
The title of the form template that produced the row.
Example:
Day Works Docket- claimable_under_sopTrue or false
Whether the amount may be included in a Security-of-Payment claim in the governing jurisdiction.
Example:
true- client_representativeText
The client's authorised representative.
Example:
T. Aldous- contractor_representativeText
The contractor's authorised representative.
Example:
Aaron Patel
Example record
A sample from Bridgeworks Group, Demiton's demonstration company. The values are illustrative; the shape is exactly what the contract describes.
{ "amount": 4820, "asset": "9302", "claimable_under_sop": true, "client_reference": "CHRC-DW-014", "client_representative": "T. Aldous", "contractor_representative": "Aaron Patel", "creator_name": "Aaron Patel", "currency": "AUD", "delay_days": 0.5, "description": "Additional kerb and channel removal due to unforeseen utility conflict", "external_id": "DWD-2026-0031", "financial_period": "2026-07", "hours": 8.5, "narrative": { "work_performed": "Excavated and relocated unmarked stormwater line" }, "occurred_at": "2026-07-14T16:30:00Z", "project": 8101, "rate": "62.00", "signature": "T. Aldous", "source_form_id": 4410, "source_form_title": "Day Works Docket", "source_system": "ASSIGNAR", "tax_basis": "GST exclusive", "work_date": "2026-07-14", "worker": 5503}Version history
- v2 (current)
- v1
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/day_works_docket/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.