A buried conflict between a structural beam and ductwork sits on the drawings. You’ve got three days of slab work left before the framers need that detail resolved. This is where RFI construction process either saves your schedule or quietly wrecks it.
Most GCs lose time not because the answer is hard, but because the request sat in someone’s inbox for two weeks. A tight RFI construction workflow fixes that – not with more software, but with better habits at the point of submission.
What Is an RFI in Construction
An RFI, request for information, is a formal written question. It goes from the field or office to the design team. You send one when drawings, specs, or contract documents don’t give you enough to build from. It’s not a complaint and it’s not a change order request dressed up politely. It’s a documented gap between what’s drawn and what’s buildable.
A proper RFI construction document covers five things. State the question and the drawing or spec section it references. Offer a proposed solution if you have one. Give the date you need an answer by. Then note the cost or schedule impact if the answer comes late. Skip any of those and you’ve written a memo, not an RFI.
Take a tenant improvement job in Texas. A sub flags that the reflected ceiling plan shows a soffit at 9 feet. The mechanical drawing routes a duct through that same space at 8′-6″. That’s a textbook RFI: two documents conflict, and someone needs a licensed decision before the ceiling grid goes up.
The number that matters most on an RFI log is the “need by” date. Architects and engineers triage by urgency, and an RFI without a real deadline sits at the bottom of the pile.
Building the Submission So It Gets Answered Fast
The way you write the question decides how fast you get an answer. Vague RFIs get vague answers, and vague answers generate a second RFI.
Start with the drawing reference: sheet number, detail number, spec section. Then state the conflict in one or two sentences. Then, if you can, propose a fix. Architects answer “can we do X instead” faster than they answer open-ended “what do you want us to do here.”
Attach a photo or a marked-up PDF. On a hospital renovation, a GC in Ohio submitted an RFI about a fire-rated wall assembly with a single sentence and no sketch. It bounced back three times before the architect understood which wall the question was even about. A red-lined PDF with an arrow would have closed it in one round trip.
Set a real need-by date, not a padded one. If you need the answer in 5 business days to keep the drywall sub on schedule, say 5 business days. Padding it to “2 weeks just in case” trains the design team to treat your real deadlines as soft, too.
Number every RFI sequentially and never reuse a number, even for a void. Your log integrity depends on it, especially when a claim goes to mediation later and someone subpoenas the full RFI history.
RFI Tracking Methods Compared
You’ve got two real choices once you’re past a handful of RFIs on a job. Use a dedicated construction management platform, or a disciplined spreadsheet. Both work. Neither works if nobody owns the log.
Option A: Dedicated Software Platforms
Procore, PlanGrid, and Autodesk Build all handle RFI routing, auto-numbering, and deadline alerts. Procore’s RFI module ties directly into your drawing set, so a reviewer clicks straight from the question to the referenced sheet. That link-back is the single biggest time-saver on a multi-trade job with hundreds of open items.
These platforms are priced per project or per user seat, quote-based through a sales rep, and the cost scales with how many modules you turn on. The failure mode is adoption: if your architect’s office still wants PDFs emailed, you end up running two systems in parallel, which defeats the purpose.
Procore is bad at letting you quickly eyeball overdue items across multiple jobs without building a custom report first. PlanGrid’s RFI tool is lighter and cheaper to roll out on a small crew. But it lacks the deep submittal-to-RFI linking that bigger GCs rely on for complex MEP coordination.
Option B: Spreadsheet and Email Logs
A shared Excel or Google Sheets log still runs plenty of small commercial and residential jobs fine. Give it columns for RFI number, date issued, and date due. Add date answered, cost impact, and schedule impact. It costs nothing beyond labor.
The weakness is enforcement. Nobody gets an automated nag when day 6 passes with no answer. You need a PM who checks the log every morning and chases architects by phone, not email, when a date slips.
Spreadsheets also fall apart past roughly 50 to 75 open RFIs on a job, because cross-referencing drawing revisions against old answers becomes a manual hunt. If your job is routinely running that volume, the software cost pays for itself in recovered PM hours.
Five Habits That Keep Your RFI Log Clean
- Log every RFI the same day it’s written, even if you plan to hold it for batching with similar questions.
- Route through one person, usually the PM or a project engineer, so the general contractor isn’t guessing who already asked what.
- Tag every RFI with its cost and schedule impact estimate at submission, not after the fact.
- Close the loop by distributing the answer to the affected sub and the field crew within 24 hours, not just filing it.
- Reconcile the open RFI log against the schedule every week during the OAC (owner-architect-contractor) meeting, out loud, item by item.
That weekly reconciliation habit catches the RFI that’s been sitting 11 days when everyone assumed it closed. It also forces the architect’s rep to commit to a date in front of the owner, which moves things faster than a follow-up email ever will.
When an RFI Turns Into a Change Order
Not every RFI costs money, but plenty do, and this is where GCs leave dollars on the table. Sometimes the architect’s answer requires different material, more labor, or a schedule extension. That RFI then needs a cost and time impact statement attached before you proceed, not after.
Flag the RFI as “potential change order” at submission if you suspect the answer will trigger extra scope. That flag protects you if the conversation later becomes a dispute. The question is whether you gave timely notice. Most contracts require it within a specific number of days of discovering the condition.
On a multifamily project, a structural RFI about a beam pocket conflict came back from the engineer requiring added steel reinforcement. The GC had already tagged the RFI as a potential CO and logged the discovery date. That paper trail turned a six-week back-and-forth into a two-week negotiation, because nobody could argue about when the issue surfaced.
Never let field crews proceed on a verbal answer to a cost-impacting RFI. Get the written response first, even if that means holding a wall open for an extra day. A verbal “yeah, go ahead” from an architect’s junior staffer won’t hold up if the owner disputes the change order six months later.
Who Should Be Writing and Answering RFIs
The best RFIs come from the person closest to the conflict: the superintendent walking the floor, not the estimator back in the office reading drawings cold. The super sees the duct and the beam in real space, which makes for a sharper question.
Project engineers typically own the actual RFI log and numbering system, keeping the format consistent and chasing answers. On larger jobs, a dedicated document control coordinator handles nothing but RFIs, submittals, and drawing revisions, because the volume justifies a full-time role.
On the design side, answers should come from whoever has stamping authority over that discipline, structural, mechanical, electrical, not a project architect forwarding a guess. If an RFI touches a structural connection or a life-safety system, insist the response carry a licensed engineer’s name and, where your jurisdiction requires it, a stamp. Don’t accept “looks fine to me” from someone without the authority to put their license behind it.
If an RFI answer seems to contradict the building code or a prior approved submittal, that’s not a call for the GC to make in the field. Route it back to the architect of record and, if needed, the authority having jurisdiction (AHJ) for a formal interpretation before you build to it.
Running RFIs Without Losing the Schedule
The jobs that run smooth aren’t the ones with zero RFIs. They’re the ones where RFI construction habits are built into the weekly rhythm. That means same-day logging and real deadlines. It also means a PM who treats the log as a live schedule risk, not paperwork.
Software helps once your RFI count justifies the cost, but a disciplined spreadsheet beats a neglected Procore account every time. The tool matters less than whether someone owns it.
Some RFIs touch structural capacity, life-safety systems, or a likely code interpretation dispute. Get a licensed engineer or the AHJ involved before you build. When the cost or schedule impact gets contentious, loop in a construction attorney early rather than after the lien gets filed.
That log is only one of the records an inspector or owner may ask to see. Are you tightening documentation across the job? Our guide to construction project management software covers the platforms that keep requests, submittals, and daily reports in one place.
Frequently asked questions
What’s the difference between an RFI and a submittal?
An RFI asks a question when the documents are unclear or conflicting. A submittal is a product data sheet, shop drawing, or sample sent for the architect’s approval before you fabricate or install something. They’re tracked separately because they serve different purposes, though a submittal review sometimes generates a follow-up RFI.
How many days should an RFI response take?
Most contracts specify a response window, often 7 to 14 calendar days, but the real answer depends on your schedule need-by date stated on the form. Critical path items need faster turnaround, sometimes 48 to 72 hours, and you should flag those explicitly rather than relying on the contract’s default window.
Can a subcontractor submit an RFI directly to the architect?
Usually no. Most contracts route all RFIs through the general contractor so there’s one log and one point of accountability. Subs should submit their questions to the GC’s project engineer, who formats and numbers it before sending it up the chain.
Does an unanswered RFI automatically become a change order?
No, not on its own. But an unanswered RFI that delays work can support a claim for time extension or added cost. You must have documented the impact and given timely notice per your contract. The RFI itself isn’t the change order; the cost and schedule impact statement attached to it is what builds your case.
What happens if an RFI answer conflicts with the building code?
Don’t build to it. Go back to the architect of record in writing and ask for clarification. If the conflict persists, take it to the authority having jurisdiction for a formal interpretation. This isn’t a judgment call for the field to make, and proceeding on a questionable answer can cost you at final inspection.
