Construction RFI Management Guide | Best Practices for Contractors

You’re three weeks into framing a commercial tenant improvement and your lead carpenter pulls you aside. “Hey, the plans show a 36-inch door into this storage room, but the hardware schedule calls for a 42-inch commercial frame. Which one is right?”

You know the answer isn’t going to come from staring at the plans harder. Someone made a mistake, or there’s context you’re not seeing. Either way, you need a formal answer from the architect before your crew can hang that wall. You need an RFI.

RFIs are one of those things every contractor deals with but few handle well. They pile up. Responses take forever. The crew sits around waiting. And by the time you get your answer, you’ve already lost two days of production and burned through your schedule float.

It doesn’t have to work that way. Good RFI management keeps your project moving, protects you legally, and makes sure nothing falls through the cracks. Here’s how to do it right.

What Is an RFI in Construction?

An RFI, or Request for Information, is a formal written question from one project party to another. In most cases, it goes from the general contractor to the architect or engineer asking for clarification on the construction documents.

RFIs exist because construction documents are never perfect. Plans and specifications are created by humans, and humans miss things. Dimensions conflict. Details get left out. Notes on one sheet contradict notes on another. And sometimes, site conditions don’t match what the drawings assumed.

When your crew hits one of these conflicts or gaps, you have two choices: guess and hope you’re right, or submit an RFI and get a documented answer. Guessing saves time in the short term. But when that guess turns into $15,000 worth of rework and a finger-pointing match about who approved the deviation, you’ll wish you had the paper trail.

An RFI is not a change order. This is worth saying clearly because people confuse them constantly. An RFI asks a question. A change order changes the scope, cost, or schedule. Sometimes an RFI response leads to a change order, but the RFI itself is just a request for clarification.

Common reasons to submit an RFI:

• Conflicting information between drawings and specs
• Missing details or dimensions on the plans
• Unclear notes or callouts
• Site conditions that don’t match the design
• Material substitution questions
• Code compliance questions where the plans are silent

If you’re running a well-organized project, your RFI process is just another part of the system. If you’re not, RFIs become the thing that brings everything to a stop.

Why RFI Management Matters

Every open RFI is a potential delay. That might sound dramatic, but think about what happens on a real jobsite when an RFI goes unanswered.

Delays stack up fast. Your framing crew can’t close up that wall until you know which door size is correct. But your electrician is scheduled to rough in that wall tomorrow. And your insulation crew is booked for Thursday. One unanswered RFI just created a chain reaction across three trades.

This is why your daily reports should capture every RFI-related delay as it happens. That documentation is your evidence when schedule impact comes into question.

A 2022 study by Navigant (now Guidehouse) found that the average commercial construction project generates between 500 and 800 RFIs. On large projects, that number climbs into the thousands. Even if only 10% of those RFIs cause work stoppages, you’re looking at 50 to 80 points in your project where everything could grind to a halt.

The money adds up. Every day your crew can’t work in a specific area because of an open RFI costs you labor, equipment, and schedule. The average cost impact of a delayed RFI response varies wildly depending on project size, but contractors regularly report that individual RFI delays cost them $1,000 to $5,000 per day in lost productivity. Over the life of a project, poorly managed RFIs can easily eat 1-3% of total project costs.

Liability is the hidden risk. When a dispute hits and the lawyers get involved, the RFI log is one of the first things they look at. Did you ask the question? Did you get an answer? Did you follow the answer? If the RFI trail is sloppy, incomplete, or nonexistent, you’re going to have a very hard time proving your case.

Here’s a scenario that plays out more often than it should: a sub does work based on a verbal clarification from the architect’s field rep. No RFI was filed. The work doesn’t match what the architect’s office intended. Now there’s a $40,000 rework bill and nobody has a paper trail. The sub says the architect told them to do it that way. The architect says they never approved that. Without a documented RFI and response, it becomes a “he said, she said” situation that usually ends with the contractor eating the cost.

The RFI Process Step by Step

The RFI process isn’t complicated, but skipping steps is where things go wrong. Here’s what it should look like from start to finish.

Step 1: Identify the Issue

Your field crew, a subcontractor, or your project manager spots something in the documents that doesn’t make sense. Maybe it’s a conflict between the structural and architectural drawings. Maybe the specs call out a product that’s been discontinued. Whatever it is, someone flags it.

The sooner you catch these issues, the better. Don’t wait until you’re standing in front of the problem with a crew that can’t work. Review plans ahead of time during project planning and flag anything that looks off before it becomes an emergency.

Step 2: Write the RFI

This is where most contractors either do it right or completely blow it. A good RFI includes:

