Solution
Report compliance
Every consultant report, checked against the drawings.
A single job carries a stack of consultant reports - geotech, acoustic, ESD, fire, traffic, waste - and every one of them contains requirements the drawings are supposed to have picked up. Someone has to read all of it against the set. Under tender pressure that read reaches the reports the team already knows to worry about, and the rest get a skim.
CIM audits every report in parallel against the drawings and the specification, with the Principal Project Requirements run as its own audit. The BCA/NCC volumes from 2019 to 2025 and the Red Book are preloaded, so the team can query them directly against the job. Each finding comes back with a reference box showing exactly what was reviewed - the clause, the sheet, the revision - and the findings table triages to reviewed, needs action, or future RFI.
The findings that surface are the ones that cost real money when they slip: an acoustic report calling Rw 35 where the drawings show Rw 30, or a geotech recommending CFA piles against bored piles in the structural notes. Those are cross-references a design manager works through drawing by drawing. Here the whole set is done in minutes and the RFI goes out on day two.
Before CIM
- Reports get read against the drawings where someone had the time.
- A requirement missed in a report is priced at nothing and paid for in delivery.
- Findings live in one reviewer's head or a marked-up PDF.
With CIM
- Every report audited against the drawings and the spec, in parallel.
- Each finding cited to the clause, the sheet and the revision it came from.
- A findings register that triages to reviewed, needs action, or RFI.
Customer story
Catching a $50K+ discrepancy before the package was let
A three-document coordination error - RW35 required, RW30 scheduled, no seals specified - caught, cited and confirmed before the window package was let.
Read the story