Millwork RFIs and Change Orders: How to Manage Scope Changes Without Losing Your Schedule

No commercial construction project is completed exactly as originally drawn. Dimensions don't match field conditions. Owners change finishes. Engineers issue drawing revisions. Architects clarify specifications in ways that add scope. Each of these situations generates paperwork — RFIs, change orders, ASIs, or some combination — and how a millwork contractor manages that paperwork is how they protect their contract position when disputes arise at the end of a project.

Understanding the formal mechanisms for managing changes isn't just administrative overhead. It's the difference between getting paid for extra work and absorbing costs that were never in your bid. Our millwork shop drawing services include revision tracking and revision cloud documentation on every submittal cycle.

What an RFI Is — and What It Isn't

An RFI (Request for Information) is a formal written inquiry from a contractor to the architect or GC requesting clarification on the contract documents. RFIs are not casual questions sent by email. They are numbered, logged, formally submitted, and responded to in writing. The RFI and its response become part of the contract record.

On commercial projects, RFIs are submitted by the millwork sub to the GC. The GC logs the RFI (assigns it a number, adds it to the RFI log), forwards it to the architect, receives the architect's written response, and returns it to the submitting sub. This chain creates a paper trail that documents both the question and the answer — critical if the answer turns out to be wrong or if a dispute arises later about what was authorized.

What an RFI is not: a substitution request, a change order request, or a notice of claim. An RFI asks for clarification on existing contract documents — it doesn't propose changes to scope, and it doesn't request additional compensation. Those require different formal mechanisms.

When to Write an RFI on a Millwork Project

Common situations that warrant an RFI on a millwork project:

• Specification conflicts: The spec calls for AWI Premium grade on a component that appears in a detail as Economy construction. The two documents conflict — which governs?
• Missing information: The drawings show a custom molding profile without a detail or a profile reference. The spec doesn't specify it either. You can't produce the molding without knowing the profile.
• Dimension discrepancies: The plan view shows a cabinet run at 12'-6", but the elevations dimension individual cabinets that add up to 12'-3". Which is correct?
• Field condition conflicts: The drawing shows millwork in a location where a structural element, duct, or pipe is actually located. The drawing can't be built as drawn.
• Spec silence on required information: The spec references a "hardware schedule" that doesn't exist anywhere in the contract documents. What hardware is required?
• Code compliance questions: You believe the specified counter height conflicts with ADA requirements. Before drawing it to spec and risking a failed inspection, get written confirmation of the intended design.

The rule for deciding whether to write an RFI: if you have to make an assumption to proceed, write an RFI instead. Assumptions on commercial projects are expensive when they turn out to be wrong.

How to Write a Clear RFI

An effective RFI gets a useful answer quickly. An ineffective RFI gets a vague response or gets kicked back as "not clearly stated." The format matters.

Every RFI should include:

• A clear subject line: "RFI #014 — Cabinet height at Room 112 conflicts with duct per M-101"
• References to the specific drawings and specs in question: "Per architectural drawing A-401, base cabinets in Room 112 are noted at 36" AFF. Per MEP drawing M-101, duct DF-12 runs at 34.5" AFF in the same location."
• A concise statement of the conflict or missing information: "The cabinet height and duct height conflict. The cabinet cannot be installed at the specified height without cutting into the existing duct."
• A proposed solution (optional but recommended): "We propose reducing cabinet height to 34" AFF at this location to avoid the duct. Please confirm."
• A response requested by date: Include a date that accounts for your fabrication schedule. "Response requested by [date] to maintain drawing approval schedule."

RFIs that reference specific drawing sheet numbers, detail callouts, and spec section numbers get responded to faster than RFIs that describe a problem vaguely. Architects and GCs receive many RFIs per project — the clearer yours is, the faster it gets resolved. Well-structured shop drawings reduce RFI volume significantly; see our drawing rates for commercial millwork packages.

Change Orders, PCOs, and ASIs — Knowing the Difference

Changes to the contract scope follow a formal process involving several distinct documents. Using the wrong document for a given situation creates confusion and can delay compensation.

