Table of Contents Show
An RFI in construction is a formal written request used to clarify missing, unclear, or conflicting information in the contract documents before work continues. A contractor usually raises one, and the architect or engineer named in the contract answers in writing. A well run RFI process keeps the project moving and builds a reliable record of every decision.
For architects, RFIs are a routine part of construction administration, and the way you handle them shapes schedule, cost, and your relationship with the contractor. Most start as a simple question. A poorly managed one can stall a crew or grow into a claim. This guide covers what an RFI is, how the process runs, how it differs from submittals and change orders, and how to answer one without slowing the job.
What Is an RFI in Construction?
An RFI in construction, short for request for information, is a formal written question that clarifies unclear, missing, or conflicting details in the contract documents. A contractor or subcontractor usually raises it, and the architect or engineer of record responds in writing so the team can proceed with a documented answer.
RFI stands for request for information, and the tool exists because no drawing set is ever perfect. A dimension goes missing, two sheets disagree, a specification is silent, or a field condition does not match the plans. Rather than guessing, the party doing the work asks a specific question and receives a written direction that becomes part of the project record. As Wikipedia’s overview of requests for information notes, an RFI is used in construction when the documentation lacks information required to proceed with a given scope of work.
Most RFIs fall into a few familiar groups: design clarifications, requests to substitute a material, questions about a constructability issue, or coordination gaps between disciplines. Whatever the trigger, the goal is the same, to close an information gap before it turns into rework in the field.
How Does the RFI Process Work?
The RFI process runs as a short, documented loop. Someone identifies a gap, the general contractor checks that the answer is not already in the documents, a written RFI is logged and sent to the design team, the architect reviews and responds, and the answer is recorded before work continues.
In practice, the requester drafts the RFI with a clear question and, ideally, a proposed solution. The general contractor reviews it first to filter out questions already answered in the plans, then routes it to the architect, often through the construction manager or owner’s representative. The architect coordinates with structural, mechanical, or electrical consultants when needed, issues a written response, and the RFI is marked closed in the log. If the answer changes scope, cost, or schedule, that shift moves to the change order process instead.
📐 Technical Note
In most projects, the rules for submitting and answering RFIs live in Division 01, the General Requirements section of the specifications written under the CSI MasterFormat system. Division 01 is also where required response times are set, often 7 to 10 calendar days. Reading it at the start of a project tells you exactly how the RFI process will run before the first question arrives.
On larger jobs the volume adds up fast, so teams track everything in a shared log or a cloud platform. Coordinated models help here too, and several BIM collaboration platforms let architects, engineers, and contractors flag and resolve issues before they reach the field.
RFI vs Submittal vs Change Order
Architects handle three construction-phase instruments that are easy to mix up, and knowing which one applies keeps the paper trail clean. Each does a different job in the flow of a project.
How an RFI, Submittal, and Change Order Compare
The table below sums up the practical differences.
| Aspect | RFI | Submittal | Change Order |
|---|---|---|---|
| Purpose | Clarify unclear or missing information | Prove a product or assembly meets the specifications | Formalize a change to cost, scope, or time |
| Who initiates | Contractor or subcontractor | Contractor, through subs and suppliers | Owner, architect, or contractor |
| Who responds | Architect or engineer of record | Architect or engineer of record | Owner approves, architect prepares |
| Changes the contract | No | No | Yes |
| Typical timeframe | About 7 to 10 days | Set by the submittal schedule | Varies by negotiation |
| Common trigger | A gap or conflict in the drawings | A specified product ready for review | An answer or field change affecting cost or time |
The line that matters most runs between an RFI and a change order. An RFI asks what the documents already intend. A change order alters the contract. Confusing the two is where projects get into trouble.
⚠️ Common Mistake to Avoid
A frequent and expensive mistake is treating an RFI as a way to approve a change in scope, cost, or schedule. An RFI clarifies what the contract documents already intend. It does not change the contract. When an answer does affect cost or time, that belongs in a formal change order, not tucked into an RFI response, where it muddies the record if a dispute follows.
Submittals sit in their own lane. When the contractor sends product data or shop drawings to prove a product meets the specifications, that is a submittal review, one of the coordination duties architects and engineers share on nearly every job.
The Cost and Risk Behind Every RFI
Every RFI in construction carries a cost, even the ones that look routine. A widely cited 2013 study by the Navigant Construction Forum, which reviewed more than 1,300 projects containing over a million RFIs, put the average cost to review and answer a single RFI at about $1,080, with a median response time close to 10 days. The same research found roughly 10 RFIs for every $1 million of construction value, so the totals climb quickly on any sizable project.
📌 Did You Know?
The Navigant Construction Forum found that about 22% of all RFIs across the projects it studied were never answered. Unanswered RFIs are one of the clearest early signs that a project is drifting toward a dispute, often because no formal procedure was in place to track and close them.
The risk to your firm is not only time. A slow or unclear response can put you on the wrong end of a delay claim, and a thin paper trail rarely helps when a dispute lands. Keeping a clean RFI and submittal record is part of managing that exposure, which is one reason experienced architects treat documentation as seriously as design.
How Architects Can Handle RFIs Better
Handling an RFI in construction well comes down to speed, clarity, and a clean record. You cannot prevent every question, but you can shape how smoothly the answers flow.
💡 Pro Tip
When you answer an RFI, point directly to the sheet, detail, or specification section that supports your response instead of only giving an instruction. On well run projects, architects restate the question, cite the exact document reference, and give a clear direction in as few words as possible. This keeps the answer defensible later and cuts the back and forth that turns one RFI into three.
A few habits make the difference. Answer within the timeframe your contract sets, even if the reply is a short holding response. Point to the exact sheet or specification section that supports your direction. Resist the pull to solve a problem that belongs in a change order. And keep the log current, since unanswered RFIs are the ones that tend to come back as claims.
The deeper fix is upstream. Many RFIs trace back to gaps or conflicts in the drawings that better coordination would have caught, a skill that many architecture programs underteach. Tightening your documents, running clash checks, and coordinating disciplines early cuts the number of questions that reach the field at all. The response duties themselves are spelled out in the AIA A201 general conditions that govern many projects, so reading that language before construction starts helps you answer with confidence.
Cost figures cited here come from industry research and vary widely by project size, region, and market conditions. RFI procedures and response duties differ by contract and jurisdiction, so always follow your project’s specific contract documents and confirm requirements with a licensed professional or attorney.
Frequently Asked Questions
What does RFI stand for in construction?
RFI stands for request for information. It is a formal written question used during a project to clarify unclear, missing, or conflicting details in the contract documents so work can continue with a documented answer.
Who answers an RFI in construction?
The design professional named in the contract, usually the architect or engineer of record, answers the RFI. On many projects it is routed through the construction manager or owner’s representative, and the architect coordinates with consultants when the question involves structural, mechanical, or electrical work.
What is the difference between an RFI and a submittal?
An RFI asks a question to clarify intent. A submittal sends product data, shop drawings, or samples for review against the specifications. If you are missing information, that is an RFI. If you are proving that a product conforms, that is a submittal.
How long does an architect have to answer an RFI?
The timeframe is set by the contract and the project specifications, commonly 7 to 10 calendar days, with urgent field questions sometimes answered faster. Research from the Navigant Construction Forum found the industry median response time is close to 10 days.
Leave a comment