Feature
Safeguard
A package goes out when its scope risk is closed out.
A finding is worth something up to the moment it is ignored. Safeguard puts a gate on the actions that send project content out, exporting a scope of works or letting a trade package, and holds them while open RFIs, blocking findings, scope discrepancies or untriaged quote exclusions remain against that trade.
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.
The old way
Packages get let with open risk against them
The package goes out with the RFI still open
The question that would have changed the scope is unanswered, and the scope of works leaves anyway.
Checking the register depends on the day
The discipline sits with whoever remembers to look before hitting export.
The missed exclusion lands at the final payment application
A quote exclusion nobody triaged becomes your cost once the package is let and the work is on site.
With CIM
Nothing leaves while covered items remain against the trade
No package lets with open risk on it
Export and package actions are held while open RFIs, blocking findings, documented scope conflicts or uncovered scope rows remain against that trade.
Your team decides what blocks
Choose which registers a gate watches and which states count. Run it against one trade or the whole project.
The gate stays honest
Anything a person has already dismissed stops holding, so the team keeps control and the discipline stops depending on memory.
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.