RFIs in construction: The best ways to manage them on site

TL;DR

• An RFI (Request for Information) is a formal way to request clarification when drawings, specifications, or contract documents are unclear, incomplete, or conflicting.
• Raise an RFI whenever your team needs a documented answer before work can continue or a decision can be made on site.
• Poorly managed RFIs can slow down projects, create confusion between teams, and make it difficult to track why decisions were made.
• A simple RFI process with clear ownership, response tracking, and centralised documentation helps keep projects moving.

RFIs are a normal part of construction. No matter how much planning happens before a project starts, questions will come up once work begins.

The purpose of an RFI is to create a clear process for getting those questions answered and documenting the decision. When RFIs are managed properly, they help prevent mistakes, keep project teams aligned, and reduce delays.

The challenge comes when RFIs start building up. Without a clear process, questions can become buried across emails, phone calls, and conversations between site and office teams. It becomes harder to see what has been raised, who is responsible for responding, and whether a decision has actually been made.

For builders managing multiple projects, having a simple way to track RFIs can make a significant difference in keeping work moving.

What is an RFI in construction?

An RFI (Request for Information) is a formal request for clarification when something in the construction documents is unclear, incomplete, or does not match what is happening on site.

RFIs are commonly used to resolve questions about drawings, specifications, materials, or scope before work proceeds. The response creates a documented record of the decision, helping keep everyone aligned and reducing the risk of disputes later.

Typically, RFIs are raised by the builder, head contractor, or subcontractor and sent to the relevant party for clarification, such as the architect, engineer, or design consultant. The head contractor usually manages the process by reviewing requests, tracking responses, and making sure decisions are communicated back to the right teams.

RFIs are often confused with submittals and variations, but they serve different purposes:

• RFI: Used when clarification is needed. For example, a drawing detail is missing, or two documents provide conflicting information.
• Submittal: Used to provide information for review and approval, such as product data, samples, or shop drawings showing how the work will be completed.
• Variation: Used when there is a change to the agreed scope, cost, or timeframe.

An RFI does not automatically mean there will be a variation. However, if the response identifies additional work, a design change, or a gap in the contract documents, it may lead to one.

When should a builder raise an RFI?

An RFI is the right tool when you need a documented answer before work can continue. Common reasons include:

• Missing specifications: A detail, requirement, or instruction is not included in the contract documents.
• Conflicting information: Two documents provide different information, such as architectural drawings showing one requirement while engineering drawings show another.
• Design clarification: The design intent is unclear and proceeding without confirmation could create rework or delays.
• Material substitutions: A specified product is unavailable, discontinued, or unsuitable for the conditions on site.
• Constructability concerns: The design cannot be built as documented without clarification or a different approach.

A quick conversation with the architect, engineer, or project team may help identify the issue, but it does not replace the RFI process. The RFI creates a clear record of what was asked, who responded, and what direction was provided. For builders managing multiple projects, keeping RFIs documented and tracked is critical. Without a central record, important decisions can become buried in emails, messages, or site conversations.

What happens when RFIs pile up or stall?

A few open RFIs are normal on most construction projects. The problem starts when they are not tracked properly, ownership is unclear, and unanswered questions begin affecting work on site.

When RFIs sit unresolved, the first impact is usually delays. Crews may be unable to continue until they receive clarification, leaving teams waiting or forcing them to make assumptions. Neither option is ideal. Waiting affects productivity, while proceeding without approval can create rework later.

As RFIs build up, the program can also start to suffer. A delayed response for one trade can affect following activities, create coordination issues between subcontractors, and put pressure on the construction schedule.

Poor RFI management can also create cost and communication issues. Without a clear record of what was asked, who responded, and when the decision was made, it becomes harder to resolve disagreements about scope, responsibility, or changes.

The goal is not to eliminate RFIs. They are an important part of the construction process. The goal is making sure every RFI has clear ownership, a response timeline, and a documented outcome so decisions do not get lost between the office and the site.

How to write an RFI

A good RFI does more than ask a question. It gives the person reviewing it everything they need to provide a clear answer without unnecessary back-and-forth. A complete RFI should include:

• A clear title and RFI number. Give every RFI a unique reference number and a title that explains the issue. "RFI 024 – Mechanical clearance conflict at Level 3" is much more useful than "Question about drawings".
• Project details and document references. Include the project name, relevant drawing numbers, specification sections, or contract documents so everyone is working from the same information.
• Date submitted and required response date. RFIs are often linked to upcoming site activities. Including when a response is needed helps the reviewing team understand the impact of delays.
• A clear explanation of the issue. Avoid vague questions. Explain what is unclear, where the issue is located, and why clarification is required.
• Supporting information. Include anything that helps explain the problem, such as site photos, marked-up drawings, sketches, or screenshots of conflicting information.
• A recommended solution where possible. If your team has a practical solution, include it. Giving the design team something specific to review can help speed up decision-making.

The biggest mistake builders make with RFIs is treating them as simple questions rather than project records. A well-documented RFI helps keep decisions clear, reduces unnecessary back-and-forth, and provides a record of why decisions were made.

