Book a demo
Login
An engineering transmittal is the formal record used to send controlled engineering documents — such as drawings, specifications, datasheets, calculations, and vendor documents — between parties on a capital project. It records what was sent, when it was sent, who sent and received it, why it was issued, and the revision and status of each document.
A transmittal therefore acts as more than a delivery note. It creates an auditable record of document exchange between owner-operators, EPC contractors, engineering disciplines, suppliers, and vendors, helping teams establish exactly which version of a document was issued to which party and when.
On large projects across oil, gas & LNG, chemical & process, utilities, pharmaceutical, shipping, and mining & metals, thousands of documents may pass between multiple organizations. Without controlled transmittals, it becomes difficult to establish whether the correct revision was actually delivered, reviewed, acknowledged, or approved.
A typical engineering transmittal contains:
Together, these fields create a controlled record not only of the files that were transferred, but of the state and purpose of those documents at the moment they were issued.
Engineering projects commonly distinguish between incoming and outgoing transmittals.
An incoming transmittal records documents received from another organization, such as a supplier sending vendor documentation to an EPC contractor. An outgoing transmittal records documents formally issued by the organization to another project participant.
Maintaining both sides of the exchange gives the project a traceable history of information moving between organizations and helps document controllers determine whether expected documents have been received, reviewed, and responded to.
A transmittal should identify the specific revision of every document being issued. This is critical because engineering documents change continuously during design, procurement, construction, and commissioning.
Simply knowing that a drawing was sent is not enough. The project must be able to establish which revision was sent, at what status, to whom, and on what date.
This becomes particularly important when documents progress through statuses such as Issued for Review, Issued for Approval, and Issued for Construction. A reliable transmittal history reduces the risk of contractors or suppliers working from superseded information.
A transmittal and a document register serve different purposes.
The document register is the master record of project documents and normally shows their current revision and status. An engineering transmittal records a specific exchange of one or more of those documents between project parties at a particular point in time.
The document register tells you what the current document is. The transmittal history tells you what was sent, to whom, when, and at which revision.
For reliable engineering document management, the two should remain connected rather than being maintained as separate, manually reconciled records.
Transmittal records provide evidence of how engineering information moved through a project and when specific revisions were formally issued.
This becomes especially important during document handover, when an owner-operator needs to establish that required documentation was delivered and that the final records correspond to the approved or as-built condition.
Missing or inconsistent transmittal histories can make it difficult to determine whether a required document was never delivered, was delivered under a different number, or exists only as an obsolete revision.
For EPC contractors, controlled transmittals also provide evidence that contractual document-delivery obligations were fulfilled.
Transmittals can be managed manually through email and spreadsheets, but this becomes increasingly difficult as the number of documents, revisions, suppliers, and project organizations grows.
An engineering transmittal solution can automate the creation and numbering of transmittals, associate documents with their correct revisions, control recipient lists, record acknowledgements, and maintain a searchable history of incoming and outgoing exchanges.
More importantly, the transmittal workflow can remain connected to the underlying document register instead of becoming a separate spreadsheet or email archive that gradually falls out of sync with the project documentation.
For asset-intensive projects, document control does not end with knowing that a file was transmitted.
Engineering documents often describe specific equipment, instruments, packages, or systems. Those documents should therefore remain connected to the relevant records in the Master Tag Register (MTR).
This allows an owner-operator to trace not only the document's revision and transmittal history, but also the physical assets and tags the document describes.
That relationship becomes particularly valuable when preparing as-built documentation and transferring engineering information into operations and maintenance systems.
Sharecat connects engineering transmittals directly to the underlying document, revision, status, and asset information.
Instead of maintaining a standalone transmittal log that can drift out of sync with the document register, each exchange remains associated with the controlled engineering records it contains. Documents can also remain connected to their associated tags and equipment data.
This gives owner-operators, EPC contractors, and suppliers a traceable record of what was sent, which revision was sent, why it was issued, who received it, and which assets the information relates to — from engineering and procurement through construction, commissioning, and final handover.
What is an engineering transmittal?
An engineering transmittal is the formal record accompanying the transfer of engineering documents between project parties. It records the documents being sent, their revisions and statuses, the sender and recipient, the date, and the purpose of the transmission.
What is the difference between a transmittal and a document register?
A document register shows the master list and current state of project documents. A transmittal records a particular exchange of documents at a specific point in time.
What is the difference between incoming and outgoing transmittals?
An incoming transmittal records documents received from another project organization. An outgoing transmittal records documents formally issued to another organization.
Why are revision numbers important on a transmittal?
Because a document may be issued many times during a project. Recording the revision establishes exactly which version the recipient received and helps prevent work from being performed against superseded information.
Do engineering transmittals need acknowledgement?
Depending on the project's document-control procedure, acknowledgement may be required to confirm that the recipient received the package. Electronic transmittal systems can record receipt and acknowledgement as part of the audit trail.
What is engineering transmittal software?
Engineering transmittal software manages the creation, issue, receipt, tracking, and history of document transmittals. More advanced systems connect transmittals directly to document revisions, statuses, workflows, and related engineering data.
ISO
27001
Certified
