No Exceptions Taken vs Approved: Submittal Status Explained

You've spent three days preparing a submittal package for the rooftop AHU. Every spec requirement checked. Every cut sheet organized. You submit it to the design team and two weeks later, it comes back stamped "No Exceptions Taken."

Great news, right? You proceed with procurement. Eight weeks later, the unit arrives. During installation, you discover the unit dimensions don't fit the curb shown on the drawings. The design team points to their review stamp: "We don't verify dimensions - that's your responsibility." You're looking at $40,000 in modifications and a four-week delay.

This scenario plays out on construction projects every week because teams treat "no exceptions taken" and "approved" as if they mean the same thing. They don't. Understanding the difference isn't just semantics - it determines who's liable when problems arise, whether you can proceed with procurement, and what verification you still need to perform.

Here's what these construction submittal review statuses actually mean and what you need to do with each one.

How Construction Submittals Reach the Review Status Decision

Before we dive into what these statuses mean, let's quickly establish where they fit in the submittal review workflow.

The subcontractor prepares the submittal package - product data, shop drawings, certifications, and cut sheets. They send it to the general contractor, who reviews it for completeness and coordination with other trades. The GC then forwards it to the design team (architect and engineers).

The architect's review examines the submittal against project specifications and design intent. They check if the proposed materials and equipment generally conform to what's specified in the contract documents. Then they apply a review stamp to the submittal and return it.

This review status decision - "No Exceptions Taken," "Revise and Resubmit," "Rejected," etc. - is where our discussion really begins. That stamp determines what happens next with procurement, fabrication, and installation. The submittal log tracks each submission through this review process. 

For the complete picture of how construction submittals work from preparation through approval, check out our comprehensive guide about submittals.

What Does "No Exceptions Taken" Mean on a Construction Submittal?

"No exceptions taken" means the architect or engineer has reviewed your submittal and found the submittal appears to conform with the contract documents. However - and this is critical - the contractor's responsibilities remain fully intact for dimensions, quantities, field coordination, and means and methods of construction.

This is standard terminology found in general conditions that's been carefully crafted to protect design professionals from liability concerns they shouldn't carry. When a design team stamps a submittal "No Exceptions Taken," they're confirming: "Based on our review, this submittal appears to align with our design intent as shown in the specifications and drawings."

What the architect's review does NOT confirm:

• That every dimension is correct

• That quantities match field conditions

• That the product will physically fit in the space

• That fabrication details shown in shop drawings are accurate

• That the contractor's means and methods will work

• That coordination with other construction documents is complete

The common misconception: Many contractors read "No Exceptions Taken" as "We checked everything and it's perfect." That's not what it means. The design team performed a limited submittal review focused on general conformance with design intent. They didn't verify your dimensions. They didn't check if the ductwork coordinates with the structural steel. They didn't confirm the equipment fits through the door.

According to standard contract requirements, the architect's review of construction submittals is not for the purpose of determining the accuracy of dimensions, quantities, or the contractor's means and methods. That responsibility stays with the contractor - regardless of the review status.

Why design teams use this language: Professional liability. If many architects stamped submittals "Approved" and took responsibility for dimensional accuracy, their errors and omissions insurance would be prohibitively expensive. The construction industry moved to "No Exceptions Taken" terminology specifically to clarify that the contractor maintains responsibility for construction execution and means and methods.

Understanding "Approved" Status in Construction Submittals

"Approved" would imply the design team has accepted full responsibility for the submittal's accuracy and suitability. This is precisely why architects and engineers almost never use this term in modern construction practice.

If a design professional stamped a submittal "Approved" without qualification, they could be interpreted as having verified and taken responsibility for:

• Dimensional accuracy in shop drawings

• Quantities and field measurements

• Fabrication details and procedures

• Installation sequencing and methods

• Coordination with all other construction documents

• Suitability for the specific site conditions

This level of responsibility creates unacceptable liability concerns. Design teams would essentially be warranting that the contractor's proposed solution will work perfectly, including aspects like the contractor's means and methods that are explicitly outside their contractual obligations under standard contracts.

The shift away from "Approved" terminology happened as the construction industry matured its understanding of professional roles and liability. The AIA recognized that design professionals shouldn't be held liable for verifying every dimension the contractor provides or for potentially risky means and methods of construction.

