Solution
Safeguard
A package goes out when its scope risk is closed out.
Every finding CIM raises is worth something up to the moment it is ignored. A scope of works gets exported and a package gets let while the RFI that would have changed it is still open, the compliance finding against that trade is still unresolved, and the quote exclusion nobody triaged is still sitting in the register. The exposure leaves the building attached to the document.
Safeguard puts a gate on the way out. The actions that send project content out - exporting a scope of works to your template, issuing a trade package - are held while covered items remain against that trade: open RFIs, blocking findings from the latest completed audits, documented conflicts inside the trade's scope register, and scope rows the subcontractor quotes left uncovered.
Your team sets which registers a gate watches and which states of them count, and a gate runs against one trade or the whole project. Anything a person has already dismissed stops holding anything. The discipline stops depending on whoever remembers to check the register before they hit export.
How a gate runs
01/The action fires
Someone exports a scope of works to your template, or sends a trade package out.
02/The gate reads its registers
For the trade the action names, or across the whole project. Your team chooses which registers a gate watches, and which states of them count.
- Open RFIsUnanswered, in the states you choose
- Report complianceBlocking findings naming the trade
- Scope discrepanciesDocumented conflicts in the register
- Quote exclusionsScope the quotes left uncovered
03a/Held
Covered items are still outstanding. The action is held and the gate names what is holding it, item by item.
Answer the RFI, resolve the finding, triage the exclusion - in the register it lives in - and the gate reads again.
03b/Clear
Nothing covered is outstanding against that trade. The export runs and the package goes out.
Anything a person has already dismissed stops holding the gate, so what is left is real.
What it does for your team
Builders
No package let with open risk on it
The export is held while open RFIs, blocking findings and untriaged quote exclusions remain against that trade.
Developers
What you pay for is what was cleared
Nothing leaves the project record until the items raised against it have been resolved or dismissed by a person.
Certifiers and surveyors
Nothing issued over an open item
A gate on the way out means the register is closed before your name goes on the document.
Before CIM
- Packages get let with open RFIs and unresolved findings against them.
- Whether the register gets checked before export depends on the day.
- The final payment application is where the missed exclusion turns up.
With CIM
- Outbound actions held while covered items remain against the trade.
- Your team sets which registers count, and which states block.
- Dismissed items stop holding anything, so the gate stays honest.