Create the register
Write specific actions, resolve duplicates and grouping, confirm responsibility, and build schedule logic.
Specification review guide
How to find submittals in construction specifications
Part 1.4 may say “Submittals,” but the real work is often scattered through products, execution, quality assurance, and closeout language.
Start with Part 1—but do not stop there
Submittal articles commonly list product data, shop drawings, samples, certificates, delegated-design calculations, test reports, and qualification data. Read the directive and its children together; the useful action may sit several levels below the heading.
Check Part 2 for selections and fabrication detail
Product articles may require color selections, mockups, fabrication drawings, or documentation that is not repeated in the primary submittal article.
Check Part 3 for field records and testing
Execution language can create requirements for reports, logs, test results, surveys, or commissioning records. Decide whether each is a preconstruction submittal, a field record, or a closeout deliverable.
Search by intent, not one keyword
“Provide,” “furnish,” “document,” and “certify” may create deliverables. “Submit” can also appear in procedural text that does not belong in the register. Context is the deciding factor.
Review the hierarchy around every candidate.
Identify the governing section
Confirm the section number, title, and document issue before evaluating the requirement.
Read the complete lead-in
A parent paragraph may provide the action and type for several short child paragraphs.
Capture the specific subject
Use child language to identify what the product data, drawing, sample, report, or certificate covers.
Check nearby qualifications
Look for timing, required contents, professional seals, sample quantities, coordination, and related requirements.
Record the source
Save the page and paragraph before moving on so later verification does not require another search.
Useful search terms
Search terms can locate candidates, especially in a searchable PDF, but they should begin a review rather than decide the result.
- submit, provide, furnish, document
- product data, shop drawings, samples
- certificates, qualification data, calculations
- test reports, field reports, logs, records
- warranty, maintenance data, training, closeout
Why keyword lists miss requirements
Authors use varied language. A child item may contain only a noun because the action appears above it. A requirement may be expressed through “shall demonstrate,” “obtain,” or “retain for submission.” Conversely, “submit” may appear in an instruction about substitutions or a description of a process that creates no individual register item.
Examples that require context
Specification languageReview question
“Wiring diagrams.”What parent paragraph supplies the action and submittal type?
“Installer shall have five years’ experience.”Is qualification data required, or is this only a performance qualification?
“Submit in accordance with Section 01 33 00.”Does this paragraph identify a specific deliverable, or only reference the procedure?
“Provide certified test reports.”When are reports produced, by whom, and should they be tracked as field records?
“Colors as selected by Architect.”Does another paragraph require selection samples or a color chart?
Quality-assurance requirements
Installer qualifications, manufacturer qualifications, testing-agency qualifications, mockup documentation, and delegated-design credentials often appear in Part 1 but outside the main submittal list. Determine whether the section requires documentation to be submitted or simply establishes a minimum qualification.
Selections inside product requirements
Finish, color, pattern, accessory, and optional-feature selections may depend on samples or product information. Trace these back to any explicit sample or product-data requirement instead of creating a row from descriptive language alone.
Records generated during execution
Field reports, test results, inspection records, survey data, and commissioning documents may not exist at project startup. Identify them so they are not forgotten, but classify and schedule them differently from approval-dependent product submittals.
Requirements created through cross-references
A section may direct the contractor to submit information under another section or incorporate a related system’s requirements. Follow enough of the cross-reference to understand the obligation, avoid duplicates, and retain both references when they help explain scope.
Finding submittals FAQs
Are all submittals located in Part 1?
No. Part 1 is the most common location, but deliverables may appear in product, execution, testing, commissioning, and closeout language.
Is every sentence containing “submit” a register item?
No. Many are procedural instructions, cross-references, or descriptions. A row should represent a specific deliverable the project team intends to prepare and track.
Can drawings contain submittal requirements?
Yes. General notes, schedules, details, and discipline-specific notes may add requirements. Specification review is one important part of completing the register.
Reading a typical technical section without missing the edges
Begin with the section title and related requirements. In Part 1, identify the main submittal article and read each parent directive with its children. Then review quality-assurance language for qualifications, testing agencies, mockups, and delegated design. Record only the items that require information or a physical item to be provided—not every minimum qualification stated in the section.
In Part 2, note products that require project selections or fabrication information. Confirm whether those subjects are already covered by a product-data, sample, or shop-drawing directive. In Part 3, look for field reports, testing results, demonstrations, training records, and documentation produced during execution. Finally, review warranty and closeout articles.
Suppose a coating section requires product data and color samples in Part 1, states “colors as selected by Architect” in Part 2, and requires a field-application report in Part 3. The register might contain three distinct actions: coating-system product data, color selection samples, and the field-application report. The Part 2 selection language supports the sample requirement but should not become a duplicate fourth row.
When the PDF is scanned
Optical character recognition can confuse section numbers, paragraph labels, and characters. Visually verify questionable pages, especially when a search appears to skip a section or extracted text loses indentation. Record uncertainty rather than inventing a precise paragraph reference.
When the section uses unusual formatting
Performance specifications, short-form sections, consultant-authored content, and owner standards may not follow a predictable article structure. Use the same intent-based review—deliverable, source, purpose, timing, and responsibility—without assuming every manual follows one template.