Real-time dashboards, SLA monitoring, immutable audit logs, and one-click closeout packages. Everything you need to know about every RFI that has ever touched your project.
The RFI dashboard updates in real time. Here is what a typical mid-project dashboard looks like.
Open RFIs
→ 12 assigned, 35 in review
Avg Response Time
↑ 23% faster than last month
Overdue Items
↓ Down from 12 last week
On-Time Rate
↑ Up from 81% at project start
| RFI # | Subject | Trade | Submitted | Due | Status |
|---|---|---|---|---|---|
| RFI-0247 | Structural-MEP conflict at grid B-7 | Mechanical | Jun 8 | Jun 13 | In Review |
| RFI-0246 | Pipe support spacing — 4-inch gas line, level 3 | Plumbing | Jun 7 | Jun 12 | Overdue |
| RFI-0245 | Confirm beam designation B-7 (LF or SB?) | Structural | Jun 7 | Jun 9 | Overdue |
| RFI-0244 | Surface finish callout conflict — Detail 12/A-401 | Architectural | Jun 6 | Jun 13 | Open |
| RFI-0243 | Substitution request: 316L → 317L stainless | Process | Jun 5 | Jun 12 | In Review |
| RFI-0242 | Ceiling height conflict — level 2 east wing | Architectural | Jun 4 | Jun 11 | Closed |
The dashboard shows average response time broken down by:
The most common bottleneck is draft dwell time in the review queue — the interval between when a reviewer receives the item and when they act on it. This is where coaching and workload balancing have the most impact.
RFIs enter "overdue" status when the SLA timer expires without a closed response. The dashboard shows:
Weekly RFI volume is charted over the project lifecycle. Expected pattern:
Spikes in volume often correlate with document issues — a revised drawing that creates new conflicts, or a new subcontractor unfamiliar with the spec. Volume spikes are a leading indicator of coordination problems.
Per-reviewer metrics:
These metrics are for workload balancing and coaching, not performance evaluation. A high edit rate may mean the reviewer is rigorous, not that the AI is failing.
The audit trail completeness metric shows the percentage of closed RFIs that have a complete event record — intake to delivery with no gaps. This should be 100% for any properly configured workflow.
Gaps appear when RFIs are closed manually outside the workflow (e.g., via a direct email reply that bypasses the system). The completeness metric surfaces these gaps so they can be retroactively documented.
For each closed RFI where an AI draft was generated:
The "major edits + reject" rate is the primary signal for KB quality. If it is high, your KB is missing content that reviewers need. Add the documents that reviewers are consulting manually.
Every event in the RFI lifecycle is written to an immutable append-only log. Here is what a complete audit log looks like for a single RFI.
2026-06-08T09:14:22Z RFI_RECEIVED channel=email sender=john.smith@contractor.com subject="Grid B-7 MEP-Structural Conflict" rfi_id=RFI-0247
2026-06-08T09:14:23Z CLASSIFICATION_COMPLETE trade=Mechanical urgency=high spec_section=15810 question_type=conflict confidence=0.91 rfi_id=RFI-0247
2026-06-08T09:14:24Z ROUTED assigned_to=sarah.chen@owner.com sla_hours=24 sla_deadline=2026-06-09T09:14:24Z rfi_id=RFI-0247
2026-06-08T09:14:31Z KB_QUERY_COMPLETE passages_retrieved=5 top_score=0.91 sources=["DIV15-15810","RFI-0087-archive","S-001-structural-notes"] rfi_id=RFI-0247
2026-06-08T09:14:38Z DRAFT_GENERATED word_count=187 citations=3 low_confidence_flags=0 rfi_id=RFI-0247
2026-06-08T09:14:38Z REVIEW_QUEUED reviewer=sarah.chen@owner.com queue_depth=4 rfi_id=RFI-0247
2026-06-08T11:03:17Z REVIEW_OPENED actor=sarah.chen@owner.com time_in_queue=6897s rfi_id=RFI-0247
2026-06-08T11:09:44Z DRAFT_EDITED actor=sarah.chen@owner.com edit_type=minor diff_chars=42 edit_summary="Added confirmation of beam designation from S-204" rfi_id=RFI-0247
2026-06-08T11:10:02Z RESPONSE_APPROVED actor=sarah.chen@owner.com review_duration=399s rfi_id=RFI-0247
2026-06-08T11:10:04Z RESPONSE_DELIVERED channel=email recipient=john.smith@contractor.com sla_compliance=met time_to_close=6582s rfi_id=RFI-0247
2026-06-08T11:10:04Z SLA_CLOSED sla_deadline=2026-06-09T09:14:24Z closed_at=2026-06-08T11:10:04Z time_remaining=79940s rfi_id=RFI-0247
2026-06-08T11:10:06Z KB_FEEDBACK_PROMPT_SENT reviewer=sarah.chen@owner.com edit_detected=true prompt_type=add_to_kb rfi_id=RFI-0247The full audit log — for a single RFI or all RFIs on a project — is available in:
All exports are timestamped and digitally signed by the RenderDraw platform at the time of export. The signature allows recipients to verify the log has not been altered post-export.
RenderDraw RFI tracking connects to the tools your team already uses. RFI data flows in both directions — inbound from your project management system, outbound to your reporting and analytics stack.
Bidirectional sync with the Procore RFI module. RFIs submitted in Procore trigger the RenderDraw workflow. Responses write back to the Procore record. Log data stays in both systems.
Connect to ACC / BIM 360 RFI workflows via the Autodesk Construction Cloud API. RFIs flow from ACC into RenderDraw for AI drafting and route back on approval.
Connect a dedicated RFI inbox via Microsoft 365 or Google Workspace. Incoming emails are parsed and queued. Responses are sent as reply-to-thread from the same address.
Reviewer notifications, SLA warnings, and escalation alerts are delivered to your team's messaging platform. Reviewers can approve simple RFIs directly from the notification.
The RenderDraw analytics API exposes RFI log data in a schema compatible with Power BI and Tableau. Build custom dashboards on top of your project data.
Every tracking endpoint is available via the RenderDraw REST API. Build custom integrations with your ERP, project controls system, or document management platform.
At project closeout, generate a single exportable package containing:
Start your free trial and have full RFI tracking running on your project in under 30 minutes.