Direct Answer
An RFI log is a tabular record of every RFI submitted, including: RFI number, date submitted, subject, reference drawing, date response needed, date response received, and resolution summary. Maintain it in a shared location accessible to your project team, and review it in every project meeting to ensure no RFI has been dropped.
Full Explanation
A well-structured RFI log prevents questions from falling through the cracks on complex projects with dozens of open RFIs. Columns should include status (open, answered, answered-pending design drawing, closed) and a flag for any RFI that has not received a response by its needed date. The RFI log is also a project close-out document — it demonstrates that all design questions were formally resolved. For dispute resolution, the log is critical evidence.
What This Means for Your Shop
Review your RFI log weekly. Any open RFI that is past its response-needed date and is blocking production should be escalated immediately through the GC chain. An unresolved RFI is a schedule risk that compounds daily.
Common Mistakes
Maintaining the RFI log only in email chains, not a centralized document. When the project manager changes, or when a dispute arises months later, reconstructing the RFI history from emails is time-consuming and incomplete.
Recommended Process
Create an RFI log in Excel or a PM platform at project kickoff. Assign an RFI manager. Update the log within 24 hours of any submittal or response. Include the log as a standing agenda item in weekly project meetings.