Skip to content
Demiton

Sor verification tendered

The same schedule-of-rates check run on tendered jobs, compared against your own submitted rates.

Part of Contracts in the register catalog.

Register ID
sor_verification_tenderedUse 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
v1Current version.

Standards

This register holds records these standards and laws ask for. Holding them does not by itself certify compliance.

  • ISO 19650Information management using building information modellingInternational

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

24 fields: 10 required, 14 optional.

Required

Every record carries these fields.

opportunity_refText

The opportunity number/name the verified tender belongs to; the only human key that ties the fact to the spine entity it is anchored on.

Example: ITT2529

subject_entity_idWhole number

The opportunity spine entity the fact is anchored on. Recorded because it is the shelf's *only* axis: entity_id=entity.id with an empty CoordinateBundle (line 812), and there is no project_id/period column populated at all.

Example: 1

statusText

The verification outcome for the run.

Example: completed

review_stateText

Every value on this shelf is agent-derived and awaits human reconciliation; the single legal value today.

Example: pending_review

line_itemsList

The verified line items — the substance of the record and the only part the reader uses.

agent_run_idNumber

The run that produced this verification; the citation's external_ref and origin_uri are built from it.

Example: 55231

summaryText

One-paragraph rendered narrative (counts of consistent/discrepancy/unverified and number compared against the tendered submission).

Example: 2 of 2 SOR line items verified against measured quantitie…

line_items[].item_refText

The client SoR item reference for a verified line.

Example: SOR-3.02

line_items[].verdictText

The per-line verification verdict.

Example: match

line_items[].sor_qtyNumber

The line's own UoM (line_items[].uom, a string)

Example: 1200

Optional

Present when the source system records them.

baseline_provenanceText

Who issued the parsed pricing baseline. client_issued is the only clean value; pca_internal is a fallback that requires a warning finding.

pricing_documentGroup of fields

The document the SoR line items were transcribed from. Null when no pricing document was parsed.

tendered_documentGroup of fields

—.

tendered_document.revisionText

The revision label of the tendered submission, e.g. Rev 3; not an ordering or a status.

baseline_document_identifierText

An appointment/asset-scoped identifier for the client-issued baseline container.

revision_ordering_conventionText

A code-set identifier saying how to order revisions and status values (e.g. an annex or project execution-plan identifier).

line_items[].measured_qtyNumber

Same as line_items[].uom

Example: 1180

line_items[].variance_pctNumberUnit: per cent

Server-computed variance of the measured value against the SoR quantity.

line_items[].verification_strengthText

How independent the corroborating derivation is.

Example: high

line_items[].tendered_comparison.tendered_qtyNumber

line_items[].uom (with tendered_unit recorded verbatim)

line_items[].tendered_comparison.matched_byText

How the line was matched into the tendered submission.

findingsListUnit: warning\

Discrepancy, title: string, detail: string}`

Example record

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

sor_verification_tendered.example.json
{
"agent_run_id": 55231,
"line_items": [
{
"item_ref": "SOR-3.02",
"measured_qty": 1180,
"sor_qty": 1200,
"verdict": "match",
"verification_strength": "high"
},
{
"item_ref": "SOR-3.05",
"measured_qty": 395,
"sor_qty": 340,
"variance_pct": 16.2,
"verdict": "variance",
"verification_strength": "medium"
}
],
"opportunity_ref": "ITT2529",
"review_state": "pending_review",
"status": "completed",
"subject_entity_id": 1,
"summary": "2 of 2 SOR line items verified against measured quantities; one minor variance flagged."
}

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/sor_verification_tendered/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 keep current from them, on your data, in a 30-minute call.

Book a 30-minute callStart free