Connecting Schedule, RFIs and Submittals: Why Project Data Can’t Live in Silos

Every project system tells the truth, but not the whole truth

87 open RFIs. Which three actually threaten delivery?

An RFI log cannot answer that question by itself. Neither can a submittal log.

Open status and item age show workflow conditions. They do not establish schedule impact. A 60-day-old RFI may have no immediate effect if the related activity starts in four months and has sufficient float. A five-day-old RFI may require urgent action if it informs critical-path work scheduled to start next week.

To determine which RFIs and submittals threaten delivery, teams need to connect each item to the project schedule. The practical questions are:

• Which activity does the RFI or submittal inform?
• When is that activity planned to start?
• What predecessor work must finish first?
• How much float is available?
• How much review or response time remains?
• Which downstream activities and milestones depend on the work?

This is where SmartPM’s schedule-connected approach provides value. Instead of treating every open item as equally urgent, teams can evaluate RFIs and submittals against the work they may affect. SmartPM’s guidance on connecting Procore RFIs and submittals to the project schedule explains how that connection creates useful schedule context.

The relationship does not prove that an RFI or submittal caused a delay. It shows where schedule exposure may exist and where the team should investigate.

Status is not schedule impact

Consider two open RFIs:

• RFI 101 has been open for 45 days. It relates to finishes planned to begin in 90 days, with 15 days of float.
• RFI 102 has been open for six days. It affects an electrical rough-in activity planned to start in eight days, with no available float. That activity must finish before inspection, close-in, and a contractual milestone.

An aging report places RFI 101 at the top. Schedule-connected reporting prioritizes RFI 102 because its response window is smaller and its downstream exposure is greater.

The same logic applies to submittals. A pending submittal becomes a schedule concern when its remaining review, approval, procurement, fabrication, and delivery durations no longer support the planned activity start.

Every system still contributes part of the project story

The schedule shows sequence, timing, float, dependencies, and milestones. RFI and submittal systems show questions, responses, reviews, and approvals. Field, cost, document, and decision systems provide other parts of the project record.

Each source is useful, but this analysis has a specific purpose: determine whether an unresolved RFI or submittal may affect planned work. For that decision, the most important connection is not between software interfaces. It is between the open item and the schedule activity it informs.

Why construction project information becomes siloed

Construction teams use specialized systems for specialized work. The schedule preserves activity logic. RFI and submittal workflows preserve questions, responses, review dates, approvals, and status. Cost, field, document, and decision systems record other dimensions of performance.

That specialization is not the problem. The problem is that the relationship between an open item and planned work often exists only in someone’s memory, a spreadsheet, or a coordination meeting.

When those relationships are missing, teams can count open RFIs and submittals but cannot quickly determine which ones put delivery at risk.

A shared interface is not enough

Displaying RFIs, submittals, and schedule activities in one interface may improve access. It does not automatically create useful project context.

The useful connection identifies:

• The activity or activities the item informs
• The planned start date for the affected work
• The item’s required response or approval date
• The activity’s available float
• Relevant predecessor constraints
• Downstream activities that depend on the work
• Procurement, fabrication, or delivery time where applicable
• Milestones that may be exposed

Without those relationships, teams still have separate lists on the same screen. They must manually reconstruct which items matter and why.

How to assess RFI schedule impact

Start by linking the RFI to the activity that requires the answer. Then work backward from the activity’s planned start date.

For each RFI, assess:

1. Affected work: Identify the activity, scope, location, and trade that need the response.
2. Planned timing: Confirm when the activity is scheduled to start and whether predecessor work is progressing as planned.
3. Response window: Determine the latest practical response date, allowing time for coordination, revised documents, procurement, or field preparation.
4. Available float: Review whether the activity can move without affecting downstream work or project completion.
5. Dependencies: Identify successors that cannot proceed until the affected activity is complete.
6. Milestone exposure: Check whether unresolved information could affect an interim, turnover, substantial completion, or contractual milestone.

An RFI deserves attention when the time required to receive and implement the answer begins to exceed the time available before the related work must proceed.

For example, an RFI affecting a concrete pour may need more than an answer. The team may also need revised details, trade coordination, material confirmation, and inspection preparation. Comparing only the RFI due date with the pour date would understate the response time required.

How to assess submittal schedule impact

A submittal requires similar analysis, but the full workflow must be considered. Approval is often only one step before installation.

Teams should compare the planned activity start with the remaining time required for:

• Internal preparation and quality review
• Design-team review and resubmission, if needed
• Final approval
• Procurement
• Fabrication
• Shipping and delivery
• Required inspections or field preparation

Suppose equipment installation is planned to start in 45 days. The submittal is still under review, fabrication requires 30 days, and shipping requires 10 days. Even if the item is not technically overdue, the remaining duration leaves almost no time for approval or corrective action.

The schedule risk comes from the mismatch between the remaining workflow and the planned work, not from the status label alone.

SmartPM’s article on identifying which RFIs and submittals will actually delay a project provides a focused explanation of this schedule-impact analysis.

Prioritize response windows, not open-item volume

A large open-item count can indicate workload or process pressure. It does not tell leaders which items threaten the schedule.

Useful prioritization separates items into practical categories:

• Immediate exposure: The affected activity is near its planned start, float is limited, and the response or approval window is closing.
• Developing exposure: The item affects upcoming work, but the team still has time to respond or resequence.
• Monitor: The item is open, but the related work is later in the schedule or protected by sufficient float.
• No current schedule connection: The item has not been linked to planned work or has no identified timing effect. The team may still need to investigate it.

These categories should direct attention, not declare causation. A linked RFI may coincide with schedule movement without causing it. Predecessor delay, access constraints, trade performance, or another project condition may be responsible.

Schedule-connected reporting should therefore show the evidence behind the concern: the open item, affected activity, planned dates, float, dependencies, and relevant milestone. The project team can then validate the relationship and decide what action is appropriate.

What executives should expect from schedule-connected reporting

Executives do not need another undifferentiated list of open items. They need reporting that answers four questions:

1. Which RFIs and submittals may affect near-term or critical work?
2. Why does each item matter to the schedule?
3. How much time remains to respond?
4. Which project milestone or downstream sequence may be exposed?

The report should preserve access to the source-level details used in the assessment. It should also distinguish confirmed facts from possible relationships.

At the portfolio level, leaders should be able to compare projects using consistent schedule context, such as near-term activity starts, available float, overdue response windows, and milestone exposure. This helps direct attention without treating every open item as equally important.

Identify the RFIs and submittals that could affect delivery

Open-item volume does not establish schedule risk. The priority is to connect each RFI or submittal to the work it informs and evaluate timing, float, dependencies, review duration, and milestone exposure.

Read how to identify which RFIs and submittals will actually delay your project, or review the guidance for connecting Procore RFIs and submittals to the project schedule.