What is a transmittal — and why it is the most valuable boring document you own

A transmittal is a record of an issue: these drawings, at these revisions, went to these people, on this date, for this purpose. That is all it is. It is the least interesting document in a project and the one most likely to save a practice a six-figure argument.

What goes on it

• —A transmittal number, so it can be referred to
• —The date issued
• —Who it went to — organisation and individual, not "the contractor"
• —Every drawing number AND its revision letter
• —The purpose: for information, for comment, for approval, for construction
• —The medium — a printed set and a PDF are different events

The purpose line is the one people skip and the one that matters most. "For construction" and "for comment" carry entirely different liability, and a set issued for comment that somebody built from is a very different conversation if the transmittal says so.

Why an email is not a substitute

An email can be a record, and on a small project it often is enough. It stops being enough at the point where you need to answer a question about a project, not a question about a mailbox: which revision is current on site, what did we issue in March, has the structural engineer ever received Rev D.

Those are register questions. A mailbox answers them by search, in an afternoon, incompletely. A transmittal register answers them by looking, in seconds, completely — and that difference is the whole reason document control exists as a discipline. International standards such as ISO 19650 set out how project information should be organised and exchanged.

The argument this prevents

A contractor builds from Rev B. Rev D is current. Work is demolished and rebuilt. The only question that matters is whether Rev D was issued to them, and when.

With a transmittal register that question takes thirty seconds and the answer is not disputable. Without one it takes a fortnight of letters, during which the site is stopped and both parties are accruing cost — and it is usually settled by whoever kept better records rather than by who was right. See version history is not revision control.

A workable habit for a small practice

• —Nothing leaves the office without a transmittal, including a PDF sent from a phone
• —One numbering sequence per project, never per person
• —The revision letter is on the transmittal, not just on the drawing
• —Superseded revisions stay in the register, marked superseded, forever
• —The register is somewhere more than one person can read

That last point is the one that fails. A register maintained in one person's folder is a register that stops existing when they are on leave.

The same register is what makes the handover set at completion quick to assemble.