You’re three weeks into your renovation. Your general contractor submits an RFI — a written request asking the architect to clarify something in the plans. Then another. Then three more show up the next week. Now you’re six weeks in and you’ve got a backlog of unanswered questions. Your project is stalling. Your budget is creeping up. You’re wondering if the contractor is just being difficult or if this is normal.

What RFIs Actually Are and Why They Happen

An RFI — Request for Information — is a formal question from the contractor to the architect. The contractor has found something in the plans that is missing, contradictory, or unclear. They need clarification before they can proceed safely or responsibly. This is not the contractor stalling. This is the contractor doing their job correctly.

I’ve been on both sides of this. As an architect, I wrote unclear details. As an owner, I learned that unclear details cost money — in delay, in rework, and in change orders that could have been prevented. The RFI itself is not the problem. It’s a symptom. The problem is what caused the RFI to exist in the first place.

RFIs happen because drawings are incomplete, details conflict with each other, specifications are vague, or decisions were never made and passed to the contractor. The contractor can’t build around confusion. They have to ask for clarity. If your project has 50 RFIs in four months, the design was not ready when construction started.

How Many RFIs Is Normal

There is no magic number. A small kitchen remodel might generate five to ten RFIs over three months. A whole-house renovation might generate 30 to 50. A custom home could see 100 or more. The number depends on complexity, detail level, and how thorough the design was before construction.

What matters is the rate and the type. If RFIs are arriving one or two per week and they’re about legitimate clarifications, that’s manageable. If RFIs are arriving three to five per week, or if they’re addressing the same area repeatedly, or if they’re asking for basic information that should have been in the original plans, something went wrong during design.

The other indicator is responsiveness. If your architect is answering RFIs within two to three business days, the project absorbs the delay better. If answers take a week or longer, RFIs stack up and your contractor’s crew sits idle. That idle time becomes extra cost that comes back to you as a change order.

Step 1: Understand What’s Driving the RFIs

Before you can control RFIs, you need to know whether they’re caused by incomplete design or by unclear communication between design and construction. Ask your contractor directly. Not defensively — professionally. They will tell you the real pattern.

• Ask your contractor: “What are most of your RFIs about? Are they clarifications on existing details, or are they about things that seem to be missing from the plans entirely?”
• Review the RFI log yourself. Look for repeated questions about the same system or area — that signals a design gap, not a contractor problem.
• Ask your architect: “Are these questions you anticipated, or are they revealing gaps in the design?” A good architect will give you an honest answer.
• Compare RFIs to your original design timeline. If design was rushed or incomplete when construction started, RFIs are expected and predictable.

Example: On a kitchen renovation, you get five RFIs in the first two weeks, all about different things: cabinet heights, electrical outlet placement, tile layout, soffit framing, and plumbing stub heights. This is normal clarification. Then in week four, you get three more RFIs about the same kitchen soffit from three different trades. That’s a design problem — the soffit clearance was not coordinated across disciplines.

Step 2: Implement an RFI Log

You can’t manage what you don’t track. An RFI log is a shared document that lists every RFI, who submitted it, when, what it’s about, who’s responsible for answering, and the answer. It becomes your early warning system for design problems.

• Use a simple spreadsheet or shared document tool — Google Sheets, Excel, or a project management platform. The format matters less than consistency.
• Create columns for: RFI number, date submitted, submitted by, subject, assigned to, date answered, answer, impact on schedule or cost.
• Update the log weekly at minimum. Review it with your contractor and architect together so everyone sees the backlog.
• Flag RFIs that relate to each other or to the same building system. If you have three RFIs about plumbing coordination in different areas, that’s a single design coordination problem, not three separate issues.
• Track how long each RFI takes to answer. If answers are taking eight days on average, your timeline needs to account for that delay.

Example: On a $400,000 home addition, the RFI log shows 12 RFIs submitted in the first month. By month two, only four have been answered. The architect is now two weeks behind. Your contractor can’t frame the second floor because they need answers on structural details. This is visible in the log before it becomes a six-week delay.

Step 3: Distinguish Between RFIs That Are Legitimate and RFIs That Reveal Design Problems

Not all RFIs are equal. Some are quick clarifications. Others signal that a major piece of the design was incomplete or conflicting. You need to tell the difference so you can respond appropriately.

• Legitimate clarification RFI: “The plan shows a 3/4-inch return on the finished face of the cabinet. Confirm that’s correct.” Answer: yes or no. Time to resolve: one day.
• Design gap RFI: “The soffit shown in the ceiling plan doesn’t match the soffit shown in the elevation. Which is correct? Also, we need to know cabinet height to coordinate.” This requires back-and-forth and coordination. Time to resolve: three to five days.
• Major coordination problem RFI: “The plumbing rough-in location conflicts with the HVAC duct shown in the mechanical plan. We need the architect and the MEP engineer to coordinate.” This needs multiple people, multiple disciplines. Time to resolve: one week or more.
• When you see RFIs in the third category arriving regularly, that’s a signal that the architect and MEP engineer did not coordinate before construction started. This is not normal. Push back on this.

Example: You get an RFI asking which of two conflicting ceiling heights is correct — one shown in the framing plan, one in the reflected ceiling plan. This should never reach the contractor. The architect should have caught this during design review.

Step 4: Set Clear Response Expectations

RFIs don’t disappear. But you can control how quickly they’re answered, which directly controls how much they delay your project. Set a response timeline upfront and hold people to it.

