A late submittal rarely looks like a crisis on the day it slips. Two weeks later, the steel is not released, the door hardware is not ordered, and the superintendent is asking why the schedule moved. Submittals sit quietly on the critical path, and most delays come from the paperwork around them rather than from the work itself.
This guide breaks the process into plain steps. You will see what a submittal package needs, where approvals stall, and how to get documents through review faster. It is written for general contractors, subcontractors and project engineers who want fewer rejections and fewer surprises.
What Is a Submittal in Construction?
A submittal is a document or physical item a contractor sends to the design team to show that a product or assembly meets the contract documents. It is the contractor’s proof, before purchase or installation, that the right thing is about to go in the building.
Common submittal types include:
- Product data: manufacturer sheets, performance ratings and installation instructions
- Shop drawings: fabrication and installation drawings prepared for the specific project
- Samples: finish, colour or material samples for design approval
- Mock-ups: full-scale assemblies built on site to confirm appearance and workmanship
- Certificates and test reports: third-party evidence of compliance
- Operation and maintenance data: documents collected for the owner at close-out
Each type has its own review path, so lumping them together in one folder is the first mistake many teams make.
Why Do Submittals Cause So Many Delays?
Most approval delays trace back to a handful of repeat problems. Spotting them early is cheaper than fixing them in week twelve.
- Incomplete packages: a missing data sheet or unmarked option sends the whole package back
- No clear register: nobody knows which items are due, with whom, or by when
- Long lead times ignored: the review window plus fabrication time was never counted backward from the install date
- Spec mismatch: the product submitted does not match the specification section
- Slow follow-up: a package sits in a reviewer’s inbox because nobody chased it
- Poor resubmission control: revised sheets go out without a clear note of what changed
None of these is complicated. They are habits, and habits can be fixed with a repeatable process.
How to Build a Submittal Register That Works
A submittal register is a log of every item the specifications require, built before work begins. Think of it as the schedule for your paperwork.
A useful register tracks:
- Specification section and item description
- Responsible trade or vendor
- Required-by date, worked backward from the planned installation date
- Date sent, date returned and current status
- Review result and resubmission count
Build the register from the specification, not from memory. Go section by section and list every required submittal, including the quiet ones such as warranties, certificates and extended-stock items.
Then connect each line to the project schedule. If a roofing membrane needs eight weeks of lead time and two weeks of review, the submittal is due ten weeks before the roof crew arrives, plus a buffer for one rejection. That single habit prevents more delay than any software.
What Goes Into a Package That Gets Approved the First Time?
Reviewers approve what they can check quickly. Make the check easy.
- Cover sheet: project name, spec section, item, submitter, date and revision number
- Marked product data: highlight the exact model, size, finish and options being proposed
- Compliance note: point to the specification paragraph and state how the product meets it
- Clean shop drawings: show dimensions, details, connections and references to the contract drawings
- Related items bundled sensibly: group components that must be reviewed together, such as door frames and hardware sets
Submittals for envelope trades deserve extra care because small detail errors become expensive leaks. Waterproofing is a good example. Reviewers will want to see the membrane type, substrate preparation, termination details and protection layers in one coherent package. If you are working through that scope, it helps to understand how the quantities and assemblies are defined, which P2C explains on its waterproofing takeoff services page.
Understanding Review Results
Review stamps vary by firm, but most fall into four outcomes:
- Approved: proceed with procurement or fabrication
- Approved as noted: proceed, but incorporate the reviewer’s comments
- Revise and resubmit: correct the issues and send the package again before ordering
- Rejected: the item does not meet requirements and a different product or approach is needed
Read the comments before you read the stamp. “Approved as noted” can hide a change that affects cost or lead time, and a note on one sheet may apply to the whole package. Pass comments to the purchasing team the same day.
How to Speed Up the Approval Cycle
Faster approvals come from fewer cycles, not from rushing a reviewer. Aim to get it right in one round.
- Review internally first: the contractor should check each package against the specification before it goes to the design team
- Prioritise by lead time: submit long-lead and critical-path items first, not in specification order
- Agree the review window: confirm turnaround times at the kickoff meeting and write them into the register
- Send complete bundles: partial packages produce partial reviews and extra rounds
- Follow up on a schedule: a polite status check at the midpoint of the review window keeps packages moving
- Control revisions: label each resubmission with a revision number and a short list of what changed
- Keep one source of truth: a single shared log beats five spreadsheets
Many project teams also find the administrative load heavy when several jobs run at once. A dedicated support partner can take over the chasing, logging and resubmission tracking so project engineers can focus on technical review. P2C offers this through its project engineering service, which includes submittal management alongside RFIs, close-out, material tracking and change orders.
Who Should Own Submittals on a Project?
Ownership works best when it is shared and clearly defined.
- Subcontractors: prepare accurate packages for their own trade scope
- Project engineer or coordinator: logs, reviews for completeness, transmits and tracks
- Project manager: monitors the register against the schedule and escalates stalled items
- Superintendent: flags field conditions that may change a submitted detail
- Design team: reviews within the agreed window and gives clear, actionable comments
When ownership is vague, packages wait. When each role knows what it owes and when, the cycle shortens naturally.
For many firms, this is where outside construction project management services make a real difference. Document control is repeatable work, and repeatable work can be systemised. Contractors comparing construction project management companies often look for teams that work inside their existing platforms rather than forcing a new tool on the crew. That is a sensible test for any construction project management service you consider.
Coordinating Submittals With Estimating and Procurement
Submittals do not live apart from the bid. The quantities and assumptions made at estimate stage shape what you submit later.
- The takeoff defines how much of each product is needed, including waste, which feeds purchasing once approval arrives
- Substitutions proposed at bid time must match what the submittal later shows, or the price and the product drift apart
- Long-lead items identified early in estimating can move to the front of the register
This is why construction estimating services and submittal control work best when they share information. Clear quantities in the estimate lead to cleaner purchase orders after approval.
Division 08 packages show the connection well. Door frames, leaves and hardware sets must line up by opening, finish and function, and a mismatch between the schedule and the submitted hardware group can stall an entire floor. If you are building that scope, see how P2C approaches door frame and hardware quantity takeoffs so the counts behind your submittal are accurate from the start.
A Simple Submittal Checklist
Use this before any package leaves your office:
- Is the item listed in the register with the right specification section?
- Does the product match the specification, or is a substitution request attached?
- Are the exact model, finish and options marked on every data sheet?
- Do shop drawings reference the correct contract drawing and detail?
- Have related components been grouped for coordinated review?
- Is the revision number current, and are changes listed for any resubmission?
- Does the schedule still work if this package is returned once?
If you can answer yes to all seven, you have removed most of the common reasons for rejection.
Frequently Asked Questions
How long does a submittal review usually take?
Review windows are set by the contract and specifications, and they differ from project to project. Always check your own documents, then plan for at least one possible resubmission when you work backward from the installation date.
What is the difference between a shop drawing and product data?
Product data is the manufacturer’s standard information, such as ratings and installation instructions. Shop drawings are prepared for the specific project and show dimensions, details and connections for fabrication or installation.
Can I order materials before a submittal is approved?
That is a risk decision. If the design team rejects the item, the cost of returning or replacing material falls on your side. Most teams wait for an approved or approved-as-noted result before releasing long-lead or custom items.
What is the most common reason for rejection?
Incomplete or unmarked packages and mismatches with the specification top the list. An internal review against the specification before transmittal catches most of them.
When should a contractor outsource submittal management?
Consider it when project engineers are overloaded, when several jobs peak at once, or when follow-ups keep slipping. Outsourcing the logging, chasing and resubmission tracking frees your team for technical decisions.
Final Thoughts
Faster approvals are built on small, consistent habits: a complete register, clean packages, an internal check, and steady follow-up. None of this needs new technology. It needs a process the whole team follows.
If your team is short of hands on document control or you want a second pair of eyes on the workflow, talk to P2C about your project and tell us which modules you need most.
