CONSTRUCTION INTELLIGENCE / DOCUMENTS
Point Mirage at your RFIs, submittals, change orders, and site reports. Get an answer back with its exact source in under 4 seconds, live on your documents in 48 hours.
Running at OCBM, John Cockerill, and a US rail contractor.
THE REALITY
Finding the current version of one document used to take 18 to 25 minutes on a good day. Some teams kept working from outdated revisions without ever finding out.
WHAT MIRAGE DOES
01
Mirage indexes revised plans, RFIs, submittals, change orders, meeting minutes, and site reports as they're added, whether PDF, scanned, or native file. No manual tagging or folder reorganization before it starts working.
02
Every answer comes with a document name, page, and revision number. Mirage does not summarize or interpret beyond what the source document states, so anyone can check the original in seconds.
03
Connects to SharePoint, Procore, and the document systems already in place. No new login for the field team, no separate app on top of what's already installed on site devices.
THE OUTPUT
| Question Asked | Answer | Source | Page | Revision |
|---|---|---|---|---|
| What's the rebar spacing on the retaining wall? | 16 in o.c., vertical and horizontal | Structural Spec 03 20 00 | 12 | Rev 3 |
| Is RFI-114 closed? | Yes, answered April 3 | RFI Log, item 114 | 1 | Rev 1 |
| What's the platform clearance requirement?↳ The longitudinal profile drawing states a different clearance value for the same requirement, on the same revision. Flagged as a contradiction. | 150 mm above platform level | Spec Sheet, Section 4.2 | 8 | Rev 4 |
| Where's the current fencing detail for the north perimeter?↳ No fencing detail exists anywhere in the latest revision. Flagged as missing rather than answered from an outdated one. | Not found in the current document set | Site Plan index | Not found | Rev 5 |
PROOF
US Rail Contractor
Document retrieval cut from 18-25 minutes to under 4 seconds
0% of indexed sites on superseded revisions
31 spec-to-plan inconsistencies caught before inspection
OCBM
3 agents in production
100% of quantities traceable to a source drawing
0 quantities without a source reference
John Cockerill
One traceable source of truth across estimating and fabrication, replacing a spreadsheet nobody could fully audit
Fabrication bill of materials down from a month to a few clicks, no 3D model required first
3 engineering disciplines running on one platform
Send us a sample of your project documents, and we'll show you what an indexed, sourced answer actually looks like.
FAQ
No. Mirage indexes what's already in SharePoint, Procore, or your document store and answers questions against it. Your document system stays the system of record; Mirage is the layer that reads it.
It searches indexed project documents and returns the answer with an exact citation: document name, page, and revision number. It doesn't summarize or infer beyond what the source document actually states.
Yes. Field teams access it through the credentials they already use, on devices already in use on site. No separate login, and no new app to install on top of what's there.
The conflict is surfaced, not resolved automatically. Mirage flags the documents and the specific values that disagree, and routes it to the person responsible for that document to decide.
Scanned documents are indexed the same way as native files. Handwritten field notes are the one input type where accuracy drops, and flagged answers reflect that lower confidence.
It updates as documents are added or revised, so answers reflect the current version by default. Every answer states which revision it was pulled from, so nobody has to double-check separately.
Under four weeks on average to a production deployment: document infrastructure audit and indexing first, then a parallel pilot on one active site before rollout to the rest.
Pricing starts with a fixed-price pilot indexing one active project, so you see real answers 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