The Construction Submittals Process, Explained

What Construction Submittals Are

Construction submittals are the documents, samples, and data a contractor provides to the design team to prove that the materials and equipment they intend to install match what the contract documents require. Think of them as the checkpoint between “what the specs asked for” and “what actually gets built.” Before a product is fabricated or ordered, the architect and engineer confirm it conforms to the design intent.

Submittals matter because they catch mismatches while they are still cheap to fix. A wrong product caught in a submittal is a corrected email; the same product caught after installation is demolition and rework. Handled well, the submittal process is one of the strongest tools a team has to keep a job on track.

The Main Types of Submittals

Submittals come in several forms, each answering a different question about the work:

• Shop drawings. Detailed, fabrication-level drawings prepared by the contractor, subcontractor, or supplier, showing exactly how a component will be built and installed. Common for steel, millwork, and mechanical systems.
• Product data. Manufacturer catalog cuts, spec sheets, and performance data proving a proposed product meets the specified requirements.
• Samples. Physical examples of materials, finishes, or colors submitted for approval, from a brick to a carpet swatch.
• Mock-ups. Full-scale assemblies built to demonstrate workmanship, appearance, and how systems come together before the real thing goes up.

Other categories, like test reports, certifications, and operation and maintenance manuals, also flow through the same process.

The Submittal Review Cycle

The workflow follows a predictable path, and understanding each handoff is how you keep it moving:

1. Preparation. The subcontractor or supplier assembles the submittal against the relevant spec section.
2. Contractor review. The general contractor reviews it first, checking it for completeness and coordination before passing it up. Skipping this step is a common cause of rejections.
3. Design team review. The architect or engineer reviews and returns the submittal with an action: approved, approved as noted, revise and resubmit, or rejected.
4. Resubmittal if needed. Anything marked revise and resubmit goes back through the loop.
5. Release for fabrication. Once approved, the item can be ordered, fabricated, and eventually installed.

Each pass takes time, and the resubmittal loop is where schedules quietly slip.

The Submittal Register

The submittal register, or submittal log, is the master list of every submittal a project requires, who is responsible for it, and where it stands in the review cycle. A well-maintained register tracks:

• The spec section and submittal item
• The responsible subcontractor or supplier
• Required dates, tied back to procurement and the schedule
• Current status and review turnaround

Without a live register, teams lose track of what is outstanding, and long-lead items get discovered too late. A clean log is the difference between staying ahead of fabrication and constantly chasing it.

How Specifications Drive Submittal Requirements

Submittal requirements don’t come out of nowhere. They are written into the specifications, organized by CSI MasterFormat divisions. Each spec section typically includes a “Submittals” article listing exactly what the contractor must provide for that scope, whether shop drawings, product data, samples, or all three.

This is why a careful spec read is the foundation of a good submittal register. If you miss a required submittal buried in a Division section, you find out when the design team rejects an uncoordinated install. Building the register directly from the spec sections ensures every requirement is captured, and it ties naturally into how you define each trade’s scope of work.

Common Delays and How to Avoid Them

The submittal process breaks down in a few predictable ways. Each has a straightforward fix:

• Late submissions. Subs sit on submittals until fabrication is looming. Build submittal dates into the schedule and hold subcontractors to them.
• Incomplete packages. Missing product data or uncoordinated drawings trigger rejections and restart the clock. Enforce a real contractor review before anything goes to the design team.
• Slow turnaround. Reviews stall on the architect’s desk. Agree on review timeframes up front and track them in the register.
• Missed requirements. A submittal nobody logged surfaces after the material is ordered. Build the register from the spec sections so nothing is overlooked.

Getting submittals right is directly tied to your ability to reduce change orders, because most of the mismatches that become field problems could have been caught in review. For more on how submittals fit into the broader workflow, our FAQ answers common questions from preconstruction teams.

Cleaner Submittals With Constructplicity

Constructplicity reads dense technical specifications and turns them into structured project plans, pulling submittal requirements straight from the spec sections so your register is complete from day one. Instead of hunting through divisions for every required shop drawing and sample, your team starts with the list already built. See how Constructplicity streamlines the construction submittals process and stop letting missed requirements slow your job down.