Sor verification

Sor verification is one of Demiton's published registers for Australian civil construction. A client's schedule of rates checked against the tender drawings by independent measurement. 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 Contracts in the register catalog.

Register ID

sor_verificationUse 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.2)Current version.

Download JSON SchemaSee an example record

Standards

This register's contract was designed against these standards and laws. Holding these records does not by itself certify compliance.

• AS 1726:2017Geotechnical site investigationsAustralia · 2017 · paywalled, from a secondary description
• AS 5488.1:2022Classification of Subsurface Utility Information (SUI)Australia · 2022 (supersedes 2019) · paywalled, from a secondary description
• ISO 19650Organization and digitization of information about buildings and civil engineering works - Part 1 concepts and principles (identical to ISO 19650-1:2018)Australia · 2019 · paywalled, from a secondary description
• ISO 19650Organization and digitization of information - Part 2 delivery phase of the assets (identical to ISO 19650-2:2018)Australia · 2019 · paywalled, from a secondary description
• ICMS 3International Cost Management StandardInternational · 3rd edition (2021) · public summary
• ISO 19650Organization and digitization of information about buildings and civil engineering works, including BIM - Parts 1 and 2International · 2018 · paywalled, from a secondary description

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

28 fields: 26 required, 2 optional.

Required

Every record carries these fields.

statusText

Overall verification outcome for the opportunity.

Example: completed

summaryText

One-sentence human-readable statement of the result; also the fact's content

Example: SOR pricing verification for ITT2529 streetscape line ite…

findingsList

Discrepancies, warnings and synthesized advisories.

line_itemsList

The schedule rows verified.

agent_run_idNumber

Provenance: which AgentRun produced the fact.

Example: 90211

review_stateText

Human-review marker; the fact is agent-proposed, not reconciled.

Example: pending_review

opportunity_refText

The opportunity number the verification is anchored to.

Example: OPP-2451

findings[].titleText

Finding title.

Example: Asphalt quantity above SOR

line_items[].uomText

Unit of measure that makes the quantity meaningful and comparable.

Example: m2

pricing_documentGroup of fields

The baseline document the quantities were read from.

findings[].detailText

Finding detail.

Example: Plan takeoff for item 3.14 exceeds the SOR quantity by 6.…

findings[].severityText

Finding severity.

Example: medium

line_items[].sor_qtyNumberUnit: row uom

The client's claimed baseline quantity.

Example: 2400

line_items[].verdictText

Per-row outcome.

Example: over_quantity

line_items[].item_refText

Schedule item identifier.

Example: 3.14

line_items[].derivationsList

Each independent derivation for the row.

line_items[].descriptionText

Item description.

Example: Supply and lay 40mm asphalt wearing course

line_items[].variance_pctNumberUnit: percent

Server-computed (measured - claimed) / claimed; server owns its absence.

Example: 6.25

line_items[].derivations[].unitText

Unit of the derived value, matched against the row uom

Example: m2

line_items[].derivations[].valueNumberUnit: derivation unit

The derived quantity.

Example: 2550

line_items[].derivations[].methodText

How the value was derived.

Example: plan_takeoff

line_items[].derivations[].caveatsList

The measurement tool's own caveats, verbatim; a caveat qualifies a quantity and must not be lost.

line_items[].verification_strengthText

Server-computed independence of the corroboration — stops "verified" overclaiming.

Example: strong

line_items[].derivations[].citationText

Where the derivation came from (document/page/cell)

Example: Drawing C-014 Rev B

line_items[].derivations[].confidenceText

The measurement tool's own confidence, copied verbatim.

Example: high

line_items[].derivations[].evidence_urlText

Overlay evidence image produced by this run's tools.

Example: https://example.com/docs/ITT2529/C-014.pdf

Optional

Present when the source system records them.

baseline_provenanceText

Who issued the parsed baseline; pca_internal is a trust caveat.

line_items[].derivations[].methodologyText

The tool's methodology text, verbatim; prose, not a schema constraint.

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.example.json

{
  "agent_run_id": 90211,
  "findings": [
    {
      "detail": "Plan takeoff for item 3.14 exceeds the SOR quantity by 6.25%; review before submission.",
      "severity": "medium",
      "title": "Asphalt quantity above SOR"
    }
  ],
  "line_items": [
    {
      "derivations": [
        {
          "caveats": [
            "kerb returns excluded"
          ],
          "citation": "Drawing C-014 Rev B",
          "confidence": "high",
          "evidence_url": "https://example.com/docs/ITT2529/C-014.pdf",
          "method": "plan_takeoff",
          "unit": "m2",
          "value": 2550
        }
      ],
      "description": "Supply and lay 40mm asphalt wearing course",
      "item_ref": "3.14",
      "sor_qty": 2400,
      "uom": "m2",
      "variance_pct": 6.25,
      "verdict": "over_quantity",
      "verification_strength": "strong"
    }
  ],
  "opportunity_ref": "OPP-2451",
  "pricing_document": {
    "file_name": "ITT2529_Priced_BoQ.xlsx"
  },
  "review_state": "pending_review",
  "status": "completed",
  "summary": "SOR pricing verification for ITT2529 streetscape line items shows one moderate quantity variance."
}

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/v1.json

Show the full JSON Schema

Loading the schema…