Skip to content

Transmittal

Last reviewed:
The formal cover record accompanying documents sent between project parties, establishing exactly which documents, at which revisions, were sent to whom, when and for what purpose.

A transmittal is a small bureaucratic instrument with a large evidentiary job. Each one lists the enclosed documents with their revision codes, names the sender and recipient, states the purpose of issue — for review, for approval, for construction — and gets logged and numbered. Together the transmittal log answers the question that decides arguments: who had what information, as of when.

That question turns out to be the hinge of most documentation disputes. Whether the contractor built from a superseded revision because the update was never sent, or despite receiving it, is the difference between the designer's problem and the contractor's — and the transmittal record is where the answer lives. Delay claims, defect allocations and change-order entitlement all reach for the same log.

The system fails informally. Documents shared by email attachment, link or portal upload outside the transmittal process move information without moving the record, and the project develops two histories: what was formally issued and what people actually received. In quiet times nobody notices the divergence; in a dispute, the informal history is precisely the one that cannot be proven.

See this workflow in practice.

Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work.