RFI Response Tracker and Follow-Up Organizer
Track and manage open RFIs through to closure, identifying overdue responses, schedule impacts, and potential claim situations. This prompt helps contractors build a systematic RFI management process that protects the schedule, documents the decision record, and supports potential delay claims.
This prompt analyzes contractor-side RFI log data and produces a status summary, an overdue response analysis for RFIs past the contractual response period (with escalation notice template language), a critical path RFI ranking by schedule urgency, a design team response time trend analysis, a clustering analysis identifying whether multiple RFIs indicate a drawing coordination problem that warrants an architect-issued revision, and a log template optimized for this project type. RFIs where design team response delays may support a schedule delay claim are flagged with documentation requirements — formal claim preservation notices must be submitted within the contractual notice period and reviewed by legal counsel before filing. It is for general contractors and project managers tracking RFI cycles on commercial and institutional construction projects.
The prompt
You are a senior construction project manager with expertise in construction administration, RFI management, and construction claims documentation. Analyze and organize the following RFI tracking data: Project information: - Project name: [PROJECT_NAME] - Construction phase: [PHASE] - Contract completion date: [COMPLETION_DATE] RFI log data: [PASTE OR DESCRIBE RFI LOG — include RFI number, description, date submitted, status, days outstanding, response needed by date] Analyze the RFI log covering: ## RFI Status Summary Count by status: open, responded, closed, pending clarification. Average days to respond. Any pattern changes from prior period. ## Overdue RFI Analysis All RFIs exceeding the contractual response period — with days overdue, schedule impact, and recommended action. ## Critical Path RFI List RFIs on or affecting the critical path — ranked by schedule impact urgency. ## Design Team Response Time Analysis Average and range of design team response times — identify if response times are improving or deteriorating. ## Potential Claim Documentation RFIs where delayed responses may support a schedule delay or disruption claim — note documentation requirements for preserving claim rights. ## Clustering Analysis Are multiple RFIs related to the same area, detail, or system? Clusters suggest a drawing coordination issue that should be escalated to the architect. ## RFI Log Template A standard RFI log template for this project type. ## Recommended Escalation Actions For overdue RFIs: template notification language to the owner and architect documenting the delay and its impact.
Runner beta coming — join the waitlist.
In-product execution isn't live yet. Leave your email and we'll let you know if the Runner beta opens.
How to use this prompt
1. Update the RFI log at every project team meeting and distribute weekly to the owner and architect — transparency about open RFIs prevents surprises and maintains pressure on timely responses.
2. Link RFIs to the construction schedule activities they affect — this makes critical path impacts immediately visible when RFIs go overdue.
3. Close RFIs promptly when responses are received and note whether the response is adequate or requires follow-up.
Customization tips
Sample output
Related prompts
Frequently asked questions
This AI-generated content is for informational and educational purposes only. It does not replace the professional judgment of licensed engineers or construction professionals. Always verify against current contract documents, local building codes, and safety regulations.