RFI in Construction: Request for Information — Process, Format & Importance

No matter how carefully drawings and specifications are prepared, every construction project produces moments of doubt on site. The drawing shows one bar diameter, the bar bending schedule shows another. The specification names a material, but the approved vendor has discontinued it. A detail is simply missing.

A Request for Information (RFI) is the formal, documented way to resolve such doubts. It is the contractor’s structured question to the consultant or client, asking for the clarification needed to proceed. Used well, the RFI keeps work moving and protects everyone. Used badly, it becomes a source of delays, disputes, and paperwork for its own sake.

This article explains what an RFI is, when to raise one, what it must contain, how it moves through a project, and how to keep the process honest.

What Is an RFI?

An RFI is a formal project communication in which one party asks another party for information or clarification that is missing, unclear, or contradictory in the contract documents — drawings, specifications, BOQ, or prior correspondence.

It is not a complaint, not a claim, and not a request to change the work. It is a question with a paper trail. That paper trail is the point: a verbal instruction given on site is forgotten, denied, or remembered differently by two people. A logged RFI with a written response is a permanent part of the project record.

RFIs are raised most commonly by the contractor (or subcontractor) and answered by the consultant — the engineer, architect, or resident supervision team. On smaller projects, RFIs may pass through the client’s project manager.

When Should You Raise an RFI?

Raise an RFI whenever the contract documents do not give you a clear, single answer to what to build, with what, or how. Typical situations include:

• Conflicting information — the structural drawing shows 16 mm bars in a beam, but the bar bending schedule says 12 mm. Both documents cannot be right.
• Missing details — a drainage detail is referenced on the plan but the referenced sheet does not exist, or a connection detail is marked “by others” with nobody identified.
• Ambiguous specifications — the specification says “approved equivalent” but the approval process and criteria are not defined.
• Unbuildable design — the designed sequence cannot be physically constructed in the available space, or a specified product does not fit the actual site conditions.
• Unforeseen site conditions — rock is found where the soil report indicated soft clay, and the foundation design needs review.

The key rule is timing: raise the RFI the day you find the problem, not the day you need the answer. The consultant needs time to respond, and work that stops while waiting is expensive.

Key Components of an RFI

A useful RFI contains exactly one question. Trying to pack three problems into one RFI guarantees a slow, confused response. Every RFI should include:

Component	What it contains
RFI number	A unique sequential reference (e.g. RFI-048) assigned from the project RFI log
Project information	Project name, contract number, location, and the issuing party
Reference documents	The specific drawing numbers, specification clauses, or BOQ items the question relates to, with revision numbers
Location of the issue	Where on site the problem occurs — grid lines, chainage, room or level
The question	A single, precise question. “Please confirm whether the beam bars should be 12 mm as per BBS or 16 mm as per drawing STR-04 Rev C.”
Proposed solution	The contractor’s suggested answer — this is good practice and often speeds up the response
Date raised	The date the RFI is issued
Date response required	The date by which an answer is needed to avoid delay, linked to the programme
Attachments	Marked-up drawings, site photographs, relevant clauses — anything that makes the question unambiguous
Response	The consultant’s written answer, with the name and signature of the responder
Status and dates	Open / answered / closed, with dates, tracked in the RFI log

The proposed solution deserves emphasis. An RFI that says “the two drawings conflict — please advise” puts all the work on the consultant. An RFI that says “we propose to follow STR-04 Rev C with 16 mm bars, pending your confirmation” gives the consultant something to approve, often in hours rather than days.

The RFI Workflow

On a typical project, the RFI follows this path:

1. Identification — the site engineer or foreman finds an issue in the documents or on site and reports it.
2. Checking — the site engineer first searches the contract documents. Many RFIs die here because the answer was already in the specifications. Only genuinely unresolved questions become RFIs.
3. Drafting — the RFI is written with one question, references, a proposed solution, and the required-by date.
4. Logging — the RFI is entered into the project’s RFI log (a spreadsheet or project-management software) with a unique number and status “Open”.
5. Issue — the RFI is sent to the designated recipient, usually the consultant’s resident engineer or the client’s project manager.
6. Routing — the recipient forwards it to the right specialist: structural questions to the structural designer, architectural questions to the architect.
7. Response — the specialist answers in writing, sometimes with a revised sketch or drawing.
8. Distribution and close-out — the response is logged, distributed to the site team, and the RFI status is updated to “Closed”. If the response changes the work, it may become the basis of a variation order or claim.

