How does an RFI relate to a change order?

An RFI becomes the basis for a change order when the engineer's or architect's response requires the contractor to perform work beyond the original contract scope, use different materials, or accept a design change that affects the project cost or schedule. The RFI log provides the documented timeline showing when the question was asked, when the response was received, and whether any work was delayed waiting for the answer. For a change order to be approved, the contractor must demonstrate that the changed scope resulted from an ambiguity, conflict, or change in the contract documents — and the RFI is the record that establishes that sequence. RFIs without documented response dates make it difficult to prove schedule impact in a disputed change order.

Home/Blog/Field Documentation/RFI Documentation for Construction

Field Documentation

RFI Documentation for Construction: Field Engineers Guide

The RFI is the formal record of every question, conflict, and design gap that surfaces during construction. A well-documented RFI log is the difference between a project that processes change orders efficiently and one that ends in a dispute because nobody can establish when a question was asked, when the answer came back, or whether work was performed at risk. Field engineers who understand RFI documentation protect their companies even on projects where the design was incomplete.

Published May 29, 2026·8 min read

Start Free Trial

Quick Answer

What must an RFI contain on a construction project?

A construction RFI must contain: a unique sequential RFI number; project name and contract number; date submitted; requesting party name; a clear description of the question or conflict with references to the specific drawing sheet, detail number, and specification section; the specific information requested; the contractor's proposed resolution where applicable; the response-required date to avoid schedule impact; and the name of the person or firm the RFI is directed to. RFIs that lack drawing references or ask compound questions are commonly returned without response.

7 calendar days for routine RFIs; 14 days for complex; contract may specify

Standard response period

Retain for the duration of the statute of repose — typically 10 years in most states

RFI log retention

RFI requests information; it does not authorize changed work — a PCO or CO must follow if scope changes

Key distinction

Required Content of a Construction RFI

An RFI that omits critical information will be returned, rejected, or ignored — adding days to the response cycle and compressing the construction schedule. Required content fields:

Field	Content Requirement
RFI number	Sequential number; never reuse or skip numbers. The log must account for every number in sequence.
Date submitted	The date the RFI is transmitted to the architect, engineer, or GC. Not the date it was drafted.
Title	Brief, specific description: "Foundation drain direction at Grid B-7" is better than "Drain question."
Description of question or conflict	State what the contract documents show (with specific drawing and spec references) and what the conflict or ambiguity is. Include markup sketches where applicable.
Drawing and specification references	Sheet number, detail number, and specification section that the question relates to. Without these, the respondent cannot locate the referenced condition.
Proposed answer	The contractor's suggested resolution. This is not mandatory, but RFIs with a proposed answer are typically responded to faster and more favorably.
Required response date	The date by which a response is needed to avoid work stoppage or schedule delay. This establishes the baseline for delay claims if the response is late.
Directed to	The specific person or firm responsible for answering — architect, structural engineer, MEP engineer, or GC depending on the question.

RFI Log Management

The RFI log is the master tracking document for all RFIs on a project. It must be maintained in real time — not assembled retroactively at closeout. A well-managed RFI log includes:

Status tracking. Each RFI must show its current status: Draft, Submitted, Under Review, Responded, Closed, or Voided. An RFI without a tracked status is invisible to project management.
Response date tracking. Log the required response date and the actual response date for each RFI. The gap between these two dates — when the response is late — is the documented impact period for delay calculations.
Cost impact flagging. When a response authorizes changed work, flag the RFI as "Cost Impact — PCO Pending" or "Cost Impact — CO Issued" with the associated PCO or CO number. This links the change order record back to the RFI that generated it.
Schedule impact flagging. When work is delayed waiting for an RFI response, note the delayed activity and the number of days affected. This is the contemporaneous record that supports a time extension claim.

How to Write a Clear RFI

Poorly written RFIs waste time on both sides of the question. The most common RFI writing failures and how to avoid them:

Common Failure	Better Practice
Compound questions: "Please clarify the slab thickness, rebar layout, and top-of-slab elevation"	One question per RFI. Each separate issue gets its own RFI number and tracking.
No drawing reference: "The grading plan is unclear"	Reference specific sheet: "Civil Drawing C-3, Detail 2/C-3 shows finish grade elevation as 104.5, but the drainage flow arrow points uphill. Confirm design intent."
Answer embedded in question: "Please confirm the invert is 98.3 as installed"	An RFI is a question, not a CYA. State the conflict and ask for the answer — do not assume.
No required response date	Always include the date by which a response is needed. If the work is imminent, note the pour date or schedule milestone.
No proposed resolution	Include a proposed resolution where the contractor has a preference. This moves the respondent toward a decision rather than requiring them to generate a solution from scratch.

RFI Documentation and Change Orders

The RFI log is the starting point for change order substantiation. When an RFI response requires changed work, the process from RFI to change order must be documented in a traceable chain:

