Congratulations! You’re now the person responsible for making sure RFIs actually move, instead of vanishing into that mysterious gap between the field and the architect’s inbox. Where do you even begin? What’s the right approach? That’s exactly what this ZenTek Consultants blog series is here to help you figure out!

Missed Part 3? Read it here.

Part 4: Closing Out and Linking RFIs

An answered RFI isn’t necessarily a closed one, and the difference matters a lot. Properly closing out RFIs and linking them to the rest of your project record is what turns a pile of questions and answers into a defensible project history. Let’s start with what “closed” should mean on your project. A response from the architect “closes” the question, sure, but has that answer actually been incorporated into the work? Procore lets you track RFI status through multiple statuses, but they’re limited. We suggest creating custom RFI Fieldsets where you can tag “answered” and “closed” as genuinely separate states. Closed should mean the answer has been confirmed, distributed to the relevant trades, and reflected in the work, not just that someone replied in the system. You can do this at the Company Level via ADMIN > RFIs > Custom Fields, and create your own “RFI Workflow State”.

Linking answered RFIs back to drawing revisions is one of the most valuable habits you can build. When an RFI response effectively changes a detail, that connection should be explicit and traceable, not just a separate email thread someone has to remember exists. If your project later issues a bulletin or revised drawing set incorporating that answer, link the RFI directly to it so anyone looking at either document later can see the full chain of how that detail evolved. You can do this by editing the RFI and using the “Attach File” feature to open the below dialog to create connection to specific plans and revisions.

Spec section references deserve the same treatment. An RFI that clarifies an ambiguous spec callout should be linked directly to that section, not just mentioned in passing in the question text. This matters enormously for closeout and for any future dispute resolution — being able to pull every RFI tied to a specific spec section, instantly, is exactly the kind of organized record that protects everyone on the project. To connect specs (and other non-drawing Procore items) “View” the RFI in question and use the “Related Items” tab to create easily accessible links.

Think about your RFI log as a project asset, not just a workflow tool you’ll abandon once the job is done. A clean, well-linked, fully closed-out RFI log becomes part of your project. It’s useful for warranty questions, useful as precedent on the next similar project, and useful if a dispute ever requires reconstructing exactly what was asked, answered, and when.

Build closing discipline into your process the same way you built submission and tracking discipline in earlier parts of this series, and your RFI log becomes something your whole team can actually trust months or years after the project wraps. Don’t miss the next installment of our “Mastering RFIs in Procore” series!