BOQ Builder·Auto-BOQ from dimensions, DSR ratesNEW→BidEasy·Government tenders, searchableLIVE→InfraLens App·Free on Play Store, offline-readyNEW→
PMCβ€ΊπŸ“ Design Coordinationβ€ΊDrawing Transmittal Note

Drawing Transmittal Note

form
PMC-DES-FRM-001Β·v1.0-beta·⚠ Beta β€” review before use

Formal transmittal of drawings from designer / consultant / contractor to recipient. Establishes contractual sequence + dates for issued-for-review, issued-for-tender, issued-for-construction.

ReferencesFIDIC Sub-clause 5.2 (Designer's Documents)ISO 19650 (BIM CDE)CPWD Works Manual 2019Project Document Control Procedure
Download
πŸ“ When to use this template
  • Each drawing release (Concept / Schematic / GFC / As-Built).
  • Inter-discipline coordination.
  • Tender + contract documentation.
  • Audit + evidence in claims.
Sections & fields
Preview of the template structure. Download Excel to fill on site.
1Transmittal Header6 fields
Transmittal Number
_____________
Date of Issue
_____________
From (Designer/Consultant)
_____________
To (Recipient)
_____________
Subject + Project Reference
_____________
Method (Email / Hard Copy / Portal)
_____________
2Drawing List8 fields
Drawing Number
_____________
Drawing Title
_____________
Discipline
_____________
Revision + Date
_____________
Status (Issued for Review / GFC / As-Built)
_____________
Drawing Size / Scale
_____________
Number of Copies
_____________
Remarks
_____________
3Recipient Acknowledgement4 fields
Received by (Name + Signature)
_____________
Date of Receipt
_____________
Recipient's Comments (if any)
_____________
Status Update Required (Y/N)
_____________
4Distribution List3 fields
Primary Recipient
_____________
Copy To (Project Team)
_____________
File Copy
_____________
πŸ’‘ Sample filled excerpt
Transmittal #2026-145, 12-May-2026. From: Arch Consultant. To: Main Contractor. Drawings: ARCH-FL-01 to ARCH-FL-08 (8 nos, Rev 2, GFC), A1 size, 2 copies each. Acknowledged by: Site Engineer, 13-May-2026.
βš– Compliance notes
  • Transmittals create the formal documentation chain β€” essential for FIDIC Sub-clause 20.1 (claims).
  • Per ISO 19650, all transmittals via the Common Data Environment (CDE) where applicable.
  • Status (Review / GFC / As-Built) is contractually significant β€” only GFC enables execution.
  • Hard copies + digital records must be aligned; if conflict, GFC stamp prevails.

Engineer's Notes β€” Drawing Transmittal Note

Why the Drawing Transmittal Note matters

A typical construction project issues 500-5,000 drawings across architectural, structural, MEP, plumbing, fire-safety, finishes, and external works disciplines. Each drawing has multiple revisions through the design cycle. The Drawing Transmittal Note is the formal handover record β€” issued whenever a new or revised drawing leaves the designer's office for the PMC, contractor, or client.

Without transmittal records, projects descend into 'who-has-what-version' chaos. Site teams build to outdated drawings; rework cost runs into lakhs. The transmittal note creates a legal paper trail: who issued what drawing, when, to whom, with what revision number. When defects emerge years later, the transmittal log identifies which revision was current at the time of construction.

How to use it on a project

Per-issue workflow: 1. Designer prepares drawing revision (e.g., R02 of structural slab plan for Level 3) 2. Drawing Transmittal Note generated β€” lists: drawing number, revision, date issued, distribution list (PMC + main contractor + sub-contractors + client), purpose (For Information / For Comment / For Construction / GFC) 3. Receivers sign acknowledgment of receipt 4. Each receiver checks against their drawing register; supersedes prior revision 5. Old revisions stamped 'SUPERSEDED' to prevent accidental use

Critical control: GFC (Good for Construction) status must be explicit on the transmittal β€” only GFC drawings are construction-issue. Non-GFC drawings issued 'For Information' or 'For Comment' cannot be used to build.

Common transmittal failures

1. No formal transmittal β€” designer emails PDF directly to contractor; no acknowledgment; no register update. Site builds to wrong revision when newer one was issued informally.

2. Distribution gaps β€” sub-contractor not on the transmittal list never receives the revised drawing; continues using old version.

3. 'For Information' confused with 'For Construction' β€” without GFC marking, the transmittal note's purpose field is the only differentiator. Sites that ignore this distinction build to information-only drawings.

4. No revision tracking β€” multiple drawings transmitted with same revision number; designer loses track.

5. Hard-copy vs digital mismatch β€” site holds older hard-copy than current digital. The transmittal should explicitly state which is the controlling version (typically digital with GFC stamp).

6. Lost acknowledgment β€” when contractor disputes 'we never received that drawing', the transmittal acknowledgment signature is the PMC's defence.

Cross-references

Companion PMC formats: - Design Review Register (PMC-DES-REG-001) β€” design review tracking - GFC Submission Tracker (PMC-DES-LOG-002) β€” formal GFC release log - Clash Detection Report (PMC-DES-RPT-001) β€” 3D coordination outputs - RFI Review (PMC-MTG-MOM-012) β€” clarifications during construction

Process governance: ISO 19650 (BIM information management) Parts 1-5; ISO 9001:2015 Clause 7.5 (documented information) + 8.3 (design and development). For large infrastructure projects, the Common Data Environment (CDE) software (Aconex, Procore, BIM 360 Document) typically automates transmittal generation.