CONSTRUCTION INTELLIGENCE / SPECIFICATION REVIEW
Send us your specifications and current plan set. Mirage cross-references every clause against the drawings and flags what doesn't match in 48 hours, then re-checks automatically on every new revision.
Running at OCBM, John Cockerill, and a US rail contractor.
THE REALITY
Non-conforming geometry and missing work zones usually surface during field inspection, when fixing them is already disruptive and costly. Nothing cross-references the written spec against the drawings before that point.
The same consistency-checking discipline extends to CSI MasterFormat classification and prevailing wage compliance — the same underlying agents, applied to a different document set.
WHAT MIRAGE DOES
01
Mirage reads the written specification alongside the plan set, clause by clause, and resolves what each requirement means on the drawing it applies to. CCTP, DCE, and technical specifications are handled the same way as the plans themselves.
02
Every flagged conflict names the clause, the drawing, and the specific values that don't match. Nothing is corrected automatically. The flag goes to the engineer responsible for that section, with the reasoning attached.
03
Runs again automatically each time a new revision comes in, without anyone triggering it manually. Connects to Procore, Autodesk, and the document systems already in place.
FRENCH TENDER DOCUMENTS
Mirage reads CCTP, DCE, and other French-format tender documents the same way it reads English-language specifications, cross-referencing every clause against the plan set they apply to.
THE OUTPUT
| Clause | Drawing Reference | Conflict Type | Status |
|---|---|---|---|
| CCTP 04.2, curve radius tolerance | Sheet C-14, Detail 3 | Geometry deviation | Flagged |
| Work zone WZ-08, per statement of work↳ The specification calls for this work zone, but no corresponding drawing exists anywhere in the current set. | Sheet C-22 | Not shown in plan view | Flagged |
| Clearance spec, Section 6.1↳ The spec sheet states one clearance value; the longitudinal profile drawing states a different one for the same requirement. | Longitudinal profile, sheet 21 | Contradicts spec sheet value | Flagged |
| Rebar cover, Section 03 20 00 | Sheet S-108 | Matches plan | Cleared |
PROOF
US Rail Contractor
31 spec-to-plan inconsistencies caught before inspection
14 geometry, 9 missing work zones, 8 contradictory tolerances
0 required post-inspection remediation
OCBM
3 agents in production
100% of quantities traceable to a source drawing
1 dedicated agent for drawing and document consistency
John Cockerill
Automatically applies the API 650 standard's platform-clearance and shell-course rules on every boilermaking drawing
Catches incomplete or wrong nomenclatures on structural steel drawings other systems miss
3 engineering disciplines validated against John Cockerill's own drawing conventions and standards
Send us your current specifications and plan set for one active project, and we'll show you exactly what gets flagged.
FAQ
No. Mirage checks specifications against drawings continuously and flags what doesn't match. Your engineers still decide what each flag means and whether it needs a design change; Mirage doesn't make that call for you.
A value, clause, or requirement in the specification that doesn't match what's shown on the corresponding drawing: geometry outside tolerance, a referenced work zone missing from the plan, or two documents stating different numbers for the same thing.
Yes. Each time a new revision is committed, Mirage re-runs the comparison and flags only what changed or what's newly inconsistent. Nobody has to trigger a manual review after the initial setup.
Yes. Every flag names the clause, the drawing reference, and the specific values that disagree. The reasoning is attached to the flag itself, not just a red mark with no explanation behind it.
Every project runs through the same setup: index the specification and plan set once, and it re-checks automatically after that. There's no limit on how many active projects run at the same time, and no per-project configuration beyond the initial indexing.
The reviewing engineer dismisses them with one click. Every flag stays a proposal until a person confirms it. Nothing is corrected or resolved automatically on either side of a flagged conflict.
Under four weeks on average to a production deployment, following the same audit-then-pilot approach as our other construction agents: indexing and setup first, then a parallel pilot on one active project.
Pricing starts with a fixed-price pilot run on one active project's specifications and plans, so you see real flagged conflicts 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