Tender incoming

Client-issued documents for a tender you are estimating: brief, scope, pricing schedule.

Part of Opportunities in the register catalog.

Register ID

tender_incomingUse 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.

Download JSON SchemaSee an example record

Connectors

Connected today

Demiton keeps this register current from these systems now.

• SharePoint

On the roadmap

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

• ProcorePartial

Fields

22 fields: 7 required, 15 optional.

Required

Every record carries these fields.

titleText

The tender brief's own title.

Example: ITT2529 Streetscape Upgrade - Mill & Currie Streets, Nambour

clientText

The issuing authority/principal.

Example: Sunshine Coast Council

closing_dateText

The lodgement deadline.

Example: 2026-10-02

scope_summaryText

LLM summary of the works being tendered.

Example: Streetscape renewal including footpaths, kerb and channel…

work_typesList

Normalised work categories.

source_document_file_nameText

The file the fact was extracted from.

Example: ITT2529_Invitation.pdf

source_document_pathText

The SharePoint item path/locator.

Example: SharePoint/Tenders/ITT2529

Optional

Present when the source system records them.

stateText

AU state from the folder name.

Example: QLD

addendaList

Amendments issued against the brief.

locationText

Physical location of the works from the document.

estimated_valueDecimal numberUnit: AUD (unverified — no currency field exists in the payload)

Estimated contract value where stated.

estimated_value_noteText

The value as written ("approx $1.2M")

principal_typeText

The class of issuing party.

tender_sourceText

Where the brief came from ("TfNSW BuyNSW", "email RFQ", "VendorPanel")

contract_typeText

The commercial vehicle the brief contemplates.

documents_foundList

Catalogue of files in the source folder.

has_boqTrue or false

A bill of quantities was found.

Example: true

has_scope_docTrue or false

A scope document was found.

has_invitationTrue or false

An invitation to tender was found.

Example: true

currencyText

The currency estimated_value is denominated in.

value_tax_basisText

Whether estimated_value includes tax.

value_basisText

What kind of value was extracted.

Example record

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

tender_incoming.example.json

{
  "client": "Sunshine Coast Council",
  "closing_date": "2026-10-02",
  "has_boq": true,
  "has_invitation": true,
  "scope_summary": "Streetscape renewal including footpaths, kerb and channel, and drainage upgrades along Mill and Currie Streets.",
  "source_document_file_name": "ITT2529_Invitation.pdf",
  "source_document_path": "SharePoint/Tenders/ITT2529",
  "state": "QLD",
  "title": "ITT2529 Streetscape Upgrade - Mill & Currie Streets, Nambour",
  "work_types": [
    "streetscape",
    "drainage"
  ]
}

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

Show the full JSON Schema

Loading the schema…