Why Route RFIs to the Project Engineer, Not the PM, in 2026?

Key Takeaways

• The average commercial RFI takes 11.4 business days to resolve — 6.8 of those days are routing and queue time, not engineer response time.

• RFI misrouting rate: 22–30% in manually-managed projects; automated routing cuts this to 2–5% with a properly configured routing matrix.

• The routing matrix — mapping CSI Division to responsible engineer, backup contact, and response deadline — takes 2–3 hours to build at project kickoff and saves 30–60 minutes of PM routing work every week.

• PMs spend 23% of billable time on administrative coordination (routing, submittal tracking, document distribution); RFI automation recaptures a measurable share of that capacity.

• The highest-ROI implementation targets MEP-intensive projects (hospitals, labs, data centers) where RFI volume runs 2–3× higher than comparable office or retail builds.

On most commercial construction projects, requests for information travel through the same path: the subcontractor submits an RFI through Procore or email, it lands in the project manager's queue, the PM decides who on the design team needs to respond, and the clock starts running. The problem is that the PM's decision step — which takes between 4 hours and 3 days in practice — adds friction that has nothing to do with the actual technical question. The RFI doesn't need the PM's judgment; it needs the right engineer's answer.

Average rework cost as a percentage of project value: 9% according to the Construction Dive 2025 productivity report (2025). A significant portion of that rework traces to RFIs that were answered late, misrouted, or answered by the wrong discipline — and the response was either wrong or generated a change order that the field team acted on before it was approved.

This cost guide examines the RFI routing problem, the cost of poor routing, and the automated routing framework that gets RFIs to the project engineer responsible for each spec section within minutes of submission.

TL;DR

RFI routing automation means connecting the information on an RFI submission — spec section, CSI division, submitting subcontractor trade, and keyword classification — to a routing matrix that maps each combination to the correct project engineer or design-team contact. The PM is removed from the initial routing decision and instead receives a summary dashboard; they intervene only on RFIs that don't match any routing rule or that escalate past the response deadline.

Who This Is For

Best fit: General contractors managing commercial projects above $5M, using Procore or Buildertrend as the primary project management platform, with 3+ project engineers or design consultants responsible for different specification sections. Best ROI on projects with 10+ active subcontractors and expected RFI volume above 200 per project.

Red flags: Skip if: your projects are under $2M where a single PE covers all disciplines, you're in a pure design-build arrangement where all RFIs go to one internal team, or your current average RFI response time is already under 5 business days (you may already have an informal routing system that's working).

The Cost of Misrouted RFIs

RFI misrouting has two measurable cost components: the delay cost and the rework cost.

Delay cost is straightforward. According to the Construction Industry Institute (CII) 2024 Best Practices Benchmarking Report, the average RFI response time on commercial construction projects is 11.4 business days. Top-quartile projects average 4.6 days. The difference — 6.8 business days — is mostly routing and queue time, not engineer response time. When an RFI sits in the PM's queue for 3 days before being forwarded to the structural engineer, then sits in the structural engineer's email for another 2 days before they notice it's actually a mechanical question and forward it back, the project has lost a week on a question that the mechanical PE could have answered in 4 hours.

Rework cost is higher and less visible. When RFIs are answered late, the field often continues work based on what they think the answer should be. If the answer turns out to differ — even slightly — the rework cost on structural or MEP work can run 5–15% of the affected scope value. On a $400,000 rough-in scope, that's $20,000–$60,000 in rework on a single bad-assumption sequence.

These figures are illustrative but directionally consistent with the CII 2024 benchmarking data on administrative coordination losses in commercial construction.

Why the PM Becomes the Bottleneck

The project manager's role in RFI routing is structurally problematic for two reasons.

First, PM bandwidth: a commercial PM managing a $15M project typically handles 80–120 operational items per day — daily logs, subcontractor coordination, owner updates, procurement, schedule management. RFIs are one item in that stack. When 8 RFIs arrive on a Monday and the PM has a 9 AM owner call followed by a schedule recovery meeting, the RFIs don't get routed until Tuesday.

Second, the PM's routing knowledge: the PM knows which firms are on the design team, but they may not know which engineer within a firm is responsible for which spec section. Did Division 22 (Plumbing) questions go to the MEP firm's lead engineer or the plumbing sub-consultant? Was Division 05 (Structural Metal) divided between two structural engineers based on floor level? The PM guesses, or sends to the wrong contact, and the RFI bounces.

