The Required Elements of an Effective RFI
- Exact drawing reference — sheet number, detail number, revision, and the specific gridline or member reference
- Clear question — one question per RFI; never bundle multiple issues
- Supporting documentation — a marked-up portion of the drawing showing exactly where the conflict is
- Proposed resolution — what the detailer recommends as the answer, with basis stated
- Schedule impact — what drawing production is on hold pending this response, and what the date impact is
- Required response date — tied to the drawing release schedule, not an arbitrary date
Why Proposed Resolutions Matter
An RFI that only states a problem forces the reviewer to solve it from scratch. An RFI with a proposed resolution invites the reviewer to confirm, modify, or reject a specific answer — a much faster process. Detailers who consistently provide proposed solutions get faster responses and build credibility with EORs, who come to see them as capable technical partners rather than a source of additional work.
Routing and Response Tracking
An RFI issued to the wrong party delays the response by however long it takes to be re-routed. Know who answers what: connection design questions go to the EOR; geotech questions go to the geotechnical engineer; architectural conflicts go to the architect; spec interpretations go to the spec writer (often the EOR or a specification consultant). Track every open RFI by number, responsible party, required response date, and actual response date. Report this tracker to the fabricator weekly.
Technical Basis Citations That Accelerate EOR Responses
EORs respond faster to RFIs that demonstrate the detailer has already done the technical research. When an RFI references the specific AISC 360 section, AISC 341 provision, or AWS D1.1 clause that creates the ambiguity, the EOR can navigate directly to the relevant code language rather than starting from scratch. For example: 'Per AISC 360 Section J3.6, the bearing strength of the bolt hole governs over bolt shear at this connection. The current plate thickness of 3/8" yields a bearing capacity of X kips, which is insufficient for the 42-kip design shear. Proposed resolution: increase plate thickness to 1/2". Please confirm.' This type of RFI language cuts response time from days to hours on most projects. Detailers who write RFIs at this level of technical precision are rare — and EORs allocate review time accordingly.
Structuring RFIs to Avoid Scope Creep
A poorly written RFI can inadvertently expand the scope of a question — inviting an EOR to revisit a broader design decision when a narrow clarification was all that was needed. Structure each RFI to bound the question tightly: state what is known, what is unknown, and ask only for the specific piece of information needed to proceed. Avoid open-ended language like 'please review the attached and provide guidance.' A well-bounded RFI with a proposed resolution limits the EOR's response to approve/modify/reject and prevents extended design-phase discussions from reopening in the detailing phase.
RFI Documentation as a Contract Protection Tool
Every RFI and its response constitutes a documented design decision. The accumulation of RFI responses is effectively a supplemental specification — a record of how the EOR resolved ambiguities in the original documents. Fabricators and detailers should treat the RFI log as a contract document, maintained with the same care as the drawing register. When a scope dispute arises late in a project — a fabricator claims additional cost from a connection redesign, for example — the RFI record either supports or undermines that claim. Projects managed by Tectonix maintain a complete RFI log accessible to the fabricator in real time, with every question, response, and response date captured and exportable for dispute documentation.
Closing Out Open RFIs Before Drawing Release
The single most effective schedule protection practice is resolving all open RFIs before a drawing package is released for fabrication. A drawing package with open RFIs attached creates a production hold the moment the shop floor encounters the affected condition. Before releasing any package, run a final check against the RFI log: confirm every RFI affecting members in that package has a written response, the response has been incorporated into the drawings, and the incorporation is reflected in the current revision cloud. Packages released with unresolved RFIs should carry an explicit hold notice — 'Do not fabricate members B-103 through B-108 pending RFI-047 response' — so the shop can sequence around the hold rather than building and potentially having to rework.