RFI Management

Definition

RFI Management is the process of raising, tracking, resolving, and closing out Requests for Information on a construction project. An RFI is a written query — usually from contractor to designer — asking for clarification of a drawing, specification, or condition. The RFI system is the audit trail of design intent as executed. On a well-run job it is a design-clarification tool; on a badly-run job it becomes the primary weapon in a delay claim.

Where RFIs Come From

• Conflicts between drawings and specifications.
• Missing dimensions or details.
• Site conditions differing from documented assumptions.
• Coordination clashes between disciplines (structural vs. MEP).
• Product substitutions.
• Design changes that were verbally discussed but never issued.

The Anatomy of a Good RFI

The best RFIs are specific, referenced, and single-issue. They quote the drawing number and revision, describe the ambiguity in one paragraph, propose a solution where possible, and identify the schedule impact if a response takes longer than a stated deadline. The worst RFIs are open-ended ("Please clarify structural intent"), bundle three unrelated questions, and offer no proposed answer. Design teams triage by clarity — a well-written RFI gets answered first.

Real-World Example

On a data-centre fit-out in Dublin, the electrical contractor raised 340 RFIs in the first eight weeks. About 60% were coordination clashes with the mechanical services — the same clashes visible in the BIM coordination model, which had never been rolled forward to the site copies. The controls team stopped the flood, ran two intensive clash-resolution workshops using the current model, and re-issued the coordinated drawings. RFI volume dropped to 40 per week and average response time fell from 11 days to 3. The workshops cost four person-days; the previous RFI backlog was driving a projected 18-day slip on the critical path.

Metrics That Actually Matter

• Open count — how many RFIs are currently unanswered.
• Ageing — the distribution of open days. A tail beyond 21 days indicates a design-team capacity problem.
• Response time — median days from issue to resolution.
• Reopens — RFIs closed but re-raised because the answer was inadequate.
• Cost/schedule impact flag — RFIs that trigger a change order or delay claim.

Practical Lessons Learned

• Route through one gatekeeper. Uncoordinated RFI flow between multiple disciplines quickly overwhelms designers and produces contradictory answers.
• Set a response SLA — typically 7 working days for routine items, 3 for critical-path items — and track compliance publicly.
• Weekly RFI meeting. 30 minutes with the designer, contractor lead and project manager clears more than any email chain.
• Every RFI closes with an action. Either the answer is adequate and the drawings are marked up, or a change order is raised. Never leave "answered but unresolved."
• Trend the volume. A rising RFI curve is an early indicator of design gaps that will drive claims six months later.

Common Mistakes

• Using the RFI system as a substitute for coordination — flooding it with questions the contractor could have resolved by reading the specs.
• Answering RFIs verbally on site and never closing them formally.
• Combining multiple issues in one RFI so it can never be cleanly closed.
• Ignoring ageing until a claim consultant discovers the pattern.
• Designer responses that punt back to the contractor ("as per specification") without actually resolving the ambiguity.
• No linkage between the RFI register and the drawing register — closed RFIs never make it into revised drawings.
• Allowing subcontractors to issue RFIs directly to the designer, bypassing the principal contractor.

Expert Tips

• Include a proposed answer. The RFIs that get closed fastest are the ones where the contractor has already done the thinking and the designer just has to confirm.
• Photograph the site condition. A 15-second phone photo removes 90% of design-team ambiguity about "what does it look like on the ground?"
• Watch the drift between the model and the drawings. When the BIM model is coordinated but the 2D deliverables lag, RFI volume spikes within weeks.
• Escalate ageing weekly. An RFI older than 14 days should be on the project manager's radar, not buried in a register.
• Audit for weaponisation. When RFI volume from one subcontractor triples, it usually means a claim is being built. Get in front of it.

Key Takeaways

• RFIs are a design-clarification tool; they become claim ammunition only when they are allowed to age.
• One gatekeeper, one register, one SLA, one weekly meeting — the four ingredients that keep the system honest.
• Volume trending is a leading indicator of design maturity and coordination quality.
• Every closed RFI must feed into revised drawings or a change order — nothing floats in between.
• The best RFIs propose an answer; the worst simply pass the problem upward.

Related Concepts

Interlocks with Change Order Management, BIM Coordination, Submittal Management, Shop Drawings, and Delay Analysis. Register templates at PMMilestone.org.