A single RFI that takes 6 days to resolve can cause a 3-week schedule slip. Not because the work itself takes 3 weeks, but because the delayed information caused the crew to stand down, a subcontractor to demobilize, a following trade to lose its window, and a pour to miss its weather hold. The cascade from one unresolved information request is rarely proportional to the request — it's proportional to where that activity sits on the critical path.
This article is about how to identify when an RFI is creating schedule impact, how to calculate and document that impact, and how to present it in a way that supports a time extension request or change order for delay costs.
The Difference Between a Delay and a Schedule Impact
Not every RFI that takes longer than expected creates a compensable schedule delay. The factors that determine whether an RFI delay creates recoverable impact:
- Critical path dependency. An RFI that delays an activity with float doesn't delay the project completion date — it just consumes some or all of that activity's float. An RFI that delays a critical-path activity delays the project by the same number of days, potentially more.
- Responsible party. If the RFI delay is attributable to the owner, architect, or EOR — not to the GC's lack of coordination or late submission — the delay may be owner-caused and therefore compensable. If the GC submitted the RFI late (e.g., identified a drawing conflict 2 days before the pour rather than 10 days before), the compensability question is more complex.
- Actual impact on crews and cost. A 3-day RFI delay on a critical activity that caused a crew to stand down or be redirected has quantifiable impact. The same delay that occurred during a period when the crew was working elsewhere due to normal sequencing may have had no actual cost consequence.
How to Calculate Schedule Impact
For a specific RFI delay, the calculation follows a defined sequence:
Step 1: Identify the affected activity
Specify the schedule activity that was delayed. Not "the RFI affected the project" — specifically: "RFI #47 regarding Level 5 MEP rough-in routing, which affected Activity 5.3.1 (Level 5 Mechanical Rough-In) in the project CPM schedule."
Step 2: Establish the delay duration
The delay duration is measured from when the RFI should have been answered (the required response date per your contract or industry standard — typically 7–14 calendar days depending on complexity) to when the response was actually received. If the contract specifies a response period and the response was late, the delay is measured against the contract requirement. If the contract doesn't specify, industry standard for a routine clarification is 7 calendar days; structural or MEP questions with EOR involvement may reasonably require 10–14 days.
Step 3: Establish critical path impact
Was the affected activity on the critical path when the delay occurred? This requires reference to the project schedule as it existed at the time of the delay — ideally a schedule update or monthly schedule submission that shows Activity 5.3.1 as critical (zero float). A project schedule that shows float doesn't preclude a delay claim, but you need to demonstrate that the float was consumed by the time the RFI delay occurred.
Step 4: Document the actual crew impact
This is where daily logs become critical. For each day the crew was idle or redirected because of the open RFI:
- Daily log entry showing the crew on site, work held, and the RFI identified as the cause
- Crew count affected (from daily log)
- Labor rate and burden to calculate daily cost of idle or redirected crew
- Any equipment idle costs
- Acceleration costs if the crew worked overtime to recover after the RFI resolved
Step 5: Calculate delay cost
The delay cost calculation for owner-caused RFI delay typically includes:
- Extended general conditions for the number of days of delay
- Idle labor costs for crews that were on-site but unable to work on the delayed activity
- Subcontractor delay costs (documented by sub, passed through by GC)
- Acceleration costs to recover schedule (overtime, additional shifts) if applicable
Documentation That Makes the Claim
A schedule delay claim from RFI delay that will survive owner review or a dispute process needs to be backed by contemporaneous documentation created at the time the delay occurred — not reconstructed afterward.
The key documents:
- The RFI record itself, with submission date, required response date, and actual response date. This is the foundational delay document.
- Daily logs for the delay period, showing the crew on site, the work held, and the RFI cited as the delay cause. A daily log that says "Level 5 mechanical rough-in on hold — RFI #47 open, awaiting EOR response on high-bay routing conflict" is a contemporaneous record of delay. Daily logs created weeks after the fact don't carry the same weight.
- The project schedule at time of delay, showing the affected activity and its float status. A monthly schedule update is better than a baseline schedule; it shows the schedule state when the RFI delay actually occurred.
- Correspondence documenting escalation, if any — emails or BuildVyne message threads showing that you notified the architect or owner of the delay risk from the open RFI. Documented escalation strengthens the notice argument.
Notice Requirements
Most commercial construction contracts include a notice provision for delay claims: the GC must notify the owner within a specified period (commonly 7–21 days) of the onset of a delay in order to preserve the right to claim time and compensation. Check your contract for the specific requirement and the form of notice required.
In practice, GC teams often fail to submit timely formal notice for RFI-related delays because the PM doesn't recognize the delay as compensable at the time it's occurring. The RFI is just "taking a while." By the time the impact is understood, the notice window has passed.
The practical solution is to review open RFIs against the project schedule weekly. Any open RFI past its required response date that is linked to a critical-path or near-critical activity should trigger an automatic notice review — not a wait-and-see.
Presenting the Claim
RFI delay claims that are well-documented, presented concisely, and limited to actual recoverable costs tend to be resolved faster than claims that are speculative, broadly calculated, or presented without contemporaneous support. The owner's PM and legal team will evaluate the documentation quality as a signal of claim validity.
A clear, documented claim with the RFI record, daily logs, schedule analysis, and cost calculation is harder to dispute than a vague claim for "extended general conditions due to information delays." Specificity is your protection.