Response-Time Norms

The contract should state how quickly RFIs must be answered, and it usually does — seven days is the figure written into many contracts. In practice, an industry study by Navigant found average RFI reply times of 6 to 10 days depending on region and project size.

A practical approach that many project managers use:

• Critical RFIs (work has stopped, safety is involved): 24–48 hours
• Urgent RFIs (work will stop within days if unanswered): 3–5 days
• Routine RFIs (advance clarification, no immediate impact): up to 7–10 days

If you mark every RFI “urgent”, none of them are. Prioritise honestly, and escalate the ones that genuinely threaten the programme — preferably with a reminder referencing the required-by date you set when you raised it.

Sample RFI Log

The RFI log is the management tool. A simple but complete log looks like this:

RFI No.	Date Raised	Raised By	Subject	Reference Documents	Required By	Status	Date Closed	Response Summary
RFI-045	12-Mar	Site Engr (Contractor)	Bar diameter conflict, beam B4	STR-04 Rev C, BBS Sheet 7	18-Mar	Closed	17-Mar	Use 16 mm per STR-04 Rev C; BBS to be revised
RFI-046	14-Mar	Site Engr (Contractor)	Missing drainage detail at chainage 1+250	DRG-DR-11	21-Mar	Open	—	—
RFI-047	15-Mar	Subcontractor (MEP)	Slab opening conflict, Level 2	ARC-02, MEP-03	20-Mar	Open	—	—

A log like this, reviewed in every site meeting, does two things: it stops RFIs from being quietly forgotten, and it makes the cost of slow responses visible to everyone.

Tips to Avoid RFI Abuse

RFIs are sometimes misused, by either side. Watch for these patterns:

• The cover-up RFI — raised to create a delay on paper when the real cause is the contractor’s own poor planning. The giveaway is a question that the documents clearly answer.
• The fishing RFI — asks for information that amounts to a design change disguised as a clarification, hoping for an answer that justifies extra payment.
• The silent treatment — the consultant lets RFIs sit unanswered, then blames the contractor for not following up. The required-by date and the meeting log are the contractor’s defence.
• The verbal-only answer — the consultant answers on site or by phone and the RFI stays open. Always get the response in writing and logged, even if it only confirms what was said.

The best protection against all four is the same: one question per RFI, everything in writing, everything logged, and regular review in site meetings.

How RFIs Relate to Variations and Claims

An important distinction: an RFI itself does not change the contract. But the response to an RFI can trigger a change.

• If the response confirms what was already in the documents, nothing changes.
• If the response instructs additional or different work — a revised detail, a new material, extra excavation — that instruction is a variation, and it should be documented and priced under the contract’s variation clause.
• If a late or missing response delays the work, the contractor may have grounds for an extension of time claim.

This is why the paper trail matters. A logged RFI with dates is the evidence that ties a delay or an extra cost to its cause. Projects without RFI discipline almost always struggle to settle final accounts.

Frequently Asked Questions

Is an RFI legally binding?
Not in itself. It is a question. But the written response, once the contractor acts on it, becomes part of the project record and can effectively modify how the contract is executed — so both sides should treat responses with care.

Can a consultant reject an RFI?
Yes. If the answer is clearly in the contract documents, or the question falls outside the consultant’s responsibility, a fair response is “refer to specification clause X” or “noted — no change”. That is still a response and still gets logged.

How is an RFI different from a variation order?
An RFI asks a question; a variation order instructs a change to the work. An RFI response may lead to a variation order, but the two are separate documents with separate approvals.

Should subcontractors raise RFIs directly?
Usually not. Subcontractor questions should go through the main contractor, who checks them and issues a single, coordinated RFI. Direct RFIs from five subcontractors on the same issue are a coordination failure.

Final Thoughts

The RFI is the most underrated document on a construction site. It costs little, it prevents disputes that cost a great deal, and it forces both sides to be precise about what they mean. The habit is simple: one question, in writing, with a reference, a proposed solution, and a date. Every project that adopts it works more smoothly than the one that relies on memory and phone calls.

---

Written by Mohsin Raza Adil — BSc Civil Engineering Technologist (NTC-registered), Pakistan.