How Architect’s Supplemental Instructions Work in Construction

By

Josh Krissansen

Last Updated Mar 31, 2026

By

Josh Krissansen

Architects’ Supplemental Instructions sit at a critical boundary in construction contracts. They are intended to clarify design intent without changing scope, cost, or programme. When used correctly, they keep work moving. When they are not controlled, they quietly introduce commercial risk.

The risk rarely comes from the ASI itself. It comes from how clarifications are issued, communicated, and escalated when cost or sequencing impacts emerge. Informal directions, late documentation, or unclear thresholds between an ASI and a variation can leave contractors carrying unapproved work, delayed payment, or disputed entitlement.

For experienced builders, ASIs are not an administrative detail. They are a contract control mechanism. How they are managed directly affects margin protection, payment certainty, and dispute exposure across a project.

This article explains what Architects’ Supplemental Instructions are, how they operate under Australian construction contracts, and the controls commercial teams use to manage them without blurring the line between clarification and change.

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

As a formal document issued by the architect, the ‘Architects’ Supplemental Instruction’ has one aim: to clarify, correct, or supplement construction documents after contract execution. 

There are some caveats in place: the instruction cannot change the contract sum or the programme duration, and, once issued, it becomes part of the contract documents, making it legally enforceable.

However, because of their utility, architects use ASIs in several common situations such as: 

• Resolving incomplete or ambiguous design details.
• Refining design elements that do not alter scope.
• Responding to Technical Queries.
• Providing clarifications required by site conditions that have no cost or sequencing impact.
• Adjusting specifications where alternatives are cost-neutral.

What does this look like in practice? ASIs can support the clarification or changing of seemingly minor — but significant — situations like:

• Defining 75mm Helvetica lettering where drawings say only large letters.
• Correcting a detail that shows roofing shingles installed from the top.
• Clarifying a complex flashing connection with an annotated sketch.

ASI vs Variations vs Construction Change Directives

Architects' Supplemental Instructions address clarifications that leave scope, cost, and programme intact. When a change affects labour, materials, methodology, cost, or time, a variation is required. If the work cannot wait for agreement on scope or cost, a Construction Change Directive authorises the contractor to proceed while valuation is resolved.

Clear distinctions between these documents prevent misuse of ASIs, which is a common source of disputes. Correct document selection safeguards the business against unauthorised scope changes and cost recovery issues.

• ---

  Cost Impact

  An ASI cannot introduce additional cost under any circumstances.
  
  A variation adjusts the contract value when the change affects labour, materials, or methodology.
  
  A Construction Change Directive authorises work that will carry a cost impact once the parties agree on valuation.

• ---

  Schedule Impact

  An ASI must preserve the agreed programme and cannot introduce delay or acceleration.
  
  A variation may extend or compress the programme depending on the change.
  
  A Construction Change Directive requires immediate compliance even though time implications remain unresolved.

• ---

  Approval Pathway

  The architect issues an ASI and it becomes part of the contract documents for the project.
  
  A variation requires agreement between the contractor and the client before the work proceeds.
  
  A Construction Change Directive is issued by the owner or architect when agreement cannot be reached within the required timeframe.

• ---

  Escalation Requirements

  An ASI must convert to a variation when the clarification introduces additional labour, materials, or sequencing implications.
  
  A variation must be issued when any change is expected to affect cost or time, even if the full impact has not yet been quantified.
  
  A Construction Change Directive is used when the work cannot wait for agreement on scope or cost, and it remains in place until valuation is resolved and converted into a formal variation.

• ---

  Typical Examples

  An ASI may clarify a metal trim specification with no cost change and before work begins.
  
  A variation applies when a client requests an upgraded timber species for a feature wall that requires revised pricing and a programme update.
  
  A Construction Change Directive applies when a structural engineer identifies an immediate need for foundation reinforcement and the owner instructs the work to proceed while the cost is determined.

When Should Construction Teams Use an ASI?

When it comes to using an ASI in construction, timing is everything. There’s no specific ‘period’ that governs its usage. Still, there is a process that teams will follow, which applies as soon as clarifications must be documented through the correct contractual instrument to protect commercial outcomes.

