On a large job, an RFI is not a casual email. It is a numbered question, with a due date, a person who has the ball, and a closed answer that is supposed to reach the people doing the work. That sounds formal, and it is, because the alternative is expensive. A crew installs something the right way in the wrong place, because the official answer never caught up with them.

I kept that kind of record at Mortenson Construction, on a mission-critical data center project, including the period when the job moved onto Procore. Your job does not need that platform. But the reason those logs exist is the same on a mid-size Arizona project as it is on a mega project: a question that goes unanswered, or gets answered and never reaches the field, turns into rework.

The story below is a typical case, not a specific job, and the dollar figures are examples.

How it usually goes

A light-commercial job is heading into a slab on grade. The issued-for-construction drawings show a clean structural layout. The electrical and plumbing drawings do not quite agree with it on a few sleeves that have to pass through the slab. The superintendent does the right thing: a numbered RFI goes to the design team, with a clear question, a markup, and a note that a pour is coming.

The answer comes back in four days, and it is a good one. It adds sleeves, shifts two of them, and tells the trades to proceed per the sketch attached to the response. Then the email lands with the project manager, or in a general inbox, or on a phone that is already in a meeting. The pour is still on the calendar. In an Arizona summer that calendar is tight on purpose. Heat pushes work into the early hours, and once the trucks are booked, the pressure is to go.

The field has been looking at the issued set all week. The sleeves get placed the way the IFC drawings show them. The inspection happens. The slab goes in.

A day or two later, someone forwards the RFI answer, or stumbles on it while looking for something else. The sleeves that were added are not in the concrete. Two of the ones that were placed are in the old locations. Now you are coring a green or curing slab, patching, coordinating the trades again, and explaining to the owner why a "simple question" became a mess.

Nobody on that crew was careless in the usual sense. They built what was in front of them. The miss was in how the answer was controlled.

What that costs (example figures)

The direct work is the part everyone remembers: coring, sawing, patching, resealing, extra labor, maybe an inspection that has to be repeated. That direct rework might land somewhere in the range of $8,000 to $25,000 on a miss like this, depending on how many openings you are cutting, what is already in the slab, and whether you are doing it on overtime. Treat that as a ballpark, not a quote.

The rest of the cost is easier to underestimate:

  • Schedule. If the next trade was waiting on that slab, or if a wall layout depended on those sleeve locations, you have idle time and a reshuffled week.
  • Stacked work. Other subcontractors now have to work around a repair, which is how a paperwork miss becomes a job-wide delay.
  • The dispute. The installer will say they never saw the answer. The office will say it was emailed. The design team will say they responded on time. Without a log, a distribution record, and a current-set rule, that argument has no clean ending.
  • Cash. A messy change or a damaged relationship can slow a pay application. Closeout and retention get harder when the as-built story is "we cored it later, and the file is in someone's email."

Sometimes the dollars are smaller than that example range, and the real damage is trust: an owner who starts watching you differently, or a sub who stops believing the set in their hands. That is a cost, too.

The basic controls that would have caught it

You do not need a document control department to prevent this. You need a few habits simple enough to survive a busy week.

Keep an RFI log, and keep it visible. A spreadsheet is enough. For each RFI, record the number, date sent, subject, who has the ball, the due date, the date closed, a one-line summary of the answer, and who in the field received it. Open items should be obvious at a glance. If the only copy of an RFI is a thread in someone's inbox, it is not controlled.

Put a due date on the question, and watch the calendar against the work. If a pour, a cover-up, or an inspection is coming, the open RFIs that affect that work get reviewed first. A standing rule helps: no pour or cover-up until someone has looked at the open RFI list for that area. On a heat-driven early pour, that review happens the afternoon before, not at 4 a.m. in the dark.

Treat a closed RFI that changes the work like a drawing. The answer does not live only in email. It gets filed, named, and posted where the current set lives: a "binding RFIs" packet next to the current drawings, or a clouded sketch on the current sheet, depending on how your design team issues information. If the installer cannot see it in the same place they see the drawings, it is not in the field.

Distribute on purpose, and keep proof. 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 transmittal, or even a consistent email with a reply, beats a forward with no record. This is not bureaucracy. It is being able to show that the answer left the office.

One current set, with a date. If the RFI changes a location, the current set has to reflect that, or it has to point clearly to the RFI. Two "current" sets, one in the trailer and one on a phone, are how last week's sleeves get built. Yesterday's set goes in a superseded folder, not in the truck.

Close the loop with a simple sign-off. It can be a column in the log, "field received, date, by whom," or a reply from the superintendent: "got it, posted to the current set." That one habit would have changed the story above.

A large GC buys software to enforce exactly these controls. You can run them with a spreadsheet and a rule.

Tools at your level

A shared Google Drive or Dropbox folder for the job, with a current-drawings folder that only a short list of people can reorganize, is enough structure. The RFI log can be a Google Sheet sitting in that same job file, open on a phone. Photos of the sleeve layout, taken before the pour and named with the date and area, will matter if the story is ever retold. I go through a full folder layout and naming convention in "A Procore-Level Job File With Google Drive (or Dropbox) and a Spreadsheet."

AI can help at the edges if you treat it as a clerk, not as the record. It can summarize a long RFI response, draft the short transmittal to the subs, or help you search a folder for "sleeves" when you are in a hurry. It cannot decide which answer is official, and you should not let it loose on the current set without a person checking the source PDF.

In a typical Procore project, the RFIs tool holds the numbered question, who has the ball, the due date, and the official response. A Drive or Dropbox folder and a simple log can hold the same record. The process matters more than which tool is holding it.

If the logs are more than the week can hold

A superintendent running a big project and overseeing others should not have to choose between watching the pour and hunting through email. If the revisions are coming fast, or if the inbox is already the filing system, that is a reason to get help, not a reason to feel behind.

That is why I built Built On Record, a document control service for contractors, based in Arizona and working remotely in any state: job file setup, retainer support during construction, and closeout support. If you want, I can look at how RFIs are moving on your current job and tell you whether a simple log and a current-set rule will hold, or whether you would be better off having someone else run it for a stretch.

Bring a recent RFI thread and a photo of the folder where your drawings live. That is enough to start.

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