RFIs resolve missing, conflicting, or unclear information. Submittals demonstrate how a contractor proposes to satisfy specified requirements. Neither should become a substitute for incomplete design or unauthorized redesign.
Use RFIs for real questions
An RFI should identify the drawing or specification, location, observed conflict, required decision, schedule need, and proposed solution where appropriate.
Broad or repetitive questions often signal weak document control or scope definition.
Use submittals to verify intent
Product data, shop drawings, samples, calculations, certifications, mockups, and delegated-design documents can confirm dimensions, performance, appearance, and coordination.
Review generally does not transfer the contractor's responsibility for means, methods, dimensions, or contract compliance.
Control priority and dates
Every item should have required-on-site, fabrication, approval, review, and response dates.
A late RFI or submittal can delay work even when the formal response is prompt.
Coordinate affected disciplines
Structural, architectural, mechanical, electrical, plumbing, envelope, interiors, and site interfaces may need joint review.
One discipline's response should not create a conflict elsewhere.
Close the loop in the field
Approved information must reach purchasing, fabrication, installers, inspectors, budget, schedule, and record drawings.
Superseded or rejected submittals should not remain available as field direction.
The BuildProof Question-to-Field Workflow
Question-to-Field Workflow turns the topic into a repeatable national workflow while preserving the local evidence required for a defensible project decision.
| Step | Required action | Exit test |
|---|---|---|
| 1. Ask | Create a complete RFI or submittal with location and need date. | The issue is reviewable. |
| 2. Route | Send to responsible and affected reviewers. | Coordination occurs. |
| 3. Decide | Record response, approval status, conditions, and impact. | Direction is authoritative. |
| 4. Distribute | Update procurement, field, cost, and schedule. | The decision reaches execution. |
| 5. Archive | Retain approved and superseded status correctly. | The record stays clean. |
What to document
- RFI form
- Submittal register
- Required response date
- Affected disciplines
- Approval status
- Cost and time impact
- Field distribution
- Record-drawing update
Common failure modes
- Using RFIs to request owner upgrades
- Submitting after fabrication
- Treating approved as approved as noted
- Failing to route cross-discipline items
- Leaving superseded documents in field folders
Frequently asked questions
Who answers RFIs?
The responsible design professional or authorized party answers within the contract structure.
Does submittal approval authorize extra cost?
Not automatically. Contract change procedures control cost and time.
How many RFIs are normal?
There is no universal number. Trends, cause, quality, timing, and impact matter more than count.
BuildProof next step
Use a single RFI and submittal register tied to procurement, schedule, and field document control.
If you run a building company and want to see how this looks inside a single system, book a BuildProof demo.
Sources
- National Institute of Standards and Technology — Construction
- FEMA — Building Science
- Building America Solution Center
- OSHA — Residential Construction
Editorial note: Codes, permits, contractor licensing, lien rights, taxes, insurance, environmental review, financing, and professional-practice rules vary by state and local jurisdiction. Verify project-specific requirements with qualified local professionals and the authorities having jurisdiction.