Tendered rate observation
One priced line from a tender you submitted: item, unit, rate and quantity.
Part of Opportunities in the register catalog.
- Register ID
tendered_rate_observationUse 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
- 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
15 fields: 4 required, 11 optional.
Required
Every record carries these fields.
- work_itemText
The description of the priced line, as written in the submission.
Example:
Excavate and cart to spoil, unclassified material, 0-3m d…- rateNumber
The tendered unit rate offered.
Example:
38.5- unit_normalizedText
The controlled unit of measure the rate is per.
Example:
m3- citationGroup of fields
The source workbook path, sheet name and line reference.
Optional
Present when the source system records them.
- qtyNumber
The quantity on the priced line, when the template exposes one.
Example:
12500- unit_rawText
The unit exactly as written in the workbook.
Example:
m3- gst_inclusiveTrue or false
Whether
rateis inclusive of GST.Example:
false- rate_familyText
The rate-book bucket, classified from the sheet name and unit.
Example:
earthworks- bandGroup of fields
A depth/length band extracted from the description (e.g. "up to 23.0 metres")
- derived_rate_per_mNumber
rate / band.maxfor an each-unit line with a band.- compositeTrue or false
The unit could not be normalised to a known alias, so the rate is a composite.
Example:
false- revisionText
The submission revision the agent recorded.
Example:
Rev2- counterpartyText
The party the submission was made to.
Example:
Department of Transport and Main Roads- work_activityText
A v2 taxonomy classification of the work.
Example:
earthworks- submitted_atDate and time
When the priced schedule was submitted.
Example:
2026-06-20T00:00:00Z
Example record
A sample from Bridgeworks Group, Demiton's demonstration company. The values are illustrative; the shape is exactly what the contract describes.
{ "citation": { "line": 42, "sheet": "Earthworks", "workbook": "RAMC_South_Coast_Priced_Schedule_Rev2.xlsx" }, "composite": false, "counterparty": "Department of Transport and Main Roads", "gst_inclusive": false, "qty": 12500, "rate": 38.5, "rate_family": "earthworks", "revision": "Rev2", "submitted_at": "2026-06-20T00:00:00Z", "unit_normalized": "m3", "unit_raw": "m3", "work_activity": "earthworks", "work_item": "Excavate and cart to spoil, unclassified material, 0-3m depth"}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/tendered_rate_observation/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.