Construction RFI Process Flow Chart: Contents, Timeframes, Closeout

The construction RFI process flow runs in two directions along the same chain: a field-level question travels from subcontractor to general contractor to architect (with consulting engineers looped in when needed), and the written answer travels back down to the crew doing the work. Each handoff is documented, each step has a gatekeeper, and the resolution eventually gets recorded on the drawings. On a typical project this cycle repeats hundreds of times; one study of over 1,300 projects found an average of roughly 800 RFIs per project.¹

The Chain From Field to Design Team and Back

Most RFIs start with the people doing the physical work. A subcontractor installing ductwork notices a beam where the drawings show open space. A framing crew finds two detail sheets that contradict each other. These field-level workers draft the initial question because they are closest to the conflict between the plans and the actual conditions.

The general contractor sits in the middle and acts as the first gatekeeper. Before forwarding anything to the design team, the GC checks whether the answer already exists somewhere in the contract documents. Under AIA A201-2017, the contractor has an obligation to carefully study and compare the drawings, specifications, and field conditions before requesting information from the architect.² That screening filters out questions the contractor’s own team should have caught and prevents the architect from drowning in redundant inquiries.

ConsensusDocs 200 imposes a parallel duty. The constructor must examine drawings and specifications and report errors, omissions, or inconsistencies to the owner, who then provides direction.³ The workflow is fundamentally the same: the party building the project does its homework before asking the design team for answers.

Once the GC confirms the question is legitimate, it goes to the architect of record. The architect holds the contractual authority to interpret the design intent and decide performance questions. AIA A201 Section 4.2.12 requires those interpretations to be consistent with the intent of the contract documents, in writing, and rendered impartially.² If the question involves structural loading, mechanical systems, or another specialty, the architect routes it to the relevant consulting engineer. The consultant’s answer goes back to the architect, who reviews it for consistency with the overall design before issuing a formal response. On projects where the resolution triggers a budget change, the owner gets involved to approve the financial adjustment before work proceeds.

Most projects today route these handoffs through cloud-based project management platforms like Procore or Autodesk Build. The software timestamps every step, which becomes important if anyone later disputes how long a response took. The response then descends the same chain: architect to GC, GC to subcontractor, subcontractor to the crew doing the work.

Where Subcontractors Fit In

Subcontractors rarely have a direct contract with the architect or owner. Their RFI obligations flow down from the general contractor’s prime contract, so the specific procedures that bind a subcontractor depend on how the prime contract’s RFI provisions are incorporated into the subcontract.

One trap catches subcontractors constantly: the verbal “just get it done” directive. A superintendent tells a sub to proceed with a workaround and promises the paperwork will be sorted out later. If a dispute arises, a court may find that the GC waived the written-authorization requirement by directing the work orally, even if the prime contract demands written change orders. The safer move is to insist on a written directive before performing out-of-scope work.

What a Complete RFI Contains

A vague or incomplete RFI gets bounced back at the GC’s desk or the architect’s, which resets the clock and pushes the answer further out. AIA Document G716-2004 is the most commonly used standardized RFI template, and its fields describe what every RFI should include:⁴

Project name and a sequential RFI number that keeps the log organized and makes cross-referencing straightforward.
Issue date and requested reply date. The reply date signals urgency and ties into the project schedule.
References and attachments. Specific drawing sheets, specification sections, or other documents the sender reviewed while trying to find the answer. Citing “Drawing A-101, Detail 3” or “Specification Section 03 30 00” tells the architect exactly where to look.
A concise description of the conflict, ambiguity, or missing information. The form instructs the sender to “fully describe the question or type of information requested.”
The sender’s recommendation, including any cost or schedule considerations. This field speeds up review because the architect can approve, modify, or reject a concrete suggestion rather than draft one from scratch.
Space for the receiver’s written reply, with signature and date fields that create the formal record.

If the contractor expects the resolution to affect cost or schedule, the RFI should flag that impact up front. Marking it clearly lets the project manager prioritize urgent requests over questions that can wait.

Response Timeframes

AIA A201-2017 does not set a fixed number of days. Section 4.2.14 requires the architect to respond “within any time limits agreed upon or otherwise with reasonable promptness.”² The phrase “any time limits agreed upon” means the parties can negotiate a specific turnaround period and write it into their contract.

