Project outcome
Project outcome is one of Demiton's published registers for Australian civil construction. A project's actual financial outcome at close-out or a reporting point. 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
project_outcomeUse 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
- DeclaredDefined, and fills when a source produces its first record.
- 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.
- A New Tax System (Goods and Services Tax) Act 1999 (Cth)GST and tax invoice rules (ATO guidance)
- AS 2124General Conditions of Contract
- AS 4000General Conditions of Contract
- AS 4000General Conditions of Contract (construct only)
- AS 4902General Conditions of Contract for Design and Construct
- Security of paymentQLD security of payment - excluded amounts
- Security of paymentWA security of payment - excluded amounts
- Security of paymentNSW security of payment - excluded amounts
- Security of paymentVIC security of payment - excluded amounts
- Council Directive 2006/112/ECVAT Directive
- Construction Contracts Act 2002 (NZ)Construction Contracts Act 2002 (2002 No 46)
- Goods and Services Tax Act 1985 (NZ)GST taxable supply information
- Housing Grants, Construction and Regeneration Act 1996 Part IIHGCRA 1996 Part II (Payment), as amended by LDEDCA 2009
- SI 1998/649Scheme for Construction Contracts (England and Wales) Regulations 1998
- AIA G702/G703Application and Certificate for Payment / Continuation Sheet
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
11 fields: 8 required, 2 optional, 1 defined by each organisation.
Required
Every record carries these fields.
- projectText
The project the outcome is for; asserted via
resolved_coordinates, not a coordinate.Example:
BWG-2025-001- margin_pctDecimal number
Latest project margin at the reporting cut.
Example:
8.4- external_idText
Dedup key
{project}:{period}; one upsert per project per month.Example:
po-BWG-2025-001-202607- occurred_atDate
Date the outcome asserts (min of period-28 and today)
Example:
2026-07-31- recorded_atDate and time
When the fact was written.
Example:
2026-08-03T05:00:00Z- revenue_actualDecimal number
Revenue recognised to date; cumulative.
Example:
1620000- cost_growth_pctDecimal number
Cost overrun versus budget at the cut.
Example:
2.1- financial_periodText
Reporting period the snapshot is cut at.
Example:
2026-07
Optional
Present when the source system records them.
- customerText
Client the project is for.
Example:
Central Highlands Regional Council- legal_entityText
Owning BC company for multi-entity orgs.
Defined by each organisation
Their contents come from the organisation's own forms or systems, so they differ between organisations.
- currencycurrency
Unit
revenue_actualis expressed in.Example:
AUD
Filed against
Records are indexed along these dimensions, so they can be asked for by any of them.
- Legal entitycontext for the record, from
When known - Currencycontext for the record, from
When known - Customercontext for the record, from
When known - Financial periodcontext for the record, from
Always set
Example record
A sample from Bridgeworks Group, Demiton's demonstration company. The values are illustrative; the shape is exactly what the contract describes.
{ "cost_growth_pct": 2.1, "currency": "AUD", "customer": "Central Highlands Regional Council", "external_id": "po-BWG-2025-001-202607", "financial_period": "2026-07", "margin_pct": 8.4, "occurred_at": "2026-07-31", "project": "BWG-2025-001", "recorded_at": "2026-08-03T05:00:00Z", "revenue_actual": 1620000, "source_system": "D365_BUSINESS_CENTRAL"}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/project_outcome/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.