What Is an RFI in Construction? Definition, Examples and What to Include
An RFI is how a contractor asks the design team to clarify the contract documents. Here is what an RFI is for, who sends it, what a good one contains, and what it is not for.
· 5 min read
A request for information, or RFI, is a formal written question from the contractor to the design team about the contract documents. It asks the architect or engineer to clarify something the drawings and specifications do not answer clearly: a missing dimension, two details that conflict, a product that has been discontinued, or a site condition the documents did not anticipate.
RFIs are one of the most common documents on a construction project. A small fit-out may produce a few dozen; a hospital or a large mixed-use building can produce well over a thousand. Each one is a small hold on the work until it is answered, which is why how a team writes, tracks and answers RFIs has a direct effect on the schedule.
What an RFI Is For
An RFI exists to get a documented interpretation of the design before work proceeds. Most standard contracts, including CCDC 2 in Canada and AIA A201 in the United States, expect the contractor to report discrepancies it finds in the documents and the consultant to interpret them. The RFI is the everyday tool for that exchange.
Typical reasons for an RFI include a conflict between drawings, such as an architectural section that does not match the structural framing; a conflict between a drawing and the specification; information that is missing altogether; a field condition that differs from what the documents show; and a request to confirm that a proposed approach meets the design intent.
The answer becomes part of the project record. If a question later turns into a dispute about cost or time, the RFI and its response are among the first documents anyone will read.
Who Sends an RFI, and to Whom
RFIs usually flow from the general contractor to the consultant: the architect, or the engineer of record for the discipline in question. Subcontractors raise their questions through the general contractor rather than writing to the design team directly, so that one party controls the flow of information and the contract chain stays intact.
The general contractor should review each subcontractor question before sending it on. Some can be answered from the documents already on hand; others should be combined with a related question. Sending every question straight through is one of the main reasons RFI volume climbs on a project.
What a Good RFI Contains
A clear RFI can be answered without a phone call. At a minimum it should include a unique number and the date; who is asking and who it is addressed to; the drawing sheet and revision, and the specification section, it refers to; the question itself, stated once and specifically; a proposed solution, where the contractor has one; whether the contractor believes the answer may affect cost or schedule; the date by which a response is needed, and why; and photos, marked-up drawings or other attachments that show the problem.
Each RFI should ask one question. An RFI that bundles three unrelated issues is hard to route, and it stays open until the slowest part is answered. Our free RFI template has a field for each of these items, and How to Write a Clear Construction RFI covers the wording in more detail.
An Example RFI
Here is a short example of the kind of RFI that gets answered quickly.
Subject: Guardrail anchor spacing at the Level 2 mezzanine. References: drawing A-501 revision 3, detail 4; specification section 05 52 00. Question: Detail 4 on A-501 shows guardrail posts at 1,200 mm on centre, but section 05 52 00, paragraph 2.3, requires posts at a maximum of 1,000 mm on centre. Please confirm which spacing governs. Proposed solution: install posts at 1,000 mm to meet the specification. Impact: no cost impact if 1,000 mm is confirmed; fabrication is scheduled to start in two weeks, so a response is needed by the date shown.
The question cites the exact sheet, detail, section and paragraph; it states the conflict in one sentence; and it proposes an answer the consultant can simply confirm.
What an RFI Is Not For
An RFI is not the place to request a change, to propose a substitution, or to submit product information for approval. Those have their own processes. A change in scope goes through a change order or change directive. A substitution follows the procedure in the specification, usually in Division 01. Product data and shop drawings go through the submittal process; the difference is explained in RFI vs Submittal.
An RFI also should not be used to ask a question the documents already answer, or as a way to put the design team on notice of a delay without saying so plainly. If an answer is likely to cost money or time, say so in the RFI and follow the notice requirements in the contract.
How RFIs Are Tracked
Every RFI should be entered in a numbered log that shows its status, who holds it, when a response is due and when it was answered. The log is how a project team sees which open questions are holding up work, and how a project manager spots a reviewer who is falling behind. RFI Log: What to Track on Every Construction Project lists the columns that matter.
Many teams still keep the log in a spreadsheet and send RFIs by email. That works on a small project, but it breaks down once dozens of RFIs are open at the same time. Construction RFI software keeps the log, the documents and the responses in one place, and PlanSpan can draft the response from the drawings and specifications, citing the sheet and clause it relied on, for the design team to review before anything is sent.
