Last updated on: September 23, 2026
An RFI in construction is a formal request used to clarify missing, unclear, or conflicting project information. RFI stands for Request for Information. It gives contractors, architects, engineers, and other participants a documented way to ask questions and receive answers before proceeding with affected work.
Construction drawings and specifications may not explain every condition a team encounters. A dimension might be missing, two drawings might disagree, or an existing utility might appear in an unexpected location. An RFI helps resolve that uncertainty instead of leaving the field team to make assumptions.
Why Are RFIs Important in Construction?
Construction decisions often affect more than one trade. Moving a duct, for example, could affect ceiling heights, sprinkler locations, and access to equipment. Without a documented response, different teams may proceed with different understandings of the same issue.
RFIs establish what information was requested, who responded, and what clarification was provided. When raised early and answered clearly, they can help prevent incorrect installations, avoidable rework, and delays.
However, an RFI does not automatically authorize additional cost or time. AIA’s guidance on clarification and authorization makes this distinction explicit. Any resulting change must follow the applicable contract procedures.
Common Types of RFIs in Construction
RFIs can be grouped by the issue they address. These are practical categories, not a universal classification system, and one request may involve several categories.
1. Design Clarification RFIs
These requests ask the designer to explain an unclear requirement or detail. For example, a wall section may show an assembly without identifying its connection to the structure. The contractor requests the missing connection detail before installation.
2. Document Discrepancy RFIs
These address conflicting information between drawings, specifications, or schedules. If a door schedule lists a different size than the floor plan, an RFI asks the design team to confirm the requirement rather than allowing the contractor to choose.
3. Coordination RFIs
These concern interfaces between building systems or trades. A pipe may occupy the same space as a beam, or equipment may lack maintenance clearance. The request identifies the conflict and asks for the design clarification needed to resolve it.
4. Existing Condition RFIs
These arise when actual site conditions differ from the project documents. During renovation, a contractor might uncover a column where a new doorway is planned. Photographs and measurements help the designer evaluate the condition and provide direction.
5. Material or Specification Clarification RFIs
These clarify product characteristics, finishes, or performance requirements. For example, two specification sections may indicate different insulation requirements. If the contractor wants to substitute a product, the project’s separate substitution procedure may also apply.
Key Components Included in a Construction RFI
A useful RFI gives the reviewer enough context to understand the issue without having to reconstruct it. Include the following information:
Project Details and RFI Number
Identify the project, submission date, sender, and intended reviewer. Assign a unique RFI number so the question, response, and subsequent references remain connected.
Clear Subject and Exact Location
The subject should identify the problem immediately. “Missing opening dimension at Level 2, Grid B3” is more useful than “Drawing clarification.” Include the room, floor, grid, or equipment identifier where relevant.
Issue Description and Specific Question
Explain what the documents show, what is missing or conflicting, and what answer is required. Keep each request focused on one issue so unrelated questions do not delay its resolution.
Document References and Supporting Attachments
Reference the relevant drawing numbers, revisions, details, and specification sections. Add focused markups, photographs, or model screenshots that show the issue clearly.
Proposed Resolution, When Appropriate
A contractor may suggest a potential solution to help the reviewer understand available options. Clearly identify it as a proposal requiring review, not an approved instruction.
Required Response Date and Potential Impact
Explain when the information is needed and why. For example, fabrication may depend on a confirmed dimension. Identify known potential schedule or cost impacts without presenting uncertain estimates as established facts.
The completed record should also retain the official response, its author and date, and any supporting revised documents.
How Does the Construction RFI Process Work?
The communication route depends on the project’s contract and agreed procedures, but a typical RFI process follows five steps:
01
Review the available information.
Check current drawings, specifications, revisions, and previous RFIs before submitting a new question.
02
Prepare and submit the request
A subcontractor commonly sends the issue through the general contractor, who reviews and forwards it.
03
Assign the appropriate reviewer
The architect, engineer, or other responsible party evaluates the question and coordinates input where necessary.
04
Record and distribute the response
Share the official answer with every affected team, not just the person who asked.
05
Track follow-up and close the request
Update affected documents through the agreed process and record outstanding actions.
An RFI log lists request numbers, subjects, responsible parties, submission dates, due dates, and status. It helps teams track unanswered questions and locate earlier decisions.
Receiving an answer is not the same as completing distribution. Autodesk’s documented review and closure workflow separates these steps, helping teams track whether the response has been formally shared.
Construction RFI Example
The contractor then communicates the detail to affected trades and follows any required change procedures.
This is more actionable than a request that only says, “Please resolve the clash.”
How to write clear RFI notes
01
Describe what the documents show, what is unclear or conflicting, and which activity depends on the answer.
02
Instead of “Please clarify the ceiling,” write: “Drawing A-201 shows 9 feet, while section A-401 indicates 8 feet 6 inches in Corridor 102. Please confirm the required ceiling height.”
03
Keep unrelated questions separate so each can be reviewed, answered, and tracked independently.
04
Include drawing numbers, specification sections, and focused markups or photographs that help the reviewer locate the problem.
05
Explain the condition without assigning blame. If you suggest a solution, identify it as a proposal requiring review.
06
Explain when the answer is needed and which activity could be delayed, rather than simply marking the request “urgent.”
07
Check whether someone unfamiliar with the issue could understand and answer it without requesting more context. Autodesk’s guidance on preparing clear, focused requests offers additional practical recommendations.
RFI vs. Submittal: What Is the Difference?
An RFI requests clarification. A submittal presents proposed materials, equipment, or shop drawings for review against project requirements.
Asking which equipment clearance applies is an RFI. Providing the selected equipment’s product data is a submittal. Neither should replace the other’s required workflow.
How Can BIM Help Reduce Avoidable RFIs?
Building Information Modeling (BIM) helps teams identify spatial conflicts earlier. Through clash detection and model coordination, teams can examine system intersections before installation and use model views to explain complex questions.
However, a model does not replace formal design clarification or approval. Effective RFI management combines early issue identification, clear questions, documented responses, and consistent communication with the people performing the work.
About the Author
Coordination Manager / VDC Manager at United BIM
With over 10 years of experience in the AEC industry, Akash Patel is a seasoned Coordination Manager and VDC Manager at United BIM. His expertise lies in managing complex MEP-FP coordination projects and leveraging cutting-edge BIM technology to ensure seamless collaboration and precision. Akash is dedicated to delivering high-quality, detailed models that meet the demands of modern construction. He is passionate about optimizing workflows and driving innovation within the BIM field.
