An RFI in construction is a formal written request from the contractor to the architect or engineer, asking for clarification when the drawings and specifications do not answer a question raised on site. It creates a dated record of the question, the response, and any cost or schedule effect that follows from it.
Most architecture students first meet the term during an internship, as a PDF that lands in the inbox with a deadline attached. What sits behind it is one of the faster ways to read a project.
Why RFIs Exist at All
No set of construction documents is finished in the sense that every site condition has been drawn. Drawings are produced at a resolution that suits design intent and pricing, not the resolution of a fabricator standing in front of a wall. That gap is where a request for information lives.
The RFI closes that gap in writing rather than in a hallway conversation. A verbal answer from an architect who happens to be on site carries no record and no contractual weight.
🎓 Expert Insight
"Many jurists, almost all jurors and unsophisticated arbitrators and mediators [have] the faulty impression that every design detail of a construction project has been thoroughly planned... before the project is bid. This is never the actual case."
Navigant Construction Forum, Impact and Control of RFIs on Construction Projects, 2013
RFIs are not proof that a design team failed. They are the cost of turning drawings into a building.
What Causes an RFI in Construction?
Four situations produce most of a log.
- Drawing and specification conflict. The plan calls for one product and Division 09 calls for another, and somebody has to decide which governs.
- Missing or under-resolved detail. A parapet meets a curtain wall head at an angle nobody drew, and a dimension is needed before flashing is ordered.
- Site condition differs from the documents. Existing grade sits 200 mm below the survey, or a slab edge was poured out of tolerance. Renovation work generates these constantly.
- Material availability. The specified brick has a 22 week lead time, so the contractor asks whether a named substitute is acceptable.
Coordination done before construction cuts volume. Running clash detection in BIM catches the duct passing through a beam months before a foreman does, and a well built set of architectural detail drawings removes a class of dimensional questions.
📌 Did You Know?
A case study of 1,484 RFIs on one building project, published by Shim, Carter and Kim in the 52nd Associated Schools of Construction conference proceedings (2016), found 636 of them, roughly 43 percent, logged as confirmation only. Nearly half the log existed to put an understood answer on the record.
RFI vs Submittal vs Change Order
These three get confused constantly, including by people in practice for years. An RFI asks what the documents mean. A submittal proves what the contractor will install. A change order alters the contract price or time.
How the Three Documents Compare
| Aspect | RFI | Submittal | Change Order |
|---|---|---|---|
| Core purpose | Clarify conflicting documents | Confirm products, samples, shop drawings | Adjust contract sum or schedule |
| Who starts it | Contractor, occasionally owner | Contractor and subcontractors | Owner, on architect recommendation |
| Architect action | Interpret the documents in writing | Review against design intent | Certify scope, cost and time |
| Changes the contract | No, unless the answer adds scope | No | Yes, by definition |
How the RFI Process Works, Step by Step
- A subcontractor hits a question on site and raises it with the general contractor, who screens it against the documents first.
- The contractor issues it through the project platform with a number, a date, drawing and specification references, and a requested response date.
- The architect logs it and routes any consultant portion to the relevant engineer.
- The architect issues a written interpretation. Under AIA Document A201, 2017 edition, still the current version, section 4.2.11 makes that response due within agreed time limits or otherwise with reasonable promptness so as not to delay the project.
- If the answer carries cost or time, a change proposal follows. Penn State's construction procedure shows the branch: the designer's response either triggers a bulletin or feeds into a potential change order process.
Most specifications set a five to ten working day response window. In the Associated Schools of Construction case study cited above, the average response ran 11.5 business days against a five day requirement, and about 62 percent of the 1,484 items came back late.
💡 Pro Tip
Answer the easy ones the same day. Clearing confirmation only items within hours buys credibility for the two or three hard questions that need a week and a consultant. Letting simple items sit is how a design team gets named in a delay claim it had nothing to do with.
What a Well Written RFI Looks Like
The quality of the question shapes the speed of the answer. A strong RFI holds one question per RFI and nothing else, so the log stays sortable and no half answered item hides inside a long response.
It cites the exact sheet number, detail reference and specification section rather than pointing at an area of the building. It states the field condition plainly, with a photograph or marked up sketch, and proposes a solution, which lets the architect confirm or redirect instead of designing under pressure. It carries a date and a note on what the item affects.
RFI Volume as a Signal of Project Health
Counting RFIs tells you something, though not what people assume. The Navigant Construction Forum reviewed 1,362 projects holding roughly 1.1 million RFIs and found an average of 796 per project, a median first reply of 9.7 days, and an estimated cost of 1,080 US dollars to review and answer each one, close to 859,680 US dollars per project (Impact and Control of RFIs on Construction Projects, 2013). That report also cites Hanna, Tadt and Whited in the Journal of Construction Engineering and Management (2012), who judged 13.2 percent of RFIs unjustifiable because the answer already sat in the documents.
A low count on a complex project usually means questions are resolved verbally and left off the record, which is worse than a high count. A very high count points at document quality, a design released before it was resolved, or a contractor building a paper trail. Teams that agree on level of development in BIM before documentation starts generate fewer dimensional questions.
Clarification or Design Change? The Line an Architect Holds
Answering an RFI is not an invitation to redesign. If the response adds material, changes a correctly drawn dimension, or improves a system beyond what the contract required, the architect has issued a change at no cost to the owner and at real risk to the firm.
The test is whether the answer can be inferred from the existing contract documents. If it can, the response is an interpretation. If not, it is a change and belongs in a proposal request or supplemental instruction, with the owner informed. Writing "provide as detailed on sheet A5.02" interprets. Adding a stainless steel closure piece to a drawing that never had one changes.
When an RFI Turns Into a Delay and Cost Claim
Section 3.2.4 of A201, 2017 edition, sets out the path: where the contractor believes the architect's clarification carries added cost or time, it asserts a claim under the contract's claims provisions. That is why RFI logs end up as exhibits in disputes.
Two patterns cause trouble. An unanswered RFI lets a contractor argue that work stopped or proceeded at risk while waiting. An answered but undated one leaves nobody able to prove when the response landed. Both are record keeping failures.
Digital Tracking and Record Discipline
Procore, Autodesk Construction Cloud, Aconex and Newforma turned the log into a shared, timestamped object rather than a spreadsheet on one desktop. Tooling only helps if the discipline is there. Number every item and never reuse a number, attach the sketch to the RFI rather than an email thread, and export the log monthly so the record outlives the subscription.
Why This Matters for Architecture Students
School teaches design production and model authoring, rarely construction administration, where much of a young architect's first two years is spent. A real RFI log teaches what a studio brief cannot: which details fail on site, which specification sections confuse people, and how fast a question becomes somebody's money.
Heading into a first office role, spend an hour with the log on any live project you can access. Pair it with the fundamentals in this guide to BIM basics and the tools in our essentials for architects collection.
Frequently Asked Questions
What Does RFI Stand For in Construction?
RFI stands for request for information: a formal written question, usually raised by the contractor, seeking clarification of the drawings, specifications or an existing site condition.
Who Is Responsible for Answering an RFI?
The architect answers as interpreter of the contract documents and routes any engineering portion to the relevant consultant. The owner responds only where the question concerns owner supplied information or a decision that is theirs to make.
How Long Does an Architect Have to Respond to an RFI?
Under A201, 2017 edition, section 4.2.11, the response is due within any time limits agreed in the contract, or otherwise with reasonable promptness so the project is not delayed. Five to ten working days is the common window.
Does an RFI Cost Money?
Processing one does. The Navigant Construction Forum estimated an average review and response cost of 1,080 US dollars per RFI across its 2013 data set. Whether the answer adds cost depends on whether it stays inside the contract scope.
Can a Contractor Submit Too Many RFIs?
Yes. Hanna, Tadt and Whited (2012), cited in the 2013 Navigant report, judged 13.2 percent of RFIs unjustifiable because the answer already existed in the documents. Excess volume also slows responses to questions that matter.
Where to Go From Here
Your Next Step: Open any project set you can access and write one RFI against it, citing sheet, detail and specification section, with a proposed solution. Doing it once teaches more about how documents fail than reading about the process.
Comments (0)
Back to Architecture and Design Blog