Transmittals Explained: How Documents Move Between Contractor & Client
An approved document on a desk hasn't done its job yet — it needs a formal record proving it was sent, received, and acknowledged. That record is called a transmittal.
Many engineers think of transmittals as a formality — a cover sheet attached to an email. In reality, a transmittal is a legal and contractual record. This article breaks down what a transmittal contains, why it matters, and how it's used correctly.
| Doc No. | Title | Rev |
|---|---|---|
| PV-INS-DWG-0142 | Inspection Layout | B |
| PV-INS-PRC-0011 | Test Procedure | A |
What a Transmittal Actually Contains
A properly structured transmittal includes these key fields:
- Transmittal number — its own unique identifier, separate from document numbers
- Sender and recipient — the specific parties in this exchange
- Date issued — establishing exactly when documents were sent
- Purpose code — the reason documents are being sent
- List of documents — every doc number, title, and revision included
Understanding Purpose Codes
The purpose code tells the recipient exactly what's expected. Click each card below:
A For Approval
The recipient must formally review and approve before the document can be used.
R For Review / Comment
Feedback is requested, but formal approval isn't required at this stage.
I For Information
No action required — the document is shared for awareness only.
C For Construction
The document is approved and ready for field use.
AB As-Built
A final record showing what was actually constructed, issued at project close-out.
Using the wrong purpose code causes real confusion — marking a document "For Information" when it requires approval can mean it never gets reviewed, creating a gap that surfaces much later.
Why Transmittals Matter Contractually
On most contracts, formal notice and document exchange requirements are written directly into the terms. A transmittal satisfies these requirements — proving a specific document was delivered to a specific party by a specific date.
Demonstrating that a design change was communicated before construction proceeded.
Proving an approval request was submitted within the contractually required review period.
Resolving disputes over who had access to which revision, and when.
An email with an attachment doesn't carry the same weight — it's easy to lose, lacks consistent numbering, and rarely gets logged in a central register.
The Transmittal Register
Just as documents are tracked in a Master Document Register, transmittals are logged in their own register — recording every transmittal issued, its recipient, purpose, and current status. This allows a document controller to answer, at any point, exactly which documents were sent to which party and whether a response is still outstanding.
A transmittal is far more than a cover note — it's the formal, traceable record that proves a document exchange took place, when it happened, and what response was expected. Understanding purpose codes correctly prevents real confusion on site. Treating transmittals as a formality is one of the most common — and avoidable — document control mistakes.
Comments
Post a Comment