RFI Agent — ai rfi drafting and tracking for aec
The RFI Agent drafts RFIs grounded in the project record—drawings, specifications, prior RFIs, and meeting minutes—and tracks each item’s schedule, scope, and cost implications inside Procore and BIM 360 / ACC. It cites every premise to a source document so nothing is invented. It is available now as a co-built Labs engagement under MSA + Appendix.
- RFI drafts cited to the exact drawing, specification section, meeting minute, or prior RFI so every question carries its own evidence and context.
- Per-RFI contractual-implication summary identifying the clauses triggered, notice deadlines, change-order pathways, and potential schedule impacts.
- Project-wide RFI tracker showing open-RFI age, response-rate trends, close-out patterns, and recurring topics, ready for project review or claim preparation.
What the RFI Agent does.
-
Grounded RFI drafting
Drafts RFIs directly from the project record—current drawings (Revit, IFC, and PDF exports), specifications, prior RFI threads, meeting minutes, and contract scope exhibits. Each question cites the exact sheet, detail callout, or spec paragraph it depends on, so the contractor-side drafter avoids speculative or duplicate RFIs. Pairs with the RFI drafting and tracking workflow to give both field teams and design teams one consistent source of truth.
-
RFI review on the answering side
On the architect or engineer side, the agent reads each incoming RFI against the same record set and reports whether the premise holds up: does the latest Revit model or PDF actually show what the RFI claims is missing or unclear? It flags version drift when the contractor referenced an outdated sheet set and highlights prior RFIs or ASIs that already answered the question. This shortens the review queue while keeping the professional’s judgment in the loop.
-
Contractual-implication tagging
Tags every RFI with its contractual implications: which clause it touches, whether it starts a notice clock, and whether it opens a change-order or claim pathway. It can route specific RFIs to the Scope Agent when scope drift is implied, or to the Contract Agent when a payment, delay, or termination clause is in play. This mirrors the contract-clause monitoring workflow so commercial risk stays visible instead of buried in email threads.
-
Procore and BIM 360 / ACC integration
Connects directly to your RFI platform of record, reading RFIs and attachments from Procore or BIM 360 / ACC via their APIs. Drafted questions and suggested responses write back into the same RFI modules for human review and formal issue. The agent never auto-submits; the RFI manager or project architect owns every send and close-out. Each Labs deployment picks a canonical platform, but dual-platform firms can run project-specific configurations.
-
Guardian for RFI records across the project
Acts as The Guardian for RFI records: every question, response, and follow-up stays tied to the drawings, specs, and contract text that justified it. That history supports later schedule reviews, change-order negotiations, and claim defense. It aligns with the Scope and Contract Agents so one Guardian rule pack watches RFIs, scope drift, and contract clauses together, instead of three disconnected spreadsheets and inboxes.
-
Available now as a Labs engagement
Ships today as a co-built Labs engagement under MSA + Appendix rather than a one-click add-in. VitruAI calibrates the RFI rule pack to your contract templates, typical project sizes, and preferred RFI fields in Procore or BIM 360 / ACC. Each deployment includes per-project accuracy reporting calibrated per deployment, so technical directors can see how grounded RFI drafting performs against their existing manual baselines before scaling across the studio.
RFI Agent — questions from project teams
-
When will this ship as a productised release?
The RFI Agent is available now as a Labs engagement under MSA + Appendix, running directly against your live RFI platforms and contract templates. The waitlist on the product page is for the later productised Beta release that follows the Roadmap programme. Firms that need ai rfi drafting and tracking for aec on active projects today start through Labs so the rule pack is tuned to their portfolio first.
-
Does the agent submit RFIs without our review?
No. The agent drafts RFIs and suggested responses, but a human RFI manager or project architect always reviews, edits, and submits through Procore or BIM 360 / ACC. It only asserts premises that the project record supports and shows the exact sheets, specs, or minutes it relied on. This keeps contractual authority and professional liability with your licensed team while still cutting the time spent on repetitive drafting.
-
How does it integrate with Procore and BIM 360 / ACC?
During Labs, the team connects the agent to Procore and/or BIM 360 / ACC using each platform’s API and your existing permission model. The agent reads RFIs, attachments, and status fields, then posts drafted questions or responses back into the same RFI records for review. Each deployment selects a primary system of record, but some firms configure it to read from one system and mirror summaries into the other for specific project types.
-
How does this work alongside the Scope and Contract Agents?
The RFI Agent sits alongside the Scope Agent and Contract Agent as part of the same Guardian family. RFIs often carry the first signal of scope drift or a triggered clause, so the agent tags those items for the other two agents to track. Studios that also run contract-clause monitoring see one shared rule pack watching RFIs, scope changes, and contract events instead of three separate workflows.
-
Can it draft submittals as well as RFIs?
Submittal drafting sits with the Document AI Agent, which reads contract documents and specifications to prepare submittal responses and logs. The RFI Agent focuses on RFIs only: missing dimensions, coordination questions, and design clarifications tied to drawings and specs. On projects with heavy submittal and RFI volume, firms typically deploy both agents so document reviews and question tracking follow the same calibrated-per-deployment accuracy reports.
-
Where does the RFI drafting and tracking workflow sit in the wider VitruAI stack?
The RFI Agent underpins the dedicated RFI drafting and tracking workflow, which describes the end-to-end process from field question to final close-out. It also feeds data into contract-clause monitoring so commercial teams can see which clauses drive the most RFIs. This keeps RFI trends visible to design technology, project management, and commercial leads instead of trapped in project inboxes.