Site requisitions
Site requisitions for materials, plant or resources, by worker and project.
Part of Projects in the register catalog.
- Register ID
site_requisitionsUse 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
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: 3 required, 10 optional, 2 defined by each organisation.
Required
Every record carries these fields.
- external_idText
Assignar form-result id; substrate source identity and idempotency key.
Example:
ASGN-FR-71022- occurred_atDate and time
Submission time of the requisition — the episodic event time.
Example:
2026-06-11T07:00:00- workerNumber
The worker the requisition is attributed to.
Example:
5505
Optional
Present when the source system records them.
- projectNumber
The project the request serves, when the form captured it.
Example:
8101- financial_periodText
The accounting period the request falls in; a declared coordinate, not present in the source payload.
Example:
2026-06- form_idWhole number
Which Assignar requisition form template produced the row — provenance for a title-pattern match that can sweep renamed forms.
- date_of_requestDate
The date the requester raised the request.
Example:
2026-06-11- date_requiredDate
The date the requested items are needed on site.
Example:
2026-06-13- delivery_addressText
Where the requested items are to be delivered.
Example:
Emerald Street site compound, Yamala QLD 4702- site_addressText
The site address, where distinct from the delivery address.
- project_taskText
The project task/activity the request is for.
Example:
Pavement base course- commentsText
Free-text note from the requester.
Example:
Needed before Friday pour- source_modified_atDate and time
Last modification at source; the form_pattern delta cursor.
Defined by each organisation
Their contents come from the organisation's own forms or systems, so they differ between organisations.
- requested_itemsList
The plant/equipment and staff the requisition asks for, as an itemised list rather than one top-level key per named person or machine.
- custom_questionsGroup of fields
The residual tenant form answers, including the form's own approval/authorisation answers.
Example record
A sample from Bridgeworks Group, Demiton's demonstration company. The values are illustrative; the shape is exactly what the contract describes.
{ "comments": "Needed before Friday pour", "date_of_request": "2026-06-11", "date_required": "2026-06-13", "delivery_address": "Emerald Street site compound, Yamala QLD 4702", "external_id": "ASGN-FR-71022", "financial_period": "2026-06", "occurred_at": "2026-06-11T07:00:00", "project": 8101, "project_task": "Pavement base course", "requested_items": [ { "item": "Compaction plate", "quantity": 2 }, { "item": "20mm road base", "quantity": 40, "unit": "tonnes" } ], "worker": 5505}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/site_requisitions/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.