• Establish a contract requirement that RFIs receive written answers within two business days for simple clarifications, three to five business days for more complex issues.
• If your architect is slow to respond, the delay is on them. Document it. If it continues, you have grounds for a delay claim.
• Have a weekly coordination meeting — even a 30-minute call — where your architect, contractor, and any specialty consultants (MEP engineer, structural engineer) are all on the line to discuss open RFIs and answer them together.
• Make it clear that RFIs don’t hold up the job. If an RFI takes five days to answer, the contractor should proceed on other work. RFIs should not be used as an excuse to go idle.

Example: Your contract with your architect specifies a 48-hour turnaround on RFI responses. At the end of the first month, the architect has missed that deadline six times. You document each delay. When your project runs two weeks over, you have evidence that the architect’s slow response — not your contractor — caused the delay.

Step 5: Review the Design Before Construction Starts

This is the highest-impact step. A thorough 60-minute design review with your contractor, architect, and key subcontractors — before the first shovel hits the ground — will identify 30 to 50 percent of the RFIs that would otherwise show up during construction. This investment pays for itself immediately.

• Schedule a formal “constructability review” with the contractor and any specialty consultants before construction begins. Have them look at the plans specifically for conflicts, missing information, and unclear details.
• Walk through the plan with the people who will actually build it. The framing contractor will spot things an architect won’t. The electrician will catch things the GC missed.
• Ask directly: “Will you need to submit an RFI on this, or is it clear?” If the contractor says “we’ll probably need clarification on that,” fix it now, not during construction.
• Document the decisions and clarifications made during this review. Write them down. If you decide on something that’s not in the plans, note it. Don’t leave it to memory.

Example: Before a bathroom remodel, the GC and plumber review the plans and immediately flag that the plumbing rough-in for the toilet is only 18 inches from the wall, which is too tight for the fixture shown. The architect changes the layout. That’s one RFI prevented. Multiply that across 30 areas, and you’ve prevented 30 RFI weeks of delay.

Step 6: When RFIs Cause Delays, Document It for Change Order Disputes

If RFIs are causing your project to run late, and your contractor submits a change order asking for extra payment due to schedule delay, you have documentation to push back. This is where the RFI log becomes critical.

• If a contractor claims delay costs caused by slow architectural responses, cross-reference the RFI log. Show that the delay is documented and is the architect’s responsibility, not grounds for a contractor change order.
• If your architect was contractually obligated to answer within 48 hours and consistently took eight days, that delay is not the contractor’s fault and should not cost you money.
• If the contractor was slow to proceed on other work while waiting for an RFI answer, that is the contractor’s responsibility to manage. The RFI alone is not a delay excuser.
• Keep notes on what work was actually held up by each RFI. Generic “delay caused by RFIs” is not as strong as “we could not frame the north wall for five days while waiting for soffit coordination.”

Example: Your contractor submits a change order for $8,000 in delay costs. They claim the architect took too long answering structural RFIs. You pull the RFI log and show that eight RFIs took 12 days on average to answer, against a contractual 48-hour requirement. That’s documented architect delay, not contractor inefficiency. You have grounds to deny the change order or negotiate it down.

What to Watch For

• RFI patterns that repeat in the same area — this is a coordination problem between disciplines, not a one-off question
• RFIs asking for basic decisions that should have been made before design was finished — this signals the design process was incomplete
• Unanswered RFIs stacking up — if more than five RFIs are waiting for answers at any time, the architect is behind
• Contractor RFIs asking about things shown in the plans that contradict other sheets — the architect did not catch coordination errors during QA
• Long gaps between when an RFI is submitted and when the architect acknowledges it — some architects let RFIs sit for days before even opening them
• RFIs that trigger change orders — if answering an RFI requires reworking the design, the original design was incomplete

Questions to Ask Your Architect About RFIs

These questions will help you separate normal RFI activity from patterns that indicate a design problem or process failure. Ask them calmly and specifically. You’re not accusing anyone — you’re asking for clarity.

• “Before we started construction, did you do a constructability review with the contractor? If not, why not?”
• “Are these RFIs revealing gaps in the design, or are they routine clarifications?”
• “Did you coordinate the structural, mechanical, and electrical plans before we sent them to the contractor, or are we discovering conflicts now?”
• “What’s your target turnaround time for RFI responses, and are you meeting it?”
• “How many RFIs do you typically expect on a project of this size and complexity?”
• “Are there any areas of the design you know are incomplete or need more detail work during construction?”
• “If we’re running more RFIs than expected, what should we do to catch up on the schedule?”

Questions to Ask Your Contractor About RFIs

Your contractor is in the best position to tell you whether RFIs are excessive or normal. They’ve built before. They know what kind of questions are routine and what kind signal a design problem.

• “Are we running more RFIs than you typically see on a project like this?”
• “What categories are most of the RFIs falling into — clarifications on details, missing information, or design conflicts?”
• “How are RFIs impacting the schedule? Are you able to work on other areas while waiting for answers, or does the backlog hold up the whole job?”
• “If you could go back to the design phase, what would you want to see done differently?”
• “Are you building this the way the architect drew it, or are you modifying things in the field to make it work?”
• “How much of the design do you think we’re still figuring out, and how much is finished?”

The Bottom Line

RFIs are normal, but volume matters. If you’re averaging more than one or two per week, the design was not ready when construction started. That costs you money in delay and rework. The best defense is a thorough pre-construction review with everyone involved — contractor, architect, and specialists — to catch design gaps before they become field problems. Then track every RFI, hold your architect to response timelines, and document delays. When RFIs cause cost overruns, you’ll have proof of who caused the problem.