An RFI — Request for Information — is a formal, tracked question a contractor sends to the architect or owner to clarify something unclear, contradictory, or missing in the construction documents. It does two jobs at once: it gets you the answer you need to build, and it creates a record that protects you if that answer later causes a cost or schedule impact. For a small contractor, the RFI is one of the cheapest forms of insurance on the job — and the most common way to lose its value is to not track who owes the answer. This guide covers the RFI process end to end.
What an RFI is — and isn't
No set of drawings is perfect. The architectural plans say one thing, the structural detail says another; a dimension is missing; a specification is silent on a product you need to order. Rather than guess — and own the consequences of guessing wrong — you raise an RFI: a written question that references the exact drawing, detail, or spec section in question and asks for a documented decision.
An RFI is not a complaint, and it's not a change order. It's a request to clarify or resolve an information gap. Sometimes the answer is free (the architect points you to the right detail). Sometimes the answer reveals added scope or a conflict that leads to a change order. But the RFI itself is the question and its documented answer — and that documentation is the point. An RFI turns a hallway conversation into a record of who decided what, when, which is exactly what you want if there's a dispute later about why something was built the way it was.
Small residential builders use RFIs for the same reason large GCs do: to turn verbal agreements with owners, architects, and subs into a paper trail that protects their time, money, and reputation.
When to raise an RFI
Raise one whenever proceeding would mean guessing on something that matters. Common triggers:
- A conflict between two documents — plans vs. specs, architectural vs. structural vs. MEP.
- A gap — a missing dimension, detail, or product selection.
- An ambiguity — language that could reasonably be read two ways.
- A field condition that doesn't match the drawings.
- A substitution — you want to confirm an equivalent product is acceptable before you order it.
The judgment call is to raise it early. An RFI sent the moment you spot the gap gives the design team time to respond before the answer blocks your schedule. The same question raised the day the crew is standing around waiting becomes a delay.
How to write an RFI that gets a fast, useful answer
A vague RFI gets a vague answer, or a slow one. A good RFI is easy to say yes to:
- A unique, sequential RFI number and the date. This is how the question gets tracked.
- A precise reference — the exact sheet number, detail, or specification section the question is about. Make the reviewer's job of finding the issue trivial.
- A clear, specific question. One issue per RFI. "Does the canopy footing at grid line C-4 require the #5 rebar shown on S-201 or the #4 shown on A-410?" beats "please clarify the footing."
- Context — what you found, why it's a problem, and what it's blocking.
- A proposed solution where you have one. Architects respond faster when they can approve your suggestion rather than engineer one from scratch. "We propose following S-201 (#5); please confirm" is easy to answer.
- A needed-by date tied to your schedule, so the urgency is visible.
- Cost or schedule flag. If you believe the resolution may carry a cost or time impact, say so — it puts everyone on notice and starts the clock on any change.
The RFI process, step by step
1. Identify the unclear, conflicting, or missing information. 2. Write and submit the RFI on the project's standard form, referencing the exact document, and route it to the architect — usually through the construction manager or owner's rep, depending on the project structure. 3. The architect responds within the timeframe the contract sets — commonly on the order of one to two weeks (often expressed as something like 6 to 10 working days), though the contract governs. 4. Log the answer in your RFI tracking system, distribute it to everyone affected (your subs, your field team), and act on it. 5. Convert to a change if needed. If the answer adds scope, costs money, or extends the schedule, it flows into a change order request — and your RFI is the paper trail showing where that change came from.
The RFI log: the part small contractors skip
Writing the RFI is the easy half. The half that determines whether the process actually protects you is the RFI log — the running record of every RFI on the job: its number, the question, who it's with, when it was sent, when it's due, and its status.
The hidden failure mode is ball-in-court. An RFI goes out, and then nobody can answer the only question that matters day to day: whose desk is it on, and how long has it been there? Without that, RFIs quietly age. The architect thinks the ball is with you; you think it's with them; the schedule slips while a question sits unanswered for three weeks. When the delay claim comes, the contractor who can show "RFI 042 sent on the 3rd, still unanswered on the 24th, framing held the whole time" is in a far stronger position than the one reconstructing it from an email thread.
A good RFI log tracks ball-in-court at a glance and flags overdue items so they escalate before they become a schedule problem — not after.
A cleaner way to run RFIs
On email and spreadsheets, RFIs age out of sight — the question nobody tracked, the answer that never reached the sub, the overdue item that became a delay. Jobsite tracks every RFI from open to answered with ball-in-court visibility and overdue escalation, and cross-links each RFI to the drawing, task, or change order it touches — so nothing sits on the wrong desk for three weeks. See how Jobsite handles RFIs →
FAQ
What is an RFI in construction?
An RFI (Request for Information) is a formal, written question a contractor sends to the architect or owner to clarify something unclear, contradictory, or missing in the construction documents. It resolves information gaps before they cause rework, and it creates a documented record of the decision — which is valuable both for building correctly and for protecting yourself in a later dispute.
How long does the architect have to respond to an RFI?
It's set by the contract. A common window is on the order of one to two weeks — often expressed as something like 6 to 10 working days — but the governing number is whatever your contract specifies. Tying a needed-by date to your schedule when you submit helps keep the response on track.
What should an RFI include?
A unique sequential number and date, a precise reference to the exact drawing sheet, detail, or specification section in question, one clearly stated question, the context for why it matters, a proposed solution where you have one, a needed-by date, and a flag if you believe the answer may carry a cost or schedule impact. One issue per RFI gets faster, cleaner answers.
Is an RFI the same as a change order?
No. An RFI is a question that clarifies or resolves an information gap; a change order is a signed amendment that changes the contract's scope, price, or time. They're related — an RFI answer sometimes reveals added scope that leads to a change order — but the RFI itself is just the documented question and answer. Keeping them distinct (and linked) is part of a clean paper trail.
Why do I need an RFI log?
Because writing RFIs without tracking them is how they age out of sight. An RFI log records every RFI's number, question, status, who owes the next move (ball-in-court), and when it's due, and flags overdue items. That record is what keeps a question from sitting unanswered for weeks, and it's the evidence that supports a delay claim if an unanswered RFI holds up the work.
See how Jobsite handles this in practice: Project management on the platform →
About the author
The Jobsite Editorial Team — Construction safety & OSHA compliance
The Jobsite Editorial Team writes the safety and compliance library behind Jobsite, the construction safety, OSHA compliance, and training platform for contractors. Every article starts from the primary regulatory text — the CFR section itself, not a summary of it — and is fact-checked against that source before it publishes, so what you read here is what the standard actually requires of small and mid-size contractors in the field.