A submittal log that treats every PDF as the same kind of document is how an unreviewed shop drawing travels with a stack of catalog cuts and gets treated as "already approved." Shop drawings, product data, and samples are all submittals. But they carry different risks, and they should not be filed or released to the field as if they were the same.

This is a practical filing guide, not a specification. Your project specs and the contract tell you what has to be submitted, what can be fabricated before review, and what "approved" means on that job. Read those sections. The habit below is how you keep the types straight so the field is not guessing.

Three types, three different risks

Shop drawings are the fabricator's or installer's drawings, diagrams, or schedules showing how they intend to build or install the work: duct layouts, steel details, millwork, sprinkler shops, and the like. If the shop draws it wrong, or the reviewer never sees it, the piece that shows up may not fit. Do not release a shop drawing to fabrication or to the field until it has come back from review, and then only with the comments.

Product data is the catalog information: cut sheets, performance data, model numbers, manufacturer literature. The risk is a wrong product, a substitution that was not accepted, or a "this is close enough" sheet that nobody flagged. The model number, the options, and the reviewer's notes all matter.

Samples are physical pieces: finishes, colors, materials, mock-ups if the job requires them. The risk is a finish approved in a meeting that never gets recorded, or a field product that does not match what was approved. A sample needs a date, a description, who approved it, and a photo or written record in the job file, because the physical sample will not sit on a table forever.

Your log should have a type column, as I describe in "A Submittal Log a Superintendent Can Keep Up With." When you filter the sheet, you should be able to see open shop drawings in one pass.

The miss this prevents

Here is the usual sequence.

A sub sends a package that includes product data and a shop drawing. The product data comes back approved, or approved as noted. The shop drawing is still under review, or it was never logged separately. Someone treats the package as approved and fabricates to the unreviewed drawing. The piece arrives, and it does not match. Now you have a remake, and an argument about whether the stamp on the cut sheet was a stamp on the shop drawing.

The real miss was a pile that did not separate types, statuses, and what was actually released to the field. I am not quoting a typical remake cost here.

How to keep them straight in the file

In the Google Drive or Dropbox job file, keep submittals named with the type, the number or spec section, and the status. Do not store an open shop drawing in the same "ready for the field" place as an approved product data sheet. If you use a current-set or "released to field" folder for approved submittals, only reviewed documents, with their comments, belong there.

A few practical rules:

  • Log each shop drawing as its own line, even if it arrived in a combined package.
  • When a package comes back mixed (some items approved, some approved as noted, some to be resubmitted), split those statuses in the log. Do not mark the whole package approved.
  • Put "approved as noted" comments where the installer will see them.
  • For samples, file a photo, the transmittal, and the approval note.
  • Do not let an unreviewed shop drawing be printed onto a plan rack just because it looks official.

If the types are already mixed

You do not have to rebuild the history of every catalog cut on the job. Start by pulling out the open and recently returned shop drawings, confirming their status, and making sure nothing unreviewed is in the field.

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 a recent package that mixed types or statuses. I will tell you straight whether a cleaner log 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