Change event
Change event is one of Demiton's published registers for Australian civil construction. The early warning of a potential change, before it is priced as a variation. 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
change_eventUse 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
- v2 (2.0.2)Current version.
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 Contract (superseded)
- 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
- Directive 2014/24/EUDirective 2014/24/EU on public procurement
- Procurement Act 2023Procurement Act 2023 (c. 54) and Procurement Regulations 2024 (SI 2024/692)
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.
- titleText
What the potential change is.
Example:
Extend rock armour toe beyond original alignment- statusText
Where the event is in its lifecycle.
Example:
pending- projectText
The project the change event is on.
Example:
BWG-2025-002- external_idText
The source system's own change event id.
Example:
var-2026-0022
Optional
Present when the source system records them.
- scopeText
Whether the change is in or out of the contract scope.
Example:
Moore Park Beach Coastal Protection - rock armour toe ext…- numberText
The change event number.
Example:
VAR-002- originText
What raised the event, e.g. an RFI or an instruction.
Example:
site_instruction- currencycurrency
The currency of the impact amounts.
Example:
AUD- raised_atDate and time
When the event was raised.
Example:
2026-07-09T09:15:00+10:00- raised_byText
Who raised the event.
Example:
Mia Okafor- change_typeText
The kind of change.
Example:
variation- cost_impactMoney amount
The estimated effect on cost.
Example:
28000- descriptionText
What happened.
Example:
Extend rock armour placement 40m further north than the t…- change_itemsList
The event's itemised cost, budget and revenue lines.
- accepted_daysWhole number
The programme extension accepted.
Example:
0- budget_impactMoney amount
The estimated effect on budget.
Example:
28000- change_reasonText
Why the change arose.
Example:
Erosion beyond original survey extent identified during e…- prime_contractText
The head contract the event is estimated against.
Example:
TEN/2963- requested_daysWhole number
The programme extension sought.
Example:
4- revenue_impactMoney amount
The estimated effect on revenue.
Example:
28000
Example record
A sample from Bridgeworks Group, Demiton's demonstration company. The values are illustrative; the shape is exactly what the contract describes.
{ "accepted_days": 0, "budget_impact": 28000, "change_items": [ "Rock armour supply", "Additional cartage" ], "change_reason": "Erosion beyond original survey extent identified during earthworks", "change_type": "variation", "cost_impact": 28000, "currency": "AUD", "description": "Extend rock armour placement 40m further north than the tendered alignment to protect the exposed dune toe.", "external_id": "var-2026-0022", "number": "VAR-002", "origin": "site_instruction", "prime_contract": "TEN/2963", "project": "BWG-2025-002", "raised_at": "2026-07-09T09:15:00+10:00", "raised_by": "Mia Okafor", "requested_days": 4, "revenue_impact": 28000, "scope": "Moore Park Beach Coastal Protection - rock armour toe extension", "source_system": "D365_BUSINESS_CENTRAL", "status": "pending", "title": "Extend rock armour toe beyond original alignment"}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/change_event/v2.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.