Transmittals

Why transmittals are critical

Consider the most common documentation dispute in construction. A revised structural drawing is issued. Weeks later, a subcontractor’s work is found built to the old revision. The subcontractor says: we never received Rev C.

If Rev C went out under a numbered transmittal, with a defined recipient list and an acknowledgment on record, the liability conversation is short. If it went out as an email attachment to whoever someone remembered to copy, the main contractor now owns an evidence-poor argument about an expensive piece of rework.

Every out-of-date sheet on a site is a transmittal that didn’t happen, wasn’t acknowledged, or didn’t recall what it superseded.

The role of transmittals in project performance

• A transmittal is proof of issue; email is proof of sending. A transmittal adds what email lacks: a sequential number in a register, explicit revision and purpose-of-issue codes, a recipient list drawn from the project’s distribution matrix, and an acknowledgment loop. “It was in an email somewhere” and “Transmittal T-0457, Rev C, issued for construction, acknowledged 14 May” are different universes of evidence.

• Purpose-of-issue codes govern use. For construction, for information, for approval. Building from a “for information” issue is a classic site failure, and the code on the transmittal is what makes the error attributable. The companion discipline is recall: superseded copies withdrawn or stamped, so the site holds one truth.

• The distribution matrix decides who gets what — before anyone has to remember. A controlled table of document type against role: structural revisions reach the formwork subcontractor automatically; commercially sensitive documents don’t reach everyone. It is a living document, because firms change and people leave — and email-based distribution decays with every departure, since inboxes are personal silos and transmittal registers are project records.

• Issue is not comprehension. A transmittal proves the drawing arrived. It does not prove the field understood what changed. Disciplined teams pair a major revision with a clouded markup or a revision note, so the crew knows what is different rather than merely that a new PDF exists.

What happens without transmittal discipline

Distribution runs on memory and email. The one recipient who mattered gets missed. Work proceeds on the superseded revision, and the cost is rework, delay to the following trades, and a liability fight with no clean record on either side.

Meanwhile, unacknowledged issues pile up unnoticed, and nobody can state what the current construction set was on a given date — which is the central question in defective-work disputes. At handover, the “issued” record turns out to be scattered across three years of inboxes belonging to people who no longer work there.

The average US dispute costs upwards of $60 million and takes over a year to resolve. A great many of them are, at root, arguments about who had which information when.

How Zepth runs transmittals

Transmittals are generated from the document register itself: current revisions only, recipients pulled from the project’s distribution rules, purpose codes enforced, acknowledgments tracked with read status visible. Superseded-revision alerts reach every registered holder automatically.

The transmittal log, the document register and the acknowledgment trail are one connected record. When the “who received Rev C” question arrives, the answer is a search, not an excavation.