Construction projects run on information. A GC who doesn't have a clear answer about which beam goes where, which product type is correct, or how two conflicting details should be resolved cannot build that portion of the project. Work stops until the answer arrives.

An RFI (Request for Information) is the formal mechanism for asking the question. It's a written document — numbered, tracked, and assigned to a specific reviewer — that asks the architect, engineer, or owner to clarify an ambiguity, resolve a conflict, or provide missing information in the construction documents.

A healthy project has RFIs moving quickly: issued, responded to, closed. An unhealthy project has RFIs sitting open for weeks while the affected work is on hold.

Construction plans and blank clipboard on a kitchen renovation worktable
Editorial illustrationA plan-review table with abstract drawings and a blank clipboard establishes the documented questions and coordinated responses behind the RFI process.

What an RFI Is and What It Isn't

An RFI is a formal written question from the contractor (GC or sub) to the design team (architect, structural engineer, MEP engineer) or the owner. It asks for clarification on something that is ambiguous, contradictory, or missing in the construction documents.

Examples of legitimate RFIs:

What an RFI is not:

The distinction matters because some GCs use RFIs strategically — to document that they raised a question before starting work that later becomes a change order, or to create a paper trail for a delay claim. Owners and architects who see large RFI volumes should distinguish between legitimate coordination questions and RFI-as-strategy.

Why Unanswered RFIs Kill Schedules

When a GC issues an RFI on an item affecting active work, the standard response to that situation is to stop work in the affected area until the answer arrives. This is the safe and professionally appropriate response — proceeding without clarity risks building something wrong that has to be torn out.

The problem is that RFI response times are often slow.

Who responds to RFIs: The GC issues the RFI to the architect. The architect either responds from their own knowledge or forwards the RFI to the relevant engineer (structural, MEP, civil) for a response. The engineer responds to the architect. The architect synthesizes and responds to the GC. This chain has multiple handoffs, and each one adds time.

Contract review periods: Most construction contracts specify a review period for RFIs — typically 10-14 calendar days. But the 10-day clock starts when the architect receives the RFI, not when the GC issued it. If the architect takes 3 days to forward to the engineer, and the engineer takes the full 10 days, and the architect takes 2 more days to respond, the GC has waited 15 days for an answer.

What "waiting 15 days" means on a schedule: If the RFI is on the critical path — meaning the work can't proceed until the question is answered — the project is 15 days behind before any physical work is delayed. All the trades downstream of that work absorb the delay.

Open warehouse duct stopped beside a crossing fire sprinkler main
Editorial illustrationA duct route blocked by a crossing sprinkler main shows the kind of field conflict that can stop dependent work until designers clarify the path forward.

Examples of RFIs That Stopped Work

Structural vs. architectural conflict — ceilings: A framing crew discovers during installation that the structural beam depth at a corridor intersection doesn't leave enough room for the finished ceiling height the architect specified. The GC issues an RFI. Until the response arrives — which beam or which ceiling changes — the framing crew can't close that section. If the MEP rough-in is waiting on framing, and drywall is waiting on MEP rough-in, one unanswered RFI cascades into a two-week delay for three trades.

Specification conflict — drywall type: Drywall is in the field, panels staged, crew ready to hang. The GC notices the specification calls for Type X (fire-rated) but the drawing notes say Type C (a combined fire-and-moisture-resistant board). They're different products. The GC can't order and hang the wrong product and expect it to pass inspection. RFI issued. Until the answer arrives, no drywall goes up in those rooms.

Civil conflict — existing underground utilities: During excavation for a foundation, the crew hits an unmarked utility not shown on the civil drawings. Work stops immediately. The GC issues an RFI to the civil engineer and owner: what is this utility, who owns it, does it need to be relocated, and who pays for the relocation? Until those answers arrive, that section of the foundation can't proceed.

In each case, the RFI is legitimate. The schedule impact is real. And the speed of the response directly determines how long work is stopped.

What a Healthy RFI Log Looks Like

On a healthy project, RFIs move fast:

What to ask your GC about their RFI process:

  1. What is your average RFI response turnaround time on this project? (They should be tracking this.)
  2. Who on your team is responsible for following up on open RFIs before the contract period expires? (There should be a named person, not "we track it.")
  3. How many RFIs are currently open beyond their response due date? (Any significant number is an active schedule risk.)
  4. Are there any open RFIs affecting critical path work? (This is the question that matters most for schedule.)

RFI Response Times and Delay Claims

When design team response times consistently exceed the contract period, the GC has a basis for a delay claim against the owner. This is a legitimate construction law position: if the GC can't build because they're waiting for answers, and the answers are delayed beyond the contractually specified period, the GC's schedule extension claim is compensable.

This is why RFI tracking matters to the owner, not just to the GC. An owner who sees that the architect is taking 20 days to respond to RFIs on a 10-day contract period should address it — because the GC's delay claims are going to arrive at the owner's desk.

Dark tablet and abstract MEP drawing before coordinated framed-wall rough-ins
Editorial illustrationA field-ready tablet and abstract drawing connect reviewed information to coordinated rough-ins, helping clarified decisions reach the workfront.

How JK Prestige Manages RFIs

On JK Prestige projects, every open RFI is tracked in the project management system with the issue date, the reviewer, the response due date, and the current status. The owner sees the full RFI log in real time through the project owner portal.

When an RFI approaches its response deadline without a response, JK's superintendent follows up directly with the architect and documents the follow-up in the project log. If a response is overdue and affects critical path work, JK notifies the owner in writing — not as a threat, but as a schedule alert that requires the owner's attention.

The JK Way covers how open RFIs, submittals, and schedule risks are reported in the weekly written owner update. The owner portal gives 24/7 access to live RFI and submittal logs — not a monthly meeting.

For ground-up construction and renovation projects in Jacksonville and beyond, a JK principal answers directly — (904) 944-0278.

Get a written estimate in 48 hours.

No call center. No coordinator. A JK principal reviews every inquiry and replies with a real number, not a range, not a follow-up form.

Request Free Estimate →

Frequently Asked Questions

Why can an RFI response take 15 days even when the contract says 10 days?
The contract clock usually starts when the architect receives the RFI, not when the GC issued it, and the RFI often has to pass through multiple handoffs before it gets answered. The GC sends it to the architect, the architect forwards it to the relevant engineer, the engineer takes their full response window, and then the architect has to synthesize and send the answer back. Add up a few days for each handoff and a straightforward 10 day contract period can easily stretch to 15 days in practice.
How do I tell a legitimate RFI from one being used strategically against me as the owner?
A legitimate RFI points to an actual ambiguity or conflict in the documents, like a structural beam depth that does not leave room for the specified ceiling height, or two drawing sheets that specify different products at the same location. What is not a legitimate RFI is a request framed as clarification but actually asking to get paid for scope that was already included in the original contract, or a question raised mainly to build a paper trail for a future delay claim. If you are seeing a high volume of RFIs, it is worth asking your GC to separate genuine coordination questions from the rest.
What should I be asking my GC about their RFI process to protect my schedule?
Ask what their average RFI response turnaround time has been on your project, since they should already be tracking this, and ask who specifically is responsible for following up on open items before the contract review period expires. Ask how many RFIs are currently open past their due date, and specifically whether any open RFIs are affecting critical path work, since that is the question that actually determines whether your schedule is at risk. A GC who cannot answer these with real numbers is not managing RFIs the way they should be.