The single biggest preventable schedule risk on most commercial projects isn’t a labor shortage or a material delay. It’s RFIs sitting unanswered.
A normal commercial project generates hundreds of RFIs. The good ones get answered in days. The bad ones bounce back and forth between the GC, the architect, and the engineering consultants — three rounds of “please clarify your question,” six weeks of elapsed time, and a delay claim by the time work could finally start.
The difference between a fast-answered RFI and a stuck one is rarely the question itself. It’s how the question is written. Here’s how to write RFIs that get answered.
What an RFI Actually Has to Do
An RFI is not a question. It is a structured communication that has to do four things:
- State the question clearly enough that an architect or engineer can understand it without context they don’t have.
- Provide the documents and conditions that make the question necessary.
- Propose a path forward where one is reasonable.
- Establish a date by which an answer is needed to avoid schedule impact.
If your RFI does the first three and skips the fourth, you’ve written half a request. If it does the first two and skips three and four, you’ve written a question — and the answer will reflect that.
The Anatomy of a Good RFI
A well-formed RFI has the same structure every time. Some PMs use a software template; some use a standard format in their own document. The format isn’t what matters. The completeness is.
Subject Line
The subject line is what determines whether the architect opens this RFI today or tomorrow. A subject line of “RFI 047 — Question” tells the architect nothing. A subject line of “RFI 047 — Conflict between mechanical drawing M-303 and structural drawing S-201 at Grid C-7, Level 3” tells them exactly what it concerns and lets them route it correctly.
A good subject line includes the topic, the location, and the document references. Three to five seconds of effort by the GC saves hours of back-and-forth.
Description of the Condition
The first paragraph describes what the GC is seeing in the field, in the documents, or in the proposed work. It is descriptive, not interpretive.
“During mechanical rough-in at Grid C-7 Level 3, the contractor observed that the supply duct shown on M-303 sheet 4 cannot be installed without conflicting with the structural beam shown on S-201. The clear height available is 12.5 inches; the duct shown is 14 inches by 24 inches.”
This is specific, measurable, and grounded in the documents. The architect can verify the condition without the contractor in the room.
The Specific Question
After the description, the actual question — written as a question, with a question mark.
“Should the supply duct be relocated, resized, or routed differently to clear the structural beam? Please provide direction.”
If you have multiple sub-questions, list them. Numbered. Each as a separate item.
Documents Attached
What documents are needed for the architect or engineer to answer? Reference them explicitly and attach them.
“Attached: Sheet M-303, Sheet S-201, photo of field condition (DSC_4523), and a markup of the conflict location.”
Don’t assume the architect has the right drawings open. The minute you require them to find the documents themselves, you’ve added time.
Proposed Solution (When Reasonable)
If the GC has a reasonable view of how to resolve the issue, propose it. The architect can accept, modify, or reject — but proposing a path is faster than asking the architect to develop one from scratch.
“The contractor proposes resizing the duct to 12 inches by 28 inches, which maintains airflow per the engineer’s calculations and fits within the available clear height. Please confirm acceptability or provide alternate direction.”
Some projects and some architects discourage proposed solutions, taking the position that design decisions belong to the design team. That’s their right. But on most projects, a reasonable proposed solution is welcomed and accelerates resolution.
Schedule Impact
This is the field that most RFIs get wrong, and it’s the field that determines how the architect prioritizes the response.
“This RFI affects mechanical rough-in scheduled for May 18-22, 2026. A response is required by May 13 to avoid schedule impact. After May 13, this work cannot proceed and downstream activities, including drywall hang on May 25, will be affected.”
Be specific about which activities are affected and which dates are at risk. “ASAP” and “as soon as possible” are not schedule impact dates. Real dates with real consequences are.
Cost Implications
If the resolution will likely involve cost — change order, owner-directed change, or no-cost work — flag it. The architect’s response will often need owner involvement, and surfacing cost early lets the architect involve the right parties from the start.
“This condition may require an owner-directed change order if the resolution involves duct resizing or rerouting beyond what is shown on the contract documents.”
What Slows RFIs Down
Once you understand what a complete RFI looks like, the patterns that cause slow responses are obvious.
Vague or Conversational Questions
“What about the door at room 301?” is not an RFI. It’s a hallway question. The architect has to come back and ask “what about it?” — adding a round and a week of time.
A complete RFI states what about the door is in question, what document or condition created the issue, and what answer is needed.
Missing or Incomplete Documents
An RFI that references “the drawings” without attaching them puts the burden on the architect to find the relevant sheets. If the architect’s office is busy that day — and it always is — your RFI moves to the bottom of the stack.
Attach the specific sheets, the relevant specs, photos, and any prior RFIs or submittals that bear on the question.
No Schedule Impact Stated
When an RFI has no schedule impact field, or has “ASAP” written there, it gets prioritized below RFIs with concrete dates. Architects on busy projects prioritize what’s about to delay work over what is undefined urgency.
Even if the schedule impact is two weeks out, state it. “Response needed by May 13 to avoid mechanical rough-in delay” is far stronger than “please respond when convenient.”
Bundling Unrelated Questions
An RFI titled “Multiple questions on Level 3” with seven different questions about different conditions is harder to answer than seven separate RFIs. Each question may need a different consultant — mechanical, electrical, structural, architectural — and bundling them means the RFI sits with whichever consultant has the slowest response.
Separate RFIs by topic. They’re easier to track, easier to route, and faster to close.
Using RFIs to Surface Disagreements
An RFI that’s actually a position paper — “the contractor disagrees with the design intent shown on…” — is not an RFI. It’s a dispute. RFIs that read as adversarial get treated as adversarial, and the response process slows accordingly.
If the contractor disagrees with the design or the spec, the right vehicle is a notice letter, a clarification request, or a change order proposal — not an RFI. Use the right tool for the situation.
Re-Submitting Without Adding Information
An RFI that comes back from the architect with “please clarify your question” should not be re-submitted with the same content. The clarification is a signal that something in the original wasn’t clear.
Read the architect’s response carefully. Identify what was missing — the specific document, the location, the proposed solution — and add it before re-submitting.
Building an RFI Process That Works
The individual RFI is one piece. The process around RFIs determines whether they actually flow.
Single point of submission and tracking. RFIs should go through one person on the GC’s team — typically the project manager or a dedicated PE — so that the format is consistent, the log is current, and prior RFIs and responses are referenced when relevant.
Pre-submission review. Every RFI should be reviewed by a senior PM or assistant PM before it goes to the architect. The review is for completeness, not for content. The reviewer is checking: subject specific? Question clearly stated? Documents attached? Schedule impact stated? Cost flagged?
Weekly RFI log review. Open RFIs should be reviewed weekly with the architect. The log surfaces overdue responses, identifies stuck items, and creates a forum to escalate when needed.
Escalation path defined. When an RFI passes its needed-by date without a response, what happens? The contract usually defines this — often a notice letter, a delay notice, or a formal escalation to the owner. The team needs to know what triggers the escalation and execute it consistently. Inconsistent escalation teaches the architect that the schedule impact dates are not real.
Response acceptance discipline. When an architect’s RFI response arrives, the GC’s team needs to actually read it, understand it, and confirm acceptance — or send it back if the response doesn’t actually resolve the question. RFIs that arrive and sit in the inbox unread are a frequent source of downstream problems.
The Architect’s Side
A note on the design team’s perspective, because the GC who understands what slows down the architect’s response will write better RFIs.
Architects on commercial projects typically respond to dozens of RFIs per week across multiple projects. The good ones are organized; the bad ones are drowning. A well-formed RFI with clear documents and specific questions reduces the architect’s work and gets prioritized accordingly.
Architects also have to coordinate responses with consultants — structural, mechanical, electrical, plumbing — many of whom are not in the architect’s office and operate on their own schedules. An RFI that requires a response from three consultants will be slower than one that requires a response from one. This is partly why bundling unrelated questions is counterproductive: the RFI becomes the slowest consultant’s response.
The architects who respond fastest aren’t the ones with the lightest workload. They’re the ones who’ve built a process for it. The GC’s job is to make their RFI fit into that process cleanly.
The Bottom Line
RFIs are one of the highest-leverage documents in commercial construction project management. A team that writes them well moves projects forward; a team that writes them poorly creates schedule problems for itself.
The difference is not talent or experience. It’s discipline — the discipline of writing complete RFIs with clear questions, attached documents, stated schedule impact, and consistent format.
Build the discipline. The schedule recovery you don’t have to do later is the cheapest schedule recovery there is.
Jobsite Blog covers the design-construction interface from the GC’s perspective. If you have a specific RFI process challenge, reach out through our contact page.