An ASI is the architect’s tool for small clarifications and minor changes during construction. AIA G710 is the standard form. By definition, an ASI is supposed to involve no change in contract sum or contract time. Common uses include answering an RFI with a revised detail, correcting a dimension, clarifying a finish, or making a small field adjustment.
The form typically warns the contractor: if you think the instruction changes cost or time, notify the architect before proceeding. That’s the important part. Under AIA A201, the architect may order minor changes not involving an adjustment in sum or time. If the contractor disagrees that the change is minor, the next step is a change order request, and the contractor shouldn’t just do the work and absorb the cost.
Why it matters
ASIs are a common source of hidden scope. Each one looks small and arrives with “no cost” printed on it, so it gets built without pricing. Over a big job, dozens of ASIs can add real cost. The contractor needs to review each one, decide whether it changes cost or time, and respond in writing within the contract’s notice window.
Common mistakes
- Treating every ASI as no-cost because the form says so.
- Missing the notice window to object.
- Not distributing ASIs to every affected sub.
- Losing track of which ASIs revised which details, so as-builts are wrong.
How os.construction handles it
We’re building ASIs linked to the RFIs and drawings they affect, with a one-step path to a change event when an instruction does change cost or time. It’s in development.