On this page
A submittal shows the architect or engineer what the contractor intends to furnish and install, such as shop drawings, product data or samples, so they can check it against the design. An RFI (request for information) asks the design team what the drawings or specifications mean when they are unclear, incomplete or in conflict. A submittal says “here is what we will build”; an RFI asks “what do you want us to build?” Neither one changes the contract price or time by itself.
Both go to the same people, both carry a ball in court and a due date, and both sit in logs the PM reviews every week, so they get mixed up. Sending the wrong one costs days, because the reviewer returns it, and sometimes costs money, because an answer that changes scope never gets priced.
Side by side
| Submittal | RFI | |
|---|---|---|
| Purpose | Show how the work will meet the documents | Clarify what the documents require |
| Direction | Contractor proposes, designer reviews | Contractor asks, designer answers |
| Required by | The specifications, item by item | Whatever question comes up |
| Usually prepared by | Sub or supplier, reviewed and stamped by the GC | Field staff or a sub, reviewed and sent by the GC |
| Typical content | Shop drawings, product data, samples, test reports, calcs | Question, drawing and spec references, photos, a proposed answer |
| Typical response | An action code: approved, approved as noted, revise and resubmit, rejected | A written answer, sketch or supplemental instruction |
| Known in advance | Yes, listed on the submittal register | No |
| Changes the contract | No, by itself | No, by itself |
| Can lead to | Fabrication and ordering | A change event if the answer changes scope or time |
When to send a submittal
Send a submittal when the specifications ask for one. The submittal procedures section, usually Section 01 33 00 in MasterFormat-organized specs, sets the general rules, and each technical section lists the shop drawings, product data, samples and other items it needs. Build the register from those sections at the start of the job, schedule each item backward from its install date, and send it after the GC has reviewed it for field dimensions, coordination and completeness.
A submittal is the right vehicle when you are proposing how you will meet the documents: the anchor layout for a curtain wall, the specific pump model, the color of the brick. If something in it deviates from the documents, call that deviation out in writing. Reviewers are not expected to find it for you, and under AIA-based general conditions an approval generally doesn’t cover a deviation you didn’t identify.
When to send an RFI
Send an RFI when you can’t tell what the documents require: two sheets disagree, a dimension is missing, a detail doesn’t fit the field condition, or a spec calls for a product that has been discontinued. A good RFI asks one question, references the sheet and spec section, includes a photo or sketch, proposes an answer and says when you need it. How to write an RFI covers the format in detail.
Before sending, check that the answer isn’t already in the documents. RFIs that are answered with “see sheet A-501” waste the reviewer’s time and erode the credibility of the ones that matter.
How they connect
The two often travel together. An RFI answer can change what a submittal has to show, and a submittal review can expose a conflict that needs an RFI. When that happens, reference one in the other so the record shows the chain, and if the answer changes scope or time, open a change event the same day. The RFI to change order explainer follows that path to billing.
Who owns each one on the GC side
On most jobs a project engineer or assistant PM runs both logs, but the ownership is different. Submittals belong to the trade that will furnish the work: the sub prepares the package, and the GC’s job is to review it, push it through on time and make sure the approved version reaches the field. RFIs belong to whoever found the problem, usually the superintendent or a foreman, and the GC’s job is to make the question clear, check it isn’t already answered, and distribute the answer to every trade it affects.
That difference shows up in the logs. A late submittal is usually a sub follow-up problem. A late RFI answer is usually a design team follow-up problem, and a pattern of them is worth raising at the OAC meeting with the dates in hand.
A worked example
Illustrative: the electrical sub prepares the lighting fixture submittal and finds that the fixture schedule calls for a recessed fixture in a corridor where the reflected ceiling plan shows an exposed structure with no ceiling.
The wrong move is to submit a surface-mounted fixture with no explanation and hope the reviewer catches it. The right sequence:
- RFI first. “Sheet E-201 schedules type F3 recessed at corridor 140. Sheet A-401 shows open structure at corridor 140. Please confirm the fixture type. Proposed: pendant version of F3 at 10’-0” AFF. Answer needed by June 12 to hold the fixture release.” The architect answers: use the pendant version.
- Submittal next. The fixture submittal includes the pendant version for corridor 140 and references the RFI number.
- Change event if needed. The pendant fixture costs more than the recessed one, plus stems and labor. The PM logs a change event tied to the RFI so the cost gets priced, rather than buried in the sub’s next invoice.
Common mistakes
- Using an RFI to ask for a substitution. Most specs set out a separate substitution procedure with its own deadline. Follow it.
- Hiding a deviation in a submittal. If it isn’t called out, approval usually doesn’t cover it.
- Treating an RFI answer as a change order. It isn’t one. Price the change and get it approved.
- Passing sub submittals through unreviewed. The GC’s review stamp means something under most contracts.
- Late submittals on long-lead items. Fabrication can’t start until the action code allows it.
- No cross-references. When the RFI, submittal and change event don’t point to each other, nobody can reconstruct the story at closeout.
Tools
The RFI checklist covers what every RFI should include, the RFI response time calculator measures turnaround, and how to track submittals and the submittals without the chase explainer cover the register.
In os.construction, RFIs carry ball in court, due dates and Related Items that link to submittals, drawings and change events, and submittals route through an ordered approval workflow with ball in court on each step. A drawing revision can link the RFIs raised against it, and an approved submittal can be prepared into a purchase request, so each log feeds the next step instead of a retyped list.
FAQ
What is the difference between a submittal and an RFI?
A submittal is a package the contractor sends to show what it intends to furnish and install, such as shop drawings, product data or samples, so the design team can review it against the design intent. An RFI is a question the contractor sends when the drawings or specifications are unclear, incomplete or in conflict. A submittal says 'here is what we will do'; an RFI asks 'what do you want?'
Can an RFI be used to request a substitution?
Usually not. Most specifications set out a separate substitution request procedure with its own deadlines and required information. Asking for a different product through an RFI tends to get it returned, and an informal yes may not count as an approved substitution.
Does an approved submittal change the contract?
Generally no. Under AIA-based general conditions, submittal approval doesn't authorize a change to the contract documents unless the contractor specifically called out the deviation in writing and the architect specifically approved it, and even then a cost or time change still needs a change order. Other contract forms take similar approaches.
Who prepares submittals and RFIs?
Submittals are usually prepared by the subcontractor or supplier who will furnish the work, reviewed and stamped by the general contractor, and sent to the architect or engineer. RFIs can start with anyone on the build side, but the general contractor normally reviews, numbers and sends them so the design team gets one official stream of questions.
Are submittals and RFIs required by the contract?
Submittals are required item by item by the specifications, usually listed in the submittal procedures section and in each technical section. RFIs are not scheduled in advance; they are raised as questions come up, though the contract often sets a procedure and a response time for them.
Share this article