Process & workflow
How to review a submittal
Reviewing a submittal is confirming that what the contractor intends to install matches what the specification and drawings require, before it is fabricated or delivered. It is easy to rubber-stamp and easy to over-mark; both cause problems. A clean review catches the substitution, the wrong dimension, or the missing detail on paper, while it is still a red-line and not a demolition. This guide covers reviewing one item and returning an action the field can actually build to.
For project engineers, QC managers, and designers' agents who receive submittals and have to review, mark, and return them without becoming the schedule's bottleneck.
Step by step
Confirm completeness before you review content
Check the submittal is the right item, the right revision, complete, and carries the contractor's own review stamp. A submittal the GC never checked first is one you send straight back — reviewing on the design team's behalf is not the GC's job to skip.
Read it against the specification section
Open the governing spec section and drawings and compare line by line — product, model, grade, dimensions, finishes, and any listed performance requirement. The question is narrow: does what is proposed meet what was specified.
Flag substitutions and deviations explicitly
Any product that differs from what was specified is a substitution and gets called out, not quietly accepted. A proposed deviation needs the designer's decision on its merits; the reviewer does not waive a spec requirement by missing it.
Check the coordination the submittal implies
Confirm the item fits what it connects to — dimensions against the opening, embeds against the structure, connections against the adjacent trade. A submittal that is right on its own but clashes with the next trade is still a problem you own.
Mark a clear, defensible action
Return one unambiguous status — approved, approved as noted, revise and resubmit, or rejected — with comments tied to the specific requirement. "Approved as noted" means the noted changes are mandatory, so the comments have to be precise enough to build from.
Route it and record the disposition in the register
Get the reviewed submittal back to the contractor and log the action, date, and revision in the submittal register. Anything short of a clean approval loops back around, and the register tracks the resubmittal until it closes.
Confirm the approved revision reaches the field
The review only pays off if the crew installs from the current, approved revision — not a superseded set. Tie the closed submittal to its definable feature of work so the preparatory phase can confirm the right paper is in hand before the trade starts.
What gets missed
- Reviewing a submittal the GC never stamped, doing the contractor's coordination review for them.
- Approving product data without checking it against the actual specification section it has to satisfy.
- Missing a substitution buried in a data sheet and unintentionally waiving a spec requirement.
- Treating "approved as noted" as done without confirming the contractor incorporated the noted changes.
- Letting a feature start against a superseded revision because the approved one never reached the field.
Questions people ask
- Does reviewing a submittal mean approving the means and methods?
- No. A submittal review confirms the proposed product or fabrication conforms to the specification and design intent — it does not relieve the contractor of responsibility for quantities, dimensions to be confirmed in field, or construction means and methods. Say so on the stamp where the review is on the design team's behalf.
- What is the difference between "approved" and "approved as noted"?
- "Approved" means build it as submitted. "Approved as noted" means build it with the marked changes incorporated — the notes are mandatory, and the contractor is expected to comply without a resubmittal unless the notes are extensive enough to require one.
Terms worth knowing
Checklists that make this a one-tap job
Free, field-ready checklists, each with the photo every item needs before it can be submitted.
Related guides
- How to track submittals on a projectBuild and run a submittal register that tracks every shop drawing and product data item from log to approval so no feature starts without the right paper.
- How to conduct a pre-installation meetingRun the pre-installation conference that gets the installer, submittals, substrate, and acceptance criteria aligned before a trade brings its first material to the wall.
- How to write an RFIWrite an RFI that gets a clear, usable answer fast — one specific question, the documents it references, and a proposed answer — instead of a slow round of clarifying questions.
Reading the steps is one thing. Proving you walked them is the job.
RTI holds the submit button until every mandatory item is answered and the photos are attached, then chains the record so it can be proven untouched later.