• A clear, specific question. Not “the plans are confusing in the bathroom area.” Instead: “Sheet A-204, Detail 3: the plan shows 2x6 framing at 16” o.c. for the bathroom wet wall, but the plumbing riser requires 8 inches of clearance. Please confirm whether the wet wall should be framed with 2x8 studs or a furred-out 2x6 wall.”
• Drawing and specification references. Sheet numbers, detail numbers, spec sections. Make it easy for the reviewer to find exactly what you’re talking about.
• Photos or markups if helpful. A picture of the actual site condition or a markup of the drawing can save days of back-and-forth.
• Your suggested solution (when appropriate). Architects and engineers are more likely to respond quickly when you propose a solution rather than just dumping a problem on their desk. “We suggest framing with 2x8 studs per the attached sketch. Please confirm or advise.”

Step 3: Log and Submit

Every RFI gets a unique number. Every RFI gets logged with the date submitted, who submitted it, who it’s directed to, and what the question is about. This is non-negotiable.

Submit through whatever channel your contract specifies. Some projects use email. Some use a project management platform. Some still use hard copy transmittals. Whatever the method, make sure you have proof of when it was sent and to whom.

If you’re keeping your project documents organized, your RFI log should tie directly into your document management system so everything is in one place.

Step 4: Track the Response

Here’s where most contractors drop the ball. You submit the RFI and then… hope someone answers. No follow-up. No tracking. Just hope.

Set a response deadline based on your contract requirements (typically 7 to 14 days). If you don’t get a response by the deadline, follow up. Then follow up again. Document every follow-up. If the response is delayed and it impacts your schedule, document that too. This paper trail matters when it comes time to discuss schedule extensions or delay claims.

Step 5: Distribute the Response

You got your answer. Great. Now make sure everyone who needs it actually sees it. That means your field superintendent, the affected subcontractors, your project engineer, and anyone else whose work depends on that clarification.

Read real contractor reviews and see why Projul carries a 9.8/10 on G2.

This sounds obvious, but it’s one of the most common failure points. The PM gets the answer, saves it to their laptop, and forgets to tell the crew. Two weeks later, the electrician is still working off the original (wrong) assumption.

Step 6: Close It Out

Once the response is distributed and the issue is resolved, close the RFI in your log. Mark it complete. Attach the response. Note any cost or schedule impacts. Move on.

A clean RFI log with everything properly closed out is worth its weight in gold during closeout, audits, or any kind of dispute resolution.

Common RFI Mistakes That Cost You Money

After years of watching how contractors handle RFIs, some patterns are painfully clear. These are the mistakes that show up on nearly every troubled project.

Vague Questions

“Please clarify the kitchen layout.” That’s not an RFI. That’s a cry for help. The architect is going to respond with “please clarify your question,” and you just wasted a week of round-trip time.

Be specific. Reference exact drawings, details, and spec sections. Describe the conflict clearly. Propose a solution when you can. The more specific your question, the faster and more useful the response.

Waiting Too Long to Submit

You spotted the conflict during plan review three weeks ago but figured you’d deal with it when you got to that phase of work. Now your crew is standing there, and the RFI response is going to take 10 business days. That’s two weeks of delay that could have been avoided if you’d submitted the RFI the day you noticed the problem.

Submit early. Even if the affected work is months away, get the question in the pipeline now. There’s no penalty for asking early.

Not Tracking RFIs Centrally

The PM tracks some RFIs in their email. The superintendent has a few in a notebook. The project engineer has a spreadsheet on their desktop. Nobody knows how many total RFIs are open, which ones are overdue, or which responses have been distributed.

All RFIs need to live in one place that everyone on the project team can access. Full stop.

Accepting Verbal Responses

The architect tells you at the OAC meeting that they want you to go with the 2x8 framing. Great. Now get that in writing. A verbal response is not a valid RFI response. If that verbal direction leads to additional cost or a problem later, you have nothing to back you up.

Always insist on a written response. If the architect gives you direction verbally because the crew needs to keep moving, follow up immediately with an RFI confirming what was discussed and asking for formal written confirmation.

Not Distributing Responses

Getting the answer is only half the job. If the people actually doing the work don’t see the response, it might as well not exist. Build a distribution process into your RFI workflow so every response automatically goes to the right people.

Using RFIs to Create Change Orders

Some contractors use RFIs as a backdoor to get scope changes approved. They phrase questions in a way that implies additional work, hoping the architect’s response will serve as authorization. This is a bad idea. It damages your credibility with the design team, slows down future RFI responses (because now they’re reviewing every question through a legal lens), and it rarely holds up in a dispute anyway.

Keep RFIs for clarifications. Use the change order process for scope changes. And once the project nears completion, unresolved RFIs can show up as punch list items that delay your final payment.

RFI Tracking: Spreadsheets vs Software

Let’s be honest. Plenty of contractors still track RFIs in spreadsheets. And for a single small project with a dozen RFIs, a spreadsheet works fine. It’s when you scale up that things fall apart.

The Spreadsheet Approach

A typical RFI tracking spreadsheet has columns for RFI number, date submitted, description, directed to, response due date, date received, status, and notes. It’s straightforward and cheap.

But spreadsheets have real limitations:

