Why the humble transmittal still matters
Every job has the same argument at least once: "We never got that." The submittal that sat on someone's desk for five weeks. The revised drawings the sub says they never saw. The O&M manuals the owner claims weren't delivered. A document transmittal — and a transmittal log that tracks every one — ends that argument with a numbered record of what went out, to whom, how, and what you asked them to do. The free template above gives you a clean transmittal cover sheet and a log that counts days out and flags overdue responses automatically.
What a transmittal is
A transmittal (sometimes called a letter of transmittal or drawing transmittal) is a one-page cover sheet that travels with documents, drawings, samples, or other items. It records:
- Who and when: to, from, date, and a unique transmittal number.
- What: each item, with copies, the document's own date, its number and revision, and a description.
- How: email, file-share link, hand delivery, courier, mail, or pick-up.
- Why: the purpose — for approval, for your use, as requested, for review and comment, for record.
- What's next: the date a response is needed and what kind of response.
It's used for submittals, shop drawings, product data, samples, drawing revisions and bulletins, RFI responses, closeout documents, O&M manuals, warranties, as-builts, pay applications, and anything else where proof of delivery matters.
How to fill out the transmittal
| Field | What to enter |
|---|---|
| Transmittal # | One running sequence per job (T-2417-001, -002 …). Never reuse a number. |
| To / Attention | A company and a person. "Attention" is who is responsible for acting on it. |
| Subject | A short line someone can search for later: "Div 26 submittals — panelboards, lighting." |
| Items | One line per document, set, or sample. For drawing sets, list the sheet range and revision (E-001 to E-401, Rev 2). |
| Number / Rev | The document's own number and revision — the spec-section submittal number, drawing number, or RFI number. |
| Sent via | Check how it traveled. For file-share links, note in Remarks how long the link stays live. |
| Purpose | Check one primary purpose. Mixing "For Approval" and "For Your Use" on the same transmittal confuses the reviewer. |
| Response needed by | A real date, from the review period in your specs, plus the schedule impact if it's late. |
| Remarks | Resubmittal notes, related items that must be reviewed together, delivery details for samples. |
| Copies to | Everyone who received a copy, so the distribution is on record. |
| Signatures | Sender, and a "received by" acknowledgment for hand deliveries. Receipt is not approval. |
Picking the right purpose
- For Approval — the receiver must formally act (approve, approve as noted, revise and resubmit, reject). Use for submittals and shop drawings.
- For Review & Comment — you want feedback, but it isn't a formal approval. Common for preliminary layouts and coordination drawings.
- For Your Use — informational, but the receiver is expected to work from it (updated look-ahead, revised sheets for a sub).
- As Requested — sending something someone asked for. Reference the request (email date, RFI number) in Remarks.
- For Record — filing only. Closeout documents, released-for-fab drawings to a supplier, signed copies.
- For Construction / For Bidding — issue status for drawing sets. Keep superseded sets clearly marked so nobody builds from them.
The transmittal log: your follow-up list
A single transmittal proves one delivery. The log is what keeps the job moving. Every transmittal gets a row with date sent, recipient, contents, purpose, response due, and response received. The template calculates:
- Days Out — date sent to response received, or to today if still open.
- Status — Closed, OVERDUE, Awaiting Response, or No Action Required, automatically.
- Summary counts — total transmittals, awaiting response, and overdue at the top of the sheet.
Filter on OVERDUE every week and chase each one in writing. Note the follow-up in the Notes column. That paper trail is exactly what supports a time extension or delay claim when a late approval pushes your long-lead order. For submittal-specific tracking (spec section, reviewer, ball-in-court, resubmittal cycles), use the dedicated submittal log template alongside this one.
Transmittal best practices from the field
- One transmittal per purpose. Don't bury an approval request in a stack of FYI documents.
- Transmit revisions, not just new documents. Every drawing revision issued to a sub or supplier should go on a transmittal so you can prove who had which revision on which date.
- Get a signature for hand deliveries and samples. Physical samples go missing. A signed receipt settles it.
- Log it the day it goes out. A log filled in from memory at the end of the month is missing half the entries.
- Keep it where the job file lives. Transmittals belong in the project's document record, filed with what they covered.
When to move beyond Excel
Spreadsheets and email work for a few transmittals a week. On busy jobs, the log drifts from what was actually sent, and nobody can find which revision went to which sub. Field PM keeps submittals, RFIs, drawings, and the Job Book on the project with due dates, reminders, and a full history of who sent what and when. Start a free 30-day trial.
Related templates
- Submittal log — spec-section tracking, reviewer, and resubmittals
- RFI template — questions that come back with a transmitted response
- Project closeout checklist — the documents you'll transmit at turnover
- Purchase order template — for released-for-fab orders to suppliers
- Browse all free construction templates
