Project management

How to manage submittals on a construction project

Manage submittals by building a register from the spec sections at the start of the job, scheduling each one backward from its install date and lead time, reviewing sub submittals before they go to the architect, and tracking every item until the approved copy is in the field.

Two construction professionals compare an aluminum frame sample with shop drawings in a site office.
Check the proposed sample and coordinated drawings before releasing fabrication. AI-generated illustration.

A submittal is anything the contractor sends the design team to show what it plans to install: shop drawings, product data, samples, mock-ups, test reports, and certificates. Managing them well comes down to four habits. Build a complete register from the specifications in the first two weeks. Schedule each submittal backward from when the material must be on site, using real lead times. Review every subcontractor submittal against the specs before forwarding it. Track each one in a single log with a due date and ball in court until the approved copy reaches the crew. Late submittals are one of the most common reasons material shows up late, and they are almost always preventable.

The contractor's responsibility for submittals

Architect approval does not move the risk off the contractor. On federal jobs, FAR 52.236-21 requires the contractor to coordinate shop drawings and review them for accuracy, completeness, and compliance with contract requirements before submitting them, says the contracting officer's approval does not relieve the contractor of responsibility for errors or omissions, and says any work done before approval is at the contractor's risk. The same clause requires the contractor to describe any variation from the contract in writing at the time of submission. Private contracts based on standard forms put similar duties on the contractor, so read yours.

In practice this means a GC stamp on a sub's submittal should mean something. If the GC forwards a door hardware submittal that does not match the hardware schedule, the GC owns the problem when the wrong locksets arrive.

How to manage submittals in 7 steps

  1. Build the submittal register. Go through every spec section, usually in the submittals paragraph of Part 1, and list each required item. Organize the register by MasterFormat section so it matches the project manual.
  2. Assign each item. Name the sub or supplier responsible and send each one its list with dates. Include the requirement in subcontracts so submittals are a contract obligation, not a favor.
  3. Schedule backward from install. For each item: install date, minus delivery lead time, minus fabrication time, minus review time, minus a resubmittal cushion. That gives the date it must be submitted. Put long lead items at the top.
  4. Review before you forward. Check the submittal against the spec section, the drawings, and related trades. Mark deviations clearly. Return incomplete packages to the sub instead of sending them on.
  5. Transmit with a clear cover sheet. Submittal number, spec section, revision, what is included, any deviations, and the date you need it back.
  6. Track the ball in court. Log dates sent and received at every step. Follow up a few days before a response is due, not after.
  7. Distribute and file the approved copy. Send it to the sub, the supplier, the super, and the field set. Mark superseded versions void. Approved submittals become part of the closeout record.

Common submittal types and what to check

Submittal types and review checks
TypeExamplesWhat the GC should check
Shop drawingsSteel, millwork, curtain wall, ductworkDimensions, connections, coordination with other trades
Product dataFixtures, equipment cut sheets, finishesModel numbers, options, and listings match the spec
SamplesPaint colors, tile, carpet, brickCorrect selections, sample size and quantity per spec
Mock-upsMasonry panel, window installationLocation, scope, approval before production work
Test reports and certificatesConcrete mix design, fire ratingsCorrect standards cited, current and project-specific
Closeout submittalsWarranties, O&M manuals, attic stockCollected during the job, not at the end

Worked example: scheduling a storefront submittal

Here is an example on a retail building. The superintendent needs aluminum storefront installed by June 30 so the building can be dried in before interior finishes. The storefront sub says fabrication and delivery take 8 weeks after approved shop drawings. The contract gives the architect 10 working days to review, and the PM assumes one resubmittal.

Working backward from the install date (example)
MilestoneDateHow it was set
Install completeJune 30From the schedule
Material on siteJune 16Two weeks of installation
Approved shop drawingsApril 218 weeks fabrication and delivery
Resubmittal sentApril 7Two weeks for second review
First submittal to architectMarch 24Two weeks for first review
Sub submits to GCMarch 17One week for GC review

