Project outcome
A project's actual financial outcome at close-out or a reporting point.
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
- 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
12 fields: 9 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- financial_periodText
Reporting period the snapshot is cut at.
Example:
2026-07- occurred_atDate
Date the outcome asserts (min of period-28 and today)
Example:
2026-07-31- margin_pctDecimal number
Latest project margin at the reporting cut.
Example:
8.4- cost_growth_pctDecimal number
Cost overrun versus budget at the cut.
Example:
2.1- revenue_actualDecimal number
Revenue recognised to date; cumulative.
Example:
1620000- source_systemText
Provenance; always
DERIVEDfor this shelf.Example:
D365_BUSINESS_CENTRAL- external_idText
Dedup key
{project}:{period}; one upsert per project per month.Example:
po-BWG-2025-001-202607- recorded_atDate and time
When the fact was written.
Example:
2026-08-03T05:00:00Z
Optional
Present when the source system records them.
- legal_entityText
Owning BC company for multi-entity orgs.
- customerText
Client the project is for.
Example:
Central Highlands Regional Council
Defined by each organisation
Their contents come from the organisation's own forms or systems, so they differ between organisations.
- currencyText
Unit
revenue_actualis expressed in.Example:
AUD
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"}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/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 keep current from them, on your data, in a 30-minute call.