What Is an RFI in Construction? Meaning, Process & Examples

Construction drawings are never perfect. Two sets of plans disagree, a detail is missing, a spec contradicts what's actually on site. When that happens, a crew can't just guess — guessing wrong means tearing out finished work. Instead, they raise an RFI: a formal, written request for the answer they need to keep building.

RFIs are one of the most common documents on any jobsite, and also one of the most mismanaged. This guide explains what an RFI is, what goes in one, how the process works, and how to stop RFIs from quietly eating your schedule.

What does RFI stand for?

RFI stands for Request for Information. In construction, it's a formal question sent from one party — usually a contractor or subcontractor — to another, usually the architect, engineer, or owner, to clarify something that isn't clear, complete, or consistent in the project documents.

The key word is formal. A question shouted across the site or buried in a text message isn't an RFI. An RFI is written down, numbered, tracked, and answered on the record — because the answer often changes what gets built, and everyone needs to be able to prove what was asked and what was decided.

Why RFIs matter

An unanswered RFI can stop a crew cold. If the team doesn't know which beam size to use, work stops until someone tells them. That makes RFIs directly tied to the three things every project lives or dies by:

• Schedule. Every day an RFI sits unanswered is a day work may be blocked. Slow RFI turnaround is one of the most common causes of construction delays.
• Cost. Building on a wrong assumption means rework — and rework is expensive. An RFI is far cheaper than tearing out a finished wall.
• Liability. A documented RFI creates a clear record of who asked what, who answered, and when. If a dispute arises later, that paper trail matters.

What goes in an RFI?

A good RFI gives the person answering everything they need to respond quickly and correctly. A typical RFI includes:

• RFI number. A unique reference so it can be tracked and cross-referenced.
• Project and location. Which project, and exactly where on the plan the question applies.
• A clear question. One specific issue, stated plainly — not five questions bundled together.
• Context and references. The relevant drawing number, spec section, or detail that's unclear or in conflict.
• A photo or markup. A picture of the actual condition on site removes all ambiguity.
• A proposed solution. Often the contractor suggests an answer ("we propose to use X") to speed things up.
• A date needed by. So the recipient knows the urgency and the impact on the schedule.

The best RFIs are specific and answerable. "There's a problem with the foundation plan" forces a back-and-forth. "Detail 4/S-201 shows a 600mm footing but the structural notes call for 800mm — which governs?" can be answered in one reply.

The RFI process, step by step

1. Identify the gap. Someone on site or in the office spots a conflict, omission, or unclear instruction in the documents.
2. Write the RFI. The question is documented clearly, with references, a photo, and ideally a proposed answer.
3. Submit and log it. The RFI is given a number and sent to the right party — usually the architect or engineer.
4. Review and respond. The recipient researches the issue and provides an official answer.
5. Distribute the answer. The response goes back to everyone affected, so the whole team builds to the same decision.
6. Close and file. The RFI is marked answered and kept on record. If the answer changes cost or scope, it may trigger a change order.

RFI vs. submittal vs. change order

These three documents are easy to confuse, but each does a different job:

• RFI — asks a question to clarify the documents ("which detail governs?").
• Submittal — proposes a product or material for approval before it's installed ("here's the window we plan to use; please approve").
• Change order — formally changes the contract's cost or schedule ("this revision adds €4,000 and three days").

They're often connected. An RFI answer can reveal that the original scope won't work, which leads to a change order.

Common RFI mistakes

• Vague questions. An RFI without a specific reference and location triggers a slow back-and-forth instead of a fast answer.
• Bundling issues. Five unrelated questions in one RFI means it can't be closed until all five are answered.
• No tracking. RFIs scattered across email and paper get forgotten — and a forgotten RFI is a blocked crew nobody is watching.
• No deadline. Without a "needed by" date, urgent questions sink to the bottom of someone's inbox.
• No reference to the drawings. When the question doesn't name the specific drawing or detail it relates to, both sides waste time figuring out where the issue even is.

How to manage RFIs efficiently

The real cost of RFIs isn't writing them — it's tracking them. Knowing which are open, who owns the answer, how long they've been waiting, and what work is blocked behind them is where most teams lose control.

With PlanoTrak, each RFI gets its own number, subject, and question, then a priority, a due date, and an assignee. You can reference the related drawings, attach photos and PDF files straight from the jobsite, and move every RFI through a clear status — open, answered, closed. Everything syncs instantly across iPhone, Android, Mac, and the web, so the team can see at a glance which RFIs are still waiting and which work is blocked behind them, whether they're on site or in the office.

Instead of chasing answers through email and phone calls, every RFI is numbered, prioritized, assigned, and tracked in one place — with its photos, files, and status visible to everyone until it's answered.

The bottom line

An RFI is how a construction team turns "the drawings don't make sense here" into a documented answer everyone can build on. Keep each RFI specific, tie it to the exact spot on the plan, attach a photo, propose a solution, set a deadline, and track every one in a single shared place. Do that, and RFIs stop being a hidden source of delay and become what they're meant to be: the fastest way to get an answer and keep building.