Construction Submittals: A Practical Guide for GCs and Project Managers
Construction submittals are the documents, samples, and product data a contractor provides to the design team to confirm that what will actually be installed matches what the drawings and specifications call for. They are the paper trail that connects the design intent on paper to the real materials showing up on the loading dock. Get them right and the job flows. Get them wrong, or late, and you end up with the wrong fixtures, a rejected mockup, or a crew standing around waiting on an approval that never came.
For general contractors, project managers, and superintendents, submittals are less about paperwork and more about protecting the schedule. Long-lead items in particular live or die by how fast the submittal log moves. This guide walks through what submittals are, the review workflow, the common types you'll handle, and a practical approach to keeping the log from becoming your critical-path bottleneck.
What Construction Submittals Actually Are
A submittal is documentation the contractor sends up the chain to the architect or engineer for review before a material is fabricated, ordered, or installed. The specifications section of the contract documents tells you what needs to be submitted, and the drawings tell you where and how it goes. The submittal is your proof that the specific product you intend to use satisfies both.
Think of it as a verification loop. The designer specified a performance requirement or a named product. You, or your subcontractor, respond with the actual cut sheets, shop drawings, or physical samples for the item you plan to buy. The design team reviews it against their intent and returns it marked with an action, and only then does procurement or fabrication proceed.
The key point that trips up new PMs: a submittal review is not the designer redesigning the work or taking on the contractor's means and methods. It is a check that the proposed item conforms to the design. The contractor remains responsible for dimensions, quantities, and coordination. That distinction matters when a dispute comes up later.
Common Types of Submittals
Not every submittal is the same, and knowing the category helps you set expectations for how long review will take and how much detail is required.
- Shop drawings: contractor- or fabricator-prepared drawings showing how a component will actually be built and installed, such as structural steel, rebar, curtain wall, or millwork.
- Product data: manufacturer cut sheets, catalog pages, and performance specs for items like plumbing fixtures, HVAC equipment, and light fittings.
- Samples: physical examples of finishes, colors, and materials, such as brick, tile, paint, or carpet, so the design team can approve appearance in the flesh.
- Mockups: full-scale assemblies built on or off site to confirm workmanship and appearance before full production begins.
- Quality-assurance and closeout submittals: test reports, certifications, warranties, operation and maintenance manuals, and as-builts that document compliance and hand the building over to the owner.
The Submittal Review Workflow
Most projects follow the same basic path, even if the tools differ. Understanding each handoff helps you spot where days quietly disappear.
First, the subcontractor or supplier prepares the submittal and sends it to the general contractor. The GC reviews it before passing it along, and this internal check is the step teams most often skip. A GC review catches obvious errors, confirms the item matches the spec, and stamps that coordination with adjacent trades has been considered. Forwarding a subcontractor's package untouched just uses up a review cycle and invites a rejection.
Next, the GC logs the submittal and transmits it to the architect or engineer of record. The design team reviews and returns it with an action stamp. Approved items move straight to procurement. Anything marked revise and resubmit goes back down the chain, and the clock starts over. That resubmission loop is where schedule risk concentrates, so the goal is always to get it approved on the first pass.
Reading Submittal Review Stamps
The action the reviewer marks determines what you can do next, so everyone touching the log should read these the same way. Exact wording varies by firm, but the intent is consistent.
- No exceptions taken (or approved): proceed with fabrication and installation as submitted.
- Make corrections noted (or approved as noted): proceed, but incorporate the marked corrections; usually no resubmission required.
- Revise and resubmit: the item does not conform; correct the issues and send it through the review cycle again before proceeding.
- Rejected: the submittal does not meet the requirements and a different product or approach is needed.
- For record only or reviewed for information: no action stamp is expected, typically used for closeout and informational items.
Building and Managing the Submittal Log
The submittal log is the master register of every item that needs to be submitted, its status, and its dates. Build it early, ideally right after contract award, by reading the specifications section by section and pulling every required submittal into a single register. Waiting until items come up organically almost guarantees a long-lead item gets missed until it's too late.
The log is only useful if it stays current. Each entry should carry a clear responsible party, a required-on-site or need-by date worked backward from the schedule, the review turnaround built into the contract, and the current status. When a submittal is tracked in a shared system like MyBuildTracks, the whole team sees the same live status instead of chasing the latest version over email, and overdue reviews surface before they become schedule problems rather than after.
A Submittal Checklist for the Field and Office
Use this as a repeatable routine on every project to keep the process disciplined.
- Create the submittal register from the specifications immediately after award, not weeks into the job.
- Prioritize long-lead items and work every need-by date backward from the installation date, adding time for review and possible resubmission.
- Require subcontractors to submit early and complete; an incomplete package burns a review cycle.
- Perform a genuine GC review before forwarding anything to the design team.
- Log every transmittal with dates so review turnaround is visible and enforceable.
- Track status actively and follow up on anything approaching or past its due date.
- Confirm the review stamp before releasing any item for fabrication or ordering.
- Distribute approved submittals to the field so crews install from the current, approved version.
- Capture closeout submittals such as warranties and O&M manuals as the work completes, not at the end.
Common Pitfalls That Delay Projects
A few recurring mistakes cause most submittal-driven delays. The first is starting late; a submittal log assembled a month into the job means long-lead items are already behind. The second is forwarding subcontractor packages without a real GC review, which produces avoidable rejections and wastes review cycles you can't get back.
The third is treating review turnaround as open-ended. The contract usually specifies a review period, and holding the design team to it, while giving them complete packages to work with, keeps the loop tight. Finally, poor version control means crews sometimes build from a superseded submittal. Making sure only the approved, current version reaches the field prevents rework that no one budgeted for.
Key takeaways
- Submittals verify that the actual products and assemblies being installed conform to the design drawings and specifications before they are ordered or built.
- Build the submittal log from the specifications right after contract award and work every need-by date backward from installation, prioritizing long-lead items.
- A genuine GC review before forwarding to the design team prevents avoidable rejections and wasted review cycles.
- Learn the review stamps: only proceed with fabrication or ordering once an item is approved or approved as noted.
- The revise-and-resubmit loop is where schedule risk concentrates, so aim for first-pass approval and keep the log current.