What a transmittal is actually for
A transmittal exists to answer one question later: who had what, and from when. The content of a drawing is in the drawing. The fact that revision C reached the steel fabricator on 14 March, and revision D did not reach them until 2 April, lives only in the transmittal record.
That is why transmittals survive as a practice even on projects running modern document platforms. The platform records the transfer automatically, but the record still has to exist, be numbered, and be retrievable years later when the people involved have moved on.
What belongs on one
A usable transmittal lists each document by number, title and revision, not as "drawings attached". It names the sender and every recipient, carries a date, and states the reason for issue: for review, for approval, for construction, for information, or for record. Many forms add a transmission method and a response-required-by date.
The reason for issue is the field teams skip and later regret. A set issued "for information" that a subcontractor built from is a different conversation than a set issued "for construction", and the transmittal is where that distinction was recorded.
Transmittal versus submittal
They are routinely conflated, including by software that should know better. A submittal is content the contractor provides for review: product data, samples, shop drawings, mix designs. It comes back with a review action. A transmittal is the delivery record that carries it, and nothing is ever approved or rejected on a transmittal.
A single transmittal can carry several submittals, and a submittal can travel under multiple transmittals across its review cycle. Both records matter: the submittal register answers what the review decided, and the transmittal register answers when each party received it.
The register is the part that has value
An individual transmittal is a cover sheet. The register, which is the numbered sequence of every transmittal on the project, is the document-control backbone. It shows revision history by recipient, exposes gaps where a revision never went out, and supports the notice requirements most contracts attach to time and cost claims.
Projects that let the register drift discover the cost at exactly the wrong moment. Reconstructing who held revision C from email threads two years after handover is expensive, and the reconstruction is weaker evidence than the log would have been.
Numbering and naming discipline
Transmittal numbers run in a single sequence per project, and the documents they list are identified by the project’s document numbering convention rather than by file name. On projects following ISO 19650 information management, that convention is already defined, and the transmittal simply carries the agreed identifiers and revision codes.
Where the discipline breaks down is attachments named after whoever exported them. A register entry pointing at "Final_rev2_FINAL.pdf" cannot be matched to a controlled document later, which defeats the purpose of having kept the record at all.
