The drawing transmittal: the ninety seconds that decide the argument
A free transmittal template, and the four fields on it that decide disputes: date, revision, purpose and acknowledgement. How to write the supersession line, how to chase an acknowledgement without nagging, and who should get DWG rather than PDF.
- A transmittal is a covering note for one issue: these sheets, at these revisions, to this person, on this date, for this purpose.
- Four fields decide arguments — date, revision, status and acknowledgement. Everything else on the form is courtesy.
- Always name what the issue supersedes, by drawing number and revision. It is the line most often left blank and the one that causes the most damage.
- Send it as a document, not as a sentence in an email body. An email is a conversation; a transmittal is a record.
- Every row on a transmittal becomes a row in your drawing issue register. If it doesn't, you have a note and no memory of it.
Most drawings in most Indian practices are issued with a sentence. "Hi Rakesh, attached the updated plans, please check." It is friendly, it is fast, and it records almost nothing: not which revision, not what the recipient is allowed to do with the sheets, not what the old set is now worth, and not whether anybody read it.
A transmittal is that same email with the ambiguity removed. It takes about ninety seconds once the format exists, and it is the difference between a project where the paper trail supports you and one where it merely exists.
What a transmittal actually is
It is a covering note addressed to one recipient, listing one issue. It answers five questions and stops: what am I sending, at which revision, what may you do with it, when did it go, and does it replace anything you already have.
What it is not is a filing system. The cumulative record — every sheet on the project, every occasion each one went out — is the drawing issue register, which is addressed to nobody and lives in the studio. The two are often spoken of together and are easy to confuse, so the distinction is worth holding: a transmittal is useful for a week, a register is useful for the life of the building.
| Transmittal | Register | |
|---|---|---|
| Addressed to | One recipient, by name | Nobody. It is the studio's own record. |
| Covers | One issue, on one date | Every issue, for the whole project |
| Lives | In the recipient's inbox and yours | In the studio, permanently |
| Useful for | About a week | The life of the building |
| If you keep only one | Not this one | This one |
One transmittal produces one register row per drawing listed on it. If the rows do not appear, the transmittal was a courtesy and not a record.
The fields, and which of them matter
A transmittal form has about a dozen fields and four of them do the work. Fill the rest because they are cheap; understand the four because they are the ones a dispute turns on.
| Field | Example | Why |
|---|---|---|
| Transmittal number | TR-014 | So the issue can be referred to in one word later. Sequential per project, never per client. |
| Project and project number | Residence at Kothrud / 2026-07 | A recipient who works on three of your jobs needs to know which one this is. |
| To, and copy to | Contractor; cc structural consultant | Establishes who was told. The cc list is who cannot later say they weren't. |
| Date of issue | 14 May 2026 | The single most argued-about fact on any project. Never leave it to the email timestamp. |
| Drawing list | Number, title, revision, status, sheets | The revision column is the point of the whole document. A list without revisions is a packing slip. |
| Purpose of issue | For construction | What the recipient may do with the sheets. Sets the consequence of everything else. |
| Medium | PDF by portal link; 2 prints by courier | Matters when a dispute turns on what was actually usable on site. |
| Supersedes | Rev C of the sheets listed, withdrawn | The line most often left blank. Without it the recipient keeps using the old set in good faith. |
| Reply required by | 22 May 2026 | Only on approval and comment issues. A date turns a request into a deadline. |
| Acknowledgement | Signed and returned, or replied to by email | The difference between sent and received, which is the difference most cases turn on. |
The four that decide arguments: date, revision, purpose, acknowledgement. If you are in a hurry and cutting the form down, cut everything else first.
The supersession line, written properly
This is the field studios skip, and skipping it is how a contractor ends up building from a drawing you replaced in May. Compare:
- Weak. "Please find the revised drawings attached." The recipient now has two sets and no instruction about the first.
- Better. "These supersede the previous issue." Better, but which previous issue, and of which sheets?
- Right. "This issue supersedes Rev C of A-01-P-201, A-10-P-201 and A-01-S-301. Rev C of those three sheets is withdrawn and must not be used for construction. Please destroy or clearly mark any prints held on site."
The third one takes twenty seconds longer to write and moves the responsibility. A recipient who was told in those words and built from Rev C anyway is in a different position from one who was sent an attachment and left to work it out.
Chasing the acknowledgement
An unacknowledged transmittal is a letter you posted and never confirmed arrived. It is still evidence — it shows you sent it — but it leaves the most useful half of the record missing, and the missing half is the one a contractor will point at.
You do not need a signed form back. A one-line email reply is enough, and in practice it is what you will get. What matters is that something exists, from them, dated, referring to the issue.
Ask for it in the transmittal itself
One sentence: "Please acknowledge receipt by return." A request made in the document is easier to follow up than one that was never made.
Chase once, at one week
Not three times over three weeks. One follow-up, referring to the transmittal number, is both more effective and better-looking on a file than a trail of nudges.
Record the silence
If nothing comes back, write that in the register: chased 21 May, no response. An unanswered chase is a stronger record than a blank column, because it shows the studio did its part.
Escalate at a stage boundary, not before
Non-acknowledgement is worth raising when the set is about to be built from. Before that it is administrative; at that point it is material.
The reason so many studios stop chasing is that it feels like nagging. It reads differently on paper than it feels in the moment: a file showing one polite chase per issue reads as a competently run project, and a file showing none reads as an assumption.
Should it go by email, WhatsApp, or a portal?
The medium is not a detail. It decides whether the record survives, whether the recipient can tell what is current, and whether you can prove anything about either.
| Channel | The record it leaves | Where it fails |
|---|---|---|
| A timestamp, and a compressed file with a mangled name. | No revision context, no supersession, scrolls out of reach in a week, and the file is often unusable at full size. | |
| Email with attachments | A real record, if the transmittal is attached as a document rather than typed into the body. | Attachment size limits, threads that fork, and no way to know whether it was opened. |
| Email with a Drive link | The email; the folder is not part of it. | The folder keeps changing after the email was sent, so the record and the files disagree by the following month. |
| A client portal | The issue, the revision, the recipient, the timestamp and whether it was opened — as one event. | Nothing, if the issuing and the recording are the same action. Everything, if the portal is just another folder. |
The test for any channel: six months from now, can you produce what was sent, at which revision, to whom, and on what date, without reconstructing it from memory?
Whatever you use, send the transmittal as a document — a PDF, or an attached sheet — rather than as prose in the body of a message. An email body is a conversation and gets replied to, edited, forwarded and quoted. A document is a fixed thing with a date on it, and that is what you want six months later. The Drive-and-WhatsApp question is really this question, asked once for the whole practice.
A transmittal is not a polite covering note. It is the moment you convert an act into a record, and it is worth ninety seconds because nothing later can recreate it.
Who gets what
One issue often goes to four recipients who need different things. Sending everyone everything is not generous, it is how a client ends up holding a DWG they can hand to another architect, and how a contractor ends up pricing a sheet marked "for information".
| Recipient | Format | Typical purpose | Watch for |
|---|---|---|---|
| Client | PDF only | Information or approval | Sending editable files. The licence you granted rarely extends that far. |
| Consultants | PDF, plus DWG where they must draw on it | For comment, or coordination | Sending a background at the wrong revision, which propagates into their drawings. |
| Contractor | PDF, plus prints if the site works on paper | Tender, then construction | Superseded prints on the site wall. Name them in the supersession line. |
| Authority or municipal office | Whatever the submission format demands | Approval | Their copy is a snapshot and does not track later revisions. Note that in the register. |
Format follows purpose, not seniority. The person who needs to draw on it gets the editable file; everyone else gets the PDF.
The consultant case is the one worth setting up properly, because it repeats weekly. A structural engineer needs the current architectural background and nothing else, and does not want an account on your systems to get it. A private share link with an expiry does exactly that: they open the package, the link dies at the end of the stage, and the issue is still recorded on your side. The full protocol by recipient is a longer conversation, but that one pattern covers most of it.
Making it take ninety seconds
None of this survives contact with a busy Thursday unless issuing is cheap. Three things make it cheap.
- One template, filled in from the last one. Duplicate the previous transmittal on the project and change what differs. Starting from a blank form is how the habit dies.
- Number the drawings so the list writes itself. If your sheet names already carry the number, the revision and the status, most of the transmittal is copy-paste. That is half the argument for a numbering scheme with fields in it.
- Make the register a by-product, not a second job. Typing the same nine facts twice is what nobody keeps up. Either paste the transmittal rows straight into the register, or issue from somewhere that records the issue as it happens.
Issue once, and let the record write itself
AtelierLab issues a drawing set from the client's own workspace: the revision, the recipient, the timestamp and whether it was opened are one event rather than four things to type. Start with the free transmittal template, or see how the portal is put together.
Questions, answered
The questions architects ask most about this, in plain language.
Ask us anythingA covering note that accompanies one issue of drawings. It lists the sheets being sent with their drawing numbers, revisions and status, names the recipient, carries the date of issue and the purpose, and states what the issue supersedes. It answers five questions and stops: what am I sending, at which revision, what may you do with it, when did it go, and does it replace something you already hold.
A transmittal is addressed to one recipient and covers one issue on one date. A register is addressed to nobody, lives in the studio, and is the cumulative record of every drawing on the project and every occasion each one went out. One transmittal produces one register row per drawing listed on it. A transmittal is useful for about a week; the register stays useful for the life of the building.
Yes — download it here. It is a plain CSV that opens in Excel, Numbers or Google Sheets, with a worked example filled in and notes on each field. The matching drawing issue register template is on the register guide. Both are free to use and to modify, with no email required.
You can, and a great many Indian practices do, but understand what it leaves you with. WhatsApp compresses files, mangles names, carries no revision context, gives you no way to state what is superseded, and scrolls out of reach within a week. It is fine for "the site meeting moved to four o'clock" and poor for anything you might need to produce later. If drawings must go by WhatsApp, send the transmittal as an attached PDF alongside them so at least the record exists.
Name them by drawing number and revision, and say what must happen to them. "This issue supersedes Rev C of A-01-P-201 and A-10-P-201. Rev C of those sheets is withdrawn and must not be used for construction; please destroy or clearly mark any prints held on site." Prints matter more than PDFs here: a PDF is replaced the moment a new one arrives, but a print on a site office wall stays current until somebody physically removes it.
You want one, and a one-line email reply is enough. It does not have to be a signed and returned form. Ask for it in the transmittal itself, chase once at about a week, and if nothing comes back, record the silence in the register — "chased 21 May, no response" is a stronger record than a blank column, because it shows the studio did its part. Escalate at a stage boundary, when the set is about to be built from, rather than earlier.
PDF, in almost every case. The client is receiving the drawings to review and to build from, not to edit, and the licence in a normal appointment rarely extends to handing them editable files they could pass to another architect. Consultants who have to draw on your background get the DWG because they cannot work without it. Format follows what the recipient has to do, not their seniority on the project.