In practice, most project teams negotiate an RFI response window during contract formation. Seven to fourteen calendar days is a common negotiated range, but it varies by project size and complexity, and some owners push for shorter windows on fast-track schedules. What matters legally is whatever the contract actually says. If the contract is silent, the “reasonable promptness” standard applies, which is subjective enough to fuel plenty of disputes.

ConsensusDocs 200 takes a slightly different approach. Under Section 14.2.2, the owner’s clarification on omissions or errors is “final and binding on all Parties,” though the constructor may be entitled to an equitable adjustment in time or price.³

An RFI Is Not a Change Order

This is where projects go sideways. An RFI asks a question. It does not authorize changes to the contract price or the project schedule. If the architect’s response reveals that additional work is needed, a separate change order must follow before anyone can bill for that work or claim extra time.

AIA A201 draws this line explicitly. Section 3.2.4 states that if the contractor believes additional cost or time is involved because of the architect’s clarifications or instructions issued in response to an RFI, the contractor must submit a formal claim under Article 15.² The claim triggers a separate process with its own notice requirements and deadlines. Skipping that step and just doing the work usually means eating the cost.

The same logic separates RFIs from submittals. A submittal sends product data, shop drawings, or material samples to the architect for approval. An RFI asks about the design intent when something is unclear. Using the wrong document for the wrong purpose wastes review time and delays both processes.

Why RFIs Get Rejected

A returned RFI resets the process. The most frequent reasons for rejection are avoidable at the GC’s screening step:

The answer is already in the contract documents. If a specification or a drawing note addresses the question, the architect will send it back.
The question is really a submittal. Product data, shop drawing approvals, and material substitutions belong in the submittal process.
The question is about means and methods. Sequencing concrete pours, scaffolding choices, and delivery staging are the contractor’s responsibility. Architects interpret design intent; they do not direct construction methods.
Insufficient detail. An RFI that says “please clarify the wall detail” without a specific drawing reference, a location, or a photograph gives the architect nothing to work with.

When You Disagree With the Response

An architect’s RFI response is not the final word if the contractor believes it changes the scope of work or imposes additional cost. Under AIA A201-2017, the path forward is a written claim under Article 15, filed within the contract’s notice deadline. Missing that window can forfeit the right to seek additional compensation or a time extension entirely.

Under ConsensusDocs 200, the owner’s clarification is binding, but the constructor is entitled to an equitable adjustment if the clarification changes the work.³ The key difference: under ConsensusDocs, the constructor generally must proceed with the work as directed while the equitable adjustment is resolved.

In either framework, the practical steps are the same. Comply with the response, document the objection in writing immediately, and follow whatever claim procedure the contract specifies. Do not ignore the response, and do not perform the work without preserving your rights.

When a slow or missing response holds up the work, a delay claim may be available for additional time, extended overhead, or both. The right to that claim usually depends on whether the contractor delivered a written notice of delay within the deadline set by the contract. A notice of delay is not itself a claim; it is the initial notification that grounds for a potential claim exist, and the actual claim follows with supporting documentation, a schedule analysis, and a cost breakdown. The strength of any delay argument depends almost entirely on the timestamps in the RFI log.

Closing Out an RFI

When a response comes back, the general contractor marks the RFI as resolved in the project management system and distributes the answer to every field supervisor and crew affected by the clarification. This step gets skipped more often than it should. An answered RFI that never reaches the foreman installing the work is no better than an unanswered one.

The technical details from the response must also be recorded on the working set of drawings. This typically means redlining the affected sheet with the RFI number, the date of the change, and a brief description of what changed. Those marked-up drawings become the source material for the final as-built set.

Accurate as-built drawings serve as the permanent record of what was actually constructed, as opposed to what was originally designed. They are typically required for obtaining a certificate of occupancy, closing out construction financing, and handling future renovations or maintenance. An as-built set that fails to incorporate RFI responses creates a gap between the documented building and the real one, and that gap causes problems years later when someone opens a wall expecting to find what the drawings show.

The RFI log itself should be archived as part of the project closeout documents. In the event of a warranty claim, a latent defect dispute, or a future renovation, that log provides the documented history of every design clarification made during construction.

1
ASC Online. Request for Information (RFI) and Rework
2
AIA. AIA Document A201-2017 General Conditions of the Contract for Construction
3
ConsensusDocs. ConsensusDocs 200 Standard Agreement and General Conditions Between Owner and Constructor
4
AIA. AIA Document G716-2004 Request for Information