Planning & documentation
Sequencing a Steel Building Submittal Register
Build a steel building submittal register around package dependencies, reviewer responsibilities, resubmittals, and release milestones.
Define the condition and its scope
The register should show dependencies, not simply an alphabetical list of product names.
Coordination connects the steel package to the rest of the building. Red iron framing, cold-formed infill, foundations, doors, roof equipment, and interior finishes can each have a different document author. A correct component can still arrive with an unresolved interface. Establish which issued drawing governs each condition, how questions reach the responsible professional, and where responses are recorded. Separate a contractor's field measurement from a designer's acceptance of that measurement, and keep both available to the people preparing fabrication or installation documents.
References: Commissioning documents: process, contents, and acceptance · Project Planning Guide
Gather the inputs before deciding
Group submittals by the work they enable and identify upstream information required to prepare them. Include equipment dimensions, opening geometry, foundation interface data, enclosure transitions, and selected products where relevant. Assign preparation, review, response incorporation, and release roles separately. Record the specification or agreement defining required review status. A package submitted for information should not be placed in the same release category as a package requiring technical acceptance before fabrication. Keep incomplete inputs visible in the register.
- Package dependency chain
- Named review responsibility
- Required review status
- Procurement release milestone
References: Commissioning documents: process, contents, and acceptance · Project Planning Guide
Set observable handoff deliverables
Reviewing a roof curb before equipment dimensions are stable can require repeated revisions.
| Input | Evidence to keep with it | Review status |
|---|---|---|
| Package dependency chain | Package dependency diagram | Identify reviewer and written decision |
| Named review responsibility | Reviewer and response log | Identify reviewer and written decision |
| Required review status | Accepted release status and date | Identify reviewer and written decision |
Sequence review and release
Build the dependency chain with the contractors and designers responsible for each package. Compare submission and review dates with actual procurement milestones, allowing for the project's agreed review and resubmittal process. When comments return, record who incorporates them and whether a revised package must be reviewed again. Update successor packages when an upstream selection changes. Reconcile the register at coordination meetings using actual statuses instead of replacing overdue dates with optimistic forecasts that conceal the unresolved dependency.
- Locate package dependency chain in the current record.
- Compare named review responsibility with the table's evidence.
- Document the decision: Resolve upstream inputs before treating downstream packages as final.
Worked project coordination example
The register links mechanical equipment selection to curb details, roof-opening coordination, and panel release. A pending equipment decision remains visible as the predecessor of three later packages.
Apply the stated release decision to the case: Resolve upstream inputs before treating downstream packages as final. The responsible team determines acceptance for the actual project and records any condition that still requires resolution.
Keep a closeout record another team can use
For every released package, retain the reviewed revision, disposition, incorporated comments, and release authorization. Mark superseded submissions so installers do not retrieve an old apparently approved detail. Carry accepted products into purchasing and handoff schedules. At project closeout, distinguish completed submittal obligations from deferred testing or remaining records. The register should explain the path from submitted information to the actual installed package; a final column of dates is insufficient if the accepted revision cannot be located.
For this issue, include accepted release status and date in the handoff. If review remains pending, identify the dependent work and its owner; do not present the record as a completed technical acceptance.
Common questions
Is submitted the same as ready for purchase?
No. The register must identify the review status required for release.
How should package dependency chain be documented?
Resolve upstream inputs before treating downstream packages as final. Retain package dependency diagram and check that the decision reached the team performing the dependent work.
Sources & further reading
Use the current documentation for the exact product and project. Source links do not imply a partnership or endorsement.
- Commissioning documents: process, contents, and acceptance Whole Building Design Guide
- Project Planning Guide U.S. General Services Administration / WBDG
Prepared with AI assistance. Linked references require current project-specific review. How these guides are prepared.
Prepare a supply inquiry
- Record the project drawing or detail and the specified product, profile, or system.
- List the complete configuration, physical units, quantities, and cuts per piece.
- Request current manufacturer documents; confirm compatibility, price, and availability before ordering.
- Obtain the responsible professional's review for loads, code requirements, or installation.