How to review a construction submittal

How a submittal gets reviewed is where a lot of projects quietly win or lose. A missed deviation that shows up after fabrication means a change order, a schedule hit, and an uncomfortable call with the owner. This guide walks through the process the way a seasoned PM would hand it off: pull the right spec, read the package, compare it line by line, classify and rank every difference, then return clean redlines the sub can act on.

Step 1: Pull the governing spec section (and the right revision)

Before you open anything the sub sent, find the spec section that governs the work. One CSI MasterFormat number, the full text, including the part 2 product requirements and part 1 submittal requirements. If you do not know which division a section lives under, the CSI division hubs map the numbers to scopes.

The revision matters as much as the section. Specs get amended by addenda during bidding and by ASIs or bulletins during construction. Reviewing a product against a superseded version is how you approve something the current contract documents already changed. Confirm you are holding the latest issued-for-construction version plus every addendum, and note the date. If a submittal references an old section number, that is your first flag.

Step 2: Read the submittal as a package

A submittal is not one document. It is a package, and the first job is confirming it is complete before you judge any single piece. Open the transmittal first. It tells you what the sub claims to be sending and which spec section they think they are answering.

Then inventory the parts against what part 1 of the spec actually required:

• Product data and cut sheets - manufacturer pages with model numbers, dimensions, ratings.
• Shop drawings - the sub's fabrication and installation drawings, dimensioned to the actual building.
• Samples - physical pieces for color, finish, and texture sign-off.
• Certifications and test reports - UL listings, fire ratings, structural calcs, mill certs, warranties.

If the spec called for three samples and a fire-test report and you only see product data, stop. An incomplete submittal goes back as incomplete. Do not spend an hour reviewing cut sheets when the certification that decides approval was never sent.

Step 3: Compare line by line against the spec

This is the work. Go through part 2 of the spec requirement by requirement and find where each one is answered in the package. Do not skim for a brand name and call it matched. Check:

• Manufacturer and model - is the named product actually one the spec allows, or a substitute dressed up to look approved?
• Performance values - STC, R-value, PSI, gauge, fire rating, wind load. Numbers against numbers. A spec calling for STC 50 and a cut sheet showing STC 45 is a real miss, not a rounding issue.
• Certifications - the listing has to cover the exact assembly, not a similar one.
• Details and dimensions - shop drawing connections, anchor spacing, and clearances against the detail sheets.
• Finishes - color, gloss, and texture against the sample and the finish schedule.

Mark every place the submittal is silent. Things left out are as much a problem as things that are wrong, and subs sometimes leave out what they know does not comply.

Step 4: Classify every difference as a deviation

A difference from the spec is a deviation, and naming what kind it is keeps your report consistent and defensible. Most differences fall into six categories, covered in depth in the six categories of submittal deviation:

• Manufacturer or product substitution
• Performance specification gap
• Missing certification or documentation
• Aesthetic deviation
• Detail or installation mismatch
• Submittal package incompleteness

Substitutions deserve a sharp eye. A genuine "or-equal" claim is not the same as a formal substitution request, and the two carry different review duties and paperwork. If you are not sure which one is on your desk, or-equal vs substitution requests draws the line.

Step 5: Assign severity

Not every deviation carries the same weight, and the sub needs to know which ones actually hold up the job. Three levels work on most projects:

• Blocker - violates code, defeats a life-safety system, or misses a hard performance floor. The package cannot be approved as-is. A fire-rated door submitted with an unrated frame is a blocker, full stop.
• Fix and Resubmit - a real deviation that needs correction but does not threaten safety. Wrong finish, missing cert, undersized component that has an easy in-spec swap.
• Note - minor or cosmetic. Worth flagging so it is on record, not worth stopping the work.

Severity climbs fast when code and life safety enter the picture. Fire, structural, egress, and accessibility deviations default to Blocker until proven otherwise. When in doubt, rate it up and let the design team rate it down.

Step 6: Write the deviation report and return redlines

Your output is a deviation report the sub and the design team can act on without a phone call. For each deviation, give it a category, a severity, the exact spec language it breaks, a verbatim quote from the submittal showing the conflict, and a plain instruction for the fix. Quotes matter. "Does not comply" starts an argument; "spec section 2.2.A requires STC 50, cut sheet lists STC 45" ends one.

Then mark up the documents. A redline on the cut sheet or shop drawing, right where the problem is, tells the sub exactly what to change far better than prose. Land your verdict in the standard language: approved, approved as noted, or revise and resubmit. If you wrote even one Blocker, the package is revise and resubmit. Send the marked-up set back with the report so the sub is correcting against your actual markups, not guessing.

Where deviations slip through

The misses are predictable. Watch these:

• Reviewing the wrong revision. The product matched a spec that an addendum already superseded. Always confirm the date first.
• Brand-name matching. The cover page names the specified manufacturer, but the attached model is a cheaper line that misses a rating. Read past the logo to the model number.
• Silent omissions. The sub leaves out the fire test or the warranty and hopes you fixate on the data that is present. Inventory against part 1 every time.
• Near-miss numbers. STC 45 next to a required 50, 16-gauge where 14 was called for. They read fine at a glance and fail in the field.
• Rubber-stamping resubmittals. A package comes back the second time and you only check what you flagged before, missing a new deviation the sub introduced while fixing the old one. Re-review the changed sheets fresh.

Speeding it up

A careful manual review of a dense submittal can eat an hour or more, and on a busy job the backlog grows. An automated first pass can read the spec and the submittal together, surface the likely deviations with quotes and severities, and hand you a draft report to verify rather than build from scratch. You stay the reviewer of record; the tool does the line-by-line cross-check so you spend your time on judgment calls instead of hunting for mismatched numbers. If that is the bottleneck on your projects, you can start a review and see the draft it produces.

Frequently asked questions

What is the first step in reviewing a submittal?

Pull the governing CSI spec section and confirm you have the latest issued-for-construction revision plus every addendum. Reviewing against a superseded spec is how non-compliant products get approved.

What is the difference between an or-equal and a substitution request?

An or-equal claims a product is equivalent to the specified one and gets a lighter review, while a formal substitution request proposes a different product and requires more documentation and design-team approval. They carry different review duties, so confirm which one you have before judging it.

When should a submittal be marked revise and resubmit?

Mark a submittal revise and resubmit whenever it contains at least one Blocker-level deviation, such as a code violation, a life-safety conflict, or a missed hard performance requirement. Minor notes alone do not require a resubmittal.