The Role of Requests for Information (RFIs)
An RFI is the formal mechanism used to resolve gaps, conflicts, or ambiguities in the construction documents. Because architectural blueprints and engineering plans cannot perfectly predict every real-world field condition, questions inevitably arise during construction.
The RFI serves to document the question, propose a solution from the field, and receive a binding, official answer from the design professionals. This process ensures that the building is constructed safely, according to code, and aligns with the owner's design intent.
Who Writes and Responds to RFIs?
The applicability of the RFI process is strictly defined by project hierarchy. Subcontractors generally identify issues in the field and submit their questions to the General Contractor (GC). The GC evaluates the question to ensure the answer isn't already in the plans. If valid, the GC formally issues the RFI.
The Architect or Engineer of Record receives the RFI, reviews the documentation, and provides a formal response. In some cases, the architect must forward the RFI to a specialized consultant (like a structural or mechanical engineer) before compiling the final answer to send back to the GC.
Essential Data to Track in an RFI Log
A standardized RFI log is essential for tracking accountability. It must include sequential RFI numbering, a clear subject line, and references to the specific drawing sheets or specification sections in question.
To manage workflow, the log must track the date submitted, the required date for an answer, and the actual date returned. Tracking the 'Ball in Court' ensures everyone knows who is currently responsible for the next action. Identifying whether the RFI will potentially cause a cost or schedule impact is also a critical standard practice.
- Sequential RFI Number and Subject.
- Reference to Drawing Number or Spec Section.
- Date Submitted, Due Date, and Date Returned.
- Potential Cost/Schedule Impact Flags.
Assessing Cost and Schedule Impacts
Not all RFIs are simple clarifications; many alter the scope of work. When submitting an RFI, the contractor should flag if the proposed solution will require additional materials, labor, or time.
When the design team responds, the GC must evaluate the answer. If the response requires work outside the original contract scope, the RFI serves as the initiating documentation for a formal Change Order, shifting the financial liability or schedule extension to the project owner.
Best Practices for RFI Management
To prevent RFIs from bottlenecking a project, GCs should practice 'proposing a solution.' An RFI should not just ask a question; it should provide a sketch or written proposal of how the contractor intends to solve it, allowing the architect to simply agree or make minor tweaks.
Additionally, setting clear Service Level Agreements (SLAs) for response times in the contract—typically 7 to 14 days—and prioritizing critical-path RFIs during weekly coordination meetings are standard methods to maintain momentum.
Frequently asked questions
What makes an RFI different from a Change Order?
An RFI is a question seeking clarification. A Change Order is a formal amendment modifying the contract's price or schedule. Often, the answer to an RFI leads to the creation of a Change Order.
Can a subcontractor submit an RFI directly to the architect?
Standard contracts require all communication to flow through the General Contractor. Subcontractors generally submit questions to the GC, who then issues the formal RFI to the architect.
What happens if an RFI is not answered on time?
If an unanswered RFI delays critical path activities, the contractor may be entitled to a schedule extension or delay claims to cover the cost of idle labor and equipment.
What is an 'Unjustified RFI'?
An unjustified RFI is a question where the answer was already clearly detailed in the contract documents. Excessive unjustified RFIs waste the design team's time and can strain project relationships.