When you might see "Approved": Extremely rare circumstances where there's a specific contractual arrangement transferring more responsibility to the design team. Even then, it's typically "Approved as Noted" with significant qualifications.

Modern practice has moved to clearer terminology: "No Exceptions Taken," "Reviewed," or "Reviewed - No Exceptions Taken." All of these make it explicit that the contractor maintains responsibility for the work and construction procedures.

No Exceptions Taken vs Approved: Key Differences for Construction Submittals

Here's the critical comparison every PM and PE needs to understand about submittal review statuses:

The liability distinction matters for construction submittals. When you receive "No Exceptions Taken," your contract requirements still make you responsible for:

• Verifying dimensions match field conditions

• Ensuring products and materials fit in allocated spaces

• Coordinating with structural, MEP, and other construction documents

• Confirming installation means and methods will work

• Checking that products meet code requirements

If something goes wrong after receiving "No Exceptions Taken," you can't claim the submittal review constituted verification of these items. The review stamp explicitly preserves the contractor's responsibilities.

Insurance and legal standing: Your general liability insurance expects you to perform due diligence regardless of submittal review status. "No Exceptions Taken" doesn't give you legal cover if you install non-compliant work or equipment that doesn't fit.

How it affects design team relationships: Design teams remember which contractors consistently submit quality, well-documented packages with proper product data and shop drawings versus those who treat the submittal review process as a QC service. Understanding that "No Exceptions Taken" isn't a full verification helps you maintain the verification responsibility that's actually yours under contract requirements.

For a deeper dive into what happens during the review process and why submittals get rejected, our complete guide covers the seven most common failure points.

Contract Language and Liability: What You Need to Know

The difference between "No Exceptions Taken" and "Approved" isn't just terminology preference - it's rooted in decades of contract evolution and hard-learned lessons about liability in construction.

What Standard Contracts Actually Say

AIA Document A201 (General Conditions of the Contract for Construction) - the most widely used construction contract in the industry - explicitly states that the architect's review of submittals "is not conducted for the purpose of determining the accuracy and completeness of other information such as dimensions, quantities, and installation or performance of equipment or systems, which are the contractor's responsibility."

This language appears in Section 3.12.8, and it's not accidental. It's the result of extensive litigation where architects were held liable for reviewing and "approving" submittals that later proved to have dimensional errors, coordination conflicts, or installation problems - aspects that were always meant to be the contractor's responsibility under the contract.

Why This Protects Both Parties

This contractual framework actually protects everyone involved. Design teams can focus their review on design intent and specification conformance without assuming liability for the contractor's means and methods of construction. Contractors maintain control over their construction procedures, sequencing, and field coordination - which they're better positioned to manage anyway.

The shift to "No Exceptions Taken" language makes this division of responsibility crystal clear. When the submittal appears to conform with contract documents, the architect can say so without inadvertently accepting responsibility for aspects outside their scope.

The Liability Reality: Who Pays When Things Go Wrong

Here's what matters in practical terms. If you install equipment based on a submittal stamped "No Exceptions Taken" and discover:

• The unit doesn't fit the space: Your liability. The architect's review didn't verify dimensional accuracy against field conditions.

• Coordination conflict with structural steel: Your liability. Trade coordination remains your contractual obligation.

• Product doesn't meet an obscure spec requirement the architect missed: Shared liability depending on circumstances, but you had the responsibility to verify spec compliance before submission.

• Design intent itself was flawed (wrong capacity specified): Design team's liability. This is a design error, not a submittal review issue.

Your professional liability insurance and the design team's E&O coverage are written with these distinctions in mind. "No Exceptions Taken" language aligns with how insurance companies expect risk to be allocated.

Red Flags in Your Contract Language

Review your project's general conditions carefully. Watch for:

• Non-standard language that expands the architect's review scope beyond design intent

• "Approval" terminology without a clear limitation of responsibility

• Vague statements about who verifies dimensions, coordination, or means and methods

• Clauses that shift the contractor's traditional responsibilities to the design team

If your contract includes unusual submittal review language that creates ambiguity about liability, address it during contract negotiation. Once you're in construction, that ship has sailed.

