The RFI is the project's question channel — and the most abused. Here's the playbook.
Why RFIs stall
The vague question (the 'please clarify' — the what-exactly; the reference's — the missing), the shotgun (the 50 — the Friday's; the reviewer's — the buried), and the no-needed-date (the answer's — the whenever; the schedule's — the ignored). The cause is the asking — the question's discipline.
The clear RFI
The reference (the spec section — the drawing's; the detail's — the clouded), the question (the specific — the one; the options' — the proposed), the suggestion (the contractor's — the recommended; the cost/time's — the stated), and the needed-date (the schedule's — the realistic; the 7-day — the contractual).
The fast answer
The reviewer's (the A's — the 7 days; the E's — the concurrent), the triage (the critical — the first; the FYI's — the last), the standing (the weekly's — the open; the aging's — the escalated), and the consolidated (the related's — the batched; the duplicative's — the merged).
The accountability
The log (the numbered — the status; the aging — the overdue), the cost (the frivolous's — the backcharged; the contract's — the clause), the schedule (the delay's — the documented; the notice's — the timely), and the design (the errors' — the acknowledged; the bulletin's — the issued).
The digital workflow
The platform (the routing — the timestamps; the ball-in-court), the BIM (the model's — the referenced; the clash's — the prevented), and the analytics (the response times — the measured; the repeat offenders — the named).
The bottom line
The RFI is the project's clarity channel — the question revealing the documents' gaps, the answer revealing the team's responsiveness. Ask specifically with references and suggested solutions, answer within the contractual window, log everything, and backcharge the frivolous. The project that manages RFIs manages its information flow; the project that doesn't manages its claims.