What Is an RFI in Construction?
An RFI — Request for Information — is a formal question used on a construction project when drawings, specifications, scope, or field conditions do not provide enough information for the team to proceed confidently.
A good RFI identifies the exact issue, references the relevant contract documents, asks a specific question, assigns responsibility for the response, and records the answer so the project team can move forward from one documented decision.
RFI at a glance
- RFI stands for
- Request for Information
- Used when
- The project team needs clarification before proceeding
- Usually submitted by
- Contractor, subcontractor, project engineer, or other project participant depending on the project's workflow
- Usually answered by
- Architect, engineer, owner, consultant, or other responsible party
- Common triggers
- Drawing conflicts, missing information, scope questions, field conditions, coordination issues
- Why it matters
- An unanswered RFI can delay procurement, fabrication, field work, inspections, or downstream decisions
What does RFI mean in construction?
RFI stands for Request for Information. It exists because construction documents cannot anticipate every field condition, coordination conflict, dimension question, product issue, or interpretation that comes up during execution. The drawings and specifications describe the intended result; the RFI resolves the gaps that appear when that intent meets the actual building.
An RFI should clarify information. It is not a casual email, an undocumented conversation in the field, or a substitute for the project's formal change process. The value of the RFI is that the question, the answer, the date, and the parties involved all end up in the same record.
A simple example. Drawing A-201 shows one partition dimension. Structural drawing S-103 conflicts with that dimension. The contractor cannot confidently lay out the wall. An RFI documents the conflict and asks the responsible designer which dimension governs.
When should a construction team issue an RFI?
An RFI is appropriate whenever the team cannot proceed confidently on the information available. Common situations include:
- Architectural and structural drawings show conflicting information
- A drawing and the specification section disagree
- A dimension, elevation, or detail is missing
- Scope between two trades is unclear at an interface
- An unforeseen field or existing condition is discovered
- Design disciplines conflict in the same physical space
- A detail is incomplete or not constructible as drawn
- A specified product or material needs clarification or is unavailable
- Sequencing between trades or long-lead items conflicts
- The owner or a consultant needs to confirm an interpretation
- A condition may affect the schedule, procurement, or contract value
Just as important is knowing when not to write one. Do not create RFIs for questions already answered clearly in the contract documents. Good teams first verify the drawings, specifications, addenda, submittals, meeting records, and prior RFIs before issuing another question. That habit reduces unnecessary RFI volume, keeps reviewer attention on the questions that matter, and avoids duplicated work on both sides.
Who submits an RFI — and who answers it?
Exact responsibility depends on the project structure and the contract requirements. On most projects the pattern looks like this:
Common submitters
- General contractor
- Project engineer
- Project manager
- Superintendent
- Subcontractor, routed through the GC
- Construction manager
- Owner representative
Common responders
- Architect
- Structural, MEP, or civil engineer
- Design consultant
- Owner
- Construction manager
- Other responsible consultant
Whatever the structure, the workflow should make five things unambiguous at any moment: who submitted it, who it is assigned to, whose court the ball is currently in, the required response date, and the current status. When any of those are unclear, the question tends to sit.
The construction RFI process, step by step.
The specific procedure is set by the project's contract documents, but the sequence below reflects how a well-run RFI moves from field question to distributed decision.
- 01
Issue identified
The field or project team finds an ambiguity, conflict, or missing piece of information that prevents confident work.
- 02
Source documents checked
Confirm the answer is not already in the drawings, specifications, addenda, submittals, meeting minutes, or a prior RFI.
- 03
RFI drafted
State one clear question and reference the exact documents, sheet numbers, details, and location involved.
- 04
Supporting information attached
Drawing snippets, markups, field photos, specification references, sketches, and field-condition documentation.
- 05
Responsible party assigned
Route the question to the architect, engineer, consultant, owner, or reviewer who can actually answer it.
- 06
Response date set
Tie the requested response to the decision or activity it protects — fabrication release, layout, procurement, or inspection.
- 07
Response received
Document the answer along with any revised sketches, details, or supporting information issued with it.
- 08
Response distributed
Everyone affected by the decision — including the trades performing the work — has access to the current answer.
- 09
Downstream impact reviewed
If the response affects scope, cost, schedule, procurement, or contract requirements, route it through the appropriate downstream workflow.
An RFI response is not automatically an approved change order. Project-specific contract documents and procedures govern how an RFI response affects scope, cost, or time.
What should a good construction RFI include?
Most RFIs that come back with a question instead of an answer are missing one of the fields below. Treat this as the anatomy checklist before you send, or start from our free construction RFI template, which already includes each of them.
- Unique RFI number
- Project name
- Date submitted
- Submitted by
- Assigned / responding party
- Concise subject line
- Drawing reference (sheet and detail)
- Specification reference (section)
- Exact location, area, grid, level, or room
- Description of the conflict or missing information
- One clearly stated question
- Proposed solution where appropriate
- Marked-up drawings, photos, and attachments
- Requested response date
- Potential schedule impact
- Potential cost impact if known
- Response
- Response date
- Current status
- Distribution and history
How to write an RFI that gets answered.
A returned RFI usually costs more time than the original question. These seven habits remove most of the round trips.
Ask one clear question
Do not bury three unrelated issues inside one RFI. Separate questions get separate answers, separate due dates, and a cleaner record.
Reference the exact document
Use the drawing number, detail callout, specification section, grid line, room number, level, or elevation. Precision removes a round trip.
Explain the conflict
Show what does not align rather than asking the reviewer to rediscover the problem from scratch.
Attach the evidence
Markups, drawing excerpts, field photos, and specification references let the responder see the same condition the field sees.
Propose a resolution when appropriate
A well-considered proposed solution can make it easier for the design team to confirm or revise the approach.
State when the answer is needed
Connect the required response date to the affected activity, procurement item, fabrication milestone, inspection, or field sequence.
Keep the question neutral
The goal is resolution and a clean documented decision, not assigning blame in writing.
Construction RFI example
The example below uses generic values to show how the fields work together on a common drawing-conflict question.
- RFI
- RFI-042
- Subject
- Conflicting north corridor wall dimension
- Drawing references
- A-201 (Level 2 partition plan) and S-103 (Level 2 framing plan)
- Specification reference
- Section 09 21 16 — Gypsum Board Assemblies
- Location
- Level 2, north corridor, grids C–E
- Question
- Architectural drawing A-201 indicates the north corridor partition at 5'-0" clear, while structural drawing S-103 indicates 5'-4" clear at the same location. Please confirm which dimension governs so framing layout can proceed.
- Proposed resolution
- Proceed using the architectural dimension shown on A-201 unless otherwise directed.
- Requested response
- Within five business days of submission
- Schedule context
- Framing layout in this area is scheduled to begin shortly after the requested response date.
- Attachments
- Marked-up A-201, marked-up S-103, field photo of the existing condition
Project-specific contracts and procedures govern actual RFI requirements, including numbering, routing, response periods, and how responses are handled downstream.
RFI vs. submittal vs. change order
These three records are often mentioned together, but they answer different questions and produce different outcomes.
| Document | Primary purpose | Typical trigger | Typical result |
|---|---|---|---|
| RFI | Clarify missing, conflicting, or ambiguous project information | A drawing conflict, missing detail, field condition, or scope question found during execution | A documented answer or clarification |
| Submittal | Submit product data, shop drawings, samples, or proposed materials for review | A specification requirement to submit before fabrication, procurement, or installation | Reviewed, approved-as-noted, or revise-and-resubmit depending on the project's process |
| Change order | Formally document an approved change affecting contract scope, price, time, or other terms | A change in scope or conditions the parties agree warrants a contract modification | A contract modification |
RFI
- Primary purpose
- Clarify missing, conflicting, or ambiguous project information
- Typical trigger
- A drawing conflict, missing detail, field condition, or scope question found during execution
- Typical result
- A documented answer or clarification
Submittal
- Primary purpose
- Submit product data, shop drawings, samples, or proposed materials for review
- Typical trigger
- A specification requirement to submit before fabrication, procurement, or installation
- Typical result
- Reviewed, approved-as-noted, or revise-and-resubmit depending on the project's process
Change order
- Primary purpose
- Formally document an approved change affecting contract scope, price, time, or other terms
- Typical trigger
- A change in scope or conditions the parties agree warrants a contract modification
- Typical result
- A contract modification
An RFI can uncover a condition that eventually leads to a change order, but an RFI and a change order are not the same thing. The RFI records the question and the answer; the change order records an agreed modification to the contract. For the full picture of how construction change orders work, see our change-order guide. For the review side of the project record, see how construction submittals work. Need to document the resulting contract change? Use the free construction change order template.
How unanswered RFIs become schedule risk.
The chain is short and predictable: a question is raised, the team waits for clarification, a decision stays blocked, a procurement, fabrication, or field activity slips, and the milestone behind it absorbs the pressure.
- A structural connection detail is needed before steel can be released for fabrication
- An equipment dimension is needed before MEP rough-in can be laid out
- A finish clarification is needed before a long-lead material order is placed
- A wall type detail is needed before framing layout in that area
- A design response is needed before an inspection can be scheduled
- An owner decision is needed before a procurement package can be issued
The practical takeaway: RFI priority should reflect the activity the answer is protecting — not simply the date the RFI was created. An RFI opened last week against a framing sequence three months out is a different problem than one opened yesterday against a steel release. That is also why teams increasingly review open RFIs inside construction scheduling software rather than as a standalone list.
When an RFI becomes a cost issue.
Some RFIs do more than clarify. The response reveals something that carries exposure:
- Additional scope not shown in the contract documents
- Changed scope
- Unforeseen or differing site conditions
- Redesign of a detail or assembly
- Material or product substitution
- Rework exposure on work already in place
- Schedule-related cost
- Trade coordination impact
The RFI itself should still do one job: document the question and the response. When the resolution affects contract value or time, the team follows the project's applicable change-management procedure. Project-specific contract documents and procedures govern how an RFI response affects scope, cost, or time.
Where that exposure lands is usually tracked in construction cost management, and the routing between the question and the change process is often handled through workflow automation.
What should you track in an RFI log?
A useful RFI log does not just tell a PM how many RFIs exist. It tells them which ones require action today, who owns them, and what work is sitting behind each one. If you need a register to start from, use our free construction RFI log template.
- RFI number
- Subject
- Discipline
- Submitted date
- Submitted by
- Assigned to
- Due date
- Response date
- Current status
- Days open
- Responsible party
- Drawing / spec reference
- Schedule impact
- Cost impact
- Related change event
- Related submittal
- Affected activity or milestone
| RFI | Subject | Discipline | Assigned to | Due | Status | Impact |
|---|---|---|---|---|---|---|
| RFI-040 | Slab depression at loading dock | Structural | Structural engineer | Day 5 | Answered | None identified |
| RFI-041 | Panel schedule conflict, Level 2 electrical room | Electrical | MEP engineer | Day 3 | Open — overdue | Gear release at risk |
| RFI-042 | Conflicting north corridor wall dimension | Architectural | Architect | Day 4 | Open | Framing layout |
Example entries only. Field names and status values should follow the project's own procedures.
RFI metrics worth watching
Useful RFI reporting is less about benchmarks and more about exposure. The measures below tend to change how a project actually behaves:
- Open RFIs
- Overdue RFIs
- Average and median response time
- RFI age
- RFIs by discipline
- RFIs by responsible party
- RFIs affecting critical activities
- RFIs with potential cost impact
- Repeat RFIs on the same issue
- RFIs awaiting owner or design decisions
Raw RFI count alone does not tell you whether the project has an RFI problem. An RFI answered in one day that affects no downstream work is a different situation from one sitting open against a procurement milestone.
Common RFI mistakes that slow projects down
Asking a vague question
"Please advise" gives the reviewer nothing to confirm. State the condition and the decision you need.
Not citing drawings or specifications
Without a sheet, detail, or specification section, the reviewer has to reconstruct the issue before answering it.
Stacking unrelated issues in one RFI
One RFI with four questions usually returns with two answered and a new round trip for the rest.
Leaving out photos and markups
A marked-up excerpt or field photo often resolves in one pass what three paragraphs of description cannot.
No needed-by date tied to real work
Without the activity the answer protects, every RFI looks equally urgent — which means none of them do.
Routing to the wrong party
An RFI sent to a party who cannot answer it does not start the clock. It just delays the day it reaches the right reviewer.
Letting the answer stop at the office
A response that never reaches the crew installing the work is a decision the project made and did not use.
Disconnecting the response from downstream workflows
When an answer changes scope or timing, it needs to reach the change and schedule processes, not just the RFI file.
How construction teams manage RFIs at scale
On a small project, an email thread and a spreadsheet can hold the RFI process together. On a large project — or a portfolio of them — that breaks down quickly, because the question and the answer end up in different places from the drawings, the schedule, and the people performing the work.
Teams running structured RFI management are generally solving for:
- One RFI register for the project
- Clear ownership and ball-in-court
- Due dates tied to real activities
- Current status visible to everyone
- Attachments stored with the question
- Links to the referenced drawings and specifications
- A complete response history
- Notifications when action is required
- Project-wide access for the parties involved
- Reporting across open and overdue items
- Connection to schedule, change, and project records
None of that requires a specific vendor. It requires that the register, the documents, and the downstream workflows are not three separate systems maintained by hand.
Keep the question, response, documents, and downstream project impact connected.
Jet.Build handles RFIs as part of the project record rather than as a separate log — alongside submittals, drawings, approvals, schedules, and cost workflows.
A centralized RFI log
Every question, response, attachment, and date lives in one project register rather than across inboxes and local folders.
Clear status and responsibility
Each item shows who submitted it, who owns the next action, when the response is due, and where it currently stands.
Routing and approval workflows
Questions move to the responsible reviewer through the project's configured workflow, with the history retained.
Attachments and document context
Markups, photos, and referenced drawings and specifications stay connected to the question and the answer.
Role-based project access
Owners, GCs, consultants, and trades see the records their role allows — with unlimited users on the project.
Reporting across the project
Open and overdue items roll up so a PM can see which questions are actually holding work, not just how many exist.
Teams can also use Jenny, Jet.Build's built-in assistant, to surface open project records and summarize project information from the underlying source documents. Jenny does not answer or approve RFIs on the team's behalf — responsibility for the response stays with the responsible party.
Frequently asked questions
A good RFI protects the decision trail.
The purpose of the RFI process is not to create paperwork. It is to make sure the project can answer a specific set of questions later, without relying on memory:
- What was unclear?
- What did the team ask?
- Who answered?
- What was the final direction?
- When was the decision made?
- Who received it?
- Did it affect cost, schedule, scope, or downstream work?
That record becomes more valuable, not less, as projects get larger, faster, and more complex — and as the people who were in the room move on to the next job.
Related Jet.Build resources.
Where RFIs connect to the rest of the project record.
- Construction project management softwareRFIs, submittals, daily logs, approvals, and tasks tracked against the work they affect.Read more
- Construction scheduling softwareSee milestones alongside the open RFIs, submittals, and approvals driving schedule risk.Read more
- Construction document managementVersioned drawings, specifications, and contracts — the documents every RFI references.Read more
- Construction workflow automationRoute questions, approvals, and notifications so responses reach the right party on time.Read more
- Construction cost managementTrack budgets, commitments, and change exposure when an RFI response affects contract value.Read more
- Construction project controls softwareHow cost, schedule, documents, and issue management fit together as one control system.Read more
See how Jet.Build keeps RFIs connected to the rest of the project.
Take about 30 minutes with our team to see how Jet.Build connects RFIs, submittals, documents, approvals, schedules, cost workflows, and reporting in one construction platform.
Schedule a Demo