Under AIA A201, approval of a submittal doesn’t excuse a contractor from meeting the contract documents. The contractor still owns the work, including its methods and details. If a deviation is needed, it must be handled through a formal contract modification—not assumed approved by the submittal review.

Multiple Choice

If the contractor receives an approved submittal, is he relieved of responsibility for deviations from the contract documents?

Approved submittals confirm that proposed products, systems, or workmanship align with the design intent, but they do not remove the contractor’s obligation to comply with the contract documents. The contractor remains responsible for ensuring that the work, including its means and methods, meets all contract requirements. If a deviation is needed or discovered, it must be addressed through the contract modification process (such as a change order) to update the contract documents, rather than being exempted simply because a submittal was approved. So, no—the contractor is not relieved of responsibility for deviations just because a submittal was approved.

What an Approved Submittal Does—and Doesn’t—Mean Under AIA A201

An approved submittal can feel like a green light. A product cut sheet comes back stamped, a shop drawing is marked “approved,” and the construction team can move ahead. But that stamp has limits. Under AIA A201, approval of a submittal does not automatically excuse the contractor from following the contract documents.

That distinction matters because a submittal is only one part of a much larger project record. It helps the architect review certain details of proposed work, but it does not quietly rewrite the agreement between the owner and contractor. If the proposed work departs from the contract requirements, the departure needs to be clearly disclosed and handled through the process the contract provides.

A stamp is not a rewrite

AIA A201, the General Conditions of the Contract for Construction, sets out a specific framework for submittals. These may include shop drawings, product data, samples, and similar materials. They help show how the contractor proposes to carry out parts of the work.

The architect’s review has a defined purpose. Under Section 3.12, review is generally limited to checking the submittal for consistency with the information in the contract documents and the design concept expressed in them. It is not a full inspection of every dimension, quantity, fabrication detail, or construction method.

That limit is easy to miss. A reviewed drawing may show that a proposed window system appears consistent with the design intent. It does not necessarily confirm every field measurement, every connection, or every coordination detail with nearby work. Those responsibilities remain with the contractor, as the contract assigns them.

Think of the approval stamp as a checkpoint, not a new set of directions. It says the architect has reviewed the submittal within the scope of that review. It does not mean the architect has taken over the contractor’s duties.

What remains the contractor’s responsibility?

The contractor is responsible for preparing and submitting information that meets the contract requirements. AIA A201 also assigns the contractor responsibility for details such as dimensions, quantities, fabrication processes, and coordination of the work. The contractor remains responsible for the means and methods used to build the project, unless the contract documents say otherwise.

Those responsibilities matter even when a submittal has been approved. If a shop drawing contains an incorrect dimension, or a product does not meet a specified performance requirement, the approval stamp alone does not transfer that risk to the architect. The contractor must still carry out the work in line with the contract documents.

This is not a claim that the architect’s review has no value. Review can catch inconsistencies and help keep work coordinated. But the review is limited by design. It is one layer of project oversight, not a substitute for the contractor’s own checks.

There’s an important exception

The rule is firm, but it isn’t quite as simple as “approval never matters.” AIA A201 addresses deviations from the contract documents in Section 3.12.8. In general, the contractor is not relieved of responsibility for a deviation just because the architect reviewed or approved a submittal.

There is, however, a defined route for handling a proposed departure. The contractor must specifically tell the architect in writing about the deviation when submitting the material. Then the deviation must receive written approval through the method required by the contract. Depending on the circumstances, that may include the architect’s written approval as a minor change in the work, or a formal contract instrument such as a change order or construction change directive.

The key is that the departure must be clearly identified and expressly addressed. A difference buried in a large set of shop drawings is not the same as a clearly disclosed deviation that receives written approval. Nor should a general approval stamp be treated as consent to every departure shown in the submittal.

This is where good documentation earns its keep. If a specified material is unavailable and the contractor proposes a substitute, the proposal should explain the difference, identify any effect on cost or schedule, and follow the required review and authorization steps. A casual email or an ambiguous mark-up can leave everyone arguing later about what was actually approved.

Why the distinction matters on site

Construction moves quickly. Materials have lead times, crews depend on timely decisions, and one small change can affect several trades. In that setting, it’s tempting to treat an approved submittal as a blanket permission to proceed.

But suppose the contract calls for a particular insulation rating, and the submitted product has a lower rating. If the difference isn’t called out and formally approved, the contractor may still be responsible for providing the specified performance. The architect’s approval of the product sheet might not resolve that issue, especially if the deviation was not clearly disclosed.

Or consider a shop drawing that changes a connection detail. The revised connection might look tidy on paper, yet affect structural performance or coordination with another system. An approval that was intended to review general conformance does not necessarily authorize that change. The project team needs to identify the departure and use the contract’s change process.

These examples show why submittal review and change control are separate functions. Submittals help confirm that proposed work fits the design and contract information. Contract modifications record changes to that information. One process should not be used as a shortcut for the other.

Clear communication beats guesswork

A useful submittal process starts before the package reaches the architect. The contractor should compare the proposed product or detail against the relevant specifications, drawings, and other contract requirements. If something differs, flag it plainly rather than hoping the reviewer spots it.

The submission should make the issue easy to understand:

  • Identify the specific contract requirement.

  • Describe the proposed deviation.

  • Explain its likely effect on cost, schedule, performance, or coordination.

  • Request the written authorization required by the contract.

The architect, in turn, can respond within the authority the contract gives them. If a proposed change affects the contract sum or time, the team may need a change order or construction change directive rather than a routine submittal approval. The right document depends on the nature of the change and the terms of the agreement.

Clear records also help avoid a common source of conflict: different people remembering a conversation in different ways. A written decision gives the field team something reliable to act on and creates a traceable project record.

Approval has value—but it has boundaries

AIA A201 draws a careful line. The architect reviews submittals for a limited purpose, while the contractor remains responsible for complying with the contract documents and managing the work. Approval does not, by itself, erase a deviation or shift the contractor’s responsibilities.

If a deviation is needed, disclose it specifically and obtain written authorization through the proper channel. That may mean approval as a minor change, or a formal contract modification. Either way, the important point is that the change must be made explicit.

A submittal stamp can help move work forward. It just can’t do every job at once. When project teams treat review and contract modification as distinct steps, they reduce ambiguity, protect the design intent, and give everyone a clearer basis for building the work.