# The 6 Categories of Submittal Deviation, Explained > Source: https://deviationcheck.com/guides/submittal-deviation-categories/ The six categories of submittal deviation give a Project Manager a shared vocabulary for sorting problems in a subcontractor's package. When every reviewer files the same finding under the same label with the same severity, reviews go faster and the record holds up if the sub pushes back. Here is what each category means, what it looks like in the field, and how hard it should stop the package. ## Manufacturer or Product Substitution The submittal names a different manufacturer or product than the spec calls out, and there is no approved or-equal on file. This is the most common reason a PM kicks a package back. A [Manufacturer or Product Substitution](/divisions/09-finishes/manufacturer-substitution/) shows up when the sub has a stocking relationship with a different supplier, or when the specified product is on a long lead time and they swapped to something on the shelf. Example: the spec section calls for USG Mars acoustical panels and the cut sheet shows Armstrong Ultima. No substitution request, no or-equal approval letter. That is a substitution every time, even if the Armstrong panel is genuinely comparable. Default severity is **Blocker**. The point is not that the substitute is worse - it might be better. The point is the substitution path in the contract was skipped. The sub owes a formal substitution request before anyone evaluates the product on merits. ## Performance Specification Gap A measurable property in the submittal misses what the spec requires. Ratings, capacities, tolerances, efficiencies - any number with a unit attached. A [Performance Specification Gap](/divisions/23-hvac/performance-specification-gap/) is the deviation that bites later, because it usually passes a glance and only fails when you check the number against the spec line. Example: the spec requires a rooftop unit with 14 SEER minimum and the schedule shows 13. Or a steel connection rated for 50 kips where the calc supports 42. The submittal looks complete and professional, but the number is short. Default severity is **Blocker**, and it is **always a Blocker for life-safety or structural** items. A missed efficiency rating on a comfort-cooling unit is serious. A missed load rating on a structural connection or a fire damper is not negotiable. Do not let a clean-looking schedule talk you out of reading the actual values. ## Missing Certification or Compliance Documentation A required listing, test report, or third-party certification is not in the package. The product itself may be fine. The proof is absent. [Missing Certification](/divisions/09-finishes/missing-certification/) is a documentation gap, not a product gap, which is why it usually clears on the second submission once the sub digs up the paperwork. Example: the spec requires a UL listing for a fire-rated door assembly and the cut sheet shows the door but no UL label data. Or a sealant with a required ASTM test report that did not get attached. Default severity is **Fix and Resubmit** - send it back, get the document, move on. But it **escalates to Blocker for code or life-safety items**. A missing UL listing on a fire-rated assembly or an absent fire-rating report is not a paperwork nicety you can resolve in the field. Treat those as hard stops until the certification is in hand. ## Aesthetic Deviation A visible attribute differs from the spec or the approved sample. Color, finish, texture, profile - anything the owner or architect will see and judge. An [Aesthetic Deviation](/divisions/09-finishes/aesthetic-deviation/) rarely affects how the building performs, but it affects whether the owner accepts the work, which makes it real money at closeout. Example: the spec calls for a satin anodized aluminum storefront and the submittal shows a clear anodized finish. Or a brick that reads noticeably redder than the approved range sample. Default severity is **Fix and Resubmit**. Catch it on paper. The expensive version of this finding is the one nobody catches until the material is installed and the architect rejects it on a walkthrough. A five-minute review note beats a tear-out. ## Detail or Installation Mismatch A submitted detail, dimension, anchorage method, or installation approach differs from the spec or the contract drawings. A [Detail or Installation Mismatch](/divisions/05-metals/detail-installation-mismatch/) hides inside shop drawings, where a fabricator's standard detail quietly overrides what the structural drawings show. Example: the structural drawings show a moment connection and the shop drawing details a shear-only connection. Or a handrail anchored with fewer fasteners than the detail calls for, at a different spacing. Default severity is **Fix and Resubmit** for ordinary cases. It becomes a **Blocker for fire-rated, seismic, or structural assemblies**. A changed anchorage on a non-structural trim piece is a correction. A changed connection on a seismic brace or a fire-rated wall assembly is a stop-work-level finding, because the mismatch defeats an engineered system. ## Submittal Package Incompleteness A required element of the package is missing, and the absence makes the rest unreviewable. A cut sheet, a schedule, a calculation, a physical sample. [Submittal Package Incompleteness](/divisions/26-electrical/submittal-package-incompleteness/) is different from a missing certification: here you cannot finish the review at all, because the piece you need to check against the spec is not there. Example: a lighting submittal that includes fixture cut sheets but no luminaire schedule, so you cannot confirm which fixture goes where. Or a package referencing a wind-load calculation that was never attached. Default severity is **Fix and Resubmit**. There is nothing to evaluate on the missing item, so the package goes back with a clear list of what is absent. The faster you flag the gap, the sooner the sub closes it instead of you guessing at intent. ## How severity works Three levels carry every finding, and the category sets the starting point: - **Blocker** - the package cannot be approved as submitted. Substitutions without an or-equal, missed performance numbers, and any life-safety or structural failure land here. A Blocker drives a REJECTED or REVISE AND RESUBMIT verdict. - **Fix and Resubmit** - a real problem the sub must correct, but not one that condemns the whole package. Most aesthetic, documentation, and ordinary detail findings sit here. The sub fixes the item and sends it back. - **Note** - worth recording for the file or the field, but it does not change the verdict. Use it for minor observations and items you want on record without holding up the work. The defaults are starting points, not a ceiling. Life-safety and structural context pushes a finding up. A [deviation](/glossary/deviation/) that would be a Note on a closet shelf becomes a Blocker on a stair rail. Read the assembly, not just the line. ## Putting it to work Run every submittal against the same six buckets in the same order. For each finding, name the category, quote the exact spec line and the exact submittal line that conflict, set the severity, and write the action the sub has to take. That structure is what turns a vague "this looks off" into a [revise and resubmit](/glossary/revise-and-resubmit/) the sub cannot argue with, because it points at their own words next to the spec. The categories also map cleanly across trades. The same six apply whether you are reviewing Division 05 steel or Division 23 mechanical, which is why they anchor every page in the [CSI division hubs](/divisions/). For the full step-by-step on working a package start to finish, see the companion guide on [how to review a construction submittal](/guides/how-to-review-a-submittal/). This is exactly the sorting an automated pass is good at - catching the missed rating buried in a schedule, the swapped manufacturer, the calc that never got attached - so the PM spends their judgment on the calls that need it. If you want to see it run against your own spec and package, you can [start a review](/#pricing). ## Frequently asked questions ### What is the difference between a Blocker and a Fix and Resubmit? A Blocker means the package cannot be approved as submitted and drives a REJECTED or REVISE AND RESUBMIT verdict, such as an unapproved substitution or a missed structural rating. A Fix and Resubmit is a real problem the sub must correct, like a wrong finish or a missing test report, that sends the package back without condemning all of it. ### Why is a manufacturer substitution a Blocker even when the product is comparable? Because the contract's substitution path was skipped, not because the substitute is worse. The sub owes a formal substitution request and or-equal approval before anyone evaluates the alternate product on its merits. ### When does a missing certification become a Blocker instead of a Fix and Resubmit? It escalates to a Blocker for code and life-safety items, such as a missing UL listing or fire-rating report on a fire-rated assembly. For non-life-safety items, an absent test report or listing is usually a Fix and Resubmit that clears once the document is attached.