"I never got that bulletin" is a short conversation when you can show what was sent, to whom, and when. It is a long conversation when the bulletin was forwarded from a personal inbox, or dropped in a folder nobody can prove the sub was told about. Then the work gets built from old information, or a change gets disputed, and the meeting turns into a reconstruction of who saw what.

This is a typical case, not a specific job, and the dollar figures are only examples.

I kept transmittal records at Mortenson Construction, on a mission-critical data center project, including the Procore onboarding. The habit is what ends the argument, and you can run it without enterprise software.

How it usually goes

The design team issues a bulletin or a revised sheet that changes a layout, a specification, or a product. Someone in the office means to get it out. They forward the email to a superintendent and maybe one sub. There is no transmittal number, no list of what was sent, no complete list of who should have received it, and no filed copy of the outgoing message. Another sub, or another person in the same company, never gets it.

Work proceeds. Later, a sub, the owner, or the designer says they never received the bulletin. The installer built from the previous information. Or a change-order conversation starts, and the other side says the instruction was never officially issued to them.

The office remembers sending it. The field remembers never getting it. Both may be telling the truth, because a casual forward to the wrong person is not the same as a distribution you can show. The argument starts, and the file cannot end it.

What that costs (example figures)

The cost is the rework, or the disputed change, plus the time in the meeting. A miss like this might put $10,000 to $30,000 in play, whether in relocation or repair, a change that is now hard to collect, or both, depending on what was built and what the bulletin changed. Call it a ballpark, not a quote.

The quieter cost is the meeting itself, and the trust it spends. Once "I never got that" has turned into a long conversation, every transmittal after it gets a harder look. A clean record would have made this a short exchange: here is what went out, here is the date, here is the list of names. I write about that record as a habit in "The Audit Trail: How a Clean File Ends Arguments Before They Start."

The basic controls that would have caught it

Send on purpose, not as a forward. A transmittal does not need special software. It can be a consistent email or a simple form: what you are sending, to whom, on what date, and why. File a copy in the job folder, named with the date first.

Send it to the people who will build from it, and list them. A forward to one superintendent is not automatically a distribution to every affected sub.

Ask for a reply, or log that it was received. A short "got it" from the superintendent is the difference between "we sent it" and "we can show it arrived."

Keep the official file in one place. The bulletin should live with the current set, or in a clearly named folder next to it, not only as an attachment in a sent-mail folder. Use the same habit for RFIs, ASIs, and revised drawings.

A shared Google Drive or Dropbox folder and a transmittals folder are enough. Used carefully, an AI tool can draft the transmittal language. You still check it, send it, and file it.

If distribution is already informal

Some teams will start a consistent transmittal habit this week and have a trail from here on. Others are mid-job, mid-argument, or already leaning on forwards and memory. Either way, you can start filing what goes out today.

If you want help, I can set up the job file, run the logs and transmittals on a retainer, or prepare closeout. The whole point of a transmittal is a short conversation instead of a long one.

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