Book a demo
Login
An engineering transmittal is the formal record used to send engineering documents — drawings, specifications, datasheets — between parties on a capital project, such as from an EPC contractor to an owner-operator, or between engineering disciplines. It captures what was sent, when, by whom, to whom, and at what revision and status, creating an auditable trail of every document exchange throughout the project.
On large capital projects across oil, gas & LNG, chemical & process, utilities, pharmaceutical, shipping, and mining & metals, transmittals can number in the thousands, and a reliable transmittal record is often the only way to reconstruct exactly what documentation was issued, to whom, and at what revision.
A transmittal typically records a unique transmittal number, the sender and recipient organizations, the date of issue, the list of documents included with their revision and status (for example, Issued for Construction or Issued for Approval), the purpose of the transmission (for review, for approval, for information), and any required response deadline.
The transmittal record is often the definitive evidence of when a document reached a specific status and who received it — which becomes important both for tracking contractual document delivery obligations during the project and for reconstructing the documentation history at handover. Gaps or inconsistencies in transmittal records are a common source of disputes over whether required documents were actually delivered on schedule.
Many projects still manage transmittals through email and spreadsheets, which becomes difficult to sustain once a project reaches hundreds or thousands of documents across dozens of contractors and disciplines. A dedicated engineering transmittal solution automates transmittal creation, keeps the transmittal log synchronized with the underlying document register and revision statuses, and gives every stakeholder a single, searchable record of what was sent and received — instead of reconstructing the history from email threads after the fact.
Transmittals should never exist in isolation from the broader document control record: each transmitted document should be traceable back to its entry in the document register, its current revision and status, and — where applicable — the tags it relates to in the Master Tag Register. Disconnected transmittal logs are one of the reasons document handover packages arrive at project close with documents that cannot be matched to the equipment they describe.
Sharecat provides a structured engineering transmittal workflow that is directly connected to the underlying document register: every transmittal references the correct document revisions and statuses, and every transmitted document remains linked to its associated tags. This gives owner-operators and EPCs a single, audit-ready record of document exchange throughout the project — rather than a transmittal log that has drifted out of sync with the documents it describes.
What is the difference between a transmittal and a document register?
The document register is the master list of all project documents and their current revision and status. A transmittal is a record of a specific exchange of one or more of those documents between parties at a point in time — the register shows the current state, the transmittal shows the history of delivery.
Do I need dedicated engineering transmittal software?
For any project with more than a handful of documents and stakeholders, manual transmittal tracking through email and spreadsheets becomes error-prone and difficult to audit. A dedicated transmittal solution that stays synchronized with the document register significantly reduces the risk of disputed or lost document deliveries.
ISO
27001
Certified
