CONSTRUCTION INTELLIGENCE / RFI & SUBMITTALS
Point Mirage at your RFI log and submittal register. Live and tracking within 48 hours, with every item's current status and source document one question away.
Running at OCBM, John Cockerill, and a US rail contractor.
THE REALITY
RFIs and submittals pile up across email, Procore, and SharePoint, with no single view of what's open, what's overdue, or who's supposed to be answering. Nobody notices the ones that stall until they're already blocking the schedule.
WHAT MIRAGE DOES
01
Mirage reads RFIs and submittals the moment they come in, by email, upload, or directly from Procore, and tracks each one's status, assignee, and days open without manual re-entry.
02
Ask whether a specific RFI is closed and get the answer with the exact date and document it was resolved in. Mirage does not guess or summarize beyond what the record states.
03
Items sitting unanswered past a threshold are flagged and routed to the responsible person automatically. Connects to Procore, Autodesk, and the systems already in place, no new login for the field team.
THE OUTPUT
| RFI / Submittal # | Subject | Status | Assigned To | Days Open |
|---|---|---|---|---|
| RFI-114 | Rebar spacing at retaining wall | Closed | Structural Engineer | 3 |
| SUB-042 | Waterproofing membrane submittal | Under review | Design Team | 9 |
| RFI-121↳ 16 days open against a 10-day response target on this project. Flagged and routed to the mechanical engineer. | Platform clearance detail | Overdue | Mechanical Engineer | 16 |
| SUB-047 | Steel connection shop drawings | Approved | Structural Engineer | 5 |
PROOF
US Rail Contractor
RFIs, meeting minutes, and inspection reports indexed and answered with an exact source
Every flagged item routed to the responsible PM or Superintendent automatically
0% of indexed sites left working from a superseded revision
OCBM
3 agents in production
100% of quantities traceable to a source drawing
Every flagged inconsistency reaches an engineer before submission
Send us your current RFI log or submittal register, and we'll show you what tracked, sourced status actually looks like.
FAQ
No. It reads whatever log or system you already track RFIs and submittals in and answers status questions against it. Your log stays the system of record; Mirage is the layer that reads and tracks it for you.
Document intelligence answers "what does this document say." This tracks the lifecycle of a specific RFI or submittal: is it open, who it's assigned to, how long it's been waiting, and what it was answered with.
Yes. Every tracked item carries its status and days open, and overdue items are flagged individually rather than buried in a long list, so nothing sits unanswered without someone knowing about it.
Yes. It reads RFIs and submittals as they're logged, whether by email, upload, or directly from Procore, and doesn't require your team to change how they submit or respond to them.
Yes. Every answer comes with the exact document name, page, and revision it was pulled from. Mirage does not summarize or infer beyond what the source document states.
Every flag and every answer is reviewable before it's used. Mirage surfaces status and routes what's overdue; the response to each RFI or submittal is still your team's call.
Under four weeks on average to a production deployment: log and document infrastructure audit first, then a parallel pilot tracking one active project's RFIs and submittals before rollout to the rest.
Pricing starts with a fixed-price pilot tracking one active project's RFI and submittal log, so you see it working before committing to anything larger. After that, it moves to an annual subscription priced by volume, quoted in your first conversation with us.
ALSO ON THIS SITE