A single unanswered RFI can stall a crew for a week and cost more than the change order that follows it. That’s what is an RFI in construction in practical terms: a formal question, not paperwork for its own sake.
If you run jobs, you already know the acronym. What trips people up is the discipline around it. When do you file one? How do you word it? And what happens if nobody answers in time?
What Is an RFI in Construction: The Core Definition
Definition: An RFI (Request for Information) is a written document a contractor, subcontractor, or sometimes the architect uses to ask for clarification on plans, specs, or site conditions that are unclear, missing, or in conflict. It creates a dated, trackable record of the question and the answer.
An RFI is not a change order. It’s not a submittal. It’s not a way to complain about a bad detail sheet, though plenty of superintendents use it that way anyway.
The format is simple on paper. You get a number, a date, and a question. Then comes a reference to the drawing or spec section, plus a space for the response. Most jobs run them through Procore or PlanGrid now, but the paper trail concept is older than any of that software. You’re asking the design team to fill a gap in the contract documents before you build something wrong.
The real value is legal, not just logistical. A logged RFI with a response date proves you didn’t guess. Say the architect’s answer causes a delay or added cost. That RFI becomes your backup when you go after a change order or a time extension.
When an RFI in Construction Belongs on the Log
Not every question deserves an RFI number. File one when the drawings conflict with each other. A spec section that references a discontinued product is another trigger. So are field conditions that don’t match the plans – say, a buried utility line missing from the civil set.
Skip the formal RFI for things a quick phone call or a site visit from the architect can fix. Burning the log with minor coordination questions slows down everyone’s ability to find the ones that matter.
Here is a real example. A crew pours a slab and checks the rebar schedule. One detail calls for #5 bars at 12 inches on center. The general notes say 18 inches. That’s a conflict between contract documents, not a judgment call. It goes on the RFI log, and you hold the pour section until you get an answer in writing.
Compare that to a sub asking which hand the door swings on a roughed-in closet that isn’t on a finish schedule yet. That’s a coordination question better handled in a quick field meeting, not a seven-day wait for formal review.
What Goes Into a Well-Written RFI
Weak RFIs get weak answers, or worse, no answer for two weeks because the architect bounces it back asking for clarification on your clarification request. A good RFI gives the reviewer everything they need to answer in one pass.
Include the spec section or drawing number and the specific conflict or gap. Add a photo if it’s a field condition. Then add your proposed solution, the part most contractors skip. Architects move faster when they can just write “approved as noted” instead of starting from zero.
Date every RFI the day it’s written, not the day it’s logged. Take a commercial job running Procore’s RFI module. A tightly written question with a photo and a suggested fix usually comes back fast. Three to five business days is typical. A vague one-liner can sit two to three weeks.
Want a deeper walkthrough on structuring the question? See this breakdown on writing, logging, and closing RFIs fast. It covers wording templates that get faster architect responses.
How an RFI in Construction Affects Your Schedule and Bid
Every open RFI on critical path work is a clock running against your completion date. Superintendents who track RFI turnaround as a schedule metric, not just a paperwork metric, catch slippage before it becomes a three-week delay claim.
Standard AIA contract language gives the architect a reasonable time to respond. That window is often referenced as 7 to 14 calendar days, depending on the contract. It varies by project, so confirm it in your specific agreement rather than assuming. Bidding work with a tight schedule? Build float around known RFI-heavy trades. Those include structural steel connections, MEP coordination in tight ceilings, and anything involving existing conditions on a renovation.
On the estimating side, factor RFI risk into your contingency line. A renovation job with incomplete as-builts will generate more RFIs than new construction on a clean site. Estimators who’ve been burned before carry 1-2% extra contingency on gut renovations specifically for the delay and rework that stacks up from field-discovered conflicts.
Here’s the part worth saying plainly. Some contractors treat RFIs as a nuisance instead of a schedule tool. Those are the ones who eat the float themselves. Log it, track the response clock, and escalate before the delay becomes yours to own.
Who Can Submit One and Who Has to Answer
On most commercial projects, the GC submits RFIs on behalf of the whole team, including subs. A plumbing sub who finds a conflict doesn’t usually email the architect directly. Instead they flag it to the superintendent. The super logs it and routes it through the proper channel.
The architect of record typically answers first, pulling in the structural or MEP engineer of record when the question touches their stamped work. This is where you draw a hard line. If the answer requires an engineering judgment call, that’s not your call to make. It isn’t the architect’s either when it falls outside their discipline. Push it to the licensed engineer of record.
Owners get copied, sometimes required to co-sign or approve RFI responses that carry cost implications, depending on the contract. Public work often runs through a construction manager or owner’s rep who logs every RFI and tracks response time against contract requirements, since public agencies face scrutiny over delay claims more than private owners do.
Know your project’s specific RFI matrix before the job starts. It should be spelled out in the contract or the pre-construction meeting minutes, not something you guess at in week six.
Common Mistakes That Blow Up RFI Logs
Bad habits around RFIs cost real money and real time. Here’s where crews and PMs consistently go wrong:
- Burying the question in a paragraph of context. Reviewers skim. State the conflict in the first sentence, then give background.
- Not referencing the exact drawing or spec section. “The detail doesn’t match the plan” means nothing without a sheet number.
- Treating RFIs as free change-order requests. If you already know the answer and just want a price bump, that’s a change order, not an RFI – mixing the two erodes trust with the design team.
- Letting the log go stale. An RFI sitting open for three weeks with no follow-up call is a PM failing to manage the critical path, not just a slow architect.
- Skipping the proposed solution. Architects are busier than your schedule; give them a yes/no option whenever you can instead of an open-ended question.
- No photo or markup on field-condition RFIs. A marked-up PDF or a dated jobsite photo turns a confusing description into a five-minute answer.
Most of these come down to the same root problem: writing the RFI like a complaint instead of a request for a specific, answerable decision.
Where an RFI in Construction Fits Into the Bigger Picture
An RFI is one piece of a bigger communication system that includes submittals, change orders, and daily reports. Treat it as the mechanism for resolving ambiguity before it becomes rework, not as a tool for documenting blame after the fact.
The contractors who manage this well build the habit into daily operations: review the open RFI log every morning, call the architect’s office if something’s been sitting more than a week, and never let an unanswered question stop work on critical path items without first documenting the delay. That discipline is what separates a clean closeout from a dispute that drags into a claim.
If you’re new to the term or training a green PM on the process, start with the basics of what an RFI actually means in a construction contract context before you get into log management and turnaround metrics. Understanding the “why” behind the form makes the discipline stick.
Frequently asked questions
What is an RFI in construction compared to a submittal?
An RFI asks a question about unclear or conflicting information in the contract documents. A submittal is a sample, shop drawing, or product data sheet sent for the architect’s approval before you order or install material. They’re different tools for different problems – don’t use an RFI to get submittal approval, and don’t submit a product cut sheet hoping it answers a design conflict.
Who pays for delays caused by a slow RFI response?
It depends on the contract and the specific circumstances. If the RFI reveals a genuine design conflict and the architect’s response takes longer than the contract allows, you may have grounds for a time extension or cost claim, but this requires documentation and often legal interpretation. Talk to a construction attorney before assuming you’re entitled to compensation – contract language varies too much to generalize.
Can a subcontractor submit an RFI directly to the architect?
Usually not on a typical general contracting setup. Most contracts route all RFIs through the GC, who logs and submits them to keep one clean communication channel. Check your specific contract and project procedures, since some CM-at-risk or design-build arrangements handle this differently.
How long should a GC wait before escalating an unanswered RFI?
There’s no universal number, but most experienced PMs follow up once the response is a few days past whatever the contract specifies, then escalate to a phone call or a meeting if it stretches past two weeks on anything touching the critical path. Waiting silently is the mistake – a documented follow-up protects your position either way.
Does every RFI need a drawing reference to be valid?
It’s not always legally required, but it’s the single biggest factor in getting a fast, useful answer. An RFI without a sheet number or spec section forces the reviewer to guess what you’re asking about, which almost always slows down the response and sometimes triggers a request for clarification before they’ll even answer.