According to the CFMA 2024 Construction Financial Benchmarker, administrative coordination tasks account for 23% of a project manager's billable time on commercial projects — up from 17% in 2019. RFI routing, submittal tracking, and document distribution are the top three contributors to that increase.

Administrative tasks consume 23% of commercial PM time, according to CFMA 2024 data. Routing automation recaptures a measurable portion of that.

The RFI Routing Matrix: What Automation Reads

Automated RFI routing doesn't require AI or natural language processing in its basic form. It requires a routing matrix — a structured table mapping input fields to responsible parties — that the automation queries every time an RFI is submitted.

The input fields:

• CSI Division (Procore's "Spec Section" field, e.g., Division 03 = Concrete, Division 22 = Plumbing)

• Submitting subcontractor trade (drawn from the sub's Procore contact record)

• RFI subject keywords (a secondary classification for RFIs filed under the wrong division)

• RFI category (field condition, design clarification, change condition, or schedule impact)

The routing matrix maps each combination to:

• The primary responsible engineer (PE, MEP consultant, specialty sub-consultant)

• The backup contact if the primary is out of office

• The required response deadline (varies by spec section criticality and project schedule float)

• Whether the PM needs to be CC'd immediately or only if the RFI escalates

Step-by-Step: Building the Automated Routing Workflow

Step 1 — Trigger on Procore RFI Submission

The Procore API exposes a rfi.created webhook event that fires when a new RFI is submitted. The automation subscribes to this event and reads: the RFI number, the spec section field, the submitting subcontractor, the RFI subject line, the attached supporting documents, and the current project schedule milestone (to determine response urgency).

Step 2 — Query the Routing Matrix

The automation queries the project's routing matrix — stored in a simple configuration table — and identifies the primary responsible party. If the spec section is Division 22 (Plumbing), the responsible party is the MEP consultant's plumbing engineer. The automation also reads the project's out-of-office calendar: if the primary contact is on vacation, it routes to the backup.

Step 3 — Send the Routed Notification

The automation sends the routed RFI notification to the responsible engineer with: the RFI document, the submitting sub's contact information, the project schedule context (current milestone, float on the affected work sequence), and the response deadline.

The notification goes out within 5 minutes of RFI submission — before the PM has even opened their email. The engineer receives the RFI with all context needed to begin evaluation immediately.

Worked Example: A $22M office renovation project is processing 18–25 RFIs per week during the MEP rough-in phase. Each Procore rfi.created event fires the routing automation. Over a 6-week rough-in period, 127 RFIs were submitted: 41 to the structural engineer, 52 to the MEP consultant (split between plumbing and electrical), 19 to the architect, and 15 to the GC PM directly (Division 01). Average routing-to-first-response time: 1.8 business days, down from 7.2 days under manual PM routing. Of the 127 RFIs, 4 (3.1%) were misrouted by the automation (spec section field left blank by the sub), versus 28% misrouting under manual PM routing. Those 4 were caught by the fallback rule that routes blanks to the PM for manual classification.

Step 4 — Track Response and Escalate Overdue RFIs

The automation monitors each routed RFI against its deadline. When an RFI has been open for 80% of its deadline without a response logged, an automated reminder fires to the responsible engineer. At 100% of the deadline without response, the PM receives an escalation notification with the RFI list, the overdue engineer, and the schedule impact of continued delay.

This escalation chain — reminder at 80%, PM escalation at 100% — is what gives the PM meaningful visibility without putting them in the routing path. The PM sees the dashboard of overdue items, not every inbound RFI.

Step 5 — Log Response and Notify the Sub

When the engineer submits their response via Procore, the automation detects the status change and sends the response package to the submitting subcontractor with a project-formatted cover page. It also logs the response time for the routing performance report — tracking which engineers respond within deadline and which consistently exceed it.

US Tech Automations connects Procore's rfi.created and rfi.updated events to your routing matrix configuration, fires notifications to the correct engineer, escalates overdue responses to the PM, and logs cycle times — without any changes to how engineers or subs use Procore itself.

For related workflows on how submittals are tracked across spec sections, see .

According to the Associated General Contractors of America 2024 Project Delivery Survey, 58% of GCs reported that RFI response delays directly contributed to schedule overruns on at least one project in the prior 12 months — with an average delay contribution of 9 calendar days per impacted project.

RFI delays caused schedule overruns on 58% of projects according to the AGC 2024 Project Delivery Survey (2024).

Building the Routing Matrix: Practical Steps

The routing matrix is the foundational configuration that makes automated routing accurate. It should be built at project kickoff, not mid-project, and should be updated whenever a sub-consultant is added or a design team contact changes.

Steps to build it:

1. Extract the project's specification sections from the project manual (divisions 00–49, filtered to those in scope).

2. Map each division to the responsible design team contact. Use the design team's own project directory, not your internal assumption about who covers what.

3. Add backup contacts for each division (for out-of-office routing).

4. Define response deadlines by division and RFI category (field condition requires faster response than general clarification).

5. Define escalation rules: who gets notified at 80% and 100% of deadline for each division's RFIs.

The matrix takes 2–3 hours to build at project kickoff. It saves 30–60 minutes per week of PM routing time for the project's duration. US Tech Automations imports the completed matrix and subscribes to Procore webhook events in a single configuration session — no custom integration code required.

For the related workflow on bid invitation routing, see .

Cost Benchmarks: Manual vs. Automated RFI Routing

RFI misrouting rate drops from 22–30% to 2–5% with automation. That is the key metric — because every misrouted RFI adds days to the response cycle, and those days accumulate across the hundreds of RFIs on a commercial project.

Glossary

FAQs

Why should RFIs go to the project engineer instead of the PM?

The project engineer (PE) responsible for a specific spec section has the technical knowledge to evaluate and respond to an RFI within that section without a routing step. The PM adds a layer of delay — typically 1–3 days — without adding technical value to the routing decision. Routing directly to the responsible PE eliminates that delay and gets the RFI to the person who can actually answer it faster.

What happens to RFIs that don't match any routing rule?

RFIs with a blank or unrecognized spec section field route to the PM as the default fallback. The PM classifies the RFI manually and adds the correct spec section before routing it onward. These fallback cases should be tracked — if a particular sub consistently submits RFIs without spec sections, the routing rules can be updated to classify by trade rather than by spec section for that sub.

How do I handle RFIs that cross multiple disciplines?

Multi-discipline RFIs — for example, a mechanical-structural coordination issue — are the most complex routing case. The best approach is to route to the lead discipline (whichever spec section is referenced) and include all affected engineers as CC recipients. The lead engineer is responsible for coordinating with the other discipline and issuing a joint response. This prevents the RFI from bouncing between engineers while the clock runs.

Can automated routing integrate with Procore's native RFI workflow?

Yes. Procore exposes rfi.created and rfi.updated webhook events that fire in real time. An orchestration layer subscribes to these events, applies the routing matrix, and sends notifications via email or in-app Procore notification. The engineer's response is logged directly in Procore; the automation simply handles the initial routing step that Procore's native workflow leaves to the PM.

What is the typical RFI volume on a commercial project?

RFI volume scales with project complexity and size. As a rough benchmark: $5M commercial project = 80–150 RFIs; $15M project = 200–400 RFIs; $50M project = 500–1,200 RFIs. MEP-intensive projects (hospitals, labs) run 2–3× higher volume than comparable office or retail projects. Automated routing ROI increases proportionally with volume.

How does RFI routing automation handle design team out-of-office periods?

The routing matrix should include a backup contact field for each division. The automation checks a configured out-of-office calendar (Google Calendar or Outlook) for the primary contact and routes to the backup if the primary is marked out. If both are out, the fallback is the PM. Maintaining this calendar is the responsibility of the design team's project coordinator — the automation reads it, it doesn't maintain it.

Next Steps

The first step for any GC is a routing audit on the last completed project: pull all RFIs, measure the gap between submission and first notification to the responsible engineer, and calculate the percentage that were routed to the wrong discipline on the first pass. On most projects, that audit reveals 20–35% misrouting rates and 2–4 days of unnecessary routing delay per RFI.

From there, the routing matrix is a half-day configuration exercise at project kickoff — spec sections to responsible engineers, response deadlines, escalation contacts. The automation reads that matrix and routes every subsequent RFI without PM intervention.

For a broader view of how construction document workflows connect, see the submittal tracking workflow at and the change order reconciliation process at .

US Tech Automations connects Procore's RFI submission events to your routing matrix, fires engineer notifications within minutes, escalates overdue responses, and logs cycle times for your project performance reporting. See the full construction workflow options at ustechautomations.com/pricing.