RFI vs. ASI vs. Bulletin vs. Change Order: How Construction Document Changes Differ

RFI vs. ASI vs. Bulletin vs. Change Order: The Difference

RFIs, ASIs, bulletins, and change orders are the four documents general contractors, architects, and owners use to manage anything the signed drawings and specs don't already settle. Project managers confuse them constantly, and that confusion is expensive: someone starts pricing a bulletin as if it's already approved, or a superintendent installs work off an ASI that quietly changed the schedule.

Each document has a different direction of travel, a different legal weight, and a different effect on cost and schedule. Get the wrong one and you either do unpaid work or wait weeks for an approval you didn't need.

What Is an RFI, and When Do You Use One?

A Request for Information (RFI) is a formal question the contractor sends to the architect or engineer when the drawings or specs are unclear, missing a detail, or contradict each other. The RFI doesn't authorize extra work, doesn't commit either party to a cost, and doesn't modify the contract on its own. It's a question, nothing more.

A subcontractor hits a duct that isn't shown on the structural plan. The GC files an RFI asking how to route around it. The architect answers, and depending on the answer, the project either continues unchanged or the RFI response gets formalized into an ASI or a bulletin. Filing an RFI that's specific enough to get a fast, useful answer matters here: vague RFIs bounce back with clarifying questions and burn days off the schedule. Helonic's RFI drafting tools pull the sheet number, detail reference, and conflict description straight from a flagged drawing issue, so the question is unambiguous the first time it's sent. Once an RFI is filed, tracking its status and response time is what keeps it from quietly becoming the reason a milestone slips.

What Is an ASI, and When Do You Use One?

An Architect's Supplemental Instruction (ASI) is a directive from the architect to the contractor, the reverse direction of an RFI. It provides additional detail within the existing scope, or makes a minor change that, in the architect's judgment, will not adjust the contract sum or the contract time.

An ASI often closes out an RFI. The contractor asked how to route the duct; the architect issues an ASI with a revised detail showing exactly how. Because an ASI can't touch cost or schedule by definition, it should only be issued before the affected work has started. Once material is ordered or work is installed, the same clarification usually has to move through a bulletin and change order instead, because now there's a real cost to account for. For the full mechanics of who can issue one and what it can and can't authorize, see what an ASI covers and where its limits are.

What Is a Bulletin, and When Do You Use One?

A bulletin is a package of revised drawings and specs the architect issues after the contract is signed, asking the contractor to price a change. Bulletins show up when a scope change is bigger than an ASI can cover: an owner wants a different finish package, a discovered condition forces a redesign, or a code review kicks back a detail that needs rework.

The bulletin itself isn't binding. It's a request for a number. The contractor prices the labor, material, and schedule impact and submits a proposal back to the architect and owner. Nothing about the contract changes until that proposal is accepted and converted into a signed change order. Teams that skip this distinction, and start ordering material or scheduling crews off an unpriced bulletin, are the ones who end up in payment disputes when the final number comes back higher than expected.

What Is a Change Order, and When Do You Use One?

A change order is the written, signed agreement that formally adjusts the contract sum, the contract time, or both. Under AIA A201-style general conditions, a change order requires signatures from the owner, the contractor, and the architect before it takes effect. That three-party signature is the line between a change that's been discussed and a change that's actually enforceable.

A change order usually starts life as a priced bulletin. Once the owner accepts the contractor's proposal, the architect issues the change order documenting the revised scope, the dollar adjustment, and any change to the completion date. For the full pricing and negotiation workflow, see the construction change order guide. Read AIA's own guidance on change order fundamentals for how A201 defines the instrument and where a Construction Change Directive fits in when the owner needs work to proceed before pricing is finalized.

RFI vs. ASI vs. Bulletin vs. Change Order: Comparison Table

Side by side, the four documents separate cleanly by who issues them and whether they're binding:

Which Document Do You Actually Need?

Match the document to what's actually happening on the project, not to what the last superintendent called it:

• You have a question about the drawings or specs: file an RFI. You're not proposing anything, you're asking for clarification.
• The architect answered with a clarification or minor fix, no cost involved: expect an ASI. If the answer touches money or the schedule, an ASI is the wrong instrument.
• The scope change is bigger, or the answer does affect cost or time: expect a bulletin. Price it before you act on it.
• The price and schedule impact are agreed and need to be locked in: that's a change order. Nothing is enforceable, and no one is entitled to payment, until all three parties sign.

Most of this confusion traces back to the same root cause: a drawing set with gaps or conflicts generates the RFI in the first place. Fewer coordination errors at the drawing stage means fewer RFIs, fewer ASIs, and fewer bulletins competing for attention mid-schedule. Teams working to cut the number of RFIs a project generates usually start there rather than trying to process each one faster.