RFI turnaround is a management metric — treat it like one

An RFI is a question that is blocking work. That is the whole definition, and it is worth repeating because of how RFIs are usually managed: as correspondence. A question gets typed into an email thread, lands with a consultant, and waits. Nobody owns the clock, because there is no clock.

The cost arrives in disguise

The cost arrives later, disguised as something else. A framing crew resequences around a missing answer and the schedule absorbs three days. An assumption gets built because the answer was slow, and the correction becomes a change order. By the time slow RFIs cost real money, the invoice never says "RFIs" on it.

Field teams know this. What is strange is how rarely RFI turnaround is managed the way other consequential numbers are managed — with a target, a measurement, and a weekly review. Budget variance gets a dashboard. The questions blocking the work get an inbox.

Part of the reason is ownership ambiguity. An RFI crosses organizational lines by design — raised by the contractor, answered by a consultant, consequential to the owner — so each party can reasonably believe the clock is someone else’s to watch. The contract may set response expectations, but expectations without measurement drift, and the drift compounds precisely on the projects too busy to notice it.

Three behaviour changes from one metric

Logging discipline improves

When RFIs live in a log with status, assignee, and due date — instead of in threads — questions stop being invisible. The log is the difference between "we have a few RFIs out" and "we have eleven open, four with the structural consultant, two overdue."

The clock creates accountability without conflict

Chasing a consultant by email is personal; a turnaround report is operational. When the average response time per project, per reviewer, is simply visible, the conversation at the OAC meeting changes from anecdotes to numbers.

Patterns surface early enough to act

A project whose RFI count is climbing while turnaround stretches is telling you something about drawing quality or scope clarity — weeks before the schedule shows it. That is the kind of early signal project executives say they want; it lives in the RFI data. The same data compounds across projects: a consultant who is consistently slow, a drawing discipline that consistently generates questions, a project type that reliably front-loads its RFIs — portfolio patterns that no single project meeting would ever surface.

What to measure

The metric set does not need to be elaborate. Five numbers, reviewed weekly, cover the management need:

• Open RFI count, per project — the raw workload.
• Average turnaround, question to answer, per project and per reviewer.
• Aging buckets — how many open items are under a week old, one to two weeks, older.
• Overdue count with assignee names — the accountability view.
• RFI density trend — questions per drawing package or per phase, which is the drawing-quality signal.

The record behind those numbers is equally simple. A useful RFI carries a number, the question stated once and clearly, the discipline it belongs to, an assignee, an asked date, a due date, an answered date — and two flags the field fills honestly: does this block work now, and does the answer likely carry cost or schedule impact. Those two flags are what let the weekly review triage eleven open items in five minutes instead of thirty.

The discipline, independent of tooling

A reasonable target depends on the project, but the discipline does not: every question gets a number, an owner, a due date, and a place in the weekly review. Average turnaround sits next to target on the project dashboard, and overdue items have names attached.

One caution from teams that have run this well: the metric is a tool for the process, not a weapon for the OAC meeting. The first weeks of measurement usually reveal that some slow answers were slow questions — ambiguous, missing context, or answerable from the documents already issued. Turnaround discipline cuts both ways, and the teams that accept that finding early get the consultants on side instead of on guard.

This is how OpSphere ProBuild models design coordination — RFIs logged with response routing, due dates, and per-project turnaround metrics, on the same record as submittals, drawings, and site instructions. ProBuild is available today; the turnaround view is one of the first screens superintendents adopt. The deeper point survives any tooling choice: put a clock on the questions blocking your work, and the schedule stops absorbing the silence.