Master this essential documentation concept
Request for Information - a formal document used in construction projects to clarify ambiguities, resolve conflicts, or request missing details from architects, engineers, or owners during a project.
Request for Information - a formal document used in construction projects to clarify ambiguities, resolve conflicts, or request missing details from architects, engineers, or owners during a project.
On most construction projects, the context behind an RFI gets discussed in team meetings, walkthrough recordings, or coordination calls — but that knowledge rarely makes it into written documentation. A project manager might record a video explaining why a particular RFI was submitted, how the design conflict was identified, and what resolution was agreed upon. That context is valuable, but buried inside a recording that no one will realistically search through later.
The challenge surfaces when a similar issue arises weeks later, or when a new team member needs to understand the history of a specific RFI. Scrubbing through hours of meeting footage to find a three-minute explanation is not a practical workflow. Important decisions about scope, responsibility, and design intent get lost in the process.
When you convert those recordings into structured, searchable documentation, your team can retrieve RFI-related decisions by keyword, date, or project phase. For example, if an RFI about structural beam placement was resolved in a coordination meeting, that resolution becomes a retrievable reference — not a buried timestamp. Your documentation library grows alongside the project, and the reasoning behind each RFI stays accessible to everyone who needs it.
If your team regularly captures project discussions on video but struggles to turn those recordings into usable records, see how a video-to-documentation workflow can help.
During framing, the contractor discovers that HVAC ductwork shown on mechanical drawings passes directly through a load-bearing beam indicated on structural drawings. Work halts because no one can proceed without risking code violations or structural compromise.
An RFI formally documents the exact conflict with drawing references, sheet numbers, and grid coordinates, forcing the structural engineer and MEP engineer to coordinate a resolution on record before work resumes.
['Contractor photographs the conflict location and annotates the relevant drawing sheets (S-201 and M-104) with red markings showing the clash.', 'Project manager submits RFI #0047 via Procore, attaching annotated drawings, specifying the affected grid location (Column Line B/4), and assigning a 5-business-day response deadline.', 'Structural and MEP engineers jointly review the conflict and issue a revised detail showing a beam penetration sleeve with reinforced framing, attached as a supplemental sketch to the RFI response.', 'PM distributes the closed RFI to all subcontractors, updates the drawing log to flag the revision, and notes the RFI number in the project schedule to track any delay impact.']
Work resumes within 7 days with a documented, engineer-approved solution on record, preventing future liability disputes and providing a clear paper trail if a change order is needed.
The finish schedule in the project manual lists 'premium luxury vinyl tile' for the lobby floor but omits the manufacturer, product line, thickness, and wear layer rating. The flooring subcontractor cannot order materials or provide accurate lead time without this information, threatening the project schedule.
An RFI formally requests the specific product data from the architect, creating a documented record of the information gap and establishing an official response that becomes part of the contract record.
['Flooring subcontractor notifies the GC in writing that Specification Section 09 65 19 is incomplete, identifying the missing product attributes needed for procurement.', 'GC submits RFI #0023 to the architect referencing Spec Section 09 65 19 and Drawing A-601, requesting manufacturer name, model number, thickness, and color selection with a 3-day urgency flag due to 8-week material lead time.', "Architect coordinates with the owner's interior designer and responds with the approved product: Shaw Contract 'Milestone' LVT, 5mm, Wear Layer 20 mil, Color #4521 Ash Grove, with two acceptable alternates listed.", 'PM archives the RFI response, forwards it to the flooring sub for immediate procurement, and updates the submittal log to track the product data sheet and sample approval.']
Materials are ordered within 24 hours of RFI response, preserving the installation schedule and creating a documented owner-approved product selection that protects the contractor if finish quality is later disputed.
Excavation crews encounter unexpected rock ledge at 4 feet below grade in an area where the geotech report predicted soil to a depth of 12 feet. The foundation design assumes soil bearing, and blasting or rock removal was not included in the contractor's bid, creating a potential cost and schedule dispute.
An RFI documents the differing site condition with photographic evidence and survey data, formally notifying the owner and structural engineer so they can issue revised foundation instructions and initiate a change order process.
['Superintendent photographs the exposed rock ledge, records GPS coordinates, and has the surveyor document the elevation at which rock was encountered relative to the design finish floor elevation.', "GC submits RFI #0061 marked 'Differing Site Condition – Potential Change Order' with photos, survey data, and reference to the original geotech boring log B-3, requesting structural engineer guidance on revised footing design.", 'Structural engineer visits the site, evaluates the rock quality, and responds with a revised footing detail that bears directly on the rock with modified anchor bolt embedment, noting that rock removal is not required in this zone.', 'PM issues a formal change order request based on the RFI response, documenting the cost of revised drilling and anchor installation, and updates the project schedule to reflect the 4-day impact.']
The differing site condition is formally documented before any additional work is performed, protecting the contractor's right to additional compensation and providing the owner with a clear, engineer-directed solution.
The project drawings show a 2-hour fire-rated wall assembly at the corridor, but the detail references an assembly number (UL U305) that requires specific stud spacing and board layers not reflected in the architectural sections. The drywall contractor and the building inspector disagree on which governs, threatening a failed inspection.
An RFI formally asks the architect to confirm the intended assembly and reconcile the conflict between the drawing detail and the UL assembly listing, producing a written directive that satisfies the building department.
['Drywall contractor documents the discrepancy in writing, comparing the drawn detail dimensions and layer counts against the published UL U305 assembly requirements side by side.', 'GC submits RFI #0038 to the architect with the UL assembly data sheet attached, the conflicting drawing detail highlighted, and a note that the building inspector has flagged the issue and is awaiting clarification before approving the rough-in inspection.', 'Architect reviews the IBC requirements, consults with the fire protection engineer, and issues a response confirming UL U305 governs with a revised sketch correcting stud spacing to 16 inches OC and specifying 5/8-inch Type X board on both faces.', 'GC provides the closed RFI response to the building inspector, who approves the revised assembly, and the drywall contractor proceeds with the corrected installation documented in the project record.']
The rough-in inspection passes on the next visit, avoiding a re-inspection fee and a potential stop-work order, while the RFI response serves as the official record justifying the as-built assembly to the AHJ.
Every RFI must receive a sequential, project-specific identifier (e.g., RFI-0001 through RFI-0999) the moment it is drafted, not after it is sent. Logging it immediately in the master RFI register prevents duplicate submissions, allows status tracking across the project team, and ensures no RFI falls through the cracks during high-volume construction phases.
Vague RFIs produce vague answers. Every RFI should cite the exact drawing sheet number, detail bubble, specification section number, and physical location (column line, room number, or elevation) where the conflict or ambiguity exists. This precision allows the design team to respond accurately without multiple rounds of clarification and creates an unambiguous record for future reference.
Every RFI should include a required response date calculated backward from the date the affected work must begin, accounting for procurement lead times if materials are involved. A standard 10-business-day response window is common, but high-priority items affecting critical-path activities should be flagged as urgent with a 3–5 day turnaround. Tracking overdue RFIs weekly in OAC meetings keeps design teams accountable.
An RFI submitted with photographs, annotated drawing excerpts, product data sheets, or survey measurements is resolved in one round rather than multiple back-and-forth exchanges. The design team should receive everything they need to make a decision in the original submission, including any contractor-proposed solutions that can be accepted or rejected, which often accelerates the response process significantly.
An RFI response only has value if every party whose work is affected receives it and understands the implications. After the design team closes an RFI, the GC must distribute the response to all relevant subcontractors, update the drawing markup set or BIM model to reflect the clarification, and note the RFI number in the project record drawings. This prevents subcontractors from building to superseded information weeks after an RFI was resolved.
Join thousands of teams creating outstanding documentation
Start Free Trial