Submittal log from spec book to finished register, manual method and import

What a finished submittal log contains

Before reading a single page, decide what each row must hold. Changing columns halfway through a spec book means going back over sections you already finished. A practical register has these columns at minimum.

Keep the description close to the spec wording. When a sub disputes what was required, the log should let anyone go straight to the paragraph and read it. If you need a blank layout to start from, the submittal log template page shows the columns in the order most teams use.

Step 1, read the table of contents

Start with the project manual table of contents, not with Division 03. List every section that is actually included in the project, by number and title, in the first column of a working sheet. Many offices issue a spec book with sections from their master that are listed but marked as not used, or sections bound into a separate volume for MEP. Note the issue date and any addenda that added or deleted sections. This list is your checklist: when the log is done, every section on it should either have rows or a note that it requires no submittals.

Step 2, read Division 01 procedures

Read Section 01 33 00 Submittal Procedures in full, then the other Division 01 sections that create requirements of their own: 01 25 00 Substitution Procedures, 01 40 00 Quality Requirements, 01 77 00 Closeout Procedures, 01 78 23 Operation and Maintenance Data, 01 78 39 Project Record Documents, and any sustainability or commissioning section. Division 01 tells you the numbering format, the review time the design team is allowed, how packages are combined, which items need the contractor's stamp and which closeout documents apply to every section without being repeated there. Write those rules at the top of the log before you add a single row.

Step 3, read Part 1 of every section

Now go section by section. In each one, find the submittals articles in Part 1, typically titled Submittals, Action Submittals, Informational Submittals and Closeout Submittals, often numbered 1.4 to 1.7 depending on the master. Each lettered paragraph inside those articles is usually one row, sometimes two. "Product Data: For each type of product" on a section with five products may be one row or five, depending on how your team packages; decide once and apply it everywhere.

• Read the lead word of each paragraph to set the type (Product Data, Shop Drawings, Samples, Qualification Data, Warranty).
• Copy the paragraph reference exactly, for example 1.4.C.
• Note any special condition in the paragraph: signed and sealed calculations, sample size, number of sets, field mockup.
• Skim Part 2 and Part 3 for submittal language outside Part 1, such as a field quality control report or a manufacturer's field service report.

Step 4, type the rows

Type each requirement as a row with its number, type, classification and description. Use the section number as the prefix and a running sequence within the section, so 093000-001, 093000-002 and so on. Assign the responsible company from the buyout list and the default reviewer from Division 01. Leave dates blank until you have lead times. This step is mechanical but long. On a large project manual, a careful engineer spends days here, and the risk of skipping a paragraph grows as the afternoon gets longer.

Step 5, cross-check schedules and drawings

The spec is not the only source of submittal requirements. The drawings carry schedules and notes that create items the specs only imply. Cross-check at least these.

• Door, frame and hardware schedules against 08 11 13, 08 14 16 and 08 71 00 rows.
• Finish schedules and finish legends against 09 sections, especially samples for each color and pattern.
• Equipment schedules on mechanical, plumbing and electrical drawings against Division 22, 23 and 26 product data rows, one per equipment tag group.
• Structural general notes that ask for delegated design or special inspections.
• Drawing notes such as "provide shop drawings for review" on miscellaneous metals or millwork.

When a drawing requires an item and no spec paragraph covers it, add the row with the sheet reference and flag it for a request for information. Do not drop it because the spec is silent.

What gets missed most often

Some items are missed on almost every hand-built log, not because engineers are careless but because the requirement sits somewhere other than Part 1 of the obvious section.

• Closeout items set in Division 01 and not repeated in each section: warranties, O&M manuals, spare parts, extra stock and record documents.
• Qualification data and installer certifications listed as informational submittals in the same article as product data.
• Samples for every exposed finish on finishes sections, typed as a single product data row.
• Hardware and keying schedules on 08 71 00, which need their own rows next to product data.
• Delegated design calculations on stairs, railings, curtain wall and cold-formed framing.
• Test and balance requirements on 23 05 93, where the agenda, the qualifications and the final report are separate items at different times.
• Manufacturer field reports and warranties on roofing such as 07 54 23 TPO Roofing.
• Items added by addenda after the log was started.

A short review of these categories at the end of the manual method catches most gaps. The types of submittals in construction article explains how action, informational and closeout submittals split, which helps when you sort the classification column.

Build the register by importing the spec

Submittal does Steps 1, 3 and 4 for you. Upload the project manual as a PDF, scanned pages included thanks to text recognition, or upload single sections when the book arrives in parts. The AI finds each MasterFormat section number and title, reads the Part 1 submittals articles, and builds one row per required item with the spec section, paragraph reference, type, a description quoted from the spec, classification and a field for lead time. Every row links back to the exact paragraph it came from, so you can open the source in one click.

From there you work the way you would on a hand-built log, just from a complete starting point. Assign rows to subcontractors in bulk, set reviewers and due dates, merge rows you package together and split rows that need separate tracking. If you already have a partial log, import it from XLSX or CSV and keep your numbering. The construction specification software page shows the paragraph tracing and the reading step in detail, and the submittal software overview covers every feature after the import.

Spec pages read by AI count against the plan's monthly allowance: 1,500 pages on Starter, 8,000 on Team, 40,000 on Business and 150,000 on Enterprise. A typical project manual fits comfortably in a single month on Team, and you can import sections as they are issued rather than the whole book at once.

What to verify after the import

The import replaces the reading and typing, not the engineer's judgment. Before you send the log to the team, verify these points.

• The section list matches the table of contents and addenda, with nothing listed that is not in the project.
• Division 01 rules are reflected: numbering format, review time and the closeout items that apply to every section.
• Rows that your team packages together are merged, and rows that need their own status are split.
• Schedule and drawing cross-checks from Step 5 are done, because the drawings are not part of the spec import.
• Responsible companies and reviewers are set, and lead times are entered for long lead items so required-by dates are calculated.

Doing the verification from a full register is faster than building one, and the paragraph link on every row means each check is one click away from the source.

A submittal log is only useful if it stays current. Once packages start moving, the log should show the current revision, the latest stamp, who holds the ball and how many days are left before the required date. In Submittal, packages are routed through GC review and then the architect and consultants with the stamps Approved, Approved as noted, Revise and resubmit, Rejected and For record only. Resubmittals create the next revision, for example 087100-002-R1, with the history kept. Reminders go to whoever holds the item, and approved warranties, certificates and O&M data assemble into a closeout binder on Business and Enterprise. The submittal register page shows how the finished register looks during construction.

Frequently asked questions