A Request for Information (RFI) should help the project team resolve a specific question before uncertainty affects the work. However, an RFI that is vague, incomplete, or sent to the wrong person can create additional questions instead of producing a usable answer.
Understanding how to write a construction RFI means knowing what information the reviewer needs, how to present the question clearly, and how to document the response. The following construction RFI best practices can help owners, architects, engineers, construction managers, general contractors, subcontractors, and project administrators make the process more effective.
What Belongs in a Construction RFI?
Every RFI should give the reviewer enough context to understand the issue without searching through unrelated correspondence. A complete RFI generally includes:
A clear, descriptive title
One specific question
The location of the affected work
Relevant drawing and specification references
A concise explanation of the conflict or missing information
Supporting attachments
The requested response date
Any schedule-related context
The appropriate recipient and routing information
A request for information construction teams can act on should be specific, neutral, and easy to review. It should describe what needs clarification without assigning blame or assuming what the answer will be.
Write a Descriptive RFI Title
Avoid titles such as “Electrical Question,” “Drawing Conflict,” or “Please Clarify.” These descriptions provide little value when someone is reviewing an RFI log or searching for the item later.
A stronger title identifies the subject and location:
Electrical Panel Clearance in Room 204
Conflict Between Door Schedule and Floor Plan at Opening 115
Required Insulation at North Exterior Wall
Ceiling Height Clarification in Second-Floor Corridor
A descriptive title helps reviewers understand the general issue before opening the RFI. It also makes the record more useful when the project team searches for the information later.
Ask One Question Per RFI
One of the most important construction RFI best practices is to limit each RFI to one primary question.
Combining several unrelated questions into a single RFI can create confusion. One reviewer may be able to answer the structural question but not the mechanical question. Another portion may require additional research. The RFI may then remain open even though part of it has already been resolved.
Separate RFIs also create cleaner documentation. Each question receives its own number, routing history, attachments, response, and status.
Related details can remain together when they are necessary to explain one issue. For example, an RFI about a door opening can reference the floor plan, door schedule, wall type, and applicable specification section. Those references support one question. A separate question about ceiling finishes in the same room should generally be submitted as another RFI.
Make the Question Direct and Actionable
The reviewer should be able to identify the requested decision immediately. Begin with a short explanation of what the project team found, then state the question clearly.
For example:
“Drawing A5.2 indicates a 7-foot-0-inch door at Opening 115, while the door schedule on A8.1 indicates a 7-foot-2-inch door. Please confirm the required door height for Opening 115.”
This wording explains the conflict, identifies both references, and asks for one clear decision.
Avoid open-ended statements such as “Please advise” without identifying what needs to be decided. Also avoid writing a long narrative before revealing the actual question. When possible, place the question in its own sentence or paragraph so it is easy to find.
Do Not Use the RFI to Direct the Answer
The person submitting the RFI may include a proposed solution when appropriate, but it should be clearly identified as a suggestion—not presented as an approved direction.
A proposed solution can help the design team understand the field condition or evaluate a practical option. However, the wording should still allow the responsible reviewer to confirm, reject, or modify that proposal.
Reference the Exact Drawings and Specifications
Specific references reduce the amount of time reviewers spend trying to locate the issue. Include the applicable:
Drawing number and detail
Specification section and paragraph
Addendum or revision
Room, area, grid line, elevation, or equipment designation
Related submittal or other project item, when relevant
Instead of writing, “The plans show two different wall types,” identify where each condition appears:
“Detail 3/A6.4 identifies Wall Type W2 at Grid B/4, while the first-floor plan on A2.1 identifies the same location as Wall Type W4.”
Before submitting the RFI, confirm that the references match the current project documents available to the team. An RFI based on an outdated sheet can create unnecessary review work and delay the answer.
Attach Only the Information Needed to Understand the Question
Useful attachments may include a marked-up drawing, photograph, sketch, product information, or excerpt from a relevant document. Markups should make the affected area easy to recognize by using an arrow, cloud, box, or short note.
Attachments should support the question—not replace it. The reviewer should not have to open several files and determine what the submitter is asking.
Use clear filenames and remove unrelated pages when practical. If a full document must be attached, identify the relevant page or section in the RFI text.
Never rely on a photograph alone when location matters. Include enough context to show where the photograph was taken and what condition it represents.
Set a Reasonable Requested Response Date
The requested response date should reflect when the project team needs the information—not simply the earliest date available.
When establishing an appropriate RFI response time, consider:
When the affected work is scheduled
Whether procurement or fabrication depends on the answer
How much review or coordination the question may require
The project’s established RFI procedures
Any related milestones or sequencing concerns
If the issue may affect scheduled work, explain that connection clearly. For example: “A response is requested by September 18 to support wall framing scheduled to begin September 23.”
Avoid marking every RFI as urgent. When everything is treated as a priority, reviewers have less information for determining which questions truly require immediate attention.
Route the RFI to the Correct People
An otherwise well-written RFI can still be delayed when it is sent to the wrong person. Follow the project’s established communication and approval structure.
Depending on the project, an RFI may move from a subcontractor to the general contractor or construction manager before reaching the architect or engineer. Owners and project administrators may also need visibility without being responsible for the technical response.
Before submitting, verify:
Who should receive the initial question
Who is responsible for answering it
Whether another discipline must review it
Who needs to receive the completed response
Consistent routing helps preserve accountability and prevents conflicting answers from circulating among separate groups.
Document the Final Response
A verbal conversation may help resolve an urgent field question, but the final direction should still be documented through the project’s established RFI process.
The completed record should preserve the original question, supporting documents, final response, response date, and any follow-up clarification. If the answer references a revised sketch, drawing, or specification, that document should remain associated with the response.
The project team should also review whether the answer affects related work, pending submittals, cost considerations, or other project documentation. The RFI response resolves the question, but additional project procedures may still be required before implementing a change.
Common Construction RFI Mistakes to Avoid
Many RFI delays begin with preventable problems, including:
Asking multiple unrelated questions in one RFI
Using a vague title
Omitting drawing or specification references
Referencing outdated documents
Failing to identify the affected location
Attaching unmarked drawings or unexplained photographs
Requesting an unrealistic response date without context
Sending the RFI to the wrong reviewer
Treating a proposed solution as approved direction
Acting on a verbal answer without documenting it
Using an RFI for a matter covered by another project process
A quick quality check before submission can prevent the RFI from being returned for clarification.
Create a More Reliable RFI Record with eComm
Good RFI writing begins with a focused question and complete supporting information. A consistent process then helps the team route, review, answer, and preserve that question as part of the project record.
eComm is cloud-based construction information management software that includes tools for managing and tracking RFIs and other project documentation. Teams using eComm can also reference the RFI support guide for instructions on posting an RFI within the platform.
If your organization is evaluating RFI workflow software and wants to see how eComm can support its construction information management process, request an eComm demo.