A construction Request for Information (RFI) is a formal record used to clarify missing, conflicting, or ambiguous information in drawings, specifications, or site conditions. It keeps the question, references, response, and responsibility in one traceable transaction instead of leaving a technical decision in an email thread or site conversation that may be difficult to retrieve later.

When should you use a construction RFI?

Issue an RFI when the project documents do not provide enough information to execute the work confidently: a missing dimension, a conflict between drawings, a specification that disagrees with a detail, a site condition that differs from the record, or an unresolved interface between architectural, structural, mechanical, and electrical work.

Before issuing it, the general contractor should check the contract, current drawings, specifications, approved submittals, and earlier responses. This internal review filters out duplicate requests and questions already answered in the documents, keeping the RFI log focused on decisions the project team actually needs.

What should a construction RFI include?

The approved project template governs the final fields, but an answerable RFI will usually include:

A unique number, issue date, sending organisation, and party responsible for the response.
A precise title and one answerable question, rather than a bundle of unrelated topics.
Exact references to the drawing number and revision, specification section, and affected location or area.
A marked-up attachment showing the conflict, such as a drawing extract, site photo, or explanatory sketch.
A proposed solution when the project procedure permits one, with alternatives presented neutrally and without assuming approval.
The required response date and any potential time or cost effect, stated in accordance with the project procedure and contract.

The construction RFI workflow, step by step

The site team records the missing or conflicting information, and the contractor checks internally that the answer is not already in the project documents.
The subject owner drafts the RFI, document control reviews it, and the request receives a unique number in the central register.
It follows the project route to the consultant, who assigns it to the relevant architect, engineer, or design authority.
The responsible party checks the question and references, coordinates with the owner or another discipline where needed, and issues a written response tied to the request.
The contractor verifies that the response resolves the question and distributes it to the affected site team and subcontractors.
An incomplete response returns for clarification without closing the record. A complete response closes the RFI with the question, answer, and attachments preserved in the audit trail.

What if the response affects time or cost?

An RFI records a question and its answer, but it is not automatically a change order, approval of additional cost, or extension of time. If the response reveals a scope change or a schedule or cost effect, open the notice, change, or claim process required by the contract and link it back to the original RFI number.

RFI vs other construction documents

RFI vs submittal

An RFI asks for clarification of a gap or conflict. A submittal presents a material, piece of equipment, shop drawing, or other technical proposal for review and approval. If the question concerns an earlier submittal, link the RFI to that submittal number and revision.

RFI vs NCR

An RFI usually seeks clarity before work proceeds. A Non-Conformance Report records work or material that does not meet a requirement and needs containment, correction, and verified closure.

RFI vs notice or change

An RFI documents the need for information. A contractual notice preserves a right or reports an event, while the change process evaluates scope, time, and cost under the required authority. An RFI should not be used as a substitute for either one.

How to manage a construction RFI log

For every RFI number, the register should show the subject, discipline, location, date sent, respondent, due date, status, response and closure dates, potential impact, and linked records. Simple statuses such as Draft, Open, Under Review, Answered, and Closed show where the request stands without creating overlapping labels that confuse the team.

Track overdue open requests, average response time, and distribution by discipline and area. Do not read volume alone: a high RFI count can indicate incomplete design, or it can reflect good coordination that identifies issues early. Review cause and impact together.

Common mistakes that delay RFI responses

Using a broad title such as “drawing problem” without asking a specific question.
Combining structural, mechanical, and architectural questions in one request.
Attaching a drawing without its revision or without marking the location of the conflict.
Routing a subcontractor request directly to the designer outside the authorised project chain.
Proceeding with a proposed solution before an authorised response, then treating the RFI as retroactive approval.
Closing the request as soon as any response arrives, without checking that it resolves the question and reaches everyone who must build from it.

Construction RFI checklist before submission

Have we checked the latest drawings, specifications, submittals, and earlier RFIs?
Does the record ask one precise, answerable question?
Have we identified document numbers, revisions, location, and a clear markup?
Have we stated the response date and potential impact under the contract?
Will the request and response follow the authorised route and remain in one controlled record?

Good RFI control starts with control of every document around it. Review the construction document management guide, understand the contractor-consultant-owner approval chain, or book a working demo to review your project register.