RFI in Construction: Meaning, Process, and 7 Examples

An RFI in construction is a written request asking the owner or design team to clarify something your plans and specs don't answer. It takes minutes to send, and it gets expensive when the answer stalls.

We went through research covering more than 1,300 projects, plus the RFI procedures public agencies hand contractors, to find what separates a fast answer from a three-week stall. 

Here's the full process, seven examples set on commercial paving and concrete jobs, and the habits that keep answers from dying in an inbox.

What Is an RFI in Construction?

RFI stands for Request for Information. On a construction job, it travels from the prime contractor to the owner, engineer, or architect, and it asks for an answer: what the contract documents mean, or how to fix an error or gap in them.

An RFI also documents what you asked and what you were told, with dates on both. 

Two years later, when somebody wants to know why the north lot got 4 inches of binder when the plan sheet showed 3, your RFI log settles the argument in about thirty seconds.

On jobs that use the AIA A201 general conditions, sending one isn't optional. A201 requires the contractor to report any errors, inconsistencies, or omissions it finds in the documents to the architect as a request for information. 

Spot a problem, skip that step, and Section 3.2.4 makes you pay the costs that reporting it would have avoided.

Why RFIs exist in the first place

On most commercial jobs, the work is designed by one team and built by another. The architect draws it, the engineer details it, you build it, and all three of you work from different desks. 

The RFI grew out of that split, then turned into a formal document from the 1970s on, after two decades of rising claims and the arrival of professional liability insurance pushed everyone to start writing things down.

Bid documents are never finished documents. By the time you run a takeoff and start staking the job, you've studied those plans harder than anyone who drew them. That's why contractors find the gaps, and why the questions land on your desk first.

Who submits an RFI and who answers it

The prime contractor submits the RFI. Subs, suppliers, and vendors send their questions up to the prime, so if you're paving under a GC, your RFI goes to the GC first. One job, one numbered log. 

The owner's design professional answers it, and A201 Section 4.2.14 puts the architect on the hook to respond in writing inside whatever time limit the contract sets, plus issue supplemental drawings when the answer calls for them.

Public work follows the same shape with different paperwork. Los Angeles, for example, sets its RFI procedures at the preconstruction meeting and routes every RFI through the city's own electronic system. 

Either way, your document management has to be tight enough that the response reaches the field before the crew does, and document control keeps everyone working from the current revision.

How this differs from an RFI in procurement

Two documents share the same three letters, and they sit at opposite ends of a project. 

The RFI in construction covered here clarifies contract documents on a job already underway. In procurement, an RFI goes out before anyone buys anything: the owner uses it to gather information on available contractors and options, then follows up with a formal RFP.

What Triggers an RFI on a Paving Job

Most RFIs trace back to the same handful of gaps. Researchers studying Wisconsin highway projects sorted them into 14 categories. On paving and concrete work, watch for these five:

1. Plan and spec conflicts: the plan sheet calls for 3 inches of surface course, and the spec section calls for 4, and you need the owner to confirm which one controls.
2. Differing site conditions: you open the subgrade and find something the soils report never mentioned. A201 Section 3.7.4 requires prompt notice to both the owner and the architect before you disturb those conditions, and no later than 14 days after you first spot them.
3. Missing dimensions and details: no slope callout on the ADA landing, no detail for the curb transition at the existing gutter, no elevation at the tie-in.
4. Utility conflicts: a valve box, storm inlet, or unmarked service line sits exactly where the new curb line goes.
5. Substitutions and constructability: the specified mix isn't produced within trucking distance, or the detail won't go in with the equipment the site allows.

Some of those answers come back carrying extra scope, and that scope belongs in a change order before your crew touches it.

In a study of highway contracts, reviewers classified 13.2% of RFIs as unjustifiable, a category that includes questions whose answer already sat in the contract documents. 

That's roughly one question in eight that never needed asking, and it earns you a reputation nobody wants. Catching those questions before bid day costs you nothing. AIA's best-practice advice, as summarized in Navigant's RFI report, includes holding a second pre-bid meeting about 10 to 14 days before bids are due. 

That meeting is where a sharp estimator raises them, so build it into your bidding workflow.

The RFI Process in Construction: Step by Step

Eight steps take an RFI from the first read of the plans to a closed loop in the field:

