A shop drawing revision transmittal register should be an issue-and-receipt register connecting each shop drawing revision to its transmittal, recipient, purpose of issue, review response, superseded state and supplier release boundary. Its release question is which revision each party is authorized to use and whether an approved drawing was formally transmitted before production, packing or change work proceeded. Build the record before ordering or shipment, keep open points visible, and require an authorized buyer decision for every exception; the framework does not replace project specifications, contracts, or destination rules.
Author: Andy, Director of Operations
Technical reviewer: Andy, Director of Operations
Last substantive review: September 4, 2026
Corrections: Send documented corrections through the HOMESEE contact page.
Editorial note: The author and revision checker are the same confirmed HOMESEE representative; this is not an independent technical review. No price, MOQ, lead-time, certification, factory-capacity, ranking, or project-result claim is made.
Table of contents
- The procurement decision this record controls
- Minimum fields and issue-and-receipt trail
- A step-by-step workflow
- A drawing issue matrix
- Category and edge-case handling
- Governance and drawing revision control
- Buyer checklist
- HOMESEE RFQ review
- Sources
What procurement decision does a shop drawing revision transmittal register control?
An approved drawing can still fail as a procurement control if the drawing recipient receives the wrong revision or cannot distinguish drawing authorization from review comments. A transmittal register records what was issued, why, to whom and what it supersedes.
The core deliverable is an issue-and-receipt register connecting each shop drawing revision to its transmittal, recipient, purpose of issue, review response, superseded state and drawing recipient drawing issue boundary. It should be readable as a decision record rather than a marketing presentation. The release-ready test is which revision each party is authorized to use and whether an approved drawing was formally transmitted before production, packing or drawing revision work proceeded. If the document-control group cannot answer that question from traceable transmittal register source files, the transmittal register is not ready, even if individual participants believe they remember the answer.
This guide describes a buyer-side control method. It does not establish a legal duty, a technical tolerance, a test method or a destination compliance result. Those come from the signed contract, project specifications, qualified designers, relevant authorities and product-specific issue-and-receipt trail. HOMESEE should be evaluated only against the drawing boundary and records actually agreed for an RFQ or order.
Start from a stable buyer identity
Keep a buyer-traceable shop drawing or decision ID even when drawing recipient references drawing revision. drawing recipient model names, carton numbers and report numbers remain valuable, but they should be mapped to the stable ID rather than replacing it. That approach preserves continuity between a BOQ, a finish schedule, a sample, a drawing, an order, an inspection record and a package mark.
Keep drawing state separate from issue-and-receipt trail
A drawing state such as approved is not issue-and-receipt trail by itself. Store the approving role, date, applicable drawing boundary, source transmittal file and revision. A photograph can show visible condition; it cannot alone prove hidden construction, performance, quantity or authorization. A drawing recipient declaration can identify a claim, but the drawing controller must decide what independent or destination-specific issue-and-receipt trail the project-specific control requires.
Minimum fields for the shop drawing revision transmittal register
Use a structured register with one drawing entry per shop drawing, package, decision or revision conflict at the level where the outcome can drawing revision independently. The table below is a field model, not a HOMESEE project record.
| Control field | authorized treatment | drawing issue test |
|---|---|---|
| Identity | Stable ID plus native references | Can a revision checker find the same shop drawing across transmittal register source files? |
| Basis | Approved source, revision and drawing boundary | Is the issued basis distinguishable from a proposal? |
| drawing state | Named owner, decision and date | Is every revision conflict visible and actionable? |
| issue-and-receipt trail | Linked transmittal record and limitation | Does the issue-and-receipt trail support only the claim being made? |
| Downstream action | Affected order, inspection, package or receiving record | Was the decision propagated? |
Drawing number
Within the transmittal register, drawing number identifies the shop drawing before the drawing-release gate. The entry points to a named revision, drawing-linked reference or issue-and-receipt trail; an unknown value remains an assigned question, not an estimate. The drawing controller tests the field from BOQ, drawing or schedule to the downstream sample, inspection or package and back again. drawing state and authorization stay separate because holding a transmittal record does not prove its content was accepted.
Revision
Within the transmittal register, revision identifies the shop drawing before the drawing-release gate. The entry points to a named revision, drawing-linked reference or issue-and-receipt trail; an unknown value remains an assigned question, not an estimate. The drawing controller tests the field from BOQ, drawing or schedule to the downstream sample, inspection or package and back again. drawing state and authorization stay separate because holding a transmittal record does not prove its content was accepted.
Transmittal id
Within the transmittal register, transmittal ID identifies the shop drawing before the drawing-release gate. The entry points to a named revision, drawing-linked reference or issue-and-receipt trail; an unknown value remains an assigned question, not an estimate. The drawing controller tests the field from BOQ, drawing or schedule to the downstream sample, inspection or package and back again. drawing state and authorization stay separate because holding a transmittal record does not prove its content was accepted.
Issue purpose
Within the transmittal register, issue purpose identifies the shop drawing before the drawing-release gate. The entry points to a named revision, drawing-linked reference or issue-and-receipt trail; an unknown value remains an assigned question, not an estimate. The drawing controller tests the field from BOQ, drawing or schedule to the downstream sample, inspection or package and back again. drawing state and authorization stay separate because holding a transmittal record does not prove its content was accepted.
Sender and recipient
Within the transmittal register, sender and recipient identifies the shop drawing before the drawing-release gate. The entry points to a named revision, drawing-linked reference or issue-and-receipt trail; an unknown value remains an assigned question, not an estimate. The drawing controller tests the field from BOQ, drawing or schedule to the downstream sample, inspection or package and back again. drawing state and authorization stay separate because holding a transmittal record does not prove its content was accepted.
Issue and receipt date
Within the transmittal register, issue and receipt date identifies the shop drawing before the drawing-release gate. The entry points to a named revision, drawing-linked reference or issue-and-receipt trail; an unknown value remains an assigned question, not an estimate. The drawing controller tests the field from BOQ, drawing or schedule to the downstream sample, inspection or package and back again. drawing state and authorization stay separate because holding a transmittal record does not prove its content was accepted.
Review drawing state
Within the transmittal register, review drawing state identifies the shop drawing before the drawing-release gate. The entry points to a named revision, drawing-linked reference or issue-and-receipt trail; an unknown value remains an assigned question, not an estimate. The drawing controller tests the field from BOQ, drawing or schedule to the downstream sample, inspection or package and back again. drawing state and authorization stay separate because holding a transmittal record does not prove its content was accepted.
Step-by-step workflow for shop drawing revision transmittal register
Run the workflow as linked gates. A later gate does not repair an undocumented earlier decision; it merely makes the missing control harder and more expensive to find. The exact drawing authorization titles and contract notices belong to the project-specific control, but the sequence below gives procurement teams a reproducible starting point.
Step 1: Create the drawing index
create the drawing index. At the opening gate, the drawing controller checks the transmittal register against named inputs rather than memory. The shop drawing is traced from its controlling BOQ, drawing or schedule to the downstream transmittal register reference and back. Differences receive an owner, due action and bounded hold. drawing entries satisfying the drawing-release gate may proceed; every reserved point remains visible. Completion leaves issue-and-receipt trail, an effective revision and an accountable disposition.
Step 2: Define issue-purpose codes
define issue-purpose codes. During the issue-and-receipt trail pass, the drawing controller checks the transmittal register against named inputs rather than memory. The shop drawing is traced from its controlling BOQ, drawing or schedule to the downstream transmittal register reference and back. Differences receive an owner, due action and bounded hold. drawing entries satisfying the drawing-release gate may proceed; every reserved point remains visible. Completion leaves issue-and-receipt trail, an effective revision and an accountable disposition.
Step 3: Send through a traceable transmittal
send through a traceable transmittal. Before the next handoff, the drawing controller checks the transmittal register against named inputs rather than memory. The shop drawing is traced from its controlling BOQ, drawing or schedule to the downstream transmittal register reference and back. Differences receive an owner, due action and bounded hold. drawing entries satisfying the drawing-release gate may proceed; every reserved point remains visible. Completion leaves issue-and-receipt trail, an effective revision and an accountable disposition.
Step 4: Record receipt and response
record receipt and response. At the reconciliation point, the drawing controller checks the transmittal register against named inputs rather than memory. The shop drawing is traced from its controlling BOQ, drawing or schedule to the downstream transmittal register reference and back. Differences receive an owner, due action and bounded hold. drawing entries satisfying the drawing-release gate may proceed; every reserved point remains visible. Completion leaves issue-and-receipt trail, an effective revision and an accountable disposition.
Step 5: Mark superseded revisions
mark superseded revisions. During revision conflict review, the drawing controller checks the transmittal register against named inputs rather than memory. The shop drawing is traced from its controlling BOQ, drawing or schedule to the downstream transmittal register reference and back. Differences receive an owner, due action and bounded hold. drawing entries satisfying the drawing-release gate may proceed; every reserved point remains visible. Completion leaves issue-and-receipt trail, an effective revision and an accountable disposition.
Step 6: Map affected procurement lines
map affected procurement lines. At traceable transmittal closure, the drawing controller checks the transmittal register against named inputs rather than memory. The shop drawing is traced from its controlling BOQ, drawing or schedule to the downstream transmittal register reference and back. Differences receive an owner, due action and bounded hold. drawing entries satisfying the drawing-release gate may proceed; every reserved point remains visible. Completion leaves issue-and-receipt trail, an effective revision and an accountable disposition.
Edge cases that need an explicit rule
Case 1: An drawing authorization email omits the drawing revision
When an drawing authorization email omits the drawing revision, the drawing controller preserves the original reference in the transmittal register. The drawing entry names the shop drawing, controlling revision and downstream work at risk. A label, photograph or message supports review but is not automatic drawing authorization. the drawing controller and the accountable project role records proceed, hold, escalate or supersede. Work already produced, inspected, packed or delivered receives its own disposition. transmittal closure requires issue-and-receipt trail and confirmation that active instructions agree.
Case 2: A drawing recipient starts from a downloaded old transmittal record
When a drawing recipient starts from a downloaded old transmittal record, the drawing controller opens a linked revision conflict in the transmittal register. The drawing entry names the shop drawing, controlling revision and downstream work at risk. A label, photograph or message supports review but is not automatic drawing authorization. the drawing controller and the accountable project role records proceed, hold, escalate or supersede. Work already produced, inspected, packed or delivered receives its own disposition. transmittal closure requires issue-and-receipt trail and confirmation that active instructions agree.
Case 3: One transmittal contains mixed statuses
When one transmittal contains mixed statuses, the drawing controller limits the affected drawing boundary in the transmittal register. The drawing entry names the shop drawing, controlling revision and downstream work at risk. A label, photograph or message supports review but is not automatic drawing authorization. the drawing controller and the accountable project role records proceed, hold, escalate or supersede. Work already produced, inspected, packed or delivered receives its own disposition. transmittal closure requires issue-and-receipt trail and confirmation that active instructions agree.
Case 4: A revision alters only some drawing entries
When a revision alters only some drawing entries, the drawing controller requires a fresh comparison in the transmittal register. The drawing entry names the shop drawing, controlling revision and downstream work at risk. A label, photograph or message supports review but is not automatic drawing authorization. the drawing controller and the accountable project role records proceed, hold, escalate or supersede. Work already produced, inspected, packed or delivered receives its own disposition. transmittal closure requires issue-and-receipt trail and confirmation that active instructions agree.
Case 5: Site comments arrive after production drawing issue
When site comments arrive after production drawing issue, the drawing controller protects the audit trail in the transmittal register. The drawing entry names the shop drawing, controlling revision and downstream work at risk. A label, photograph or message supports review but is not automatic drawing authorization. the drawing controller and the accountable project role records proceed, hold, escalate or supersede. Work already produced, inspected, packed or delivered receives its own disposition. transmittal closure requires issue-and-receipt trail and confirmation that active instructions agree.
Related transmittal register source files and revision governance
For shop drawing revision transmittal register, keep the operating transmittal record connected to the drawing recipient transmittal file requirements, HOMESEE sourcing services and project inquiry form. Plan sampling in the project references, state protection in the BOQ normalization guide, and link final placement to the material submittal register guide. Before an order, reconcile the cross-category finish schedule. Commercial context remains in mixed-material AQL plan, project-specific transmittal register source files go through the export packaging specification, and published container-loading issue-and-receipt trail plan are references rather than guaranteed outcomes.
Issue the shop drawing revision transmittal register with a revision, date, preparer and accountable approver. A drawing revision notice names the affected drawing entries and downstream transmittal register source files; it never relies on a newer filename alone. Messages and meetings may resolve questions, but their authorized answer returns to the active register. Standards, photographs, declarations and sampling reports retain their own drawing boundary: none becomes a universal compliance statement merely because it is linked to the procurement transmittal record.
shop drawing revision transmittal register application exercise
Choose one live drawing entry in the transmittal register. Ask a second revision checker to locate its controlling input, downstream transmittal register reference, latest disposition and issue-and-receipt trail. Then begin with the shop drawing and trace backward. Record where the paths diverge, and repeat with one revision conflict and one superseded revision before the drawing-release gate.
Buyer checklist for shop drawing revision transmittal register
Complete the checklist against the shop drawing revision transmittal register source set, not from memory:
- A stable buyer-traceable ID exists for every affected shop drawing or decision.
- The controlling BOQ, drawing, schedule and specification revisions are named.
- drawing recipient references are mapped without replacing buyer identities.
- Proposed, submitted, approved, rejected and superseded states are distinct.
- Every revision conflict has an owner, due action and authorized decision route.
- drawing-linked samples and photographs have IDs, dates and stated limitations.
- Quantities and units reconcile at the level needed for the drawing issue decision.
- Order, inspection, packing, loading and receiving impacts are mapped.
- Destination and contract requirements are assigned to qualified revision checkers.
- No price, MOQ, lead time, compliance or capability has been assumed.
- Superseded transmittal register source files are marked and cannot be mistaken for issued releases.
- The final record names preparer, approver, issue date and revision.
Request a drawing-transmittal control review
To evaluate this control within a real sourcing package, use the export packaging specification and upload the BOQ, issued drawings, schedules, sample register and any existing shop drawing revision transmittal register. Include the destination, authorized-on-site context and the decision dates your project has actually approved. Mark unknown information as unknown rather than inserting an estimate.
HOMESEE can then prepare questions around the defined drawing boundary and organize an RFQ discussion against those transmittal register source files. The response should be assessed against the project-specific control's technical, contractual and destination requirements. Sending information does not create a claim about price, MOQ, lead time, certification, production capacity or outcome.
Sources
- ISO 19650-1 information management concepts and principles
- Digital NSW RACI responsibility model
- Build Procurement Hub material submittal process
The sources support the general control concepts identified above. Standards and public guidance must be read in their own drawing boundary and issued edition. A reference here is not a declaration that a particular product, shipment, drawing recipient or HOMESEE service complies with it.