RFI submitted. Log the submission date and the required response date. The required response date establishes when you needed the information to maintain the schedule.
Response received. Log the actual response date. If the response is late, calculate the delay period and document it in the daily field report.
Response triggers changed work. When the response confirms a scope change, issue a Potential Change Order (PCO) or Change Order Request (COR) that references the RFI number and attaches the response document.
Cost and schedule impact documented. The PCO must include: the additional work required, the direct cost breakdown, the schedule impact analysis referencing the delayed activity, and the requested extension of time.
Change order issued. When the change order is executed, update the RFI log to show the associated CO number. The RFI is now closed.

Sitemark's field documentation tools let field engineers log RFIs in the field with drawing attachments, track response status and dates, and link RFI records to daily field reports that document schedule impacts — creating the contemporaneous documentation chain that supports change order approvals.

RFI Records That Support Change Orders

Sitemark captures RFI submissions, response dates, and linked field report entries — giving your project team the contemporaneous documentation chain that makes change orders approvable and disputes avoidable.

Start Free Trial

Related Reading

Field Documentation

Daily Field Report Best Practices for Contractors

Field Documentation

How Field Documentation Protects Contractors from Liability

RFI Documentation for Construction: Field Engineers Guide

Published May 29, 2026·8 min read

Required Content of a Construction RFI

An RFI that omits critical information will be returned, rejected, or ignored — adding days to the response cycle and compressing the construction schedule. Required content fields:

Field	Content Requirement
RFI number	Sequential number; never reuse or skip numbers. The log must account for every number in sequence.
Date submitted	The date the RFI is transmitted to the architect, engineer, or GC. Not the date it was drafted.
Title	Brief, specific description: "Foundation drain direction at Grid B-7" is better than "Drain question."
Description of question or conflict	State what the contract documents show (with specific drawing and spec references) and what the conflict or ambiguity is. Include markup sketches where applicable.
Drawing and specification references	Sheet number, detail number, and specification section that the question relates to. Without these, the respondent cannot locate the referenced condition.
Proposed answer	The contractor's suggested resolution. This is not mandatory, but RFIs with a proposed answer are typically responded to faster and more favorably.
Required response date	The date by which a response is needed to avoid work stoppage or schedule delay. This establishes the baseline for delay claims if the response is late.
Directed to	The specific person or firm responsible for answering — architect, structural engineer, MEP engineer, or GC depending on the question.

RFI Log Management

The RFI log is the master tracking document for all RFIs on a project. It must be maintained in real time — not assembled retroactively at closeout. A well-managed RFI log includes:

Status tracking. Each RFI must show its current status: Draft, Submitted, Under Review, Responded, Closed, or Voided. An RFI without a tracked status is invisible to project management.
Response date tracking. Log the required response date and the actual response date for each RFI. The gap between these two dates — when the response is late — is the documented impact period for delay calculations.
Cost impact flagging. When a response authorizes changed work, flag the RFI as "Cost Impact — PCO Pending" or "Cost Impact — CO Issued" with the associated PCO or CO number. This links the change order record back to the RFI that generated it.
Schedule impact flagging. When work is delayed waiting for an RFI response, note the delayed activity and the number of days affected. This is the contemporaneous record that supports a time extension claim.

How to Write a Clear RFI

Poorly written RFIs waste time on both sides of the question. The most common RFI writing failures and how to avoid them:

Common Failure	Better Practice
Compound questions: "Please clarify the slab thickness, rebar layout, and top-of-slab elevation"	One question per RFI. Each separate issue gets its own RFI number and tracking.
No drawing reference: "The grading plan is unclear"	Reference specific sheet: "Civil Drawing C-3, Detail 2/C-3 shows finish grade elevation as 104.5, but the drainage flow arrow points uphill. Confirm design intent."
Answer embedded in question: "Please confirm the invert is 98.3 as installed"	An RFI is a question, not a CYA. State the conflict and ask for the answer — do not assume.
No required response date	Always include the date by which a response is needed. If the work is imminent, note the pour date or schedule milestone.
No proposed resolution	Include a proposed resolution where the contractor has a preference. This moves the respondent toward a decision rather than requiring them to generate a solution from scratch.

RFI Documentation and Change Orders

The RFI log is the starting point for change order substantiation. When an RFI response requires changed work, the process from RFI to change order must be documented in a traceable chain:

RFI submitted. Log the submission date and the required response date. The required response date establishes when you needed the information to maintain the schedule.
Response received. Log the actual response date. If the response is late, calculate the delay period and document it in the daily field report.
Response triggers changed work. When the response confirms a scope change, issue a Potential Change Order (PCO) or Change Order Request (COR) that references the RFI number and attaches the response document.
Cost and schedule impact documented. The PCO must include: the additional work required, the direct cost breakdown, the schedule impact analysis referencing the delayed activity, and the requested extension of time.
Change order issued. When the change order is executed, update the RFI log to show the associated CO number. The RFI is now closed.