The $880 RFI: What Slow Information Really Costs Contractors
Here is a number worth sitting with. Industry research puts the average cost of a single request for information, or RFI, at roughly 880 dollars, with a typical resolution time of about eight days. Read past the figure for a moment and think about what it represents: eight days where a question sits open, work waits, and money leaks out of a project one hour at a time. Now multiply that across every open job in your portfolio.
Here is a number worth sitting with. Industry research puts the average cost of a single request for information, or RFI, at roughly 880 dollars, with a typical resolution time of about eight days. Read past the figure for a moment and think about what it represents: eight days where a question sits open, work waits, and money leaks out of a project one hour at a time. Now multiply that across every open job in your portfolio.
What an RFI actually costs
The 880 dollars is not the cost of asking the question. It is the cost of everything around it. The time the person spends writing it up and routing it. The time the recipient spends locating the answer. The follow ups when the first response is not clear. And most expensively, the work that stalls or gets redone because a decision was made without the answer, or made on the wrong drawing version. The direct cost is small. The indirect cost, in delay and rework, is where the real money goes.
Why RFIs drag on
Most of the eight days is not thinking time. It is waiting and searching. Someone has to find the latest drawing, confirm which version is current, and track down who actually has the authority to answer. When that information is scattered across inboxes, texts, and shared drives, every step adds a delay. The question is often simple. Getting to the answer is not.
The bigger pattern: 13% of hours spent searching
The RFI is a symptom of a larger problem. Research from the construction industry suggests field teams can spend around thirteen percent of their total work hours simply looking for project data. For a company with fifty people in the field, that is thousands of hours a year spent not building, just hunting for information that should have been one click away. Slow information is a tax on every project, and RFIs are just its most visible line item.
What governed data does about it
When your project data lives in one governed system instead of scattered across tools, the delay shrinks fast. RFIs are logged against the project. Drawing versions are controlled, so there is never a question of which one is current. And because everything is time stamped, you can measure the gap between opened and resolved across your whole portfolio and drive it down deliberately. A question stops being a black hole and becomes a metric you manage.
A quick portfolio example
Suppose you run twenty active projects, each generating a handful of RFIs a month. At 880 dollars apiece, even a modest volume adds up to real money over a year, before you count the schedule impact of eight day resolution times on critical path work. Now imagine cutting that resolution time in half by putting the data in one place. You have not just saved on the RFIs themselves. You have pulled schedule risk out of every project at once. That is the leverage of fixing information velocity.
How HubSpot and ServiceIQ close the gap
This is exactly what pairing HubSpot with ServiceIQ delivers for contractors. HubSpot holds the commercial relationship. ServiceIQ holds the governed project and job data, with RFI tracking, revision history, and approval workflows built in, and it syncs field status back to HubSpot in real time. Instead of a system that just stores the RFI, you get one that is built to close it faster, with the drawing, the history, and the accountability all in one place.
Steps to reduce RFI latency
Put all project data in one system, not scattered across inboxes and drives.
Enforce drawing version control so no one ever works from an old set.
Log every RFI against the project, with a clear owner and timestamp.
Track time to resolve as a metric, and review it by project manager and office.
Use zero-login approval links so outside stakeholders can respond in a click.
The three places RFI time disappears
If you break down the eight days, the time hides in three predictable places. The first is routing: the question bounces between people before it reaches whoever can actually answer it. The second is searching: someone has to locate the relevant drawing, spec, or prior decision, and confirm it is current. The third is verification: once an answer comes back, it often has to be checked against the latest documents before anyone acts on it. Each of these is a data problem, not a knowledge problem. The expertise to answer usually exists. The friction is in getting the right information in front of the right person quickly.
Why version control is the hidden lever
Of all the fixes available, drawing version control has the highest payoff for the least effort. A huge share of RFI delay and rework traces back to two people looking at different versions of the same document. When the system guarantees a single current version, an entire category of questions simply never gets asked, and the ones that do get answered against a source everyone trusts. It is unglamorous, and it is one of the most valuable things a governed system does for a construction business.
Measuring information velocity
You cannot improve what you do not measure. When RFIs live on the project record with timestamps, you can track the average time from opened to resolved, and you can slice it by project, office, or manager. That turns a vague sense that things are slow into a specific number you can drive down quarter over quarter. It also surfaces where the friction concentrates, so you can fix the process at its worst point rather than guessing. Information velocity becomes a managed metric instead of a complaint.
A note for project managers
For the people living this day to day, the promise is simple: less time chasing, more time building. When the drawing is always current, the RFI has a clear owner and a clock, and the answer is logged where everyone can see it, the PM stops being a human router for information and gets back to actually managing the project. That is not just a cost saving on paper. It is a better job for the person doing it, and better outcomes for the work.
The compounding effect across a portfolio
The reason this number deserves attention is that it does not occur once. It repeats on every project, every month, and the schedule impact stacks on top of the direct cost. An eight day RFI on non critical work is an annoyance. The same delay on critical path work can push a milestone, trigger penalties, or idle a crew that is booked on the next job. When you run many projects at once, small information delays across all of them add up to a portfolio wide drag that never shows up as a single, obvious line item but quietly erodes margin everywhere.
From reactive to proactive
The deeper win is not just faster answers, it is fewer surprises. When project data is governed and visible, leadership can spot a project accumulating open RFIs before it becomes a crisis, and step in early. You move from reacting to problems after they have cost you to managing information flow as a leading indicator of project health. That shift, from firefighting to foresight, is what separates contractors who scale smoothly from those who lurch from one avoidable delay to the next.
Frequently asked questions
Is the 880 dollar figure realistic for smaller jobs?
It is an industry average, so your number will vary. But even at a fraction of that, the pattern holds: the indirect cost of delay and rework dwarfs the direct cost, and it compounds across projects.
What is the fastest way to cut RFI time?
Get everything into one governed system with version controlled drawings, then measure resolution time so you can manage it. That single move addresses most of the delay.