What Is an RFI in Construction? A Builder's Plain-English Guide

The drawings might show one thing while the specification says another. A dimension may be missing. Existing structure may sit exactly where the new service needs to run. The fire-stopping detail may not match the tested system. In each case, somebody on site needs a clear answer before the work can proceed safely and correctly.

The document might say one thing, but the site condition says another. That is the practical reason RFIs exist. They give the project team a visible question, a responsible respondent and a recorded answer. Without that record, the issue is often solved through calls and corridor conversations that are difficult to reconstruct later.

An RFI should not be used simply because a person has not read the documents. It should also not become a substitute for normal coordination. Good teams first check the drawings, specification, schedules, approved submittals and previous responses. If the answer is still unclear or authority is required, raise one focused RFI.

Raise an RFI when a real ambiguity prevents the team from understanding or carrying out the work. Common examples include a missing dimension, a service clashing with structure, joinery that cannot fit the documented opening, a detail that cannot physically be built, or a conflict between a drawing and the specification.

Existing projects create another category. A ceiling is opened and the existing beam is lower than the survey suggested. A wall believed to be non-structural contains bracing. Fire services, hydraulics and electrical containment compete for the same narrow route. These are not questions a trade should answer by guessing.

Compliance issues also require care. If a proposed detail appears inconsistent with a tested system, fire requirement, accessibility provision or other statutory obligation, stop and obtain clarification through the project’s authorised process. Do not use an RFI to transfer responsibility while continuing the work regardless.

The immediate temptation is to keep the trade moving. That can be the most expensive option. A guessed detail may need to be demolished and rebuilt. A service installed in the wrong zone can block following trades. A late clarification can create trade stacking, lost productivity and a programme argument that is difficult to separate from the technical issue.

The true cost is not always the physical rework. It may be the time spent working out who knew what and when. It may be a scope dispute because the question, answer and resulting direction were recorded in different places. It may be a compliance problem discovered after the area has been closed.

Not every uncertainty justifies stopping a project, but unanswered technical questions should be visible. The responsible people can then decide the risk, priority and temporary measures rather than leaving the trade to make that decision alone.

A formal process does not replace a working relationship. Architects, engineers and consultants receive too many weak RFIs. If the question is urgent or difficult, a short call can help everyone understand it. The phone call may solve the immediate problem, but it still needs a record afterwards.

The question must be easy to answer. Good site teams identify the precise clash, mark the drawing, suggest a practical option and explain the real date by which the decision is needed. That is more useful than sending a long narrative and expecting the consultant to find the question.

Some RFIs are really coordination failures. A subcontractor should not use the RFI process as the first time the builder hears about an obvious clash. Equally, the builder should not expect a trade to design around missing information without authority. The process works when each party does its checking and the remaining question reaches the right person.

The required response date should come from the construction sequence, not from a default number of days. Work backwards from the date the answer must be incorporated into procurement, fabrication, set-out or installation. If joinery needs an approved dimension before shop drawings can be released, the useful date is earlier than the day the joiner arrives on site.

Explain that logic in one sentence. “Response required by 24 July to release fabrication for the 18 August installation” gives the recipient something practical to plan around. “Urgent” does not. A clear consequence also helps the project team distinguish a genuinely programme-critical question from an ordinary clarification.

Priority should reflect the effect of waiting. A high-priority RFI may stop work, affect safety planning, hold a long-lead order or block several following trades. A lower-priority question may concern work that is weeks away or an area with an available alternative sequence. Do not mark every question urgent; doing so removes the signal the priority is meant to provide.

If the response date changes, retain the original need date and record the agreed revision rather than silently overwriting it. Escalate through the project’s communication process before the question becomes a site emergency. The RFI register should make that follow-up visible without turning a technical clarification into an accusation.

An RFI register is more than a list of numbers. At minimum it should show the subject, location, date raised, responsible recipient, required response date, current status and the action created by the answer. That lets a site meeting focus on the small number of questions that are actually affecting work.

Use statuses people understand. “Draft” means the question is still being checked. “Open” means it has been issued and awaits an answer. “Answered” means a response has arrived, but it does not necessarily mean the issue is finished. “Closed” should mean the team has understood the response and transferred any resulting action, instruction, drawing revision or commercial review to the correct process.

Review open and overdue RFIs on a regular rhythm. The frequency should reflect the project pace: a fast fitout may need daily review, while a slower stage may be manageable in the weekly coordination meeting. The review should identify the next responsible person and action, not merely repeat that a response is outstanding.

Before closing an RFI, check that the answer responds to the direct question. A partial response, an unmarked drawing or an answer that creates a new ambiguity may need clarification. Then confirm who must act, which document controls the work and whether cost or programme review is required. Keep that review separate from any contractual notice.

At project close-out, unresolved RFIs deserve deliberate attention. Some may be superseded by later drawings; others may still affect commissioning, as-built information, defects or handover. Record why an item is closed or superseded so the final register is intelligible to someone who was not part of the original conversation.

The person who finds the issue owns explaining it clearly, but may not be the person authorised to issue the formal RFI. A foreman or subcontractor can identify the clash, mark the location and explain the construction effect. The builder’s project manager or contract administrator may then check the documents, remove duplicate questions and issue it through the agreed channel.

The named consultant or client representative owns responding within their authority. If the question belongs with another discipline, redirect it promptly and record who now holds it. A response such as “coordinate on site” is only useful when responsibility and the controlling requirements are clear; it should not quietly pass a design decision to someone who lacks authority.

After the answer, the site team owns making the result operational. That may mean briefing a trade, revising set-out, waiting for an issued drawing, raising a separate commercial review or recording that no change is required. Closing the RFI without transferring that action is how an answered question still becomes lost work.

One person should maintain the register and lead overdue follow-up. That role creates visibility, not ownership of every answer. Keeping the issuer, respondent, action owner and register owner distinct prevents a single administrator becoming responsible for decisions that belong elsewhere.

The site question often begins in conversation. Capture it while the people and location are clear. Decide whether it needs a formal RFI. If it does, create the project record, attach the approved supporting information, name the responsible recipient and record the required response date.

When the response arrives, link it to the question and the work it affects. Confirm any resulting action, owner and date. Keep the answer searchable so the same issue is not raised again by another trade.

Convoe currently supports a narrower part of this loop: text project conversation, generic task extraction, human confirmation and commitment tracking. It does not yet provide a formal RFI register, drawing attachments or linked responses. That product boundary should be clear before a team chooses its RFI system.