If the storefront sub is not under contract until March 10, the PM has one week of slack. That is the kind of thing to know in January, not in May. The same math applied to switchgear, elevators, or rooftop units can reveal that the schedule was impossible before a shovel hit the ground. Read more in how to manage long lead items.

Handling rejected and resubmitted items

Rejections happen. What matters is how fast the corrected package goes back. When a submittal returns marked revise and resubmit, log the date, send the comments to the sub the same day, and set a firm resubmittal date in the log. Ask the sub to answer every review comment in a short response letter, so the reviewer can check each comment instead of rereading the whole package. Keep the revision number on every page. If the same item gets rejected twice, call a short meeting with the sub and the reviewer. A 20-minute conversation usually resolves what three rounds of markups could not, and it protects the delivery date you planned around.

Mistakes to avoid

  • Building the register late. If the register is made as submittals arrive, missing items are found when the material is needed.
  • Rubber-stamping. Forwarding a sub's package without reading it wastes a review cycle when it comes back rejected.
  • Hiding substitutions. Products that differ from the spec must be called out. Use a substitution request where the specs require one.
  • Ordering before approval. Releasing fabrication on an unapproved submittal is at your risk.
  • Not tracking review times. If the design team consistently runs late, the log is your evidence for a time extension.
  • Forgetting closeout submittals. Warranties and O&M manuals are submittals too. Collect them as each trade finishes.
  • Letting the field build from the bid set. Crews should work from approved submittals and current drawings. Pull outdated cut sheets from the trailer when a new revision is approved, and tell the foreman what changed.

Templates, terms, and tools

Start with the submittal log template and keep it beside the RFI log template, since many submittal questions turn into RFIs. Related terms: submittal schedule, lead time, mock-up, and specifications. For questions that come up during review, see how to manage RFIs without slowing the job.

Smart Business Automator tracks submittals and RFIs together with due dates and ball in court, extracts key data from product sheets, and alerts the PM when a long lead item is falling behind. See RFI and submittal tracking automation.

Frequently asked questions

What is a submittal register?

A submittal register lists the items the specifications require, with an identifier, responsible party and planned dates. Build it from the contract documents before packages start arriving. Add submission, review and revision status as work progresses so missing items remain visible.

How to create a submittal?

Identify the applicable specification section, assemble the required drawings, product information or samples, and check the package against the project requirements. Use a cover sheet identifying the project, item and revision. Clearly flag proposed deviations, then send the coordinated package through the agreed review route.

What are some examples of submittals?

Examples include equipment product data, coordinated fabrication drawings, finish samples, mock-ups, test reports and operation manuals. Each serves a different purpose: a sample can establish an accepted finish, while a shop drawing can show dimensions and connections. The specifications determine what the project requires.

What are the three main reasons submittals are rejected?

There is no universal ranking of three reasons. Three useful checks are whether the package is complete, whether the proposed product or detail matches the specified requirement, and whether dimensions and interfaces are coordinated. Read the actual review comments before deciding what needs correction.

What does a submittal schedule look like?

Use one row per required package, showing its specification section, supplier, review duration, planned submission date, required approval date and linked installation activity. Include time for correction and resubmission. Keep the current forecast beside the original target so changes in procurement timing are visible.

What is a submittal vs RFI?

An RFI asks for missing information or clarification; a submittal presents the product, material or detail proposed for the work. A submittal review can reveal a question that needs an RFI. Track the connection, while following the contract's separate process for changes in price, time or scope.

What is a technical submittal?

A technical submittal presents information needed to assess a proposed product, system or detail against project requirements. It might contain performance data, drawings, test information or calculations requested by the specifications. Its required contents and reviewer depend on the item and the contract.

Who approves submittals?

Follow the review responsibilities in the contract. Contractors generally coordinate and review their packages before sending them to the designated reviewer. On federal work using FAR 52.236-21, the Contracting Officer indicates shop-drawing approval or disapproval; that approval does not remove the contractor's stated responsibilities.

Sources

  1. Acquisition.gov: FAR 52.236-21 Specifications and Drawings for Construction
Written and edited by

Maurice Francois writes and edits construction operations guides for Smart Business Automator. More from Maurice on the Scaling Legends podcast.

Get a free assessment