How to manage drawing transmittals
A drawing transmittal is your formal record of which drawings, in which revision, went to whom, on which date. It's the paper trail that protects you if drawings are ever disputed.
What a Transmittal Is and Why It Matters
A transmittal is a form (paper or digital) that documents the official distribution of drawings. Every transmittal includes:
- Project name and address, so there's no confusion about which project
- Date of transmittal, when it was sent
- Sender and signature, who is sending it (usually architect, engineer, or GC)
- Recipient and contact, who it's going to (GC, subs, owner)
- List of drawings, sheet number, sheet name, revision number/date
- Purpose code, why it's being sent (For Construction, For Review, For Record, For Coordination)
- Signature of receipt, recipient acknowledges they received the drawings
Why it matters: If a dispute arises, "I didn't receive that revision," or "The drawings were unclear", the transmittal proves who received what, when. It's your protection against claims and change orders.
Transmittal Purpose Codes
Every transmittal has a purpose. Know these four:
For Construction
The drawings are approved and ready to build. This is the official release to the GC and subs. Only transmittals marked "For Construction" authorize work to proceed. Anything sent "For Review" or "For Coordination" is not construction-ready.
For Review
Drawings are sent to a recipient (often the owner, lender, or code official) for review and comment. Work cannot proceed until a "For Construction" transmittal is issued. These are draft drawings; changes are expected.
For Record
Drawings are sent to create a file copy. Typically used near project end to distribute final marked-up or "as-built" versions. These are for documentation, not construction authorization.
For Coordination
Drawings are sent to subs or trades so they can coordinate their own work. Not final approval; the receiving party should review for conflicts and submit comments. Common between MEP engineers and the general contractor.
Who Sends Transmittals and to Whom
Transmittals flow through the project hierarchy:
Architect/Engineer to GC
Architect issues "For Construction" transmittals to release drawing sets. GC acknowledges receipt (signs the transmittal). Example: "Architectural drawings, revision 2, for construction of 123 Main Street, released March 1."
GC to Subcontractors
GC distributes drawings to subs (framing, electrical, plumbing, etc.). GC prepares a transmittal listing which sheets were sent. Subs return a signed copy acknowledging receipt. This protects the GC: "We provided you the drawings, as documented by your signed transmittal."
Architect to Owner/Lender
Architect sends submittals to owner and lender "For Review" (if required by contract). These are often early coordinations before the GC release.
Revised Drawings
During construction, revised sheets are issued via transmittal. Example: "Addendum 1: Revised plumbing sheet P2 due to field change." Only the revised sheet is listed on the transmittal, not the entire set. But the revision date or number must be clear.
Transmittal Format and Key Information
Transmittals follow a standard format. Here's what must be included:
Header Section
- Transmittal Number: Sequential (T-001, T-002, etc.) for tracking
- Date: Date issued
- Project: Project name and address
- From: Sender's name, title, company, signature
- To: Recipient's name, company, address, phone
Drawing List (Table)
Each drawing included in the transmittal is listed in a table with:
- Sheet Number: A1, A2, S1, P1, etc.
- Sheet Title: Cover Sheet, Foundation Plan, Electrical Plan, etc.
- Revision Number/Date: Rev 1, or March 1, 2024
- Quantity: How many copies sent (usually 1 per recipient, but can be more)
Purpose and Notes
- Purpose Code: For Construction / For Review / For Record / For Coordination (checked or selected)
- Notes: Any special instructions. Example: "Rev 2 replaces Rev 1. Discard Rev 1." or "Plumbing drawings superseded by Addendum 1."
Signature Block
- Recipient Signature and Date: Proves the recipient got the drawings on that date
- Comments: Optional space for recipient to note any missing pages or concerns
How to Acknowledge Receipt and Manage the Log
Once you receive a transmittal, you must manage it:
Check Receipt Immediately
Count the pages. Verify all sheets listed are included. If anything is missing, note it on the transmittal and return it for correction before proceeding with the drawings.
Sign and Return
Sign the receipt block (name, title, date). Return a copy to the sender (or keep on file if digital). This is your proof that you received it. If a dispute arises later, you have documentation.
Log It
Keep a master transmittal log (spreadsheet or in Procore/Autodesk) with columns: Transmittal #, Date Received, Drawing List, Revision, Purpose, Sender, Your Signature, Date Signed. This is your master record.
Distribute to Your Team
If you're the GC, make copies or send digitally to each trade that needs the sheets. Require them to sign a receipt transmittal acknowledging they got their copy.
Handling Updated Drawings Without a Transmittal
Sometimes you receive updated drawings (via email, Dropbox, etc.) without an official transmittal. This is a problem. You don't have proof of what was sent, when, or which revision. Here's what to do:
- Request an official transmittal immediately. Don't use the drawings until you have formal documentation. Email the sender: "We received updated electrical drawings via email on March 1. Please provide an official transmittal documenting the revision and purpose."
- If the sender refuses: Create your own internal transmittal documenting what you received and when. Not as good as an official one, but better than nothing.
- Don't rely on email dates. Email can be forwarded, resent, or lost. A signed transmittal is the only proof of official receipt.
- Mark the drawings clearly: Write "RECEIVED [DATE], NO TRANSMITTAL" on the drawings so no one assumes they came through proper channels.
Superseded Drawings: How to Track Which Sets Are Void
As the project progresses, drawings get revised. Old versions must be marked void so no one builds from them accidentally. Here's the process:
Issue a New Transmittal with Superseding Notes
When revised drawings are issued, the transmittal must clearly state: "Revision 2 of sheet A1 supersedes Revision 1. Discard Revision 1." or "Addendum 1 replaces Architectural drawing A3 issued March 1."
Collect Old Drawings
Ask all trades to return or destroy old versions. This prevents anyone from accidentally building from an outdated set. Large projects often require a signed statement: "We have destroyed all copies of Drawing A1, Revision 1."
Update Your Master Set
Your office keeps a "master set" of current drawings. When revisions are issued, replace the old sheets. At project end, the master set becomes the as-built record.
Digital Transmittals (Procore, Autodesk) vs. Email
Many projects now use platforms like Procore or Autodesk Docs for document management. These platforms have built-in transmittal workflows. Advantages:
- Automatic logging: Every distribution is logged with timestamps
- Acknowledgment tracking: The platform records when each recipient views or downloads
- Version control: Old versions are archived; no confusion about which is current
- Audit trail: If a dispute arises, you have a complete record
Important: Email alone is not sufficient for official transmittals. If your project uses email for drawings, require printed transmittals to be signed and returned. Digital platforms are better.
Common Mistakes in Transmittal Management
- Sending drawings without a transmittal. You have no proof of distribution. If a sub claims "I never got those drawings," you can't prove them wrong. Always use a transmittal.
- Not specifying the purpose code. "For Construction" vs. "For Review" is the difference between authorization to build and a draft. Be explicit.
- Not collecting signed receipts from subs. A sub can later claim "We didn't know about that revision." Signed receipts prevent this claim.
- Losing track of which revision is current. Multiple versions of a drawing floating around leads to mistakes and RFIs. A clear transmittal log prevents this.
- Not marking old drawings as void. Someone builds to an old plan because they didn't know a revision had been issued. This causes rework and claims.
- Mixing official and unofficial distributions. If some subs get official transmittals and others get email, inconsistency causes disputes. Use one method for the whole project.
- Not documenting transmittals in the project file. Years later, a dispute arises. You have no transmittal records. Keep digital copies or scans of all transmittals in the project folder.
Sample Transmittal Log Columns
Keep your transmittal log in a spreadsheet or Procore/Autodesk. Here are the essential columns:
| T# (Transmittal #) | Date Issued | Drawings Included | Revision | Purpose | Recipient | Signed Receipt |
|---|---|---|---|---|---|---|
| T-001 | Feb 1, 2024 | A1, A10, S1, S5 | Rev 1 | For Construction | General Contractor | Yes, Feb 1 |
| T-002 | Mar 15, 2024 | P2 (Plumbing Plan) | Rev 2 | For Construction | Plumbing Sub | Yes, Mar 15 |
Keep exploring
Related guides on document control, drawing review, and version management.
Review and mark up drawings before transmitting them.
Reference spec divisions in transmittal notes for clarity.
Review drawings for issues before issuing "For Construction" transmittals.
Track submittals tied to drawing revisions and transmittals.
Manage multiple revisions and keep your team on the current version.
Use your final transmittal log and master set to create as-built records.