How Documentation Protects You

When liability questions arise - and they do on complex projects - your submittal documentation becomes critical. 

Can you prove the submittal you installed matched what received "No Exceptions Taken" status? Can you show you addressed all review comments? Did you maintain records of your dimensional verification and coordination efforts?

This is where systematic submittal review processes and detailed compliance documentation make the difference between a quick resolution and a prolonged dispute. BuildSync's characteristic-by-characteristic analysis creates exactly this type of clear documentation trail - showing what you verified, what the submittal complied with, and what due diligence you performed before and after receiving approval.

Understanding the contractual framework isn't just legal theory - it's about knowing your responsibilities, protecting your company, and maintaining the professional relationships that keep projects moving forward.

Other Construction Submittal Review Statuses You Need to Know

Beyond "No Exceptions Taken" and "Approved," you'll encounter several other review statuses in the submittal review process. Here's what each means and what you need to do:

Approved as Noted / No Exceptions Taken as Noted

The submittal appears to generally conform, but the design team has noted corrections, clarifications, or minor changes required in the product data or shop drawings. You can typically proceed with procurement - but verify with your specific contract language. You must address all noted items before fabrication or installation. Document how you addressed each note in your submittal log and project records.

Revise and Resubmit

The submittal doesn't meet contract requirements and cannot be approved in its current form. You cannot proceed with procurement or installation. You must correct the identified issues in your product data, shop drawings, or other materials and resubmit for another review. 

Each revise and resubmit cycle adds 2-4 weeks to your submittal schedule, which is why getting construction submittals right the first time is critical for schedule management.

Rejected

The submittal does not conform to contract documents and has major issues preventing approval. You cannot proceed under any circumstances. This often requires consultation with the design team about acceptable alternatives or may necessitate a substitution request if the specified product cannot be provided as required.

Reviewed (Non-Committal)

This status has a similar intent to "No Exceptions Taken." The design team has completed its submittal review and found no major objections, but the term "Reviewed" makes the non-committal nature even clearer. The contractor maintains full responsibility for all construction execution aspects and means and methods. In practice, "Reviewed" and "No Exceptions Taken" are essentially synonymous.

The pattern here is clear: modern submittal review terminology consistently preserves the contractor's responsibilities while allowing design teams to confirm general conformance with design intent.

Next Steps After Receiving No Exceptions Taken Status on Your Submittal

You can proceed with procurement and installation - but the contractor's responsibilities remain for verifying all dimensions, coordinating with other construction documents, and ensuring the submittal complies with actual site conditions.

Here's your action checklist:

1. Review the stamp and comments carefully

Even "No Exceptions Taken" often includes notes, clarifications, or conditions in the submittal review. Read every word on your shop drawings and product data. Don't just see the status and move on.

2. Read all the architect's review comments thoroughly

The design team may have included clarifications about their interpretation of design intent, concerns about specific aspects, or requirements for coordination with other elements.

3. Update your submittal log

Record the approval status, date, and any conditions. Save the stamped submittal in your project records. You'll need this documentation for closeout, warranty issues, and if any disputes arise about what was approved.

4. Verify dimensions yourself

Don't assume the architect's review checked that the 48" wide unit will fit through the 42" door or that the equipment height clears the ductwork. Verify critical dimensions against field conditions and coordination drawings. This remains part of the contractor's means and methods responsibility.

5. Coordinate with affected trades

Your "No Exceptions Taken" approval doesn't mean the structural engineer verified the support requirements in their review or the electrical engineer confirmed the disconnect location. The submittal appears to conform with design intent, but coordination is your responsibility. Perform your coordination meetings.

6. Proceed with procurement

You have the approval needed to issue purchase orders for materials and begin fabrication. The design team has confirmed the submittal complies with general design intent shown in the contract documents.

7. Maintain your verification records

If issues arise during construction, you'll need proof that you performed due diligence - field measurements, coordination meeting notes, dimensional checks, site condition verification. These records support your contractual obligations.

Watch for potential red flags in the submittal review:

• Comments that seem to contradict the "No Exceptions Taken" status

• Notes requiring specific action before installation begins

• Coordination items affecting mechanical, electrical, or structural trades

