Construction RFIs: connect the answer to the scope and number it changes
An answered construction RFI can leave the estimate stale. Review tracing clarifications into trade scope, proposals, pricing and approval records.
Author
Ido Gedanken, CEOPublished

Bring a current or completed project and see how Piper saves review time, surfaces scope gaps, and applies your company's knowledge.
Book a demo- Type
- Guide
- Read
- 3 min
- Published
On this page
A request for information, or RFI, asks for clarification of project information. For an estimating team, receiving an answer is only one step. The useful closeout is showing what the answer changes in trade scope, quotation coverage, the estimate and any decision already made from the earlier information.
A clarification is also different from contractual authorization to change the work or price. The executed agreement and procurement instructions determine the applicable process.
Ask a question that can change a decision
Identify the conflicting or missing requirement, cite its document location, explain the affected package and state what the team needs clarified. Avoid asking a broad question without showing why its answer matters to pricing or scope.
AIA's construction-administration guidance describes RFIs as a way to obtain clarification from the design team. Its discussion of changes also makes clear that the clarification process and formal change instruments have different roles.
Separate the question from the pricing assumption
Before an answer arrives, record what the estimate currently carries and who approved that provisional basis. Do not let a question marked “open” coexist with an undocumented plug that later appears to be a firm price.
An illustrative equipment-support detail might leave the structural and mechanical bidders each assuming support work is by others. The RFI needs to clarify the requirement, while the scope review needs to identify who carries the resulting work.
Route the answer to the affected packages
List the recipients and downstream records that must be revisited. The answer may change an installation detail, quantity, access need, testing requirement or responsibility boundary. It can affect more packages than the one that originally raised the question.
Use the drawing-revision method to trace those consequences. Do not assume that copying every bidder on an email proves the quoted work was updated.
Verify the treatment in the proposal and estimate
Record the revised proposal or other pricing support, the selected carry and any remaining qualification. Distinguish “answer received,” “scope reconciled” and “price reviewed” as different statuses.
The addenda-management guide addresses the same gap between document distribution and completed estimating work. Acknowledgment is useful evidence of receipt, not proof of substantive coverage.
Preserve the contract-administration boundary
If the answer appears to change the contracted work, follow the applicable procedure and review the difference between directives and change orders. Do not infer authority or entitlement from the title “RFI response.”
Piper's Survey workflow can help apply company questions to source documents and identify unanswered items. Its Scope Generation workflow helps turn confirmed requirements into reviewable packages. The project team still issues the RFI through the required process and approves the resulting scope and pricing treatment.
For Summit Playground reconstruction review, turn missing design and package information into specific bid questions rather than assuming the tracker supplies a construction scope.
For the related project-specific decision, see how to review OGS construction bid requirements and carry the result into bid review.
For an Albany designated property, the historic exterior scope review tests the approved material against a proposed substitute before procurement.
Where this fits in Piper
Survey
Turn your company's experience into a repeatable survey that captures what the team learns and improves over time.
Scope Generation
Turn drawings, specifications, addenda, and company standards into source-backed trade scopes.
Related reading
Construction addenda management for GC estimators
Addenda are official bid-document revisions. Log them, distribute them, retakeoff the deltas, and require subcontractor acknowledgments so your estimate and every bid reflect the final scope.

What Changed? How Drawing Revisions Cascade Through Scope, Bids, and the Estimate
A drawing revision is not only a sheet delta. Trace what it does to trade scopes, live bids, and the estimate before bid day locks the number.

Construction change directive vs. change order: keep authority, scope and price separate
A change directive can move work ahead before price and time are agreed. A GC review method for preserving the scope baseline, cost evidence and open decisions.

Piper removes manual review from the critical path and brings project data, company knowledge, and expert checks into every preconstruction decision and workflow
See Piper on your project
Bring a current or completed project and see how Piper saves review time, surfaces scope gaps, and applies your company's knowledge.