Unanswered RFI Construction Delay: What Project Teams Should Check Before It Reaches the Critical Path

A critical RFI is submitted because the drawings do not provide enough information to complete a planned activity. Five days pass with no answer. By day ten, the work is approaching the critical path. The project manager keeps chasing the designer. Commercial sees delay accumulating. Contract administration asks a different question: what did the contract require the relevant party to provide, and what should happen when that information is late?

That distinction matters. An unanswered RFI can be an operational frustration, but it is not automatically a contractual delay event. The contract may allocate responsibility for design information, approvals, directions, coordination and response timing in different ways. The project team therefore needs to connect the unanswered question to the underlying contractual obligation before assuming that an EOT, cost claim or other entitlement exists.

Direct answer: can an unanswered RFI cause a construction delay?

Yes. An unanswered RFI can contribute to construction delay where the missing information prevents or disrupts planned work. But the RFI itself does not automatically establish contractual responsibility or entitlement. Teams should check who was required to provide the information, when it was required, whether the RFI was properly framed and submitted, what notice provisions apply, and whether the delay actually affected the programme.

Key takeaways

• An RFI is a communication tool; the contractual issue is the underlying information, clarification or approval obligation.
• “Late” operationally does not necessarily mean late contractually. Check the contract, programme and agreed review periods.
• An unanswered RFI does not automatically create an EOT; programme impact, responsibility and notice compliance still matter.
• Notice obligations may arise before work physically stops.
• Records should connect the RFI to the required information, responsible party, programme activity, mitigation and actual consequences.
• Chasing the answer and protecting contractual processes should happen in parallel.

Why an unanswered RFI is not automatically a contractual event

RFIs may seek clarification of drawings, conflicting documents, missing dimensions, specifications or design decisions needed before procurement, fabrication or installation. But “RFI” is usually the name of the communication, not the contractual source of the obligation.

The contract may instead deal with principal-supplied information, contractor design, discrepancies, approvals, directions, programmes or information-release timing. That creates an important distinction:

Operational question: Has the RFI been answered?

Contractual question: Was another party required to provide the information by a particular time, and what happens if it is not provided?

A ten-day-old RFI may not create compensable delay if the information was not yet required, the request was late, responsibility sat with the contractor, or other work could reasonably proceed. Conversely, the issue can become commercially significant before work stops if procurement, fabrication or a critical activity is clearly approaching the point where the information is needed.

Event-to-contract map for an unanswered RFI

The last row is particularly important. An RFI response can solve one problem and create another. If the answer changes scope, materials, dimensions, sequence or design requirements, the team may need to assess a variation or change pathway separately from the delay caused by waiting for the response.

When is an RFI response actually late?

There is no universal contractual response period for every RFI.

A project procedure may nominate a target turnaround, but the contract may use a different mechanism. It might require information by dates shown in the contract programme, require submissions a specified period before use, set an approval period, or require a party to respond within a stated or reasonable period.

NSW Government guidance for GC21 illustrates the point: certain information, documents or instructions are tied to programme timing or timing that could reasonably have been anticipated. Information timing therefore needs to be considered alongside the programme, not just as an inbox metric.

A commercially useful RFI register should capture the required-by date, responsible party, affected activity or procurement package, forecast impact date, notice trigger and escalation owner. An internal turnaround KPI may help administration, but it is not automatically the contractual deadline.

Does an unanswered RFI entitle the contractor to an EOT?

Not automatically.

An EOT assessment should start with the contract, not with the number of days the RFI has been open. The team should examine at least six questions.

1. Who carried the information risk? Was the principal, superintendent, designer, contractor or another party responsible for the missing information?
2. Was the request necessary and properly submitted? Did it identify a genuine ambiguity or information gap, or was it asking the other party to resolve something already allocated to the contractor?
3. When was the answer required? Was there a contractual date, programme date, review period or other timing mechanism?
4. Did the delayed answer affect the relevant programme? Which activity, float, milestone or critical-path sequence was affected?
5. Were notice requirements satisfied? Did the contract require early notification, an EOT claim, continuing notices or supporting particulars?
6. What mitigation or concurrent delay existed? Could other work proceed, and were there independent delays affecting the same period?