1. Read the documents first: Plan sheet, spec section, addenda, general conditions. If the answer already sits in there, you've saved everyone a day and kept your credibility.
2. One question per RFI: Navigant's recommended owner clause limits each request to a single subject, and for good reason. Three questions in one RFI means all three wait on the slowest answer.
3. State your own interpretation: Say what you believe the documents require and why. Best case, the response agrees with you and tells you to proceed, which closes the door on a dispute before it opens.
4. Give a real date: Tie your response deadline to a schedule activity with a calendar date on it. Navigant's model RFI form rules out "ASAP" as a response date.
5. Flag cost and time impact: Yes or no, your estimate, and the activity it touches. That one field decides whether a reviewer triages your RFI or buries it.
6. Submit through the contract channel: Sequential numbers, one system, no side texts to the inspector. A verbal yes from the inspector is worth nothing when the pay app gets questioned. 
7. Watch it against your float: An RFI sitting on an activity with two days of float is a completely different animal from one on a task nobody touches until August, and the first kind needs a phone call to go with the paperwork. Good project tracking shows you which is which before it bites.
8. Close the loop same day: Send the answer to the foreman, mark up the plans, and update your quantities if they moved.

That last step trips up more contractors than any other. An answer that reaches the office and stops there does nothing for the guy holding the screed. 

Fold each clarification into the project plan and the as-builts too, and your closeout package builds itself. Skip it, and December turns into a three-week scavenger hunt through old email.

What RFIs Cost You

Navigant Construction Forum's 2013 report, which analyzed 1,362 projects and more than a million RFIs, estimated from design-firm interviews that reviewing and answering a single RFI runs about $1,080 in administrative and technical time. The typical one eats about eight hours of somebody's day.

Then there's the clock. The median reply time in that data set came to 9.7 days, with first replies averaging 6.4 days. On projects with 100 to 200 RFIs, about 28% never got an answer at all, against roughly 18% once a job passes 500 RFIs, and Navigant calls a pile of unanswered RFIs a leading indicator of fundamental problems with the project.

Bigger jobs generate more RFIs, but smaller jobs generate more RFIs per dollar. 

Projects between $5 million and $50 million averaged 17.2 RFIs per $1 million of construction cost, against 1.1 per million on $1 billion to $5 billion work. A $2 million lot reconstruction falls below even the smallest bracket, so if the trend holds, plan for plenty of RFIs.

Road work has its own rhythm. A study of 18 highway contracts in southeast Wisconsin averaged about 94 RFIs per contract and a 7.1-day average response, with only about two-thirds answered inside the window the contractor asked for. 

By the halfway mark, those contracts had typically issued about three-quarters of all their RFIs, so the questions arrive early and heavy.

The bigger damage happens in the field: a paving crew standing on a subgrade nobody will sign off on, a curb built to the wrong detail, or a response that quietly adds scope you never priced.

RFI vs Change Order and Submittal

Contractors mix these three up constantly, and the mix-up costs money.

RFI vs change order

An RFI asks a question, while a change order changes the deal. An RFI response on its own moves neither your contract price nor your schedule. When the answer calls for a design change, the City of Los Angeles' construction procedures say a change order has to follow. 

A201 also requires written notice from you when a response adds work. Build the extra first and argue later, and you can end up on the hook for the cost.

RFI vs submittal

A submittal proves compliance, and an RFI asks what compliance means. Your mix design, gradation reports, and pipe data are submittals showing how you'll deliver what the spec already requires. 

Filing those as RFIs inflates your own log. In one claim Navigant reviewed, roughly 500 of 4,000 alleged RFIs turned out to be submittals and shop drawings, and another 1,700 were routine project correspondence.

7 Examples of an RFI in Construction

Here's what an RFI in construction looks like on commercial paving jobs, plus what to attach so the answer comes back the first time.

1. Subgrade doesn't match the soils report

You strip the existing lot and find wet, pumping material where the geotechnical report showed compactable subgrade. 

Ask whether the owner wants undercut and stone backfill or a stabilization approach, and how they want the extra quantity measured. Attach proof roll photos, station numbers, and the report page.

2. Plan thickness conflicts with the spec section

The typical section shows 2 inches of surface and 4 inches of binder. Division 32 calls for 5 inches of binder. 

Ask which document controls, state your read of the order of precedence in the general conditions, and price both depths (our free asphalt tonnage calculator gives you the tons at each one) so the answer can move straight into a change order.

3. Specified mix isn't available locally

