Document transmittal
Document transmittal is one of Demiton's published registers for Australian civil construction. Transmittals recording which documents went to whom, and when. 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 Documents in the register catalog.
- Register ID
document_transmittalUse this name to ask for the register. The API calls it a shelf ID.- Status
- PlannedDefined ahead of the connector that will fill it.
- Data
- OrganisationPrivate to each organisation's own workspace.
- Version
- v1 (1.0.3)Current version.
Standards
This register's contract was designed against these standards and laws. Holding these records does not by itself certify compliance.
- ISO 19650Organization and digitization of information about buildings and civil engineering works, including BIM - Information management using BIM - Part 1: Concepts and principles
- ISO 19650Information management using BIM - Part 2: Delivery phase of the assets
- Privacy Act 1988Privacy Act 1988 - Australian Privacy Principles
- ISO 19650European adoptions of ISO 19650-1/-2 (CEN)
- GDPRGeneral Data Protection Regulation
- ISO 19650Information management using building information modelling - Part 1: Concepts and principles
- ISO 19650Information management using building information modelling - Part 2: Delivery phase of the assets
- Privacy Act 2020 (NZ)Privacy Act 2020 - Information Privacy Principles
- ISO 19650UK adoptions of ISO 19650-1/-2 (UK BIM Framework, now IMI Framework)
- ISO 19650UK National Annex to BS EN ISO 19650-2 (status and revision codes)
- UK GDPRUK General Data Protection Regulation with Data Protection Act 2018
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
20 fields: 6 required, 14 optional.
Required
Every record carries these fields.
- numberText
The transmittal number.
Example:
TRN-0021- statusText
Whether it is outstanding, responded or closed.
Example:
outstanding- projectText
The project the transmittal is on.
Example:
BWG-2025-001- sent_atDate and time
When the transmittal was issued.
Example:
2026-06-20T09:15:00- subjectText
What the transmittal is.
Example:
Issue for Construction - Pavement Design Drawings Rev C- external_idText
The source system's own id for the transmittal.
Example:
SP-TRN-2201
Optional
Present when the source system records them.
- threadText
The correspondence thread it belongs to.
- revisionWhole number
The submittal revision.
- documentsList
The documents transmitted, each with number and revision.
- from_partyText
Who sent the transmittal.
Example:
Bridgeworks Group Pty Ltd- to_partiesList
Who received it, with the distribution type.
- in_reply_toText
The transmittal this one answers.
- confidentialTrue or false
Whether the transmittal is confidential.
- response_dueDate
When a response is due.
Example:
2026-07-04- approval_statusText
The approval state of the transmittal.
- reason_for_issueText
Why the documents were issued.
- response_requiredTrue or false
Whether a response is owed.
Example:
true- correspondence_typeText
The kind of correspondence, e.g. transmittal or submittal.
Example:
transmittal- specification_sectionText
The specification section the documents address.
- responsible_contractorText
The contractor responsible for the submission.
Example record
A sample from Bridgeworks Group, Demiton's demonstration company. The values are illustrative; the shape is exactly what the contract describes.
{ "correspondence_type": "transmittal", "documents": [ { "number": "BWG-001-CIV-201", "revision": "C" } ], "external_id": "SP-TRN-2201", "from_party": "Bridgeworks Group Pty Ltd", "number": "TRN-0021", "project": "BWG-2025-001", "response_due": "2026-07-04", "response_required": true, "sent_at": "2026-06-20T09:15:00", "source_system": "SHAREPOINT", "status": "outstanding", "subject": "Issue for Construction - Pavement Design Drawings Rev C", "to_parties": [ { "name": "Central Highlands Regional Council", "type": "for_approval" } ]}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/document_transmittal/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 fill from them, on your data, in a 30-minute call.