NSW Government guidance on extensions of time emphasises the need for evidence of the alleged delaying event and evidence that it affected the critical path. That is a useful discipline even where the project uses a different contract form.

The practical point is straightforward: ten days without an RFI answer does not necessarily equal ten days of EOT.

The notice clock may start before the work stops

This is where unanswered RFIs can become dangerous commercially.

The site team may think, “We are not delayed yet; the activity is still two weeks away.” But some contracts require notice when a party becomes aware of an event that may cause delay, not only after critical-path delay has already occurred.

If the RFI has been outstanding for several days and the required information date is approaching, the team should check the notice provisions immediately.

Depending on the contract, relevant steps may include:

• notice of a potential or actual delay;
• an EOT notice or claim;
• notification of failure to provide information;
• early warning or risk notification;
• continuing or updated notices;
• a separate cost or claim notice; and
• downstream notices to subcontractors or suppliers.

Perfomir’s guide to notice obligations in construction contracts explains why trigger events, deadlines, recipients, service methods and supporting information need to be checked against the actual contract.

The existing Perfomir article on notice of delay in construction contracts provides deeper guidance on the distinction between a delay notice and an EOT claim. That broader process should not be confused with simply sending reminder emails on an RFI.

Chasing the designer is necessary, but it is not contract administration

Repeated follow-up is often the correct operational response, but “please respond urgently” emails may not establish when the information was required, what activity depended on it, when delay became foreseeable, what mitigation was available or whether formal notice was required.

A well-administered project therefore runs two processes together:

Operational process: obtain the answer as quickly as possible.

Contractual process: manage the relevant obligations, notices, programme effects and records.

Doing both early is more effective than reconstructing the sequence after completion has moved.

What records should support an unanswered-RFI delay?

The RFI itself is only one piece of the evidence.

Contemporaneous records are also a core theme in the Society of Construction Law Delay and Disruption Protocol, which emphasises transparency of information and methodology when delay and disruption are assessed.

Good records help both parties. They can support a genuine delay position, but they can also show that an RFI did not affect the critical path, that sufficient information was already available, or that mitigation prevented the forecast impact from occurring.

What if the RFI response changes the work?

An unanswered RFI and the eventual response can create separate events. The waiting period may raise delay questions; the answer itself may raise change questions.

If the response changes the priced or planned basis, project teams should compare it with the contractual scope, drawings, specifications and prior directions. A response that changes what must be procured, fabricated, installed or sequenced may require a variation or other change pathway in addition to any delay analysis.

How should the project team respond? An 8-step framework

When a critical RFI remains unanswered, use the following process.

1. Define the missing information. Make sure the RFI is specific, necessary and tied to the relevant drawings, specifications or project decision.
2. Confirm responsibility. Check which party is contractually responsible for the design, information, approval or direction being sought.
3. Establish the required-by date. Use the contract, programme, procurement schedule and agreed review periods to determine when an answer is actually needed.
4. Link the RFI to the programme. Identify affected activities, float, milestones, procurement and the date at which the issue becomes time-critical.
5. Check notice requirements. Do not wait until the work physically stops if the contract requires earlier notice of a likely delay.
6. Escalate operationally. Chase the responsible reviewer, clarify the consequence of continued delay and obtain a committed response date where possible.
7. Mitigate and record. Consider alternative workfronts, resequencing, partial information, deferred procurement or other reasonable options, while recording their consequences.
8. Reassess when the answer arrives. Determine whether the response resolves the issue only or also introduces a change, variation, rework or new programme effect.

This framework changes the RFI register from a document-control list into a project-risk control.

Who should ask what?

This shared ownership matters because an RFI can move from technical coordination to programme and commercial exposure quickly.

Common mistakes with unanswered RFIs

Common mistakes include treating every overdue RFI as principal-caused delay; using an internal response KPI as if it were a contractual deadline; waiting for critical-path impact before checking notice clauses; failing to link the RFI to a specific activity; issuing vague RFIs; ignoring contractor design responsibility; failing to assess the eventual response as a possible change; and recording reminders without recording mitigation.

The common thread is failure to connect the technical query with the contract and programme early enough.

From unanswered RFI to commercial risk

A practical contract-intelligence chain for this event is:

Project Event → Relevant Clause → Contractual Obligation → Notice Requirement → Potential Entitlement → Commercial Risk