The spec names a mix design no plant within 45 minutes produces. Ask if the owner will accept the closest equivalent and how they want it submitted. Attach the local plant's mix design and gradation, note the haul time difference, and estimate how many trucks the longer haul needs. 

Send this one weeks ahead of paving, because the formal substitution request that follows usually travels as its own document under its own contract clause.

4. ADA ramp won't work as drawn

The plan puts a ramp between two fixed elevations, and holding both produces a running slope over 8.3%, the ADA maximum for ramps. 

Ask for a revised layout or a new grade break location. Include your shot elevations, because this answer needs a designer to redraw something and it rarely comes back fast.

5. Curb transition detail is missing at the tie-in

New curb and gutter meets 30-year-old existing curb sitting an inch and a half low, and the sheet shows no transition detail. Ask for one and propose a taper length based on what you've built before. Attach a photo with a tape in the frame.

6. Utility conflict shows up during excavation

Excavation for the new island exposes an unmarked irrigation line the plans never showed. Ask who relocates it and whether the island shifts. Put the daily impact right in the RFI, because this one usually stops a crew where it stands.

7. Phasing won't work with the owner's access requirements

The plans show full-depth removal across the whole drive aisle, and the tenant's lease requires two-way access during business hours. 

Ask for approved phasing or written permission for night work, and propose a phase plan yourself. Owners approve a plan they can picture far faster than they answer an open question.

What to Include in an RFI

Owner and agency RFI forms all look a little different, but they ask for the same core fields. Fill in every one, and the reviewer has nothing to send back.

• RFI number and date: The next number in your log and the day it goes out.
• Subject: One line naming the conflict, so anyone can find it in the log later.
• References: Every drawing and spec location the question touches.
• Question: A single question someone off-site could follow from the RFI and its references alone.
• Proposed answer: Your reading of the drawings and specs, so the reviewer can simply confirm it.
• Impact: Whether the answer moves your price or your dates, even when the honest answer is "none."
• Answer needed by: A calendar date tied to the work it holds up.
• Attachments: Field photos, plan markups, and any pricing that backs up the impact.
• Response block: Space for the reviewer's answer, name, and date.

Sample RFI for a binder thickness conflict

Here's Example 2 written up as a full RFI. The project details are illustrative, so swap in your own sheet numbers, dates, and log number.

• RFI number and date: RFI 014, sent February 24
• Subject: Binder course thickness, typical section vs spec
• References: Sheet C-501, Typical Pavement Section; Section 32 12 16, Asphalt Paving
• Question: Sheet C-501's typical section calls for a 4-inch binder course under the surface course, but the asphalt paving spec requires 5 inches. Which binder thickness controls?
• Proposed answer: Our contract's order of precedence puts the specifications ahead of the drawings, so we plan to place the thicker binder course unless directed otherwise.
• Impact: Yes. The added inch increases binder tonnage across the full lot, and both depths are priced on the attached sheet. Binder paving starts March 17.
• Answer needed by: March 10, a week ahead of the binder lift
• Attachments: Marked-up Sheet C-501, the spec page, and pricing for both depths
• Response block: Left blank for the engineer of record

How to Write an RFI That Gets a Fast Answer

Reviewers answer clear questions quickly and vague ones eventually. Six habits keep your questions in the first group:

• Give reviewers two weeks, plus a buffer: Navigant suggests giving the design team 10 working days, about two calendar weeks, to respond. Send the RFI early enough that the answer lands with a few days to spare.
• Point to the exact document: Sheet number, detail number, spec section, paragraph. Never make a reviewer hunt for what you're looking at.
• Attach one good photo: A marked-up plan snip or a field photo with a tape in it removes half the back-and-forth.
• Skip the batching: Ten RFIs dropped at once on a Friday afternoon become one stack in somebody's queue, and the whole stack moves at the speed of the hardest question in it.
• Write it for a stranger: Someone three offices away from your job may be the one answering, and they can't see what you see.
• Know your contractual clock: Chico, California, commits to five business days, and Wisconsin DOT sets a seven-day response goal on its Milwaukee-area freeway projects. Knowing the number tells you when to escalate, and hoping tells you nothing.

RFI Mistakes That Eat Your Margin

Some contractors flood a job with RFIs to establish that the design was incomplete. Courts don't take the count at face value. 

In Caddell Construction Co. v. United States, the judge held that a large volume of RFIs proved nothing on its own, and that the requests had to cumulatively demonstrate a serious deficiency in the plans to support a claim.

