Skip to content
Demiton

Job progress

Job progress is one of Demiton's published registers for Australian civil construction. Job progress from your ERP: percent complete and percent invoiced. 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
job_progressUse this name to ask for the register. The API calls it a shelf ID.
Each record is
A stateThe current value of something, replaced when it changes.
Status
AvailableFilled today from connected systems, uploads or public data.
Data
OrganisationPrivate to each organisation's own workspace.
Version
v1 (1.0.3)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 ContractAustralia · 1992 (superseded) · clause Annexure Part A · paywalled, from a secondary description
  • AS 4000General Conditions of ContractAustralia · 1997 (superseded edition, still in use) · clause cl 37.1/37.2 (per commentary) · paywalled, from a secondary description
  • AS 4000General Conditions of Contract (construct only)Australia · 2025 · clause cl 37.2 (per commentary) · paywalled, from a secondary description
  • AS 4902General Conditions of Contract for Design and ConstructAustralia · 2000 (R2005); status unverified · paywalled, from a secondary description
  • Security of paymentQld security of paymentAustralia · as amended · clause s 76 · public summary
  • Security of paymentACT security of paymentAustralia · as amended · clause s 19(2) · public summary
  • Security of paymentWA security of paymentAustralia · as amended · clause ss 23(7), 25 · verified against full text
  • Security of paymentNSW security of paymentAustralia · as amended · public summary
  • Security of paymentVic security of payment (2026 reforms)Australia · as amended · clause ss 14A-14D · public summary
  • Security of paymentSA security of paymentAustralia · as amended · clause s 17(2) · public summary
  • Security of paymentTas security of paymentAustralia · as amended · clause ss 17-19 · verified against full text
  • Construction Contracts Act 2002 (NZ)Construction Contracts Act 2002 (2002 No 46)New Zealand · as at 5 Oct 2023 · clause ss 17, 20-22 · verified against full text
  • Housing Grants, Construction and Regeneration Act 1996 Part IIHGCRA 1996 Part II (Payment), as amended by LDEDCA 2009United Kingdom · as amended (2011) · clause ss 110-113 · verified against full text
  • SI 1998/649Scheme for Construction Contracts (England and Wales) Regulations 1998United Kingdom · as amended 2011 · clause paras 4-10 · verified against full text
  • AIA G702/G703Application and Certificate for Payment / Continuation SheetUnited States · 1992 (current base editions) · public summary

Connectors

Connected today

Demiton keeps this register current from these systems now.

On the roadmap

Systems in the planned connector rollout that can fill this register. Partial means the system holds only some of its fields.

  • MYOB Acumatica
  • PayappsPartial
  • Xero Accounting

Fields

10 fields: 4 required, 5 optional, 1 defined by each organisation.

Required

Every record carries these fields.

job_noText

The external BC job number, kept as the reconciliation key back to the ERP.

Example: BWG-2025-001

project_idText

The project (BC job) the KPIs belong to; the fact's subject anchor.

Example: BWG-2025-001

percent_invoicedNumberUnit: %

The share of the job claimed/invoiced to date, clamped [0, 105]

Example: 52

percent_completedNumberUnit: %

WIP / cost-recognition completion for the job, clamped to [0, 105], null when the BC WIP calc is invalid.

Example: 56.8

Optional

Present when the source system records them.

suspectGroup of fields

The raw rejected value(s) and the reason, present only when a percentage fell outside [0, 105]

job_statusText

BC's own job status text, passed through verbatim.

Example: Open

job_end_dateDateYYYY-MM-DD

BC's planned job end.

job_start_dateDateYYYY-MM-DD

BC's planned job start.

percent_overdue_planning_linesNumberUnit: %

Planning-line slippage signal on the job.

Defined by each organisation

Their contents come from the organisation's own forms or systems, so they differ between organisations.

project_managerText

The job's responsible person.

Example: Brett Hollis

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

Example record

A sample from Bridgeworks Group, Demiton's demonstration company. The values are illustrative; the shape is exactly what the contract describes.

job_progress.example.json
{
"job_no": "BWG-2025-001",
"job_status": "Open",
"percent_completed": 56.8,
"percent_invoiced": 52,
"project_id": "BWG-2025-001",
"project_manager": "Brett Hollis",
"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.

Schema URL
https://docs.demiton.io/registers/job_progress/v1.json
Show 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.

Book a 30-minute callStart free