How to Build a Submittal Register From the Specifications
Turn every submittal requirement in the specifications into a register your team can schedule, track, and review against the source.
A submittal register looks like an administrative list, but it is the procurement plan in disguise. Every row is a product, drawing, sample, or certificate that has to be prepared, reviewed, approved, ordered, and delivered before the work it supports can start. When the register is built late or from memory, the misses show up as long-lead surprises, rejected packages, and crews waiting on material that was never released.
The requirements already exist. They are spread across the project specifications, one section at a time. The work is to find each one, record it in a form the team can schedule, and keep it connected to the language that created it.
Start with the procedures in Division 01
Before reading individual sections, read the general submittal procedures, usually in Division 01. This is where the project sets the rules every package must follow: the submission format and transmittal requirements, how long the design team has to review, how resubmittals are handled, and what must accompany each package.
Those rules shape the dates in your register. A ten-working-day review period, an extra cycle for a likely resubmittal, and a required coordination drawing all push the submission date earlier than the field schedule alone would suggest.
Read every section's submittal article
Most specification sections list their submittals in Part 1, often split into action submittals, informational submittals, and closeout submittals. Read each one in full. Typical items include:
- Product data for each specified product or system - Shop drawings showing fabrication, layout, and connections - Samples for color, finish, or texture selection - Certificates and test reports demonstrating compliance - Delegated-design submittals with the required professional seal - Qualification data for installers, fabricators, or testing agencies - Operation and maintenance data and warranties for closeout
Requirements also hide outside Part 1. A quality-assurance paragraph may require a mockup, a field-testing article may require a report, and a coordination paragraph may require drawings that reference another trade. Treat the whole section as the source, not just the heading labeled Submittals.
Make each row one requirement
A register row that says "Section 26 24 13: product data and shop drawings" hides two submittals with different preparers, review paths, and dates. Split compound requirements so each row has one deliverable. At a minimum, capture:
- Specification section and paragraph - Submittal type and a plain-language description - Responsible trade or subcontractor - The governing quote and the page it came from
Keeping the quote and page with each row matters more than it looks. When a reviewer, subcontractor, or architect questions a row, the team can open the source instead of debating what the specification probably meant.
Add the dates that drive procurement
A register becomes a planning tool when each row has dates. Work backward from when the material must be on site:
1. Start from the date the field needs the material delivered or installed. 2. Subtract fabrication and delivery lead time. 3. Subtract the review period, plus time for at least one resubmittal on complex items. 4. Subtract the time the subcontractor needs to prepare the package.
The result is the date the package must be submitted, not the date someone hopes to see it. Flag long-lead items such as switchgear, elevators, curtain wall, and major mechanical equipment early, because their submission dates often fall during buyout, before every subcontract is signed.
Keep the register connected as the documents change
Addenda, bulletins, and RFI responses can add, change, or remove submittal requirements. Update the affected rows, note the document that changed them, and keep the history instead of overwriting it. A register that silently drifts from the current specification is worse than no register, because the team trusts it.
Review against the requirement, not the summary
When a package arrives, review it row by row against the requirement it answers. A package that includes product data but omits the required test report is partially compliant, not compliant. If the evidence is missing, record it as missing. A reviewer who can see the governing quote beside the submitted evidence makes a faster, more defensible decision than one comparing a summary to a memory.
How Mobus builds the register
Mobus Submittal Review builds an editable, cited register from the specification. Each requirement carries its source quote and page, and a reviewer can clean up or add rows before any package is reviewed. When the submittal arrives, Mobus places each governing requirement beside the submitted evidence and records one of four explicit states: fully compliant, partially compliant, non-compliant, or not found.
The reviewer stays in control. Mobus preserves its initial classification while the reviewer sets the final status, rationale, and action needed, and the register and review report become exportable only after finding counts and citations reconcile. Today the workflow reads native-text English PDFs; scanned files that need OCR are outside its current scope.
A short checklist to start
- Read the Division 01 submittal procedures first and note the review periods. - Walk every section, including quality-assurance and closeout articles. - Split compound requirements into one deliverable per row. - Keep the governing quote and page on every row. - Back-schedule submission dates from need-by dates and lead times. - Update rows when addenda or RFIs change requirements, and keep the history.
Built this way, the register stops being a spreadsheet the team maintains for compliance and becomes the plan that keeps buyout, procurement, and the field moving together.