When you actually need an RFI
An RFI belongs in the process whenever something in the drawings or specs is unclear, conflicting, or missing — not for every question a foreman has during the day. A detail that contradicts the structural plans, a spec that references a product no longer available, or a dimension that does not match the site: these are RFI territory, because the answer changes what gets built.
The line most crews get wrong is treating an RFI as a formality after the fact, once work already happened based on a guess. At that point it stops protecting the project and starts documenting a problem instead of preventing one.
What a real RFI record needs
A usable RFI has four things: what is being asked, who is responsible for answering, by when, and what impact a delay has on the schedule. Missing any of those turns the RFI into just another unanswered message.
The impact field is the one crews skip most often — and the one that matters most. An RFI with no stated urgency gets the same priority as one holding up a concrete pour tomorrow morning, which is exactly backwards.
Why RFIs get lost in text messages
A question sent over text gets answered, and then it is gone — no timestamp anyone can point back to, no proof of who said what, no way to tell a superintendent "we asked about this three weeks ago and here is the answer." When a dispute comes up later about who knew what and when, a text thread is not evidence, it is a guess.
This is the exact gap construction management software is built to close: an RFI becomes a tracked record with a status and an owner, not a message that gets buried under the next hundred texts in the group chat.