---
title: 'Construction submittals: build the register before procurement commitments'
url: 'https://piper-ai.com/resources/construction-submittal-register-prebid'
description: 'Build a submittal register from project requirements and connect review, procurement and installation dates to the cost and schedule assumptions in the bid.'
contentTypes: [guide]
publishedAt: '2026-11-16T16:37:09.446Z'
updatedAt: '2026-11-16T16:37:09.457Z'
author: 'Ido Gedanken, CEO'
readingTime: 2
---

# Construction submittals: build the register before procurement commitments

Build the submittal register before procurement dates are promised. For each required item, identify the source, preparer, GC review, designer or other reviewer, required lead time and release gate. Then include the work of preparing and coordinating it in the relevant trade and GC carries.

A submittal conveys required information for review, such as a product data sheet or shop drawing. An RFI asks for clarification; a response may change what the submittal must show. Under [FAR 52.236-21](https://www.acquisition.gov/far/52.236-21), when that federal clause applies, the contractor must coordinate and review required shop drawings. Other contracts can assign different procedures and review periods. Read the actual agreement and specification rather than assuming this clause governs.

## Extract the register from the bid set

Review Division 01 and each technical section for required items and review procedures. Capture specification section and paragraph, equipment or work area, required format, responsible trade, reviewers, review duration, resubmission allowance, milestone and cost owner. Cross-check procurement dates against required decisions. [Turn specifications into trade scope](https://piper-ai.com/resources/construction-specifications-masterformat-scope-review), and [connect RFIs to scope and pricing](https://piper-ai.com/resources/construction-rfi-prebid-scope-review) when the documents do not specify a review gate.

## Example: air-handler shop drawing

Assume an illustrative contract requires a reviewed air-handler shop drawing before order release. The mechanical subcontractor prepares the drawing; the GC checks coordination; the designer responds. A supplier needs eight weeks after release. If preparation takes two weeks, GC review one week and designer review two weeks, the planned path is 13 weeks before delivery, excluding resubmission and holidays. These are assumed durations, not standard review periods. Add a project-specific resubmission allowance where justified, and confirm whether the schedule permits early procurement.

| Register field | Illustrative entry | Bid action |
| --- | --- | --- |
| Source and item | Mechanical specification, air-handler shop drawing | Verify exact paragraph and model |
| Preparation | Mechanical trade and supplier | Confirm quote includes drawing and revisions |
| Review gate | GC then designer before order | Confirm contract language and durations |
| Release and delivery | After required response, eight weeks to delivery | Compare to construction milestone |
| Open issue | Duct connection conflicts with steel | Assign resolution before final drawing |

The duct connection may require BIM coordination, but a model check does not replace the specified submittal review. If a bidder excludes coordination or revisions, normalize its price and ask for a defined scope. Include GC review time and avoid counting trade preparation twice.

## Transfer the register at award

Mark each item pending, submitted, returned or accepted using the agreement's terminology. Preserve the controlling revision and show changes to dates and responsible parties. A register is a planning tool; it does not itself grant approval or alter the contract.

### Develop the submittal scope

Piper's [Scope Generation](https://piper-ai.com/use-cases/scope-generation) turns project requirements into trade scopes with source-linked findings. The team builds and maintains the register and decides the approval and procurement sequence.
