A Request for Information (RFI) is a formal, numbered question sent by the contractor (usually through the GC to the architect or engineer) when the drawings and specs are unclear, incomplete or contradict each other. The answer becomes part of the project record and tells the field how to build.
Why it matters
RFIs are where cost and schedule risk first show up. A slow answer can stall a crew. An answer that changes scope is the start of a change order. Unanswered or late RFIs are also evidence in delay claims, so the dates matter as much as the content.
Worked example
On Riverside Medical Center (Job #24-118, sample data), the superintendent finds that the mechanical drawings show duct penetrations through a rated wall with no fire dampers. The PM issues RFI-212: “Confirm fire damper requirement at rated wall, grid C/4.” The engineer confirms dampers are required. Because that work is not in the contract, RFI-212 becomes a change event and is later priced as CO #14 at $86,400. The project has 23 open RFIs, 4 overdue, which the PM reviews weekly.
Common mistakes
- Asking vague questions without a proposed solution, drawing reference or photo.
- Not tracking the response time the contract requires, then losing the delay argument.
- Treating an RFI answer that adds scope as “free” instead of opening a change event.
How os.construction handles it
We’re building RFIs on the same record as cost and schedule, so an answer that adds scope can open a change event linked to the original question, the photo and the daily log entry.