RFI vs Submittal: Key Differences Every Construction Professional Should Know
RFIs and submittals are both formal document processes on construction projects, and both are frequently misused, confused, or poorly managed. Understanding the difference — and when to use each — matters more than most people realize.
· 8 min read
On almost every construction project, you will encounter both Requests for Information (RFIs) and submittals. Both are formal document processes. Both generate paper trails. Both require responses from the design team. And both are routinely confused with each other, misused as substitutes for the other, and managed with insufficient rigor. The confusion is understandable — both processes involve the contractor communicating with the design team about the project documents — but the purposes, correct uses, and contractual implications of each are genuinely different. Understanding those differences is not just administrative housekeeping. It has real consequences for project schedules, claims, and professional liability.
What an RFI Is — and What It Is For
A Request for Information is a formal written question submitted by the contractor to the design team — typically the architect, engineer, or owner's representative — asking for clarification, direction, or resolution of an ambiguity in the contract documents. RFIs are used when the drawings or specifications are unclear, conflicting, incomplete, or silent on a condition that the contractor has encountered or anticipates encountering in the field. Examples of appropriate RFI subjects include a conflict between the architectural drawings and the structural drawings at a specific location, a specification that references a product standard without specifying which version or edition applies, an undocumented condition encountered during demolition or excavation that affects how the work should proceed, a request for clarification on the intent of a design detail that appears ambiguous in execution, and a question about what the contractor should do when a specified material is unavailable. The essential characteristic of an RFI is that it is a question seeking direction. The contractor does not know or is not certain what to do, and is asking the design team to tell them. The design team's response to an RFI becomes part of the project record and may affect scope, schedule, and cost.
What a Submittal Is — and What It Is For
A submittal is a document, drawing, sample, or calculation that the contractor provides to the design team to demonstrate that a product, material, or fabrication approach conforms to the requirements of the contract documents. The contractor is not asking a question — the contractor is making a statement: here is what we plan to use or build, and here is the evidence that it meets the specification. Examples of appropriate submittal subjects include product data for a specified piece of mechanical equipment, shop drawings for a structural steel connection, a paint sample for a specified interior finish, a calculation demonstrating that a proposed concrete mix design meets the specified compressive strength, and a test report confirming that a roofing membrane meets the specified fire rating. The essential characteristic of a submittal is that it is an assertion pending review and approval. The contractor has already determined their intended approach; they are submitting documentation for the design team to confirm that the approach conforms to the contract documents.
The Core Distinction: Question vs Confirmation
The simplest way to distinguish between an RFI and a submittal is the direction of the communication. An RFI flows from contractor to design team as a question: what should we do? A submittal flows from contractor to design team as a confirmation: here is what we plan to do; does it conform? This distinction has practical importance. If a contractor is uncertain about what the contract documents require, that is an RFI situation. If the contractor knows what the contract documents require and is demonstrating that their intended product or approach meets those requirements, that is a submittal situation. The misuse that causes the most problems in practice is contractors using submittals to resolve questions that should have been RFIs. Submitting a product for approval when the specification is unclear about which products are acceptable, or when the contractor is aware of a conflict between the drawings and the specification, is not a substitute for an RFI. The submittal approval process is not designed to resolve design ambiguities; it is designed to confirm compliance with a clearly defined requirement. When a contractor submits an alternative product hoping the reviewer will approve it without noticing that it does not fully meet the specification, or submits shop drawings that show a proposed approach without disclosing that it differs from the design drawings, the submittal process is being used incorrectly.
Contractual Implications and Liability
The contractual implications of RFIs and submittals are distinct and significant. When a design team responds to an RFI, they are issuing a design direction. That direction may have implications for the contractor's scope, schedule, or cost. If the RFI response requires work that was not included in the contract, the contractor may have entitlement to a change order. If the RFI response resolves an ambiguity in a way that delays field work, the contractor may have entitlement to an extension of time. RFI responses are therefore treated as binding contractual directions and are routinely referenced in claims and disputes. When a design professional reviews and approves a submittal, they are confirming general conformance with the design intent. Most standard contract forms are careful to specify that submittal review does not relieve the contractor of responsibility for errors in the submittal, for means and methods, or for compliance with all requirements of the contract documents. An architect's approval stamp on a shop drawing does not mean the architect has checked every dimension; it means the architect has reviewed the drawing for general conformance with the design. Contractors sometimes claim that a submittal approval constitutes design team acceptance of an approach that actually differed from the contract documents. Whether such a claim succeeds depends on how clearly the deviation was disclosed in the submittal and whether the reviewer had a reasonable opportunity to identify it.
Notice Requirements and RFI Timing
Most construction contracts include provisions requiring the contractor to provide written notice within a specified number of days of discovering a condition that may entitle the contractor to additional time or compensation. This notice requirement is one of the most important reasons that RFIs must be submitted promptly. If a contractor encounters a specification conflict, a changed site condition, or a design ambiguity that will delay work or require additional cost, the RFI is often the first written documentation of that condition. If the RFI is submitted late — or if the condition is not formally documented with an RFI at all — the contractual notice window may be missed, and the entitlement to an extension of time or additional cost may be forfeited regardless of the merits of the underlying claim. Submittals do not generally trigger the same notice requirements, but late submittals have their own schedule consequences: if a contractor fails to submit a required product for approval in time to allow for the review period and manufacturing lead time, the resulting schedule delay is typically the contractor's own risk.
Tracking Each Process Separately
Because RFIs and submittals are different processes with different purposes, timelines, and contractual implications, they must be tracked separately. Combining them in a single log creates confusion, makes it difficult to monitor response times for each process independently, and complicates the project record at closeout. A well-maintained RFI log tracks every RFI by number, question, responsible party for response, date submitted, required response date, date returned, and final response. A separate submittal log tracks every required submittal by specification section, type, submitter, date submitted, review status, date returned, review action, and any resubmittal history. Both logs should be reviewed at every project meeting and updated in real time as items are transmitted and returned. For teams managing significant volumes — a mid-size commercial project may have 200 RFIs and 150 submittals concurrently in progress — dedicated tracking tools that surface overdue items, flag approaching deadlines, and give the whole team visibility into current status are essential. PlanSpan provides separate, structured logs for both RFIs and submittals, keeping each process organized and visible throughout the project.
When an RFI Should Accompany a Submittal
There are situations where both an RFI and a submittal are needed, and where the sequence matters. If a specification requires a product that is no longer available from the specified manufacturer, the correct approach is typically to submit an RFI first, asking the design team how they want to handle the unavailability — either by designating a substitute product, identifying an alternative manufacturer, or revising the specification. Once the design team has responded to the RFI with direction on what is acceptable, the contractor then prepares and submits the product data for the approved alternate through the formal submittal process. Attempting to resolve this situation through the submittal process alone — by submitting an alternative product and hoping for approval — puts the contractor in a weak position if the submittal is rejected, because the schedule delay caused by the resubmittal cycle will generally be the contractor's risk rather than a compensable event. Using the RFI process first to get design team direction, then confirming compliance through the submittal process, is both the contractually correct approach and the most effective schedule management practice.
Common Mistakes to Avoid
The most common RFI and submittal management mistakes on construction projects fall into a few predictable categories. Using submittals as a substitute for RFIs — submitting an alternative product without disclosing that it differs from the specification, hoping the reviewer will not notice — frequently results in rejections that could have been avoided with a direct question. Submitting RFIs for information that is clearly contained in the contract documents — either because the submitter did not read the specification carefully, or to create a paper trail for a change order that is not actually supported by the contract — wastes project team time and damages the professional relationship between the contractor and design team. Failing to track either process rigorously — allowing RFI responses to sit in an inbox without being distributed to the field, or allowing approved submittals to be filed without being compared against what was actually installed — defeats the purpose of both processes. And allowing either process to fall behind the construction schedule, rather than treating both as front-loaded procurement and coordination management activities, is one of the most reliable predictors of project delays.
