An Architect’s Supplemental Instruction is a one-page form, AIA Document G710, that an architect uses to clarify the contract documents or order minor changes in the work without triggering the full change-order process. Its authority comes from Section 7.4 of AIA A201-2017, which lets the architect act alone, but only when the change does not adjust the contract sum and does not extend the contract time. That narrow scope is what makes the form useful on an active project, and what makes it a liability trap when it gets stretched past its limits.
What a G710 Actually Does
The G710 does two things: it provides additional instructions or interpretations of the contract documents, and it orders minor changes in the work. “Minor” has a specific contractual meaning here. The printed text on the form states that the contractor shall carry out the work “without change in Contract Sum or Contract Time.” That language defines the document’s entire legal authority. An architect who uses a G710 to direct work that genuinely costs more or takes longer has exceeded the authority the contract grants. A contractor who performs that work without objecting may lose the right to recover those costs.
The form is binding on receipt. It does not require the contractor’s signature or the owner’s approval to take effect. The architect signs, the contractor receives it, and the obligation to perform begins.
How an ASI Differs from a Change Order or Construction Change Directive
Three AIA instruments modify the work, and confusing them creates real problems.
- The G710 (ASI) is issued by the architect alone. No owner or contractor signature is required. It is limited to minor changes that do not affect cost or schedule.
- The G701 (Change Order) is a formal amendment signed by all three parties: owner, contractor, and architect. It is used when scope, price, or schedule actually changes. Nothing happens until everyone agrees and signs.
- The G714 (Construction Change Directive) is signed by the owner and architect but not necessarily the contractor. It is used when a change is needed urgently and the contractor has not yet agreed to the cost or time impact. Work proceeds while the final price is negotiated.
The key distinction is authority. Only the G710 lets the architect act unilaterally. A Change Order requires consensus. A Construction Change Directive at least requires the owner’s agreement. When an architect reaches for a G710 to direct work that genuinely affects the budget or timeline, the safeguards of the other instruments get bypassed. That is where disputes start.
When the Architect Can Issue One
Section 7.4 of AIA A201-2017 sets three conditions, all of which must be true at the same time:
- The change must be consistent with the intent of the contract documents. An ASI cannot introduce scope that was not contemplated in the drawings and specifications.
- It must not adjust the contract sum. If the work costs more than what the contractor already priced, it is not a minor change.
- It must not extend the contract time. If the work pushes the schedule, the architect needs a different instrument.
A clarification that aligns with the design intent but adds cost still fails. An interpretation that costs nothing but delays the schedule also fails. Section 7.1.2 adds that a minor change “may be issued by the Architect alone,” so the architect is not required by the contract to notify the owner first. Most do, as a matter of professional practice, but it is not a contractual prerequisite the way it is for the other two instruments.
Cumulative ASIs and Scope Creep
A single ASI that swaps one tile pattern for another is clearly minor. Ten ASIs issued over two weeks, each individually small, can collectively amount to a significant shift in the contractor’s work. This is where the “consistent with the intent of the Contract Documents” requirement does the heavy lifting. If a pattern of ASIs starts to look like a redesign rather than a series of clarifications, the contractor has grounds to push back. No bright-line rule says how many ASIs become too many. The test is whether the cumulative effect exceeds what a minor change was meant to cover.
Filling Out and Transmitting the Form
The G710-2017 is available through the AIA Contract Documents online service and through project management platforms that integrate with it. The header fields identify the project, the parties, and the document’s place in the project record:
- Project name and address, matching the owner-contractor agreement exactly so the instruction ties to the correct legal entity and site.
- Names and addresses for owner, architect, and contractor.
- A sequential ASI number (ASI-001, ASI-002, and so on) that keeps the project’s supplemental instructions organized through closeout.
- The date the architect issues the instruction, which establishes when the contractor’s obligations begin.
- The specific contract the instruction applies to, which matters on projects with multiple prime contractors.
The description field is where the substance lives. The architect explains the clarification or change in enough detail that a superintendent can execute it without guessing. Vague instructions invite field errors and later finger-pointing. If the change involves dimensions, materials, or installation methods, spell them out. Attachments often accompany the description: revised sketches, updated specification sections, or marked-up detail drawings. Each attachment should carry a unique number and date so it can be distinguished from the original contract documents, and the description should reference each attachment by sheet number and revision date.
Once transmitted, the instruction should be logged and marked up on the master set of drawings so the documents on site match the work being performed. An ASI that lives only in an email thread and never makes it into the drawing set is a dispute waiting to happen at closeout.
What a Contractor Must Do to Preserve Its Rights
This is where most contractors get into trouble. Section 7.4 of AIA A201-2017 contains a waiver that is easy to miss and expensive to ignore. The rule works in two steps.
First, if the contractor believes the proposed minor change will affect the contract sum or contract time, the contractor must notify the architect and must not proceed with the work. The contract is explicit about both pieces: notify, and do not perform.
Second, if the contractor goes ahead and performs the work described in the ASI without first notifying the architect of the cost or time impact, the contractor waives any right to an adjustment in the contract sum or an extension of the contract time. The waiver is automatic. It does not matter that the work genuinely cost more or took longer. It does not matter that the owner knew about the work. Performing without objecting is consent.
The reason the rule works this way is simple. The owner needs the chance to evaluate the cost impact and decide whether to proceed before the money is spent, not after. A contractor who skips the notice step and tries to recover later through a claim faces an uphill battle. Object in writing the moment you receive an ASI you believe exceeds the minor-change threshold. Do not wait to see how it plays out. Do not perform the work thinking you can sort out the cost later. The contract’s waiver language makes “do first, argue later” a losing strategy.
If the architect disagrees that the instruction affects cost or time, the dispute moves into the claims process under Article 15 of A201-2017, which has its own notice deadlines and procedures. Work on unaffected parts of the project continues while the claim is pending.
Common Mistakes That Create Liability
A few recurring errors show up in how teams handle ASIs:
- An architect uses a G710 to avoid the Change Order process because it is faster, even though the change affects cost. That puts the architect outside their contractual authority and creates professional liability. If the change is not truly minor, use the right instrument.
- A contractor treats every ASI as a change-order opportunity. Objecting to every instruction as a negotiating tactic erodes trust and slows the project. The objection mechanism is for genuine cost and schedule impacts.
- The description is too vague. “Adjust framing as needed at the east wall” tells the contractor almost nothing. Instructions that lack detail get executed incorrectly.
- Attachments are not clearly identified. A sketch labeled “revision” with no date or number cannot be distinguished from other revisions months later. Every attachment needs a unique identifier and a date.
- ASIs never make it into the record drawings. At closeout, the record documents should reflect every modification. An ASI that changed a ceiling detail but was never marked on the reflected ceiling plan creates confusion for the owner and for anyone who maintains the building later.
The G710 works best when everyone treats it as what it is: a narrow tool for keeping construction moving through minor adjustments that do not change the deal. The moment a change starts to feel like more than a clarification, stop, flag it, and let the formal change process handle it.