How to Manage the RFI in Your Construction Project

On any construction project — whether a high-rise tower, a highway upgrade, or an industrial facility — information gaps are inevitable. Drawings are never perfect, specifications contain ambiguities, and site conditions sometimes differ from what designers envisioned. The Request for Information (RFI) is the formal mechanism that bridges these gaps, ensuring that contractor, subcontractors, designer, and client are working from the same understood set of instructions.

Yet despite its importance, the RFI process is one of the most mismanaged workflows on construction sites. Poorly tracked RFIs lead to delays, rework, cost overruns, and — in contractual disputes — lost claims. This article provides a comprehensive, practical framework for managing RFIs professionally, from initiation through to close-out.

What is an RFI?

A Request for Information is a formal written query raised by a contractor, subcontractor, or other project participant to seek clarification, additional detail, or direction from the designer, engineer, or client regarding the contract documents — drawings, specifications, or scope of work.

RFIs are not change orders, nor are they vehicles for requesting additional money or time. They are a clarification mechanism. However, the response to an RFI can trigger a variation or change event if the clarification reveals that the original scope was ambiguous or incomplete.

An RFI seeks information. A Variation Order or Instruction directs a change. Never use an RFI as a substitute for a formal change order — it creates contractual risk.

Why RFI Management Matters

Poorly managed RFIs have real consequences. Studies of large construction projects consistently identify unresolved or delayed RFI responses as a primary driver of schedule delay. The impacts compound quickly:

• Schedule delays: when a tradesperson cannot proceed because a detail is unclear, productivity stops. A backlog of 50 unresolved RFIs can cripple a fast-track programme.

• Cost overruns: waiting for information causes idle labour, extended preliminaries, and disruption to follow-on works.

• Rework: if a contractor proceeds on an assumption rather than waiting for an RFI response, the result is frequently rework when the correct information eventually arrives.

• Contractual disputes: an unresolved RFI can form the basis of a delay or prolongation claim. Proper management creates a contemporaneous record that protects all parties.

• Relationship breakdown: a designer overwhelmed with poorly drafted or unnecessary RFIs loses trust in the contractor's capability. Conversely, a contractor ignored on valid clarification requests loses confidence in the design team.

The RFI Lifecycle

Understanding the full lifecycle of an RFI is essential to managing it well. Each stage represents a gate that requires a defined action, responsible party, and timeframe.

1. Identification of Information Gap

Owned by the contractor or subcontractor. Continuous — anyone on site who encounters ambiguity or missing detail must be empowered to flag it.

2. RFI Drafting & Internal Review

Owned by the contractor PM or engineer. Typical timeframe: 1–2 days. Every RFI should pass an internal sense-check before leaving your office.

3. Submission to Designer / Engineer

Owned by the contractor PM. Submission must follow the contract's formal communication protocol, with full reference data attached.

4. Designer Review & Response

Owned by the lead designer or engineer. Typical contractual window: 5–14 days.

5. Review of RFI Response

Owned by the contractor PM. 1–2 days to confirm the response actually closes the gap and is technically buildable.

6. Distribution to Affected Parties

Owned by the contractor PM. Same day as receipt — do not let new information sit in an inbox.

7. Close-Out & Register Update

Owned by document controller or PM. Immediate.

8. Variation Assessment (If Applicable)

Owned by the contractor PM and QS. Per contract mechanism — assess whether the response triggers a cost or programme change.

How to Draft a Good RFI

The quality of an RFI response is almost always a direct reflection of the quality of the RFI itself. A vague, poorly drafted RFI invites a vague or delayed response. An RFI should be precise, concise, and actionable.

Essential Components

• RFI Number — a unique sequential identifier (e.g. RFI-001, RFI-002). Use a consistent numbering system throughout the project.

• Project Details — project name, contract number, contractor name, and date of submission.

• Reference Documents — list the specific drawing numbers, revision levels, specification clauses, or other contract documents the RFI relates to.

• Location — define the building element, grid reference, floor level, or zone affected.

• Subject — a brief, clear subject line (e.g. 'Rebar Lapping Detail at Column C3, Level 4').

• Description of Issue — describe the information gap or ambiguity factually and objectively. Avoid blame or commentary on design quality.

• Contractor's Proposed Solution (CPS) — propose your interpretation. This accelerates response and signals competence.

• Response Required By Date — derived from the programme, not arbitrary.

• Attachments — annotated drawings, site photos, sketches.

Before issuing any RFI, your team should conduct a 30-second document check: is this already answered in the drawings, specs, or previous correspondence? Eliminating unnecessary RFIs preserves your credibility with the design team.

