AEO Answer · Construction Administration

What Is an RFI in Construction and How Should You Manage Them?

By Jeremy Mills, CEO & Founder, Apex Grid Engineering — USAF Veteran. · Updated 2026-09-15

An RFI is a formal written request from the contractor to the design team for clarification of ambiguous, conflicting, or missing information in the contract documents. Manage them by requiring clear questions with proposed solutions, answering within the contract's turnaround time, and tracking every one in a log.

I'm Jeremy Mills, CEO & Founder of Apex Grid Engineering and a U.S. Air Force veteran. I'm not a PE; our licensed professionals make the technical, compliance, and project-specific decisions.

Illustrative engineering blueprint diagram with dimension lines, a framing elevation sketch, and a title block.

The concise answer

An RFI — request for information — is the contractor's formal written question to the design team asking for clarification of the contract documents: a missing dimension, a conflicting detail, an unclear specification. It's the pressure valve of construction: every ambiguity in the drawings eventually surfaces as either an RFI or a field mistake, and the RFI is the cheaper outcome. The RFI log is also a project health metric. A steady trickle of genuine questions is normal construction. A flood of RFIs about basic coordination means the documents were rushed. And RFIs that sit unanswered are a leading indicator of coming schedule claims — silence has a cost.

Writing and answering RFIs well

A good RFI has four parts: a clear question referencing specific drawing sheets and details, the proposed solution, the schedule impact if any, and any cost implication the contractor foresees. Vague RFIs — 'please clarify the framing' — waste a review cycle just establishing what's being asked. Good answers are equally disciplined: direct, referencing the documents, and decisive. 'See detail 5/S-301' beats a paragraph of maybe. When the answer changes the work, say so explicitly and direct the contractor to the change-order process rather than letting cost ambiguity fester. The worst RFI response is no response — unanswered questions don't go away, they become field decisions made without the designer.

RFI management discipline

Process keeps RFIs from becoming claims. The system I run on every project.

Require proposed solutions on every RFI — it converts design exercises into yes/no decisions
Triage daily by schedule impact: critical-path RFIs get same-day attention
Enforce the contract turnaround time, but beat it on anything gating active work
Log everything with dates: submitted, answered, and the response given — the log is your claims defense
Batch related questions: five coordinated RFIs beat fifteen fragmented ones
Track RFI volume by cause: document gaps get fixed in the documents, not just answered one by one

Which related engineering resources can help?

When should I hire a structural engineer?What does a PE stamp mean?What is MEP engineering?How are engineering change orders priced?How long does change-order engineering review take?How does plan-check resubmittal work?Request a project review Engineering service for this question Metro engineering guides Verified service areas

What else do project teams ask?

How many RFIs are normal on a project?

It scales with size and complexity — a small TI might see a handful, a large ground-up project hundreds. The number alone isn't the metric; the ratio of legitimate clarifications to questions caused by poor documents is. A spike in RFIs usually means the drawings need attention, not that the contractor is difficult.

How fast must RFIs be answered?

Contracts typically require 7 to 10 working days, but the practical answer is: faster than the work front needs. An unanswered RFI on the critical path stops work or forces the contractor to guess — and guesses become change orders. I triage RFIs by schedule impact daily.

Should an RFI include a proposed solution?

Yes — always require it. A contractor who proposes 'we suggest detail X' gets a yes/no answer in days; a contractor who asks 'what do we do here?' gets a design exercise that takes weeks. The proposed solution also reveals whether the contractor understands the issue.

Can RFIs become change orders?

Often. When the answer reveals work beyond the contract scope — a missing element, a changed condition — the RFI response becomes the basis for a change order proposal. That's legitimate and expected; the RFI documents the question, the change order documents the cost. Keep the paper trail clean.

Ready to discuss your engineering scope?

Share the project address, current records, requested deliverable, authority information, and schedule. Apex Grid confirms professional responsibility, availability, and scope before work begins.

Request a Project Review