The real cost of RFI delays

The number nobody puts in the project budget

On a typical $50M commercial project with a 14-month duration, you’ll close 300-500 RFIs. Industry-cited cost of an average RFI is somewhere between $850 and $1,200 in coordination overhead — PM time, drafting, routing, chasing, follow-up.

That’s $250K-$600K of pure RFI overhead on a single project. None of it shows up as a line item in the budget. It’s buried in PM hours and field downtime.

About half of that overhead is the architect-review portion, which you can’t compress without changing your design team. The other half is queuing — the time between when the field worker spots the issue and when the RFI actually lands in the architect’s inbox, plus the time between when the response comes back and when the field worker gets the answer.

The queuing breakdown

From sitting with PMs and supers and timing the actual workflow, the queuing time decomposes like this:

• Field-to-PM handoff: 4-12 hours. Foreman notices the issue at 7:30am, texts the PM. PM is in meetings until 4:30pm. The text gets answered at 4:35pm.
• PM drafting: 20-45 minutes. PM opens Procore, finds the right RFI template, types up the question, attaches the photo, picks the distribution list, submits.
• Architect coordinator triage: 4-24 hours. Architect’s RFI coordinator reviews, assigns to the right designer.
• Designer review: 2-7 days. Unfixable by process changes; this is the actual design work.
• Response routing back: 4-24 hours. Response posts to Procore. GC PM has to see it, read it, and forward to the field.
• Field delivery: 4-12 hours. PM is in other meetings; the answer doesn’t hit the foreman’s phone until the end of the day or the next morning.

Total queuing: roughly 12-48 hours. That’s 50-80% of the entire RFI cycle, and the architect didn’t spend any of it actually reviewing.

What compression actually looks like

Compressing the queuing half doesn’t require shorter meetings, more meetings, or new PM hires. It requires removing the PM from the courier role and replacing the manual drafting + routing with a structured workflow.

The pattern:

1. Foreman texts the issue, photo attached.
2. Texting layer drafts the RFI in Procore’s template shape, pre-fills drawing references, spec section, location, distribution list.
3. PM gets a notification with the pre-drafted RFI and one-click approves. Total PM time: 90 seconds.
4. RFI posts to Procore, fires to the architect.
5. (Designer review time, unchanged.)
6. Response posts. Texting layer notices, fires an SMS to the original foreman with the resolution + cited source.

Field-to-architect time collapses from 4-12 hours to 15 minutes. Architect-to-field time collapses from 4-24 hours to instant. Designer review time is unchanged.

Total cycle: typically 6-8 days instead of 9-12.

The economic math

A 30-35% cycle compression on RFIs translates to:

• Field labor savings. The 14 hours per RFI where the field is waiting on the answer becomes 4 hours. On 400 RFIs × $90/hour blended field rate × 10 hours recovered = $360K project-wide.
• PM time savings. The PM’s drafting and routing time per RFI drops from 45 minutes to 90 seconds. On 400 RFIs × 43 minutes saved × $180/hour PM rate = $51K project-wide.
• Schedule float preserved. RFIs sitting on critical-path activities are the most expensive. Even one fewer day on a CP RFI per month × 14 months × $4K/day project overhead = $56K.

These add up to roughly $450K on a typical $50M project. The texting-layer cost is a few thousand dollars per month.

What it doesn’t fix

Two things stay roughly the same:

• Architect / designer review time. If the architect needs 5 days to figure out the right answer, no amount of routing compression changes that. The designer is the bottleneck on hard questions.
• Bad RFIs. If the field is asking RFIs they shouldn’t need to ask — coordination questions that should’ve been caught in clash detection, or specs the contractor never read — compressing the cycle just speeds up a process that shouldn’t happen at all.

How to measure this on your own project

Two metrics worth pulling from Procore:

• Average days from RFI submission to architect response. This is the designer review time; it’s your baseline for the half you can’t compress.
• Average days from issue identification to RFI submission. This is the field-to-PM-to-Procore queuing time. Most PMs have to estimate this; Procore doesn’t track issue-identification time, only submission time.

If the second number is >1 day, you have low-hanging fruit. If it’s >3 days, you have a major systemic issue that’s eating real money — and the compression opportunity is enormous.

Why this isn’t obvious

The reason this compression isn’t universally captured: the cost is buried in PM hours and field downtime, neither of which shows up as a discrete budget line. RFI overhead is absorbed by salaried PM headcount and tradesperson productivity loss. You don’t see it in the project P&L.

But it’s there. Every PM running a commercial project knows the RFI cycle is the worst part of their job, and every super knows their crew sits idle waiting for answers more often than they’d admit in a Monday OAC meeting.

The fix isn’t process discipline or better PMs. It’s removing the PM from the courier role and giving the field a direct, structured path into the RFI workflow.