• Site-specific conditions not fully shown in construction documents

• "See plans" or "See specifications" notes that require you to verify details

The architect's review confirms you're on the right track with design intent. Your verification confirms it will actually work in the field according to the contractor's means and methods.

Tom Port, the co-founder of BuildSync, says

"I tell teams, the anxiety doesn't come from submitting; it comes from what may have been missed.  Confidence comes from structure, and we provide that structure out of the box. 

BuildSync reviews every requirement characteristic-by-characteristic, so nothing is assumed and nothing is buried in the spec. When a submittal comes back ‘No Exceptions Taken,’ teams can move forward knowing each detail was explicitly verified, not just skimmed."

Proven Strategies for First-Time Construction Submittal Approval

The construction industry averages a 35% submittal rejection rate. That means more than one in three construction submittals comes back requiring corrections and resubmission. Each rejection adds 2-4 weeks to your submittal schedule and costs roughly $805 in direct expenses - not counting the schedule impact on downstream trades.

Getting to "No Exceptions Taken" on first submission isn't just convenient - it's critical for maintaining your project schedule and budget.

Submit Complete Packages

Include all required documentation from day one. Your submittal package needs the cover sheet with clear project identification, all product data sheets and cut sheets, shop drawings with fabrication details, required certifications and test reports, highlighted compliance points showing where specifications are met, and any coordination drawings specified in the contract documents.

Incomplete submittals get rejected immediately. Make the reviewer's job easy by providing complete materials.

Create Internal Review Checklists

Develop standardized checklists for common equipment types - AHUs, RTUs, lighting packages, VAV boxes, switchgear. Every submittal should be checked against the relevant list before it leaves your office. 

Include verification that all spec sections are addressed, required certifications are included, dimensions are highlighted in shop drawings, and coordination requirements with other construction documents are noted. Track these procedures in your submittal log.

Highlight Where Requirements Are Met

Don't make reviewers hunt through 70 pages of product data to find critical specifications. Use callouts, highlights, or compliance matrices in your shop drawings and product data. Show your work clearly. When specifications require "minimum SEER 16," highlight where the cut sheet shows "SEER 18." Make verification obvious so the submittal appears compliant at first glance.

Address Known Concerns Proactively

If specifications include "or equal" language, justify in your submittal why your proposed product equals the specified product. If there are unique project requirements - hospital-grade components, seismic certification, specific finish requirements - show compliance explicitly in your product data and shop drawings. Anticipate coordination questions and address them in your submittal notes. This demonstrates attention to design intent and contract requirements.

Use Technology to Verify Before Submission

Here's the reality: manual submittal review misses things. When you're cross-referencing 70 pages of product data against 30 pages of specifications, checking every technical characteristic and means and methods requirement, something will slip through. It's inevitable with manual review processes.

This is where AI-powered submittal review changes the equation. BuildSync extracts every technical characteristic from your construction submittals - refrigerant type, efficiency ratings, material specifications, dimensional requirements, certification needs. Then it compares each one against your project specifications and design intent systematically.

The platform flags failures before they reach the design team. You see exactly what the submittal complies with, what fails contract requirements, and what needs clarification - before submission. No more wondering if you caught everything in your shop drawings and product data. No more hoping the reviewer doesn't find that one spec requirement you missed.

Construction teams using BuildSync for submittal review have reduced their rejection rate from 35% to 5%. That's not marketing spin - it's the result of catching non-compliant items in construction submittals before submission instead of after rejection.

The math is straightforward: More "No Exceptions Taken" on first submission means faster procurement timelines for materials, zero resubmission delays on your submittal schedule, maintained schedule for downstream trades, and better relationships with design teams who appreciate quality construction submittals.

Your PMs and PEs get detailed documentation showing exactly where the submittal complies with contract requirements and design intent. When you submit, you do it with confidence that you've verified compliance systematically through proper review procedures, not just hopefully.

Ready to get 95% of your construction submittals to "No Exceptions Taken" on first submission? 

Join construction teams who've cut their rejection rate from 35% to 5% with BuildSync's AI-powered compliance verification. See exactly what the submittal complies with - and what doesn't - before you submit. 

Book a demo to see how it works on your actual submittals.