1. Identify Triggers That Require an ASI

   ASIs should be used when the architect needs to clarify design intent without altering scope, cost, or programme. This includes resolving omissions or ambiguous details in the documents, correcting minor drafting errors, and issuing formal responses to Technical Queries.
   
   ASIs are also suitable for minor site condition adjustments that do not add labour or sequencing requirements, and for substituting equivalent materials where cost and performance remain unchanged.

2. Apply The ASI Threshold Test

   Before issuing an ASI, teams must confirm that the clarification introduces no additional labour, no change in material quantity or specification value, and no impact on the agreed programme. Additionally, it must not require any rework of completed work.
   
   If the clarification fails any part of this test, it must be escalated to a variation.

3. Recognise Red Flags That Require A Variation Instead

   Any adjustment to the scope or construction methodology requires a variation rather than an ASI. The same applies when work must be undone or repeated, when the change introduces premium time or out-of-sequence work, or when it affects commercial entitlement.
   
   Any extension or compression of the programme, regardless of size, also disqualifies the use of an ASI.
   
   The better (and faster) teams can recognise the situations that qualify for an ASI, the easier it will be to avoid unapproved scope changes, reduce disputes, and maintain clear entitlement pathways for cost and time. 
   
   And when ASIs are treated as a discipline that requires all commercially impactful changes to be captured through variations, payment claims strengthen and downstream contention reduces.

How ASIs Work During Construction Projects

On paper, an ASI appears simple: a clarification issued mid-delivery to keep work moving. In practice, how that instruction is issued, communicated, and verified determines whether it does its job — or quietly creates risk.

During construction, ASIs go beyond simple documentation and become an active component that impacts operations. Their position at the critical junction between design intent and site execution means that if they’re documented late or communicated loosely, rework, delays, and disputes become inevitable.

Understanding how ASIs move through a project — from issuance to site verification — enables teams to maintain clarity without compromising commercial control. The steps below break down that workflow, showing how disciplined handling keeps clarifications contained, traceable, and aligned with contract obligations before they impact cost or programme.

1. Issue And Document the ASI

   The architect identifies the need for an ASI through Technical Queries, site observations, or design reviews. They then prepare the instruction using the standard form, which includes project details, references to the affected documents, a clear written clarification, and any required attachments.
   
   Next, the ASI is signed, dated, and assigned a unique sequential number. This documentation process creates the audit trail required for contract administration, closeout, and dispute resolution.
   
   Digital construction platforms support this step by auto-populating project data, linking each ASI to current drawings and Technical Queries, and maintaining a sequential register that keeps records consistent and complete.

2. Communicate the ASI to the Project Team

   Once issued, the architect distributes the ASI to the head contractor, relevant subcontractors, the owner’s representative, and the project manager.
   
   Each party must acknowledge receipt and confirm understanding before the affected work begins. The team then updates the document register and drawing set so the clarification is available on site.
   
   For example, when an ASI updates a hardware finish, the architect issues the instruction, and the contractor forwards it to the supplier and the installing subcontractor, so ordering and installation reflect the clarified specification.
   
   Clear communication at this stage reduces rework, which can account for 10-15% of contract value in building projects, with poor communication identified as a major contributor.

3. Verify and Implement the ASI On Site

   Before applying the ASI, the contractor confirms that the affected work has not commenced.
   
   If work has started, the contractor notifies the architect and client and requests a variation instead of applying the ASI. If the ASI is considered valid, the contractor updates site drawings and work plans, and trades follow the clarified instructions.
   
   Site supervision then verifies compliance so the work aligns with the updated documents.
   Digital project management tools reinforce this step by providing current drawings on mobile devices and generating timestamped photo records that confirm work status at the time the ASI was received.

4. Update Progress Claims and Records

   After the ASI is implemented, the contractor updates payment descriptions and aligns claims with the clarified specification to prevent processing delays.
   
   The ASI is stored with the project records and included in the as-built documentation, supporting facility management, warranties, and future works.
   
   For example, if a progress claim lists the original paving stone size after an ASI changed the specification, the claim may be held until the description is corrected, delaying payment.

How Teams Manage ASIs for Better Project Performance

Systematic ASI management enhances commercial outcomes by preventing documentation gaps, reducing rework, shortening payment cycles, and creating defensible records in the event of disputes.

Mature teams treat ASIs as a core part of contract administration and escalate to variations as soon as any cost or time exposure is identified.

