A submittal is how the job officially proposes a product, a shop drawing, or a sample, and how the design team officially answers. The expensive part is rarely the PDF itself. It is what happens after the stamp comes back, especially when the stamp says "approved as noted" and the notes never leave the office.

You do not need a software module to prevent that. You need a log a superintendent can keep up with on a phone, and a habit of putting the returned comments in the same place the installer looks for drawings.

What the log has to show

These columns are enough for most jobs where a superintendent is keeping the log:

  • Number
  • Spec section
  • Description
  • Type (shop drawing, product data, or sample)
  • Date submitted
  • Date returned
  • Status: approved, approved as noted, revise and resubmit, or rejected
  • Notes that must reach the field
  • Field received, by whom, and date
  • Link or path to the PDF

The status column is not decoration. "Approved as noted" is not the same as approved, and the notes are part of the answer. If they change a dimension, a model number, a color, or a mounting detail, the person doing the work has to see them before the material is ordered or installed.

Filter or color the rows that are still open, late, or approved as noted with field-received still blank. Those are the rows that turn into the wrong product on the wall.

Shop drawings, product data, and samples are not the same risk, which is why the type column matters. Do not let an unreviewed shop drawing travel with a stack of catalog cut sheets and get treated as "already approved." See "Shop Drawings, Product Data, and Samples — Keep Them Straight" for more on that.

The miss this prevents

Here is how this usually plays out.

A mechanical submittal comes back approved as noted. The notes shift a unit a few inches and call out a different accessory. The PDF sits in email, or in a folder the field does not open. The installer works off the shop drawing they submitted. The unit goes in where the drawing first showed it. Then someone reads the notes, and you are looking at a relocation, a re-order, and a dispute about who was supposed to pass the comments along.

What failed was the log, specifically the last two columns: the notes, and whether the field received them.

The shape is familiar: labor, maybe material, and time spent arguing about an email.

How to run it in a folder and a spreadsheet

Keep the submittal log as a Google Sheet or Excel file in the shared job folder on Google Drive or Dropbox, next to the RFI log. File the PDFs in a Submittals folder, named with the date, the number or spec section, a short description, and the status (for example, AAN for approved as noted), so a tired person can see it in the filename.

When a submittal comes back with notes that change the work, treat it like a closed RFI that changes the work. Put a copy where the current set lives, or issue a short notice that says what changed and where the file is. A forwarded PDF with no record is how "I never saw the notes" gets started.

A cadence a superintendent can keep:

  1. Log an item when it goes out, not when you remember it on Friday.
  2. Update the status the day it comes back.
  3. Copy any field notes into the log in plain language, not "see PDF."
  4. Send the returned submittal to the superintendent and the installer, and record the receipt.
  5. Before material is released or a cover-up begins, scan the open and approved-as-noted rows for that area.

The process is the status, the notes, and the field receiving them. The tool is just where it lives.

If the log is already behind

Some jobs generate a list a superintendent can update in fifteen minutes twice a week. Others do not, whether it is a long mechanical package or a stretch with no hours left for paperwork.

When the habit will not hold on its own, I can set up the submittal log and the job file, run document control on a retainer, or prepare closeout. If you want help, bring one recent "approved as noted" submittal and the folder where those PDFs live. I will tell you straight whether a simple sheet 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