Sending an update is not the same as knowing it arrived. The last step in document control is a simple sign-off: the field got it, and, if the work changed, it was posted to the current set.

That sounds formal. In practice, it is a column in the log or a one-line reply from the superintendent: "got it, posted to the current set." Large jobs use software to force that acknowledgment. You can close the same loop with a habit that takes seconds, not a new platform.

What a useful sign-off looks like

You do not need a wet signature on every RFI. You need a dated record of who received the official answer, and enough detail to end a later "I never saw that."

These are enough on most jobs:

  • A "field received" column in the RFI and submittal logs: by whom, and the date
  • A one-line email or message reply from the superintendent, filed with the document or noted in the log
  • For a drawing revision, a note that the current set was updated, and that the old sheet was moved to Superseded
  • For an approved-as-noted submittal, a confirmation that the notes, not just the stamp, reached the installer

Make the sign-off specific enough to be useful. "Got it" is better than silence. "Got RFI 017, posted the sketch next to the current structural sheets, 6/12" is better than "got it." You are not writing a novel. You are closing the loop.

Ask for the acknowledgment when you send the notice, not a week later. A consistent subject line and a single question ("Please reply that you have this and that it is posted") will do more than a new form nobody uses.

If a sub is the one installing, the superintendent's sign-off is still the job's record that the field was informed. If you also want the sub's reply, ask for it on the items that change their work, and file it.

The miss this prevents

This is how it tends to unfold.

An RFI answer comes back and changes a sleeve layout. The office emails the PDF to a group list. Nobody replies. The pour is still on the calendar. The crew builds to the issued drawings that have been on the rack all week. After the slab is in, the office says the answer was sent. The field says they never saw it. Both may be telling the truth as they remember it. There is no column and no reply to settle it.

I walk through how that pattern turns into a rip-out, as an example, in "The Missed RFI: How One Unanswered Question Turns Into a Rip-Out." The control that would have changed the story is not a better email. It is the closed loop: received, posted, dated.

How to run it in the log and the folder

Add the "field received" columns to the spreadsheet logs you already keep in the Google Drive or Dropbox job file. Do not start a second system for acknowledgments. If the sign-off lives somewhere other than the log, it will not get updated.

A practical weekly habit:

  1. When you distribute a closed RFI, a returned submittal, or a new current sheet, ask for a one-line reply.
  2. When the reply comes in, fill the column the same day. If it comes as an email, file that email or a PDF of it with the document.
  3. If a pour, cover-up, or inspection is coming, look first at open items and at closed items with a blank received column. Those are still a risk.
  4. If a reply does not come, follow up once, in writing, before the work is covered. A second silence is information. Deal with it before the concrete is in.

Keep this light enough that a superintendent will actually do it. A long form, or a rule to sign off on every daily photo, will be dead by Wednesday. Reserve a tighter sign-off for the documents that change the work.

If the loop is already open

If you have a stack of "sent" items and no idea what the field saw, start the sign-off habit on the next change. For anything still open that affects work this week, send a short recap and ask for the one-line reply now.

When the habit will not hold on its own, I can set up the logs and the job file, run document control on a retainer, or prepare closeout. If you want help, bring a recent RFI or submittal thread and the log, if you have one. I will tell you straight whether a column and a one-line reply will hold.

The files stay yours.

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