RFI vs submittal

On most projects, RFIs and submittals are the two stacks of paper that flow to the architect, and they get treated as the same kind of chore. They are not. One asks a question, the other proves an answer, and sending the wrong one - or using one to do the other's job - is how a simple issue turns into a stalled order and a backcharge.

What an RFI is

An RFI, or Request for Information, is a formal written question from the contractor to the design team to clarify or resolve something unclear, missing, or conflicting in the drawings or specs. It is the tool for when you do not yet know what the documents require. The full workflow is in what is an RFI in construction.

What a submittal is

A submittal is the contractor's proof that the products and methods they plan to use meet the spec. It is the product data, shop drawings, samples, and certifications sent to the design team for review and approval before fabrication or installation. It is the tool for when you know what the spec requires and you have to show your product meets it. What goes in one is covered in what goes in a submittal package.

The key differences

	RFI	Submittal
Purpose	Ask a question	Prove compliance
Triggered by	A gap or conflict in the documents	A spec requirement that needs proof before work proceeds
What the contractor wants	Information or a decision	Approval to proceed
Who initiates	Contractor, often the sub via the GC	Contractor, the sub via the GC
What the design team does	Answers, clarifies, or issues a sketch	Reviews and stamps: approved, approved as noted, revise and resubmit, or rejected
Output	A written answer on the record	A review stamp and any redlines
Logged in	The RFI log	The submittal log

The short version: an RFI is how you find out what the spec means. A submittal is how you prove you met it.

How the two streams interact

The streams are separate, but they hand off to each other constantly. An RFI answer can decide which product is acceptable, and the contractor then files a submittal to prove the chosen product meets the clarified requirement. Run it the other way and a submittal under review can surface a conflict in the documents that the reviewer kicks back as an RFI before the submittal can be judged.

Order matters less than recognizing which problem you have. If the documents are unclear about what is required, an RFI settles it first, then the submittal follows. If the requirement is already clear, the submittal goes straight in, and an RFI only follows if something does not line up.

Common mistakes

• Using a submittal to ask a question. Sending product data and hoping the reviewer will tell you whether it is acceptable, when the spec is actually ambiguous, wastes a full review cycle. Clear the ambiguity with an RFI first.
• Using an RFI to slip in a different product. A request to use a product the spec did not name is a substitution request, with its own form and deadline. It is not an RFI, and it is not a quiet swap buried in a submittal.
• Treating an RFI answer as approval to install. An RFI clarifies a requirement. It is not a stamped submittal. If the item needed a submittal, it still needs one after the RFI is answered.
• Logging them in one pile. RFIs and submittals are tracked separately for a reason. Mixing the logs hides what is actually outstanding and overdue.

Of the two streams, the submittal is where compliance is won or lost, and where deviations hide: a missing rating, a swapped manufacturer, an uncertified product. Deviation Check reads a submittal against the spec section it answers to and returns the deviations in a plain-language report. Run a review on a package before it goes back to the sub.

Frequently asked questions

Is an RFI the same as a submittal?

No. An RFI is a written question to the design team to clarify or resolve something in the documents. A submittal is proof that a proposed product or method meets the spec, sent for the design team's review and approval. They serve different purposes and are logged separately.

Can an RFI turn into a submittal?

Not directly, but one drives the other. An RFI answer can settle which product or detail is acceptable, and the contractor then sends a submittal to prove the chosen product meets the clarified requirement. The RFI resolves the question, the submittal proves compliance.

Which comes first, the RFI or the submittal?

Either, depending on the issue. If the documents are unclear about what is required, an RFI comes first to settle it, then the submittal follows. If the requirement is clear, the submittal goes straight in, and an RFI only follows if the review turns up a conflict.