For growing builders managing multiple projects, having a consistent RFI process makes it easier to keep questions, responses, and project documentation organised as jobs become more complex.

How to stop RFIs from stalling your jobs

Knowing what an RFI is and managing RFIs effectively across multiple projects are two different things. A strong RFI process helps ensure questions are answered, decisions are documented, and site teams have the information they need to keep moving.

1. Set expectations early

RFIs work best when everyone understands the process from the beginning. Define how RFIs should be submitted, who is responsible for responding, and expected response timeframes before work starts. Without clear expectations, important questions can sit unresolved while teams wait for direction.

2. Keep RFIs tracked in one place

RFIs are easy to lose when they are spread across email chains, spreadsheets, and conversations between different project teams. A central record helps your team see:

• Which RFIs are still open
• Who is responsible for responding
• What information has been provided
• Which items are affecting progress

For builders managing multiple projects, having visibility across RFIs becomes increasingly important as the number of jobs and trades increases. BuildPass helps teams raise, assign, and track RFIs across projects, keeping important questions and responses connected instead of buried in inboxes.

3. Assign ownership

Every open RFI should have someone responsible for following it through. Without clear ownership, questions can sit unresolved because everyone assumes someone else is managing them.

4. Provide enough detail upfront

Incomplete RFIs create unnecessary delays. Include relevant drawings, photos, specifications, and a clear explanation of the issue so the reviewer has everything needed to respond. The easier it is to understand the problem, the faster it can be resolved.

5. Keep project information connected

RFIs rarely exist in isolation. They often relate to drawings, site conditions, safety documentation, schedules, and other project records. Keeping project information organised in one place makes it easier for office and site teams to access the context they need when decisions are being made.

6. Avoid managing RFIs through inboxes alone

Email is useful for communication, but it is not a project management system. Important decisions can get buried, attachments can be missed, and follow-ups can rely on someone remembering to chase them. The right construction management platform should make it easier to track decisions and keep teams aligned without creating more administration. If your RFI process still runs through email threads, you will lose track of open items. BuildPass keeps RFI tracking alongside your other site documentation so nothing falls between the cracks.

Frequently asked questions

What does RFI stand for in construction?

RFI stands for Request for Information. It is a formal document used on construction projects to request clarification from the design team, typically the architect or engineer, when something in the contract documents is unclear, missing, or in conflict with another document.

Who is responsible for responding to an RFI?

The architect or engineer of record is typically responsible for responding to RFIs related to design intent, drawings, and specs. For RFIs that involve scope or contract interpretation, the client or their representative may respond. The builder or subcontractor who raised the RFI is responsible for following up if a response is not received by the required date.

How long should an RFI response take?

Standard industry practice is 7 to 10 business days. The right timeframe depends on the complexity of the question and what is specified in the contract. The most important thing is that a required response date is stated in the RFI itself and agreed upon in the contract before work begins. Without a contractual requirement, response time is difficult to enforce.

What is the difference between an RFI and a change order?

An RFI clarifies something already in the contract when the documents are unclear or conflicting. A change order modifies the contract itself, adjusting scope, price, or schedule. An RFI can trigger a change order if the clarification reveals work that falls outside the original contract scope, but they are separate documents with distinct purposes. Treating them as interchangeable is a common source of disputes.

What is the difference between an RFI and a submittal?

A submittal is the contractor demonstrating they will use materials or methods that meet the contract requirements, such as product data sheets, samples, or shop drawings submitted for review and approval. An RFI is the contractor asking what the requirements are when the contract documents do not make them clear. Submittals confirm compliance. RFIs resolve ambiguity.

What should a builder do if an RFI response is overdue?

First, confirm the RFI was received by the right party. Then follow up in writing, referencing the original submission date and the required response date. If the contract specifies an RFI response time, cite it in the follow-up. Document every follow-up attempt. If the delay is affecting the schedule, put that in writing too. An RFI response delay that causes a work stoppage or schedule impact needs to be documented as it happens, not reconstructed later.

How many RFIs is normal on a construction project?

It varies by project size and complexity, but a common benchmark is 10 to 15 RFIs per $1 million in project value on a typical project. Significantly more than that is often a sign of incomplete contract documents, coordination issues in the design team, or an RFI process being used for things it was not designed for. Reducing RFI volume starts with better contract documents upfront.

What is an RFI log and why do you need one?

An RFI log is a centralised record of every RFI on a project: the RFI number, description, who it was submitted to, the submission date, the required response date, and the actual response date. It gives the project team a live view of what is open, what is overdue, and what has been resolved. Without one, open items fall through the cracks and the project loses visibility on pending decisions. On any project with more than a handful of RFIs, managing them without a log creates real exposure.

Managing RFIs well is a process problem as much as a paperwork problem. The builders who stay on top of it are not doing anything complicated. They are tracking consistently, assigning ownership, and keeping documentation in one place rather than scattered across inboxes. BuildPass keeps your RFI tracking, site documentation, and project communications together so the whole team has visibility on what is open and what needs to move. Book a demo to see how it works on a live project.