What is a submittal in construction?

Submittals are the quality-control gate between "the spec says" and "the crew installs." A mid-sized commercial job can carry hundreds of them, each tied to a spec section, a reviewer, and a deadline — and each one capable of stalling procurement if it bounces. This guide covers what submittals include, how the review process actually works, why so many get rejected, and how to keep the log from becoming the reason the schedule slips.

What does a submittal actually include?

"Submittal" is a category, not a single document. The common types (Procore, Ultimate Guide to Submittals):

• Shop drawings — fabrication-level drawings prepared by the contractor, a subcontractor, fabricator or supplier, showing exactly how a specific portion of the work will be built (steel connections, ductwork routing, millwork).
• Product data / cut sheets — manufacturer literature for the specific make and model proposed, so the reviewer can check it against the spec.
• Samples — physical pieces of the actual material, color or finish (brick, carpet, paint draw-downs).
• Mockups — full-scale assemblies built for approval before production work (a window wall section, a finished room).
• Calculations & test reports — engineering calcs for delegated design items, concrete cylinder breaks, air/water test results.
• Closeout submittals — O&M manuals, warranties and as-builts at the end of the job. (See the closeout checklist.)

Each spec section lists exactly which submittals it requires — which is why the submittal register is built from the spec book, not from memory.

How does the submittal review process work?

The flow is the same on most commercial jobs:

1. The subcontractor or supplier prepares the submittal for their scope.
2. The general contractor reviews it first — checking it against the contract documents and coordinating it with adjacent trades — then stamps and forwards it.
3. The architect or engineer of record reviews it and returns it with an action: typically Approved, Approved as Noted, Revise and Resubmit, or Rejected.
4. Only after approval may the contractor order the product or perform the work the submittal covers. Work done without approval is at the contractor's risk (AIA Contract Documents).

How long review takes is its own fight: standard AIA language only requires "reasonable promptness," which has been interpreted anywhere from about two weeks to twelve (ConstructionClaims.com). Most spec sections now pin it to a stated window — commonly 14 days — but long-lead items still need submittals in early, or the review window eats the procurement window.

What's the difference between a submittal, an RFI and a change order?

The three get tangled because they all move paper between contractor and design team. The direction of travel is the difference: a submittal proposes how the contractor will meet a requirement that already exists ("here's what we plan to install — approve it"). An RFI asks a question when the documents are unclear or in conflict ("the documents don't tell us"). A change order changes the contract itself — scope, price or schedule ("the deal is now different"). The full breakdown, with the paper trail that connects them, is here: RFI vs. submittal vs. change order (and if you're starting further back: what is an RFI?).

Why do submittals get rejected — and what does it cost?

Rejection is the norm, not the exception. Industry analyses put first-review rejection at roughly 30–40% of submittals, with each rejection costing on the order of $800 in direct rework time and adding two to four weeks to the affected activity; teams typically spend 4–8 hours of labor per submittal cycle (BuildSync submittal research). On a 500-submittal project that compounds into six figures of preventable cost before schedule damages are counted.

The causes are boringly consistent:

• The product doesn't match the spec — a substitution submitted as if it were the specified item.
• Incomplete packages — missing the calcs, samples or certifications the spec section lists.
• No coordination with adjacent trades — the shop drawing conflicts with another system's approved layout.
• Submitted against a stale document — the package answers Rev 2 of the drawing when Rev 3 governs. (Related: the hidden cost of building from a superseded revision.)

Every one of those is a document question that could have been answered before the package went in: what does the current spec section actually require, which revision governs, what did the change order alter. (When the spec and the drawing themselves disagree, that's its own problem: spec vs. drawing — which governs?)

What are the best practices for managing submittals?

• Build the submittal register from the spec book at the start of the job — every required submittal, its spec section, reviewer and required-on-site date, before the first package moves. (Full workflow: submittal log management.)
• Front-load long-lead items. Sequence the register by procurement need, not spec-section order — the switchgear submittal matters months before the paint samples do.
• Check packages against the current revision before submitting. A ten-minute currency check beats a three-week resubmittal loop.
• Submit complete packages once, not partial packages twice — partials usually come back "Revise and Resubmit" on the missing pieces alone.
• Track review turnaround against the contract clock and escalate in writing when reviews stall; "reasonable promptness" is only enforceable if the delay is documented.
• Keep approvals connected to the record — an approved submittal that conflicts with a later change order is a claim waiting to be discovered. (This is a document-control problem: what is document control?)

Where does AI fit in the submittal process?

Submittal-management software tracks the workflow — who has the package, what state it's in, how long it's been sitting. The slower, quieter work is the document research around each package: what the current spec section actually requires, which revision governs, whether the product on the cut sheet matches the scheduled item, and whether an approval issued in March still holds after the change order signed in May.

That's where a grounded document-intelligence layer fits. You ask a plain question — "what does 23 05 00 require for pipe insulation submittals?", "was the RTU-2 submittal approved, and against which revision?" — and the answer comes back cited to the exact document, sheet or spec section, answered from the latest issued revision, with any conflict between documents flagged rather than silently resolved — and anything cost-, code- or safety-critical escalated to a human instead of guessed. It doesn't replace the submittal log; it makes the record behind it answerable. (More on the distinction: document intelligence vs. a chatbot, and is AI safe for construction documents?)

The short answer

A submittal is the contractor's proof, sent for approval before building, that what they plan to install matches the contract documents — shop drawings, product data, samples, mockups and calculations, each required by a spec section and each gated on the design team's review. Most rejections trace back to a document question nobody asked in time. IntelMS answers those questions from your own project record: email a question about your specs, drawings or submittals and get back a cited, revision-aware answer in minutes — or a precise list of what's missing. See real timed answers, including an honest decline.