A transmittal is a short record of what you sent, to whom, on what date, and why. That is all. It is not a legal essay, and it does not need formal language. It is the page, or the PDF, you reach for when someone says they never received a set of drawings, a submittal, or a closeout package.

Large jobs use transmittals all day because the volume of paper is high and the arguments are expensive. You can use the same idea, in a lighter way, on a job without a document control staff and without enterprise software.

What belongs on a transmittal

A useful transmittal has a few lines:

  • Date
  • Job name and number
  • Who is sending it, and who it is going to
  • A list of what is included: document type, number, revision or date, and how many pages or files
  • Why it is being sent: for review, for construction, for record, for pricing, or as a response
  • What you need back, and by when, if you need something back
  • How it was sent: email, upload to a shared folder, hand delivery, or an owner's platform

If you are sending drawings, list the sheet numbers and revisions, not just "plans." If you are sending a submittal, include the submittal number and the spec section. If you are sending a closeout package, list the contents. A transmittal that says "see attached" with no list will not help you later.

Keep the tone plain. You are not trying to sound like a lawyer. You are making a dated list. This is a filing habit, not legal advice, and it does not replace the notice language your contract may require. When a notice or a claim is at issue, read the contract and talk to a construction attorney.

You do not need a transmittal for every routine email. Use one when the document matters: official drawing sets, bid or contract documents, submittal packages, change documents, and closeout. For smaller day-to-day updates, a consistent email and a filed copy, as I describe in "Distribution: Who Gets the Update, and How You Prove It," may be enough. When in doubt on an important package, write the transmittal.

The miss this prevents

Here is the usual sequence.

A revised set goes out by email, or a closeout package is uploaded to a shared folder. Weeks later, a sub or an owner says they never got a sheet, or that a warranty was missing. The sender remembers attaching it. The recipient remembers a different file. There is no list of what was in the package, no date, and no record of who it went to. The argument turns into a reconstruction of inboxes instead of a glance at a one-page record.

The sending was never the problem. Sending without a list was.

How to run it in a folder and a simple form

Keep a one-page transmittal template in the root of the Google Drive or Dropbox job file, and save each completed transmittal in a Transmittals folder, named with the date and a short description: 2026-06-14_245_TRN_IFC-Set_Electrician.pdf. Number them if you want, or let the dates sort them. Either habit works, as long as it is consistent.

Email the transmittal with the files, or send the transmittal and a link to the current-set folder if the files are large. File the sent transmittal, and file any reply that acknowledges receipt. If you hand someone a roll of drawings, have the transmittal signed or noted as received, then scan it back into the same folder.

Used carefully, an AI tool can draft the transmittal from a list of filenames. A person still checks the sheet numbers, the revisions, and the recipient list against what is actually attached. A chatbot should not be the last word on what was sent.

If you have never used transmittals

Start on the next official package, not with a rewrite of the last six months. A simple form and a folder will do more than a perfect historical log you will never build.

When the habit will not hold on its own, I can set up that template and the job file, run document control on a retainer, or prepare closeout. If you want help, bring the last package that caused a "we never got that" conversation. I will tell you straight whether a short transmittal habit will hold.

The files stay yours.

If you want help, not just a checklist

Some jobs run fine on a clean file and a superintendent who gives the log fifteen minutes twice a week. Others do not: revisions are moving fast, closeout is already behind, or the field simply has no hours left for paperwork.

That is where I come in. I set up the job file, run the logs on a retainer, or prepare closeout before the scramble starts. Your files stay yours, and there is no software contract to sign.

Email travis@builtonrecord.com Get the free Job File Kit