Working off a verbal answer leaves you nothing to point to later, and written RFI responses carry real contractual weight. In Metric Construction Co. v. United States, the Court of Federal Claims found that the Army Corps' answer to one RFI "permits a variety of interpretations" and misrepresented how the roof joist girders would perform. Together with a defective specification, that earned the contractor an equitable adjustment of about $1.32 million. 

Then there's the quiet one. RFIs that sit unanswered while the crew keeps moving turn into rework you eat yourself. 

Rework on a paving job costs the tonnage, the mobilization, the crew day, and the slot that job was holding in your schedule, and all of it comes straight out of your margin on work you already bid tight.

How to Track RFIs Without Living in Your Inbox

A spreadsheet works right up until the job gets busy. Then the version on the PM's laptop stops matching the one your estimator opens, and the log turns into archaeology.

A workable RFI log needs 10 fields: a sequential number, the question, the sheet or spec reference, the schedule activity affected, the cost and schedule impact, a priority, the date submitted, the date the response is due, the response itself, and the date it landed. 

Categorize each one as you log it, too. A log showing 40 requests all pointing at drainage details tells you the drainage sheets are the weak spot in the plan set.

Here's a metric worth stealing. Researchers in a 2012 lean construction paper built a Forward Thinking Index that measures how far ahead a contractor asks its questions: total RFIs minus the delay-causing ones, divided by total RFIs. 

Two hundred RFIs with 50 causing delay score 0.750. Read it like a batting average, track it across jobs, and you'll see which PMs read plans in April and which ones get around to it in July.

Keep Every Answer, Document, and Crew Assignment in One Place

OneCrew is built for project-based commercial asphalt and concrete paving contractors who can't afford a stalled RFI. It connects the estimate, schedule, work orders, and invoice on every project, so when an RFI answer changes the job, a change order credits back services or adds new ones and the project's financials update with it. 

Here's what it covers:

• Price straight from the plans: OneCrew's estimating tools let you measure jobs on satellite maps or uploaded blueprints and automatically calculate tonnage, materials, and trucks.
• Reshuffle crews when answers run late: OneCrew's scheduling feature assigns specific crew members and equipment to individual services and splits multi-phase projects across weeks or crews so your office and field see the same plan at the same time.
• Keep the field on the latest answer: The field management tools push mobile work orders to crew phones with services, quantities, site maps, and equipment assignments. Crews send time, field photos, and production data back to the office as work happens.
• Spell out scope up front: OneCrew's proposal feature generates professional, branded proposals directly from your estimate with custom sections for scope notes and your standard terms attached.
• Log every RFI with the job: OneCrew's project log keeps a timestamped record of comments, @mentions, and uploaded files, and every attachment also lands in the project's Documents tab, ready to add to the crew's work order.
• Know every customer and site: OneCrew's CRM keeps accounts, contacts, and job sites as their own records, so each location's work history stays with the site.
• Bill every approved change: OneCrew's invoicing tools generate invoices from the line items already in the platform, including any accepted change orders, and sync invoicing and payment data with QuickBooks in both directions.

You need one place where the question, the answer, and the crew that has to act on it all live together. Book a Demo and see how OneCrew keeps your projects moving from takeoff to final invoice.

FAQs

1. What does RFI stand for in construction?

RFI stands for Request for Information. In construction, it names the formal written question a contractor sends the owner or design team to clarify or interpret a requirement in the plans, specifications, or contract documents.

2. Who is responsible for answering an RFI in construction?

The owner's design professional answers an RFI in construction, usually the architect or engineer of record. The prime contractor submits it, and subcontractors and suppliers route their questions through the prime so the job keeps one numbered log.

3. How long does an RFI take to answer?

The typical RFI gets answered in just under 10 calendar days. Research across 1,362 projects found a 9.7-day median for answers, with first replies averaging 6.4 days, and Navigant recommends a 10-working-day response window.

4. Does an RFI change the contract price or schedule?

No, an RFI on its own changes neither the price nor the schedule, because it only clarifies what the documents already require. If the response adds scope or time, give written notice before you perform the work, and get the change formalized through a change order or, when the price isn't agreed yet, a construction change directive.

5. What should an RFI include?

An RFI should include a sequential number and date, a one-line subject, the exact drawing and spec references, one clear question, and your own reading of what the documents require. It should also say whether the answer affects cost or time, plus the date the crew needs it. Attach a photo or marked-up sheet so the reviewer can answer without a second round.