How to track RFIs in construction

Keep RFIs from slipping through the cracks and causing problems.

An unanswered RFI can stop work, cause rework, and turn into a claim. Good RFI tracking makes sure questions get answered on time, responses reach the right people, and you have documentation if there's ever a dispute. Here's how to set up a system that works.

Step 1: Set Up a Numbering System

Consistent numbering prevents confusion and makes tracking easier:

Sequential: RFI-001, RFI-002, RFI-003

Works best for: Simple projects with a single GC

By Discipline: RFI-MECH-001, RFI-ELEC-001

Works best for: Large projects with multiple trade packages

By Submitter: RFI-ABC-001 (ABC Plumbing)

Works best for: When you have multiple subs submitting RFIs

Step 2: Track the Right Information

At minimum, your RFI log should capture these fields:

RFI Number

Subject/Title

Date Submitted

Submitted By

Assigned To

Priority Level

Response Due Date

Date Answered

Status

Cost Impact (Y/N)

Schedule Impact (Y/N)

Related Drawing Sheets

Step 3: Use Clear Status Categories

Good status labels help you quickly see where things are stuck:

Draft

Being written, not sent yet

Submitted

Sent to design team, waiting for response

Under Review

Design team is working on it

Returned for Clarification

They need more info from the submitter

Answered

Got a response, need to distribute it

Distributed

Response sent to everyone who needs it

Closed

Work done per the response, nothing left to do

Disputed

Someone disagrees with the response, needs resolution

Step 4: Set Response Time Expectations

Define how quickly RFIs should be answered based on urgency:

Critical24-48 hours

Work is about to stop

Urgent3-5 business days

Work will be affected within 2 weeks

Standard7-10 business days

Normal design clarification

Low14+ business days

Future phase, no immediate impact

Step 5: Run an Aging Report

Track how long RFIs have been sitting unanswered:

0-7 days: On track (green)
8-14 days: Getting close to due date (yellow)
15-21 days: Overdue (orange)
21+ days: Seriously overdue (red)

Review this weekly and escalate anything that's overdue.

Step 6: Make Sure Responses Get to the Right People

An RFI response is worthless if it never reaches the people who need it:

1.Figure out everyone who's affected by the response
2.Send it to subcontractors working in that area
3.Update field sets and plan rooms
4.Note if the response needs a drawing revision (ASI)
5.Get confirmation that key people received it

Step 7: Look at the Numbers

These metrics help you spot problems and improve over time:

Total RFIs submitted vs. closed
Average response time by discipline
How many RFIs get returned for clarification
RFIs with cost impact
RFIs with schedule impact
What categories or causes generate the most RFIs

To prioritize improvements, tie these metrics back to tool decisions in the comparison hub and expected cost impact on the pricing page.

If you're evaluating fit, compare workflows in product comparisons and estimate expected savings on the pricing page.

Practitioner insight

“The single biggest gain we got from rebuilding our RFI workflow was reporting on the aging buckets at weekly OAC. Once the 21-plus column was visible to the architect every Tuesday, our average answer time dropped from 17 days to 9. We didn't add anyone, we just made the bottleneck unignorable.”

Conversations with project managers and assistant project managers running RFI workflows on commercial and institutional projects between 2024 and 2026.

Frequently Asked Questions

What is the best RFI numbering system for construction projects?

There is no single best system, pick the one that matches your project's complexity. Sequential numbering (RFI-001, RFI-002) works for single-GC projects. By-discipline numbering (RFI-MECH-001, RFI-ELEC-001) helps on large projects with many trade packages. By-submitter numbering (RFI-ABC-001) makes sense when multiple subcontractors submit independently. The most important rule is consistency: change schemes mid-project and your reporting breaks.

What fields should an RFI log capture at minimum?

RFI number, subject, date submitted, submitter, assignee, priority, response-due date, date answered, current status, cost-impact flag, schedule-impact flag, and a list of related drawing sheets. If a field doesn't surface in your weekly RFI review, drop it; if a field would help you answer 'why is this stuck?' add it.

What is a reasonable RFI response time?

Industry-typical SLAs are 7–10 business days for standard design-clarification RFIs, 3–5 business days for urgent items (work affected within two weeks), and 24–48 hours for critical items where work is about to stop. Long-tail RFIs (future-phase, no immediate impact) can take 14+ business days without harming the schedule. Track your actual response time vs. SLA, that delta is the single most useful workflow metric.

What is an RFI aging report and why does it matter?

An RFI aging report buckets every open RFI by how many days it has been outstanding (typically 0–7, 8–14, 15–21, 21+). The 21+ bucket is the warning sign, those RFIs are causing schedule risk, even if no one has formally flagged them. Running the aging report weekly and escalating the 21+ bucket to the design team is the cheapest way to keep an RFI workflow healthy.

How do you reduce the number of RFIs on a project?

Most RFI volume comes from issues that should have been caught in the drawings before they reached the field, missing dimensions, coordination conflicts, unclear details, code-compliance gaps. Pre-construction drawing review (manual or AI-assisted) catches a large share of these issues before they become RFIs. Helonic's AI drawing review surfaces these categories in minutes per sheet.

Which RFIs require an ASI or change order after they are answered?

If the RFI answer changes the work shown on the drawings, the design team typically issues an ASI (Architect's Supplemental Instruction) to formalize the revised drawing. If the answer changes cost or schedule, the GC submits a change-order request. RFIs that resolve through interpretation of existing documents (without revising them) usually close out with only the answer in the RFI log.

Milind Sagaram

Co-founder & CEO, Helonic

Milind is the co-founder and CEO of Helonic, where he leads product and go-to-market for AI-powered construction drawing analysis. He works closely with general contractors, project managers, estimators, and owners to understand how drawing quality drives project outcomes - and where AI can reduce RFIs, change orders, and rework. Milind has interviewed hundreds of construction professionals across project delivery roles, from preconstruction estimators at ENR top-400 contractors to facilities directors at institutional owners, and uses those conversations to shape both product direction and the way Helonic talks about the work.

Areas of focus

Construction project delivery and preconstruction
RFI and change order economics
Owner and GC workflows for drawing QA/QC
Estimating risk and bid-stage scope assessment

Last reviewed by Milind Sagaram · May 2026

Keep exploring

Related guides for RFI management and coordination.

How to Write an RFI That Gets Answered Fast

Write clear RFIs that don't bounce back for clarification.

How to Reduce RFIs in Construction

Strategies to prevent issues from becoming RFIs.

How to Run an OAC Meeting

Coordinate decisions and clear backlogs faster.

AI Clash Detection

Catch coordination conflicts before they generate RFIs.

The best RFI tracking system has fewer RFIs

Helonic catches drawing conflicts and missing information during preconstruction. That means fewer RFIs for your team to track and chase down.