Establish Clear Governance and Issuance Protocols

Teams must formalise who is authorised to issue ASIs, typically the architect of record, and document these permissions in the project execution plan. Clear authority reduces informal directions on-site and ensures every clarification flows through the correct channel.

Each ASI must meet strict content requirements.

This includes supporting attachments, references to relevant documents, and a clear written description, making the instruction complete, traceable, and contractually enforceable. Acknowledgement rules, such as confirmation within 48 hours, create a verified audit trail.

Well-defined escalation rules are essential. Any indication of cost, sequencing impact, or rework should automatically trigger a variation review, rather than relying on informal judgment by site personnel.

Assign Operational Ownership Across the Delivery Chain

Effective ASI control depends on disciplined coordination across design, commercial, and site teams. The architect issues ASIs and confirms each instruction aligns with approved documents and statutory obligations.

The project manager oversees distribution, monitors status, and coordinates between design, commercial, and delivery teams. The head contractor implements the instruction, confirms that work has not commenced, and escalates the issue as soon as a potential impact is identified.

Meanwhile, the owner’s representative tracks broader implications for project objectives, contract compliance, and the overall programme of works.

Maintain a Single Source of Truth for All ASIs

A centralised digital log provides the backbone of ASI management. It records status, dates, attachments, cross-references, and acknowledgments to maintain full traceability.

Site teams, subcontractors, and consultants must work from the current instruction set to prevent rework and ensure payment alignment. Every ASI should connect directly to drawings, specifications, Technical Queries, and related variations to maintain a continuous record of design intent. 

Strong document control prevents parallel versions and fragmented communication, both of which remain leading contributors to rework across Australian projects.

Integrate ASIs With Commercial and Field Workflows

ASI management should extend to commercial and field processes so downstream activities reflect the clarified instructions. Linking ASIs to change events, submittals, procurement actions, inspections, and progress claims keeps delivery aligned with design intent.

When an ASI resolves a Technical Query, the platform should link the two documents automatically and prompt a variation review when the contractor identifies a potential cost impact.

Any ASI affecting materials, installation requirements, or sequencing must be reviewed immediately for commercial exposure. Integrating these requirements into subcontractor engagement documents ensures trade partners work from current information.

Apply Consistent Operational Discipline On Site

Operational discipline governs how ASIs are implemented on site. The architect of record must issue all ASIs, and the contractor must acknowledge receipt and confirm work status within 48 hours.

The project team distributes the instructions to the relevant trades, verifies that they align with the project intent, and updates the drawings before work proceeds. Site supervision confirms implementation and records compliance as part of standard inspection workflows. 

Payment claims and cost coding must reflect ASI-driven changes to avoid holds and financial discrepancies at month's end.

Use Predictive Tools, AI, and Analytics to Identify Impact Early

Modern platforms analyse ASI content for cost and time indicators, such as additional materials, resequencing requirements, or expedited procurement. Automated alerts notify the architect and project manager when an ASI may require conversion to a variation.

Analytics also highlight patterns, such as repeated ASIs in the same discipline, which can signal design coordination issues that need structured resolution. Dashboards give leadership visibility into ASI volume, cycle time, and downstream impact across the project portfolio.

Harness the Digital Transformation Advantage

Connected construction platforms maintain live ASI dashboards showing issued instructions, related documents, status, and outstanding actions. Real-time distribution ensures that subcontractors have access to updated drawings in the field, rather than relying on outdated information.

AI-powered scanning identifies potential cost or scheduling risks within ASI content before the instruction reaches the site, enabling faster and more informed decision-making.

With all teams operating from one source of truth, disputes reduce, and monthly payment cycles move faster, strengthening commercial performance across the project.

Rigorous ASI workflows protect margin and reduce disputes

When teams apply Architects’ Supplemental Instructions correctly, they preserve scope, protect cost recovery, and reduce the contractual risk associated with unclear design intent. Strong governance, accurate documentation, and integrated digital workflows ensure ASIs support successful project delivery rather than disrupt it.

Written by

Josh Krissansen

63 articles

Josh Krissansen is a freelance writer with two years of experience contributing to Procore's educational library. He specialises in transforming complex construction concepts into clear, actionable insights for professionals in the industry.

View profile