HelonicHelonic

What is an ASI (Architect's Supplemental Instruction)?

Understanding ASIs, when they're used, and how they differ from RFIs and change orders.

ASI Definition

An Architect's Supplemental Instruction (ASI) is a written document issued by the architect to clarify, interpret, or order minor changes to the construction documents. ASIs are intended for changes that do not affect the contract sum or contract time.

Key Point

ASIs are for changes that do NOT affect cost or schedule. If there's any cost or time impact, it should be processed as a change order, not an ASI.

When is an ASI Used?

Clarifying Intent

When drawings or specs are unclear and need interpretation without adding scope.

Minor Modifications

Small changes to details, finishes, or equipment that don't change the overall scope.

Substitution Approval

Approving an equal substitution that doesn't change cost (though usually a separate process).

Correcting Errors

Fixing minor errors or inconsistencies in the documents that were always intended.

ASI vs. RFI vs. Change Order

DocumentInitiated ByPurposeCost Impact?
RFIContractorAsk a questionMay lead to change
ASIArchitectClarify or modify (minor)No cost/time impact
CCDOwner/ArchitectDirect change (price TBD)Yes, pending negotiation
COAll parties signFormal contract changeYes, agreed amount

What's Included in an ASI?

1ASI number and date
2Project name and number
3Reference to affected drawings/specifications
4Clear description of the clarification or change
5Sketches or marked-up drawings (if needed)
6Statement confirming no cost or time impact
7Architect's signature
8Distribution list

ASI Best Practices

For Architects
  • • Be specific about what's changing and why
  • • Include sketches for visual clarity
  • • Reference affected drawing sheets and spec sections
  • • Verify no cost/time impact before issuing
For Contractors
  • • Review ASIs promptly upon receipt
  • • If there IS a cost/time impact, respond in writing immediately
  • • Log all ASIs and incorporate into project documents
  • • Distribute to affected subcontractors

Common ASI Pitfalls

Watch out
Scope Creep via ASI

Some architects use ASIs to add scope without going through change order process. Contractors should flag any ASI that adds work.

Watch out
Late ASIs

ASIs issued after work is complete may require rework. There may be valid claims for cost recovery.

Watch out
Vague Language

ASIs should be as clear as the original documents. Vague ASIs lead to more RFIs.

Keep exploring

Related references for RFIs, change orders, and project coordination.

Construction Change Order Guide

Understanding COs, CCDs, and PCOs.

How to Write an RFI

Write clear RFIs that get answered fast.

How to Track RFIs

Manage RFIs so nothing falls through.

How to Run an OAC Meeting

Best practices for coordination meetings.

Reduce ASIs with better drawing review

Most ASIs stem from coordination conflicts or ambiguities in the original drawings. Helonic catches these issues during design, so you have fewer changes during construction.