Architect's Supplemental Instructions (ASIs): Scope, Limitations, Cost Implications, and Issuance Protocols

Covers the Architect's Supplemental Instructions (ASIs) as a mechanism for issuing minor changes and clarifications during construction. Addresses the scope limitations of ASIs under A201 Section 7.4, cost and time implications, documentation requirements, and the distinction between ASIs and other change instruments.

ARE · Construction & Evaluation

Overview

An Architect's Supplemental Instruction (ASI) is a written document issued by the architect during construction to clarify, interpret, or order minor changes in the work. ASIs are the architect's primary tool for making adjustments that are consistent with the design intent and do not affect the contract sum or contract time.

Under AIA A201-2017 Section 7.4, the architect has authority to order minor changes in the work without requiring owner or contractor agreement, provided the change does not involve an adjustment to the contract sum or an extension of the contract time. This is a unilateral authority: the architect issues the ASI, and the contractor is obligated to comply.

The critical limitation is scope. If a change involves additional cost or time, it is not a minor change and cannot be handled through an ASI alone. Instead, it requires a change order (signed by owner, contractor, and architect) or a construction change directive (signed by owner and architect when the contractor disagrees). The contractor has a contractual obligation to notify the architect if they believe a directed minor change will affect the contract sum or time. If the contractor performs the work without giving this notice, the contractor waives the right to any adjustment.

ASIs are commonly used for dimensional clarifications, material specification clarifications where the substitution has no cost impact, minor design adjustments that maintain the original intent, and coordination corrections between disciplines. They serve as a formal written record that supplements the contract documents without the procedural overhead of a full change order.

Essential

ASIs occupy a specific and limited position in the hierarchy of contract modifications. Understanding where they fit relative to change orders, construction change directives, and RFIs is fundamental to construction administration. The Hierarchy of Contract Modifications A201-2017 establishes three mechanisms for changes in the work, each with different authority requirements. Change orders (Section 7.2) require agreement among all three parties: owner, contractor, and architect. They document agreed-upon changes to scope, cost, and time. Construction change directives (Section 7.3) require signatures from the owner and architect but not the contractor, and are used when the owner and architect agree a change is necessary but the contractor disputes the cost or time impact. Minor changes (Section 7.4) require only the architect's written order and are limited to changes consistent with the design intent that involve no adjustment to contract sum or time. ASIs are the practical implementation of Section 7.4.

Professional

ASIs carry professional liability implications that architects must manage carefully. The line between a minor change and a cost-affecting change is not always obvious, and architects who routinely use ASIs to direct work that arguably affects the contract sum expose themselves to claims from both owners and contractors. Scope Creep Through ASIs A common risk pattern involves issuing a series of individually minor ASIs that cumulatively represent a significant change in scope. Each individual ASI may legitimately qualify as a minor change, but when a contractor receives fifteen ASIs on a single project, each adding a small amount of work, the aggregate effect may justify a claim for additional compensation. Contractors sometimes compile ASI logs and argue that the cumulative impact warrants a change order.

TLDR

ASIs are the architect's written orders for minor changes during construction under A201 Section 7.4. They can only be used when the change is consistent with design intent and does not affect the contract sum or contract time. Only the architect's signature is required. If the contractor believes an ASI will affect cost or time, the contractor must notify the architect before performing the work or waive the right to adjustment. ASIs are not change orders (which need three signatures) or CCDs (which need two). Common uses include dimensional clarifications, coordination corrections, and material specification clarifications. Keep an ASI log, coordinate with consultants on their scope, and watch for cumulative scope creep.

ELI5

Think of building a house. The architect drew the plans, the contractor is building from those plans, and now the architect notices something that needs a small tweak. Maybe a light switch should be three inches to the left so it lines up with the door frame better. That is a tiny change that does not cost any extra money and does not slow anything down. An ASI (Architect's Supplemental Instruction) is the architect's way of making those small fixes in writing. The architect writes it down, sends it to the contractor, and the contractor has to do it. No meetings needed. No one else has to sign off. But here is the catch: the architect can only use an ASI for changes that do not cost extra money and do not take extra time.

Overview

Essential

Professional

TLDR

ELI5

AREConstruction & Evaluation

Architect's Supplemental Instructions (ASIs): Scope, Limitations, Cost Implications, and Issuance Protocols

2 min read255 words

ASIs as a Tool for Minor Changes and Clarifications

Want to track your progress and access more study tools?

Create a free account