"Approved as noted" is not the same as approved. It means the submittal came back with comments, and those comments are part of what you are allowed to install. If nobody reads the notes, or the notes never leave the office, the installer builds what was submitted, not what was accepted. Then the notes show up in the wall, in the wrong unit, or in a clearance that was never provided.

The story below is a typical case, not a specific job, and the dollar figures are examples.

How it usually goes

A sub submits product data and a shop drawing for a piece of equipment, say a light package, an HVAC unit, or a set of doors and hardware. The design team returns it stamped "approved as noted." The notes matter. They change a model number, a clearance, a control requirement, or a finish. It is a genuine approval, with conditions.

The stamped PDF lands in the office. Someone files it, or means to. In a loose list, if there is one, the status gets marked "approved." The notes do not get summarized and do not get sent to the person who will order or install the product. The sub orders and installs what they originally submitted, which is a reasonable thing to do if nobody told them the stamp came back with conditions.

The equipment shows up, or gets set, and it is the wrong model, or it does not fit the clearance. Now you are dealing with lead time on the right product, a possible rip-out, and a conversation about who was supposed to read the notes. The real miss was treating "approved as noted" like a clean approval.

What that costs (example figures)

The direct cost depends on whether you catch the notes before the order, before the install, or after. A miss caught after install (restocking or a second purchase, labor to swap the item, maybe a delay while you wait on the right product) might land somewhere in the range of $3,000 to $15,000 on a package like this, and more if the item has a long lead time or is already built in. Treat that as a ballpark, not a quote.

The rest of the cost is easy to underestimate. The right product may not be sitting on a shelf in Phoenix. The sub will say they were "approved." The stamp will say "as noted." Without a log that records the notes and a record that the field received them, that argument is messy. Sometimes you catch it at receiving, and the dollar figure is smaller. The habit is still worth having.

The basic controls that would have caught it

Log the actual status, not a blunt "approved." A submittal log should be able to say approved, approved as noted, revise and resubmit, or rejected. If the status is "approved as noted," the log also needs a short line for what the notes said, and a column for whether the field received them.

Send the notes on purpose. When a stamped return arrives, a short note goes to the superintendent and the sub who will order or install: submittal number, the status, the conditions that matter, and a link to the stamped PDF. Do not assume that filing the PDF is the same as informing the installer.

Keep the stamped copy where the field can see it, and look at recently returned submittals before you order or install.

A spreadsheet in a Google Drive or Dropbox job folder is enough. I go through log columns in "A Procore-Level Job File With Google Drive (or Dropbox) and a Spreadsheet." Used carefully, an AI tool can draft a short "here is what the notes said" summary. A person still has to check it against the stamped PDF.

If the returns are piling up in the inbox

If submittals are coming back faster than they can be issued to the field, or if "approved as noted" is getting flattened into "approved," that is a reason to get help.

If you want help, I can set up the job file, run the submittal and RFI logs on a retainer, or prepare closeout. Read the notes, or the notes will show up in the wall.

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