ASI (Architect's Supplemental Instruction) is issued by the architect to clarify, correct, or supplement the contract documents without changing the contract sum or time. An ASI might clarify a finish color, correct a dimension that was obviously a drafting error, or provide a missing detail. The critical word is "supplement" — an ASI is not supposed to add scope or cost. If you receive an ASI that you believe adds scope, respond in writing that you're reviewing it for cost and schedule impact before proceeding.

PR (Proposal Request) is the architect's formal request for pricing on a potential scope change before committing to it. The owner wants to know what it costs before approving the change. You respond to a PR with a written price proposal. The PR + your proposal become the basis for a change order, but neither is a direction to proceed.

PCO (Potential Change Order) is an internal document used by contractors to track identified scope changes before they're formally incorporated into a signed change order. When you identify work that isn't in your contract — or receive an RFI response that requires extra work — you log a PCO with the estimated cost and schedule impact. PCOs are the raw material for change orders. Tracking them systematically prevents changes from getting lost in the project history.

CO (Change Order) is the formal, signed amendment to the contract that authorizes additional scope and adjusts the contract sum and/or schedule. Both parties must sign a change order before it's effective. Work performed under a CCD (see below) before a CO is signed creates a disputed scope situation that often ends in litigation.

CCD (Construction Change Directive) is the GC's or owner's written direction to proceed with a change before a price has been agreed. CCDs are used when the project schedule can't wait for CO negotiations. Complying with a CCD without reserving your rights to additional compensation for the disputed scope is one of the most common ways millwork contractors lose money on commercial projects. When you receive a CCD, acknowledge receipt in writing, state that you're proceeding under protest pending CO negotiations, and document your time and materials carefully.

How Shop Drawing Revisions Connect to RFIs and Change Orders

Every revision to an approved shop drawing is a potential scope event. When an RFI response requires a design change, or when the architect issues an ASI that modifies the approved millwork, the shop drawings must be revised and resubmitted for re-approval. The revision itself takes time and may require changes to fabrication if work has already started.

The connection between revisions and compensation works like this:

• Revision to correct a drafting error by the drafter: Not compensable. Your cost to fix your own mistake.
• Revision required by an architect's review comment that addresses a compliance issue: Generally not compensable if the original drawing didn't meet the spec.
• Revision required by an ASI that changes the design after approval: Potentially compensable if the ASI adds work or requires fabrication changes. Log a PCO immediately.
• Revision required because field conditions differ from the drawings: Potentially compensable if the field condition was the GC's or another trade's responsibility to report. Requires RFI documentation to establish who was responsible for the discrepancy.

When revising approved shop drawings for any reason, use revision clouds and delta markers consistently. Each revision cycle must be clearly identified (Revision 1, Revision 2) so the reviewer can immediately see what changed. Clear revision documentation also protects you in a dispute — it creates a record of exactly what changed and when. For the baseline on what well-formatted shop drawings look like before revisions start, see our millwork shop drawing checklist.

Schedule Impact Documentation

Most change order disputes focus on cost. But schedule impact is often where the real loss is. If a scope change delays your fabrication start, pushes your installation date, or requires expedited delivery to maintain the GC's schedule, those costs need to be documented and claimed.

To support a schedule impact claim, you need:

• Your original production schedule, showing when fabrication was planned to start and finish
• Documentation of when the change event occurred (date of RFI response, ASI receipt, or CCD)
• Your revised schedule showing the impact of the change
• The critical path through your fabrication and installation — not all delays affect the critical path, and only critical path delays are typically compensable

If you don't maintain and update a production schedule throughout the project, documenting schedule impact becomes nearly impossible. A simple spreadsheet tracking drawing, approval, fabrication, and installation milestones for each millwork area is sufficient — it doesn't need to be a formal CPM schedule.

Value Engineering — Scope Reduction as a Change Order

Value engineering (VE) proposals are cost reductions offered by the contractor in exchange for a reduction in the contract price. They're initiated by the contractor and require owner/architect approval. Common VE proposals on millwork: substituting a less expensive substrate, simplifying a molding profile, reducing door construction from frame-and-panel to slab, or changing a specified hardware item to a less expensive approved equal.

If VE is accepted, the result is a credit change order — a negative change order reducing your contract price. Confirm in the CO exactly what scope has been changed and what the credit amount is. Do not proceed with VE substitutions without a signed CO — performing VE work without written approval and then presenting a credit at the end of the project creates disputes about what was actually agreed.

Protecting Your Position at Project Closeout

Change order disputes tend to surface at project closeout when the GC is reconciling the contract and comparing claimed COs against approved COs. By that point, all the work has been done. Your only protection is documentation — a complete CO log showing every change event, every PCO, every CCD, and every signed CO, matched against your actual costs.

Shops that manage this documentation in real time throughout the project close out with accurate final contract values. Shops that reconstruct it at the end spend weeks in disputes over changes that were never formally authorized. The administrative cost of maintaining a CO log on a live project is a fraction of the cost of fighting for uncompensated work at closeout.

For more on the formal submittal process that governs the baseline approval of shop drawings before changes start, see our millwork submittal process guide. For the specific reasons submittals get rejected and require costly revision cycles, our submittal rejection guide covers the most common failure points.