Maintaining an RFI Register

The RFI register is the single most important document control tool for tracking the RFI process. It provides a real-time view of all open, pending, and closed RFIs, and serves as the primary evidence trail for any future dispute or delay claim.

Minimum Fields

• RFI Number — unique sequential reference (e.g. RFI-047).

• Date Issued — the date the RFI was formally submitted to the designer.

• Subject — brief description of the information sought.

• Issued By — name and company of the party raising the RFI.

• Directed To — designer, engineer, or other responsible party.

• Response Required By — programme-driven deadline.

• Date Response Received — actual receipt date.

• Status — Open / Pending / Closed / Escalated.

• Programme Impact — Yes / No / Under Review.

• Variation Potential — Yes / No / Commercial Risk.

• Notes & Actions — escalation history and follow-up.

Keeping the Register Current

An RFI register is only useful if it is updated in real time. Assign a document controller or a nominated team member to update the register as soon as any action occurs — submission, response, or close-out. Weekly reviews of the register in project meetings will surface overdue items before they become critical path issues.

Contractual Timeframes for RFI Responses

One of the most common mistakes is failing to specify — and enforce — a contractual timeframe for RFI responses. Without a defined response period, designers have no obligation to respond promptly, and contractors have no contractual basis for a delay claim when responses are late.

FIDIC Provisions

Under the FIDIC Red Book (Conditions of Contract for Construction), Clause 1.9 addresses drawing and instruction delays. While FIDIC does not prescribe a fixed number of days for RFI responses, it requires the Engineer to issue drawings and instructions within a time reasonable having regard to the programme. Your programme must serve as the benchmark — if your RFI register shows a required response date linked to the critical path, any overrun creates a valid Clause 8.5 (Extension of Time) event.

Always agree on an RFI response timeframe in the project execution plan or pre-construction meeting — before any RFIs are raised. Define standard (10 days), urgent (3 days), and critical (24 hours) response categories with all parties' agreement.

Escalation Protocol

Even with the best systems, RFIs will sometimes remain unanswered beyond the agreed response period. A clear three-tier escalation protocol ensures overdue items are addressed before they affect the programme.

Tier 1 — Reminder (Day 1 Overdue)

The project manager or document controller sends a polite written reminder to the designer's project lead. Reference the RFI number, original submission date, and required response date.

Tier 2 — Formal Notice (Day 3–5 Overdue)

The contractor's project manager sends a formal written notice to the designer and copies the client's representative. State the programme impact and reference the relevant contract clause.

Tier 3 — Escalation to Principal (Day 7+ Overdue)

Escalate to the Principal or Employer's Representative with a request for urgent direction. At this point, the contractor should also formally record the delay under the relevant delay notification clause.

Linking RFIs to the Programme

The most powerful tool a project manager has in managing the downstream impact of delayed RFIs is a programme-linked RFI register. For every RFI, ask: which activity on my programme is dependent on this information? What is the latest date I need this information to maintain my programme?

If you are using a Primavera P6 or Microsoft Project schedule, assign a Required Information Date (RID) to each relevant activity. This is the date by which the RFI must be answered for that activity to proceed as planned. If a response arrives after the RID, you have a documented programme impact — and a contemporaneous record to support an Extension of Time claim.

Produce a weekly 'RFI Impact Report' for your programme meetings: a one-page summary of all open RFIs with their Required Information Dates and current programme float. This makes the risk visible to all stakeholders and creates pressure for timely responses.

RFI Best Practices Summary

Drawing together the guidance in this article, the following best practices will significantly improve RFI management on your next construction project:

• Establish the RFI process, response timeframes, and escalation protocol before the first RFI is raised — ideally in the pre-construction phase.

• Assign ownership: one person owns the RFI register and is accountable for its accuracy at all times.

• Conduct a weekly RFI review in your project coordination meeting to surface overdue items early.

• Link every RFI to the programme — identify the activity affected and the Required Information Date.

• Draft RFIs precisely: one issue per RFI, with full reference to drawings/specs, location, and a proposed solution.

• Never raise an RFI without first checking the contract documents — this erodes credibility with the design team.

• Record the programme impact of every overdue RFI contemporaneously and issue formal notice when required.

• Distribute all RFI responses to affected trades immediately upon receipt — do not hold information.

• Treat the RFI register as a contemporaneous legal record. One day, it may be the most important document in your dispute file.

A well-managed RFI process ensures clarity, avoids delays, reduces rework, and protects the project from claims. It is one of the highest-leverage disciplines a construction PM can master.