For an unanswered RFI:

Project event: required technical information or a decision remains unresolved.

Relevant clause: design, information, approval, direction, discrepancy, programme, delay or EOT provisions.

Contractual obligation: determine who must supply or decide the information and by when.

Notice requirement: identify whether the developing delay, information failure or claim pathway requires formal notification.

Potential entitlement: assess possible time, cost or variation consequences without assuming they exist.

Commercial risk: consider completion exposure, procurement delay, idle resources, disruption, acceleration pressure, subcontract claims and dispute escalation.

Perfomir’s contract risk intelligence framework is designed around this connection between live events and contractual obligations rather than treating the contract as a document reviewed only at mobilisation.

How Contriqo supports an unanswered-RFI review

Contriqo by Perfomir is an AI contract intelligence and decision-support platform for construction and infrastructure. It is not positioned as a generic RFI workflow or document-control system.

Its relevant role begins when the project event needs to be analysed against the contract.

For an unanswered RFI, Contriqo can help teams connect the event with relevant clauses, obligations, notice requirements and potential claim-exposure pathways. That can help commercial and project teams recognise that an apparently technical information issue may require contract review before the programme impact becomes obvious.

Perfomir’s contract administration risk intelligence guidance explains this distinction: project systems may manage RFIs and submissions, while contract intelligence adds visibility over the contractual mechanisms those events may activate.

The platform does not determine entitlement conclusively, prove delay causation or replace the planner, contract administrator, commercial manager or legal adviser. It supports earlier professional review. That matters because claim exposure can develop through ordinary events such as unresolved RFIs, delayed approvals and missing information before a formal claim exists.

Frequently asked questions

How long should an RFI take to answer in construction?

There is no universal contractual response period. Projects often use internal or agreed turnaround targets, but contractual timing may depend on a specific review period, programme date, required-by date or other obligation. The project team should distinguish an internal KPI from a contractual deadline.

Can an unanswered RFI support an extension of time?

It may, depending on the contract and facts. The team normally needs to establish the responsible party, the relevant contractual delay event, compliance with notice requirements and an actual effect on the applicable programme or completion obligation.

When should an RFI delay notice be issued?

Check the contract as soon as the missing information may affect progress. Some notice provisions are triggered by awareness of a likely delay rather than by the date work actually stops.

Is chasing the RFI by email enough?

Not necessarily. Reminder emails may help obtain the response but may not satisfy contractual notice requirements for delay, EOT, claims or other formal processes.

What records are important for an RFI delay?

Useful records include the RFI, drawings and specifications, design-responsibility information, programme links, required-by dates, follow-up correspondence, meeting minutes, site diaries, procurement records, mitigation evidence, cost records and formal notices.

Can an RFI response become a variation?

Potentially. If the response changes the contractual scope, design requirement, materials, quantities, sequence or other work requirement, the team should separately examine the contract’s change or variation provisions.

Key conclusion

The project manager is right to chase the designer. The commercial manager is right to watch the developing delay. The contract administrator is right to ask what the contract says about providing information.

None of those actions should happen in isolation.

An unanswered RFI should be treated as an event that may need to be mapped from technical issue to contractual obligation, notice requirement, programme effect and commercial exposure. The earlier that connection is made, the easier it is to preserve records, escalate the right issue and make informed decisions while mitigation remains possible.

The project event is the trigger. The contract determines what happens next.

This article provides general educational information only and does not constitute legal, contractual or financial advice. Contract terms and project circumstances vary. Obtain appropriately qualified advice for your specific contract and situation.

Have a contract? See how Contriqo analyses project events against your contractual obligations.

References

• NSW Government — Construction procurement guide: avoiding delay — guidance on delayed information, requests for information, instructions, principal obligations and avoiding unnecessary construction delay.
• NSW Government — Construction procurement guide: managing extensions of time — guidance on delay evidence, critical-path impact, mitigation, notice requirements and EOT assessment.
• NSW Government — GC21 Edition 2 — current NSW Government GC21 construction-contract documents and supporting contract-administration resources.
• Society of Construction Law — Delay and Disruption Protocol, 2nd Edition — guidance on programmes, contemporaneous records, contractual procedures, delay analysis, mitigation and EOT assessment.