PMC💬 Meetings & MoMRFI Review Meeting MoM

RFI Review Meeting MoM

mom
PMC-MTG-MOM-012·v1.0-beta·⚠ Beta — review before use

Periodic meeting reviewing open Requests for Information (RFIs). Tracks RFI lifecycle, response timelines, and identifies systemic design/scope issues from RFI patterns.

ReferencesFIDIC Sub-clause 1.9 (Drawings + Documents)PMI PMBOK GuideProject Communication Plan
Download
📍 When to use this template
  • Weekly RFI review meeting at peak construction phase.
  • Pre-MPR closure to escalate aged RFIs.
  • Pattern identification (multiple RFIs on same area = design/documentation issue).
Sections & fields
Preview of the template structure. Download Excel to fill on site.
1Meeting Header4 fields
Date + Time
_____________
Attendees (Contractor, PMC, Designer)
_____________
RFI Period Reviewed
_____________
Total RFIs Open / Closed in Period
_____________
2Open RFIs (by Age)7 fields
RFI Number + Date
_____________
Description (Brief)
_____________
Discipline
_____________
Days Open
_____________
Owner for Response
_____________
Impact (Critical / Major / Minor)
_____________
Target Response Date
_____________
3Critical Decisions4 fields
Decision Required Item
_____________
Approval Authority
_____________
Recommendation
_____________
Date of Decision
_____________
4Pattern Analysis4 fields
Discipline-wise RFI Trend
_____________
Area-wise RFI Concentration
_____________
Recurring Design Issues
_____________
Root Cause Recommendations
_____________
5Action Items4 fields
Action Required
_____________
Owner
_____________
Target Date
_____________
Closure Verification
_____________
💡 Sample filled excerpt
RFI Review 12-May-2026. Open: 24 RFIs (7 critical, 11 major, 6 minor). Aged > 30 days: 5 (design coordination office to address by 18-May). Pattern: 8 RFIs on MEP coordination at L3 — design re-review of MEP package recommended. Actions: 12 (5 owned by design, 7 by contractor for clarification submission).
⚖ Compliance notes
  • RFI response time per FIDIC Sub-clause 1.9 typically 14 days.
  • Aged RFIs = potential delay claim driver; track + escalate.
  • Pattern of multiple RFIs in one area = design quality issue; needs root-cause review.
  • RFI database serves as evidence of design coordination effort + delays.