What a transmittal contains
The standard fields have not changed in decades:
- Project name and number
- Date sent, and the sender's and recipient's names and firms
- Transmittal number (sequential per sender)
- Contents: item-by-item list — submittal number, spec section, description, copies, revision
- Action requested: for approval, for review and comment, for record, for use in the field
- Remarks: deviations flagged, urgency notes, response-by dates
- Sent via: email, delivery, or the project management platform
Transmittal vs. cover sheet vs. submittal
The three get conflated constantly. The submittal is the content — the cut sheets, drawings, samples. The cover sheet is the front page of that content, carrying the submittal number, section, and the stamps. The transmittal is the routing record that says this package moved from A to B on this date for this purpose. In paper days they were physically separate documents; modern platforms generate the transmittal automatically when you hit send, but the legal function — proof of delivery and requested action — is unchanged.
Why transmittals still matter in a software age
Because construction disputes run on dates. Delay claims turn on when a submittal entered the architect's court and how long it sat. Payment disputes turn on when closeout documents were delivered. A clean transmittal log answers those questions in minutes; a shared-drive folder of PDFs with ambiguous filenames answers nothing. This is also why the 'action requested' field matters: a package sent 'for record' does not start a review clock, and a reviewer who received something 'for approval' cannot claim it was informational.
The discipline costs nothing when it is automatic. It only costs when it isn't there.
Practical habits that keep the trail clean
Three habits separate a useful transmittal log from a decorative one. Number sequentially and never reuse a number, even for a voided send — gaps are explainable, duplicates are not. Match the item list to reality: if the package holds three submittals and a sample, the transmittal lists four items with their numbers, so a later claim that 'the sample was never sent' dies on the page. And state the action requested every time, with a response-by date on anything schedule-critical; a transmittal that just says 'see attached' starts no clock and obligates no one.
Transmittals in Submittal.App
Every package sent through Submittal.App carries its transmittal record automatically — who sent it, who opened it, when it was returned, and with what action — so the log builds itself as the project runs. The AI Builder assembles the package; the platform handles numbering, routing, and the timestamped history you will want fourteen months from now.