Closing the log in the office is not the same as putting the answer in the hands of the person doing the work. An RFI can be numbered, sent, answered on time, and marked "closed," and still produce a rip-out if the installer never saw the answer. The field kept building from the issued set, which is reasonable when nobody told them the official answer changed the work.

This is a close cousin of the miss in "The Missed RFI: How One Unanswered Question Turns Into a Rip-Out." In that story, the answer sits unprocessed. In this one, the office processed it, and the loop still never reached the field.

This is a typical case, not a specific job, and the dollar figures are only examples.

How it usually goes

A question goes to the design team about an equipment pad, a roof curb, or a sleeve location that does not agree across the drawings. The superintendent writes a numbered RFI, with a markup, and a note that the install is coming. The answer comes back, and it is a good one. It shifts the location and attaches a sketch.

Someone in the office files the PDF, marks the RFI closed in a list, and reasonably feels the question is done. The closed file lives on a laptop or in a folder the field does not open every morning. No short note goes to the superintendent. No copy is posted next to the current drawings. No sub is told that the location moved.

The crew sets the curb, or the pad, or the sleeves, per the issued-for-construction drawings. A day or two later, the closed RFI turns up in a meeting. Now you are moving work that was installed to the wrong information. The office closed the question. The field never received the answer. Those are not the same event.

What that costs (example figures)

The direct work is relocation, patching, maybe a re-inspection, and a reshuffled trade. That direct rework might land somewhere in the range of $8,000 to $25,000 on a miss like this, depending on what was set and whether you are doing it on overtime. That is a ballpark, not a quote.

The rest of the cost is a particular kind of argument. The office can show the answer arrived, and the installer can show they never had it in hand. Both can be telling the truth. Without a "field received" record, and without the answer posted at the current set, there is no clean ending. In an Arizona summer, a reset like this also lands in the heat.

The basic controls that would have caught it

Closed is not complete until the field has received it. The RFI log needs a column for "field received, by whom, and date." If that column is empty, the item is not done, even if the PDF is filed.

Treat a closed RFI that changes the work like a drawing. Post it where the current set lives. If the installer cannot see it in the same place they see the drawings, it is not in the field.

Distribute on purpose. When the answer arrives, a short note goes to the superintendent and the affected subs: RFI number, what changed, and where the file is. A two-word reply from the superintendent, "got it, posted," is the loop that would have changed this story.

Review the log for "closed but not received" before a pour, a setting, or a cover-up. The afternoon-before look should ask whether any recently closed answers have actually reached the people installing. A spreadsheet in a Google Drive or Dropbox job folder is enough.

If the office-to-field loop is already dropping

This miss often happens on jobs that look organized from the office chair. The PDFs are filed and the log is current, but the last mile of distribution slips.

If that sounds like your job, I can set up the job file, run the logs and the field distribution on a retainer, or prepare closeout. An RFI answer that reaches the office but not the field is not a closed question. It is a future rip-out with a neatly filed PDF.

If you want help, not just a checklist

Some jobs run fine on a clean file and a superintendent who gives the log fifteen minutes twice a week. Others do not: revisions are moving fast, closeout is already behind, or the field simply has no hours left for paperwork.

That is where I come in. I set up the job file, run the logs on a retainer, or prepare closeout before the scramble starts. Your files stay yours, and there is no software contract to sign.

Email travis@builtonrecord.com Get the free Job File Kit