• Version control is a nightmare. When three people have copies of the spreadsheet and they’re all making edits, which one is the source of truth? Nobody knows.
• No automatic notifications. Nobody gets an alert when a response is overdue. You have to manually check every line and follow up yourself.
• Documents are separate. The spreadsheet tracks the RFI, but the actual question, markups, and response documents live somewhere else. You’re constantly cross-referencing between the log and your email or file folders.
• No visibility for the field. Your superintendent has to call the office to find out if the RFI they submitted last week got answered.

The Software Approach

Construction project management software handles RFIs as part of the overall project workflow. You create an RFI, attach drawings and photos, assign it to the right person, and the system tracks everything automatically.

The advantages are significant:

• One source of truth. Everyone on the project sees the same RFI log, the same statuses, and the same documents.
• Automatic notifications and reminders. The system pings people when responses are due or overdue.
• Documents attached directly. The question, markups, photos, and response all live in one record. No digging through email.
• Field access. Your super can check the status of any RFI from their phone on the jobsite.
• Reporting. You can pull reports on average response times, overdue RFIs, RFIs by trade, and other data that helps you manage the process proactively.

With a tool like Projul, your RFIs tie into the rest of your project management system. Documents, photos, schedules, and communication all live in one place. When an RFI response comes in, the people who need to see it can access it immediately without waiting for someone to forward an email.

The cost difference between a spreadsheet and software is real, but so is the cost of a single delayed RFI that holds up your crew for a week. For most contractors running more than one or two projects at a time, software pays for itself quickly.

Best Practices for Faster RFI Resolution

If there’s one thing every contractor wants, it’s faster RFI responses. You can’t control how fast the architect reviews your question, but you can control a lot of the factors that affect turnaround time.

Write Better RFIs

This is the single most effective thing you can do. A well-written RFI with specific references, clear questions, and a proposed solution gets answered faster than a vague one every time. Architects and engineers are busy. If they have to spend 30 minutes figuring out what you’re even asking about, your RFI goes to the bottom of the pile.

Spend an extra five minutes writing a clear, complete question. It will save you days on the back end.

Submit Early

Don’t wait until the work is imminent. Review upcoming phases during your weekly planning meetings and identify potential RFI items in advance. Getting questions into the pipeline early gives the design team time to respond without creating schedule pressure.

Some of the best project managers review plan sets section by section before each phase kicks off, specifically looking for conflicts and ambiguities. This one habit can cut your critical-path RFI delays in half.

Batch Strategically

If you have six questions about the same drawing or the same building system, submit them together. The architect has to pull up that drawing set and get into the context once instead of six separate times. Batching related questions speeds up the review process for everyone.

But don’t batch unrelated questions into one RFI. A question about the roof flashing detail should not be in the same RFI as a question about the basement floor drain. Keep each RFI focused so responses don’t get delayed because one part of a multi-topic RFI needs more review than the others.

Build Relationships with the Design Team

This isn’t a formal process tip, but it matters more than most people realize. If you have a good working relationship with the architect and their consultants, your RFIs get attention faster. Be professional. Don’t use RFIs to play gotcha or make the design team look bad. Ask clear questions, propose reasonable solutions, and make their job easier. They’ll return the favor with faster, more thoughtful responses.

Hold Weekly RFI Review Meetings

Dedicate 15 minutes of your weekly OAC meeting (or a separate internal meeting) to reviewing the RFI log. Go through every open item. Identify what’s overdue. Flag anything that could impact the schedule. This keeps RFIs from falling through the cracks and puts consistent pressure on the response timeline.

Track Response Times and Follow Up Consistently

Know what your contractual response window is and enforce it. If the contract says 10 business days and it’s day 12, send a follow-up. Be polite but persistent. And document every follow-up. If delayed responses eventually impact your schedule, that documentation supports your delay claim.

Use Photos and Markups Generously

A photo of the actual site condition or a markup of the conflicting detail is worth a thousand words in an RFI. These visual references help the reviewer understand your question immediately instead of having to visit the site or pull up drawings from scratch. Take the extra two minutes to attach a photo. It’s one of the simplest ways to speed up the process.

Keep Your Document Management Tight

Your RFIs don’t exist in isolation. They’re connected to plans, specs, submittals, and change orders. If your document management is a mess, your RFI process will be a mess too. Keep everything organized so that when an RFI references a specific drawing or submittal, anyone reviewing it can pull up that document in seconds.

Stop Letting RFIs Run Your Schedule

RFIs are never going away. As long as humans design buildings and other humans build them, there will be questions that need answering. The difference between a project that runs smoothly and one that’s constantly behind schedule often comes down to how well the team manages those questions.

The contractors who get this right share a few things in common. They submit RFIs early. They write clear, specific questions. They track everything in one central system. They follow up consistently. And they make sure every response gets to the people who need it.

None of this is complicated. It’s just discipline and having the right systems in place.

Try a live demo and see how Projul simplifies this for your team.

If you’re still tracking RFIs in spreadsheets and email threads, take a hard look at how much time and money that’s actually costing you. The answer might surprise you. And if you’re ready to get your project documents, RFIs, and communication into one place, check out what Projul can do for your team.