# Architect's Supplemental Instruction (ASI)

> The instrument by which the architect clarifies or minorly adjusts the work without changing the contract sum or time — and the recurring flashpoint over whether an instruction is really a no-cost clarification or a disguised change.

- Source: https://briq.ai/acu/object/architects-supplemental-instruction
- Department: Field Operations & Project Controls (https://briq.ai/acu/department/field)
- Catalog code: FLD 207 · Level: Practitioner · Track: Operations · 10 min read
- Also known as: ASI, Supplemental Instruction, Architect's Instruction, AI, Field Instruction

## Definition

An Architect's Supplemental Instruction is a document issued by the architect to clarify the design intent or order minor changes in the work that, in the architect's judgment, do not involve an adjustment to the contract sum or the contract time. It is a device for keeping the project moving on matters too small to warrant a formal change order — a clarified detail, a minor dimensional adjustment, a substitution of an equivalent product — issued under the architect's authority within the contract. Its defining constraint is the phrase not involving adjustment to contract sum or time: an ASI is legitimate only when it genuinely carries no cost or schedule impact, and the entire tension around the instrument lives in disagreements about whether that condition is actually met. An ASI is not a change order and cannot by itself authorize additional cost or time; when an instruction the architect issues as an ASI in fact carries cost or schedule impact, the contractor's remedy is to give notice and pursue a change, and silently absorbing such an instruction is one of the most common ways contractors perform uncompensated work.

## Why it matters

It keeps the project moving without the overhead of a change order for genuinely minor matters. Formal change orders are slow and expensive to process, and forcing every clarified detail or trivial adjustment through that machinery would grind a project to a halt. The ASI exists precisely to resolve the small, no-impact items quickly under the architect's authority, and used properly it is a lubricant that keeps the field from stalling on minutiae.

It is a recurring flashpoint over disguised changes, and the contractor's response determines whether it gets paid. Because an ASI is defined as carrying no cost or time, an architect who issues an instruction that does carry impact as an ASI has, intentionally or not, directed extra work while denying it is extra. The contractor that recognizes this, gives notice, and pursues a change preserves its rights; the contractor that quietly complies performs the work for free, and this dynamic makes disciplined ASI review a direct margin issue.

It modifies the documents and must be incorporated, or the record drifts from reality. An ASI clarifies or adjusts the work, which means the drawings and specifications now say something different, and that change has to flow into the controlling set, the affected submittals and shop drawings, and eventually the as-builts. An ASI issued and then never incorporated leaves the documents inconsistent with what is actually being built, seeding future RFIs, conflicts, and coordination errors.

It carries ripple effects that a quick instruction can hide. A clarified detail can invalidate an approved shop drawing, contradict a prior RFI answer, affect an interfacing trade, or touch a schedule activity, and because the ASI is meant to be minor it is often issued and filed without tracing those ripples. The gap between how casually an ASI is issued and how far its effects can reach is where a small instruction turns into a real problem.

## Lifecycle

1. **Trigger** — A need for clarification or a minor adjustment arises — often from an RFI answer, a field condition, or a design refinement. The trigger frequently determines whether the matter is genuinely minor or is being routed as an ASI to avoid a change.
2. **Architect's determination** — The architect judges that the instruction involves no adjustment to the contract sum or time and elects to issue it as an ASI rather than initiate a change. This judgment is the crux, and it is the architect's, not the contractor's, which is why the contractor must review it independently.
3. **Issuance** — The ASI is numbered, described, and issued to the contractor with any attached sketches or revised details. A vague ASI that does not clearly define the instruction breeds its own RFIs.
4. **Contractor review and impact assessment** — The contractor evaluates whether the instruction truly carries no cost or time, and traces its effect on shop drawings, submittals, other trades, and the schedule. This is the step most often skipped, and skipping it is how disguised changes get absorbed for free.
5. **Acceptance or notice of impact** — If the instruction is genuinely minor, the contractor proceeds. If it carries cost or schedule impact, the contractor gives written notice and initiates a change rather than silently complying. The response here decides whether rights are preserved.
6. **Execution** — The clarified or adjusted work is performed. Where the ASI invalidated an approved shop drawing or a submittal, those must be revised before fabrication proceeds on the old configuration.
7. **Incorporation into the record** — The ASI is reflected into the controlling drawing set, the affected submittals, and eventually the as-builts, so the documents stay consistent with the built work. Un-incorporated ASIs leave the record drifting from reality.
8. **Closure and audit trail** — The ASI is logged, its impact resolution recorded, and the trail retained. In a later change or claim dispute, the ASI log and how each was handled is examined for a pattern of absorbed impacts.

## Anatomy

- **ASI number and date** — Sequential identifier and issue date, anchoring the instruction in the project record and any notice clock it starts.
- **Description of instruction** — The specific clarification or minor change directed. Vague instructions defeat the purpose and generate follow-on RFIs.
- **Affected drawings and specifications** — The sheets and specification sections the instruction clarifies or modifies. Determines what must be incorporated into the set.
- **Attached sketches / revised details** — The graphic content defining the instruction, often a revised detail or a supplemental sketch.
- **Cost and time representation** — The architect's statement that the instruction involves no adjustment to contract sum or time. The assertion the contractor must independently test.
- **Originating RFI or trigger** — The RFI, field condition, or design refinement that prompted the ASI, connecting it to its cause.
- **Contractor impact assessment** — The contractor's evaluation of whether the instruction actually carries cost or schedule impact. The record that preserves the change right.
- **Affected shop drawings / submittals** — Approved shop drawings and submittals the instruction invalidates or requires revising, so fabrication does not proceed on a superseded configuration.
- **Interfacing trades** — Other trades the clarified condition touches, since a minor change to one scope can ripple into another's coordinated work.
- **Schedule activity affected** — The activity the instruction touches, checked so a supposedly no-time instruction is not quietly consuming float.
- **Incorporation status** — Whether the ASI has been reflected into the controlling set and the as-builts. Tracks whether the record stays consistent with reality.
- **Linked change record** — Any change event or PCO opened because the instruction carried impact, keeping cost joined to the instruction that caused it.

## Failure modes

- **Disguised change absorbed for free** — An instruction that genuinely adds cost or time is issued as an ASI asserting no impact, and the contractor complies without review or notice. The extra work is performed uncompensated, and by the time the cost surfaces in the job cost report the leverage and the notice window to recover it are long gone.
- **No contractor impact assessment** — The contractor treats the architect's no-impact representation as settled and skips its own evaluation. Because the cost-and-time judgment was the architect's, not a neutral fact, this abdicates exactly the review that would have caught a disguised change.
- **ASI invalidates an approved shop drawing, unnoticed** — A clarified detail contradicts an approved shop drawing, but the ripple is never traced, and the fabricator builds to the now-superseded approved configuration. The mistake is discovered at delivery or erection, turning a minor instruction into expensive rework.
- **Never incorporated into the set** — The ASI is issued, complied with, and filed, but never reflected into the controlling drawings or the as-builts. The documents now disagree with the built work, and the inconsistency seeds later RFIs, coordination conflicts, and an inaccurate record set for the owner.
- **Contradicts a prior RFI answer or ASI** — The instruction conflicts with an earlier interpretation without acknowledging or reconciling it. The field is left with two contradictory directions on the same condition and no clear governing answer, and work stalls on which to follow.
- **Vague instruction breeds its own RFIs** — The ASI is too imprecise to act on, so the contractor must issue an RFI to clarify the clarification. The instrument meant to resolve a minor matter quickly instead adds a round trip and delay.
- **Pattern of impactful ASIs unchallenged** — Over a project, a series of ASIs each individually carry small impacts the contractor lets pass. In aggregate they represent significant absorbed cost and time, and the pattern — visible only across the ASI log — reveals a systematic erosion of margin that no single instruction made obvious.

## Metrics

- **ASI volume and rate** — ASIs issued per period and per value. A high rate can signal incomplete documents being patched through instructions rather than proper changes.
- **Impact-assessment completeness** — Share of ASIs with a documented contractor impact evaluation. Measures whether the review that preserves change rights is actually happening.
- **Disguised-change conversion rate** — Share of ASIs that, on review, carried cost or time and were converted to changes. Reveals how often instructions understate impact.
- **Incorporation rate** — Share of ASIs reflected back into the controlling set and as-builts. Measures whether the documents stay consistent with the built work.
- **Downstream conflict rate** — ASIs that invalidated a shop drawing or contradicted a prior interpretation. Measures how well ripple effects are being traced.
- **Absorbed-impact exposure** — Aggregate cost and time of impacts accepted without a change across the ASI log. Quantifies the margin quietly given away.
- **Clarification-return rate** — ASIs that required an RFI to clarify. Measures the precision of the instructions being issued.

## The AI shift

- **Conversational** — The ASI log becomes something you interrogate rather than a filing cabinet. You ask which recent ASIs the contractor has not independently reviewed for impact, whether a specific ASI invalidates any approved shop drawing, whether it contradicts a prior RFI answer, or what the aggregate absorbed-impact exposure across the log looks like, with the instructions and affected records cited.
- **Generative** — Impact review gains a drafting assistant: given an ASI, a model drafts the contractor's impact assessment — identifying whether the instruction plausibly carries cost or schedule effect, which shop drawings and submittals it touches, and which trades and activities it ripples into — and, where impact appears real, drafts the notice and the change-event narrative for the contractor to validate before relying on it.
- **Orchestrated** — The ASI stops being an isolated instruction. It is cross-referenced against the approved shop drawings and submittals it may invalidate, checked against prior RFI answers and ASIs for contradiction, tied to the schedule activity it touches, tracked for incorporation into the controlling set, and, where it carries impact, linked to the change event it should generate so cost stays joined to the instruction.
- **Autonomous** — The routine motion runs continuously: every issued ASI is checked for likely cost or schedule impact and flagged for review, ripple effects on shop drawings, submittals, prior interpretations, and interfacing trades are traced and surfaced, incorporation into the set is tracked, and the aggregate absorbed-impact exposure is monitored, while the judgment of whether an instruction truly carries impact, the decision to give notice, and any change or acceptance remain firmly human.

## Prompts

### Conversational — Deciding whether an ASI is really a no-cost clarification.

```text
ASI 09 was just issued as a no-cost, no-time clarification adjusting the detail at the storefront head condition. Before we simply comply, help me test whether that representation holds. Read the instruction and the revised detail against the original documents and tell me: whether the change plausibly adds labor, material, or a different product that carries cost; whether it invalidates any approved shop drawing or submittal for the storefront; whether it contradicts any prior RFI answer or ASI on this condition; which interfacing trades it touches; and whether the affected schedule activity has the float to absorb any added work. Tell me plainly whether this looks like a genuine clarification or a change issued as an ASI, and what notice we would need to preserve our rights.
```

**Expected output:** An independent impact test citing the specific documents, shop drawings, prior interpretations, and schedule activity, with a clear judgment on whether the ASI is a genuine clarification or a disguised change and what notice is required.

**Follow-ups:**

- If it carries impact, draft the notice and the change-event narrative.
- Which approved shop drawings does this invalidate before fabrication?
- Show me our absorbed-impact exposure across all ASIs on this project so far.

### Generative — Drafting the contractor's impact assessment and, if needed, the change.

```text
Draft our contractor impact assessment for ASI 12, which directs a change from the specified light fixture to a different model the architect asserts is equivalent at no cost. Compare the two products against the specification and the approved submittal, and identify any difference in cost, lead time, mounting, or coordination with the ceiling and electrical scope. If the substitution plausibly carries cost or schedule impact, draft the written notice reserving our rights and a change-event narrative describing the delta; if it is genuinely equivalent and no-impact, draft the acceptance and note what must be incorporated into the set and the submittal record. State your assumptions and flag anything I need to verify with the electrical subcontractor before we rely on this.
```

**Expected output:** A documented impact assessment comparing the directed substitution against the specification and submittal, producing either a notice-and-change draft or an acceptance-and-incorporation note, with assumptions stated and verification points flagged.

**Follow-ups:**

- Get the actual lead time and price delta from the supplier and revise the assessment.
- Which approved submittal must be superseded if we accept the substitution?
- Draft the incorporation note for the drawing set and the O&M record.

### Orchestrated — Tracing the full ripple of an instruction across the project.

```text
ASI 15 clarified the connection detail at the canopy-to-facade interface. Trace its full impact across the project and tell me everything it touches: which approved shop drawings and submittals for the canopy and facade it invalidates or requires revising; whether it contradicts any prior RFI answer or ASI on this interface; which interfacing trades — steel, glazing, waterproofing — are affected; which schedule activities it touches and whether they have float; and whether, despite being issued as no-cost, it plausibly carries impact that warrants a change. Return a single impact summary with each conclusion tied to the specific record, and flag anything you are not confident about rather than guessing.
```

**Expected output:** A cross-referenced impact summary spanning shop drawings, prior interpretations, interfacing trades, schedule, and cost, each conclusion cited to its record with uncertainty flagged, so no ripple of the instruction is missed.

**Follow-ups:**

- Draft the resubmittal instructions for the shop drawings this invalidates.
- If it carries impact, open a change event and draft the cost narrative.
- Confirm this ASI is reflected into the controlling set and the as-builts.

### Autonomous — Standing policy for handling ASIs.

```text
Handle our incoming ASIs continuously under these rules. For every ASI issued, run a first-pass impact check for plausible cost or schedule effect and flag it for the project manager's review — never accept the architect's no-impact representation on our behalf. Trace and surface ripple effects: approved shop drawings and submittals the instruction invalidates, contradictions with prior RFI answers or ASIs, interfacing trades affected, and the schedule activity touched and its float. Track incorporation of each ASI into the controlling set and the as-builts, and flag any not incorporated. Maintain a running total of absorbed-impact exposure across the log. Never decide that an instruction carries no impact, never give or waive notice, and never open or accept a change on your own; route every impact judgment and change decision to the project manager with your reasoning and the affected records cited.
```

**Expected output:** Continuous first-pass impact flagging, ripple tracing, and incorporation tracking with running exposure, where the impact judgment, notice, and change decisions always remain with a human, fully audited.

**Follow-ups:**

- Show me this week's ASIs flagged for possible impact and any that invalidate a shop drawing.
- What is our current aggregate absorbed-impact exposure across the ASI log?

## Maturity ladder

- **Level 0 — Level 0 — Comply and file** — ASIs are accepted at face value, complied with, and filed with no impact review, no ripple tracing, and no incorporation into the set. Disguised changes are absorbed unknowingly.
- **Level 1 — Level 1 — Logged** — ASIs are logged with numbers, dates, and affected sheets, but impact assessment and incorporation remain inconsistent and manual.
- **Level 2 — Level 2 — Reviewed and linked** — Each ASI gets a documented impact assessment, ripple effects on shop drawings and trades are traced, impactful ones convert to changes, and incorporation is tracked.
- **Level 3 — Level 3 — Assisted** — Impact checks and ripple tracing are drafted, contradictions with prior interpretations are surfaced, and notices and change narratives are proposed for human review.
- **Level 4 — Level 4 — Operated** — Impact flagging, ripple tracing, incorporation tracking, and exposure monitoring run within guardrails, while impact judgment, notice, and change decisions stay human.

## FAQ

### What is the difference between an ASI and a change order?

An ASI is an instruction the architect issues to clarify design intent or make a minor change that, in the architect's judgment, involves no adjustment to the contract sum or time, and it is meant to keep the project moving on trivial matters without formal change machinery. A change order modifies the contract sum, the contract time, or both, and requires the agreement or directive process the contract defines. The critical point is that an ASI cannot authorize additional cost or time; if an instruction issued as an ASI actually carries impact, it must be converted into a change, and the ASI label does not make the extra work free.

### What should a contractor do if an ASI actually carries cost or time?

Give written notice within the contractual window and pursue a change, rather than silently complying. The architect's representation that an instruction carries no impact is a judgment, not a neutral fact, and the contractor is entitled and obligated to evaluate it independently. Quietly performing an instruction that adds cost or time means doing extra work for free and, once the notice window closes, losing the ability to recover it. The disciplined response is to comply if the instruction is truly minor and to notice-and-change it if it is not, documenting the impact assessment either way.

### Does complying with an ASI waive the right to claim its cost impact?

It can, which is exactly why the impact assessment and timely notice matter. Many contracts require prompt written notice of any instruction the contractor believes carries cost or schedule impact, and proceeding without that notice can be argued to waive the claim or at least weaken it substantially. Compliance itself is often required — the contractor generally must carry on with the work and dispute the impact separately — but compliance combined with silence about impact is what forfeits the right. The safe practice is to preserve rights through notice before or while complying, not to refuse the work.

### Why does an ASI need to be incorporated into the drawing set?

Because an ASI clarifies or modifies the work, which means the contract documents now require something different from what the original sheets show, and if that change is not reflected into the controlling set the documents no longer describe what is actually being built. Un-incorporated ASIs leave the drawings inconsistent with reality, which seeds later RFIs when another trade reads the un-updated sheet, causes coordination conflicts, and produces an inaccurate as-built record that the owner inherits for the life of the building. Incorporation is what keeps the single source of truth actually true.

## Related objects

- [Request for Information (RFI)](https://briq.ai/acu/object/rfi)
- [Owner Change Order (OCO)](https://briq.ai/acu/object/owner-change-order)
- [Change Event](https://briq.ai/acu/object/change-event)
- [Shop Drawing](https://briq.ai/acu/object/shop-drawing)
- [Drawing Set & Specifications](https://briq.ai/acu/object/drawing-set)
- [Submittal](https://briq.ai/acu/object/submittal)