AI-routed RFIs with suggested responses based on similar past requests and spec references.
RFIs slow projects down when they pile up unanswered or get routed to the wrong person. RFI Management fixes the routing problem (correct recipient based on RFI category and project role) and the response problem (drafts a starting answer based on similar past RFIs and the relevant spec).
The RE never has to start from a blank page. Every new RFI lands with a draft response that cites the relevant Special Provision section and pulls language from how similar issues were resolved on past projects. The RE edits, signs, and sends. Cycle time drops from days to hours.
When an RFI does require a contract change, it links straight into the change-order workflow without re-keying.
Built for construction professionals — not generic SaaS.
Each new RFI gets a draft response based on the question content, the relevant spec section, and the response patterns from similar past RFIs on this contract or other contracts using the same spec.
RFI category + project role + RFI urgency determines the correct recipient. No more "RFI lost in someone's inbox" — the system tracks acknowledgment, response, and approval cycles.
Every draft response cites the spec sections it relies on. The RE sees exactly what the AI grounded its draft in and can verify before signing.
When a response triggers a change, one click promotes the RFI thread to a change-order draft. Original question, response, and any attached drawings flow forward.
How long does each RFI category take to close on this project? Where is the bottleneck — design team, RE, contractor? Surfaced in the project dashboard.
When a new RFI lands, the system searches similar RFIs across the company's project history. "We answered this exact question on the I-94 deck job last year — here's how."
RFI text is embedded against the same vector store that holds the Special Provisions and the Construction Manual for this project, so semantic similarity drives routing and draft generation. Past resolved RFIs are also embedded; new RFIs find their nearest precedents and the responses that closed them.
The draft response generation uses Claude with a tight prompt: read the new RFI, retrieve the top 3 similar past RFIs and the top 5 relevant spec sections, then draft a response in the company's standard RFI voice. The RE always sees the source citations and can verify before signing.
Routing is rule-based on top of the AI category detection. The rules are configurable per-project — different REs handle different categories on different jobs.