Finding Every Submittal in a 900-Page Spec Book

The submittals that get missed are rarely in the sections you own. They sit in sections you marked "by others" and never opened. To catch them, count the book against its table of contents, give every section a line, search the whole book for the words that name your scope, and tie every register row to the paragraph that requires it.

Your pay app comes back with one line held. The engineer's note cites the blower section in Division 43, a section you skimmed at bid time and wrote off as the blower supplier's. Paragraph 1.4.C, three pages in: "The Process Control System Supplier shall submit interface wiring diagrams for the blower control panel." That's you. It's been you since award. Your register had 38 rows and none of them was this one, because your register was built from your sections, and this wasn't one of them.

A register is only as complete as the list of sections you walked to build it. Building the submittal register covers the rows themselves. This article is the part before and after: proving you didn't skip a section.

Count the book first

Open the table of contents and count the sections. Then count the sections actually in the PDF. On a 900-page book those numbers disagree more often than you'd think.

• A section listed but not bound. It was issued in another volume, it's "to be issued by addendum," or someone forgot to export it. If it's anywhere near your scope, ask for it by RFI now, not when its first demand surfaces.
• A section bound but not listed. Usually a late add the spec writer never put in the TOC. It's the one nobody reads, because nobody knows it's there.
• One file holding several sections. Count by section heading, not by file.

Write the count down. It's the total every later step has to add up to.

Give every section a line

Now give every section in the book one line: ours, interface, or by others. Which CSI divisions an integrator owns covers how to make that call. The point here is the sum. If the book has 212 sections, the list has 212 lines. A list of the 30 sections you care about can't tell you which of the other 182 you skipped.

Most lines take five seconds: "08 71 00, door hardware, by others." That's fine. The line exists so you know you looked.

Search the whole book for your name

Reading 182 sections you don't own isn't realistic. Searching them is. Run these through the whole PDF, not only your sections:

• Your role, every way the book spells it. "Control system supplier," "PCSS," "instrumentation contractor," "system integrator," "SCADA contractor," "controls contractor." Check Division 01's definitions for the exact term this engineer uses, then search that too.
• Your section numbers. Every place another section says "as specified in Section 40 61 13" or "per Section 13400" is a section that hands you work.
• Signal words. "4-20 mA," "dry contact," "Modbus," "EtherNet/IP," "remote monitoring," "PLC," "interface." Packaged equipment sections use these when they expect someone to wire into them.
• Hand-off phrases. "Coordinate with," "furnished by others," "by the controls," "to be connected by."

Every hit in a section you marked "by others" is a reread. Most will be harmless. One of them is the blower paragraph.

A scanned book won't search. If Ctrl+F finds nothing on a page you can plainly see words on, run text recognition on the file before you trust a single empty result.

Follow the related sections out

Your own sections point at their neighbors. Article 1.2 or 1.3 of most sections, Related Requirements or Related Sections, lists the sections that touch this one. Each listed section gets at least an interface read: the VFD section your panels talk to, the MCC section you wire into, the network section the electrician pulls cable for. A related section that isn't in the book goes on the same RFI as the missing sections from your count.

In your sections, search for "submit" past Part 1

The SUBMITTALS article in Part 1 is the obvious list. It's not the whole list. Search each section you own for "submit," "furnish to the Engineer," "for review," "certif," and "report," and read every hit in Parts 2 and 3. Part 3 is where test procedures, test reports, and training plans hide, often due weeks before the test they describe. How to read a spec section for submittal requirements has the full reading order.

Tie every row to its paragraph

Every register row cites the paragraph that requires it: "43 11 00, 1.4.C." Then run the check backward. Every "submit" hit in a section you own maps to a row, or to a written "not required" with a reason. If you found 64 hits and you have 41 rows and 9 not-required lines, 14 demands are unaccounted for.

Give each row a type while you're there: product data, shop drawings, or O&M and closeout. They come due at different points in the job and go to different reviewers, and a row with no type is a row nobody schedules. Shop drawings vs. product data covers the split.

Rerun it when an addendum lands

An addendum is a small spec book. Count it the same way: which sections it adds, deletes, or reissues. Put new sections on your line list. Run your search terms through the addendum text. A revised paragraph that adds "submit" to a section you own is a new row, and a revised paragraph in a "by others" section that now names you is a new obligation that arrived in a document most people skim for bid date changes.

Use it again at closeout

Filter the register to the O&M and closeout rows and you have the turnover checklist, already tied to the paragraphs that demand each item. No second read of the book at the end of the job, when you have the least time for it. Collecting O&M manuals during submittals covers getting those documents early.

Want this as a sheet to work from? The Spec to Submittal Checklist puts Division 01, your sections, the register, and the pre-send checks on two pages.

How Submittal Kit handles this

The section you never opened is the one that holds your pay app. In Submittal Kit you upload the spec book and every section files under its division, scanned books included, so All sections shows you the whole book to check against the table of contents. List what you supply on Spec setup and each line comes back with the section that specifies it, wherever in the book it sits, with the sentence that mentions it. Each section you own lists what it asks you to submit, quoted with its article reference and grouped by kind: product data and shop drawings, test procedures, O&M data, and the rest. Answer each with Create, Already covered, or Not required, and the Submittal Log shows how many are still unanswered. Load an addendum and each section it touches opens with what it added, removed, or changed, with the old and new wording.

Disclosure: I build Submittal Kit. The count, the line list, and the search work in a spreadsheet and a PDF reader too.