Construction RFI Guide: How to Write and Manage RFIs

1. What Is an RFI and When to Use One

A Request for Information (RFI) is a formal written document submitted by a contractor to the architect, engineer, or owner seeking clarification on the contract documents. RFIs address conflicts, ambiguities, missing information, and design questions that arise during construction.

RFIs serve two purposes: they get you the information you need to build the project correctly, and they create a documented record of questions and answers that protects you if disputes arise about scope, schedule, or cost.

When to Submit an RFI

When not to use an RFI: Don't use RFIs as a substitute for reading the drawings. If the answer is clearly in the contract documents, submitting an RFI wastes everyone's time and can undermine your credibility. Do your homework first.

2. How to Write an Effective RFI

An RFI that's vague or poorly written will generate an unhelpful response — or no response at all. A well-written RFI gets a clear, usable answer quickly.

Elements of a Good RFI

• RFI number — Sequential numbering for tracking. Never reuse numbers.
• Date submitted — Critical for tracking response time and schedule impact.
• Reference documents — Specific drawing numbers, sheet names, detail numbers, and specification sections. "See plans" is not a reference.
• Clear question — State exactly what information you need. One question per RFI whenever possible.
• Suggested answer (optional) — Providing your recommended solution speeds the response. The design team can approve your suggestion rather than drafting something from scratch.
• Response required by date — Calculate when you actually need the answer to avoid impacting your schedule. Be realistic — don't cry wolf.
• Schedule impact statement — If a late response will delay your work, say so explicitly. "If this RFI is not answered by [date], we will be unable to proceed with [scope] and anticipate a delay to our schedule."
• Attachments — Mark-up photos, sketch sketches, or drawing excerpts that illustrate the issue. A picture is worth a thousand words.

Writing the Question Clearly

Bad RFI: "Please clarify the structural connection at grid line B-7."

Good RFI: "Sheet S-203, Detail 4/S-203 shows a W8x31 beam framing into a W14x53 column with a standard single-plate shear tab. Sheet A-301 shows the same location with a structural steel moment connection. Please clarify which connection type is required and provide the moment connection details if applicable. We need this response by [date] to finalize our fabrication order."

The good RFI tells the design team exactly where to look, what they'll find, and what you need. It's respectful of their time and leaves no ambiguity about what you're asking.

3. The RFI Submission and Response Process

On most projects, RFIs flow from the subcontractor to the general contractor, who forwards them to the architect or engineer of record. Some GCs prefer to manage all RFIs centrally; others allow direct sub-to-architect communication. Know your project's protocol before submitting.

Typical RFI Timeline

1. Submission — Sub submits RFI to GC (same day as discovery when schedule-critical).
2. GC review — GC reviews for clarity and forwards to architect/engineer (typically 1-2 days).
3. Architect/engineer response — Design team responds (contractually usually 7-14 days; in practice, sometimes much longer).
4. GC distribution — GC receives response and forwards to submitting sub.
5. Close-out — Sub acknowledges response and closes RFI in the log.

If a response is late and your work is impacted, document it in writing. Send a follow-up notice stating: "RFI #[X] submitted on [date] has not received a response. This RFI is on the critical path for [scope]. We are unable to proceed and anticipate a [X]-day delay if not resolved by [date]."

4. Tracking RFIs and Response Times

An RFI log is a live document tracking every RFI on the project — number, description, date submitted, date response required, date response received, and current status. It's one of your primary project management tools and a key piece of claim documentation.

What Your RFI Log Should Track

• RFI number and title
• Date submitted to GC
• Response required by date
• Date GC forwarded to architect
• Date response received
• Days outstanding (auto-calculated)
• Status: Open / Responded / Closed
• Schedule impact (days of delay caused by late response)
• Cost impact (if the response triggers additional cost)

Review your RFI log weekly with your project manager. Flag any open RFIs past their required response date. Send written reminders for every overdue RFI — these reminders become critical evidence in a schedule delay claim.

5. Using RFIs to Support Schedule and Cost Claims

An RFI log that shows a pattern of late design responses is powerful evidence in a delay claim. If the architect took 30 days to respond to an RFI that you needed in 7 days, and that delay pushed back your rough-in by 3 weeks, you have documented proof of an owner-caused delay — which entitles you to additional time and potentially additional cost.

Building a Paper Trail for Claims

• Always state schedule impact in the original RFI — "Response required by [date] to avoid schedule impact." If you don't say it needed to be answered by a specific date, it's hard to claim the late response caused a delay.
• Send follow-up notices for every overdue RFI — Email the GC: "RFI #47 is now 8 days past the required response date. We are unable to proceed with [scope] and are recording this as an owner-caused delay."
• Document actual delays — Note in your daily work reports when a crew is idle or working out of sequence due to an open RFI.
• Tie RFI responses to change orders — When an RFI response triggers a design change, issue a change order request immediately. The RFI is your evidence that the change was design-driven, not a scope addition you should absorb.

On a disputed project, a well-maintained RFI log can be the difference between winning and losing a delay claim worth hundreds of thousands of dollars.

6. Common RFI Mistakes

7. Managing RFIs with Software

Tracking RFIs in email or spreadsheets works on a small project. On a large project with hundreds of RFIs, you need a system that makes it impossible for responses to slip through the cracks.

Construction management software like RivetCORE gives you:

• Centralized RFI log — Every RFI in one place, with status, dates, and responsible party visible at a glance
• Automatic aging alerts — Get notified when RFIs are past their required response date so nothing goes unaddressed
• Document attachments — Attach drawings, photos, and markups directly to the RFI record
• Response distribution — Forward RFI responses to field crews and team members directly from the system
• Change order linking — Connect RFI responses to change orders when the clarification triggers additional scope
• Exportable logs — Generate a formatted RFI log for owner meetings, dispute resolution, or claims documentation

When your RFI process is organized and fast, you build more efficiently, have fewer field errors, and have the documentation you need to protect your schedule and collect on delays.