Solution
Bulk compare
A whole set compared in one run, on your instructions.
Comparing one sheet against its previous issue is a small job. Comparing 400 of them is a week, so it gets sampled - the structural sheets and the wet areas, and everything else goes through on trust.
Bulk compare runs the whole set at once. You describe what matters in plain English - slab levels, fire ratings, anything the last set caught you on - and the comparison applies that instruction to every sheet, in parallel.
Save the instruction as a template and it runs the same way on the next issue, and the one after. Every run is kept with its date, its inputs and its results, so a comparison made in March can be shown intact when the claim is argued in November.
How a run works
One instruction in plain English, applied to the whole set and kept as a template.
01/Your instruction, in plain English
Compare Rev C to Rev D. Flag slab levels, set-downs, fire ratings and anything in the notes.
412 sheets
Read in one run
17 changed
Against your instruction
6 unclouded
Nothing on the transmittal
1 template
Saved for the next issue
02/Results, and the record of them
What it does for your team
Builders
The whole set, not a sample
400 sheets compared in one run, so the sheets nobody had time for get the same read as the structural ones.
Certifiers and surveyors
One instruction, every project
Save the comparison your practice always runs and apply it to the next set the same way.
Consultants
A record of what was compared
Every run kept with its inputs and results, which is what defends the read months later.
Before CIM
- A full set comparison is a week, so only part of it happens.
- Each reviewer compares to their own standard.
- No record of what was compared, or when.
With CIM
- The whole set compared in one run, sheet by sheet.
- Your comparison instructions saved as a template and reused.
- A history of every run, with inputs and results attached.