Audit a model before it goes out
Run the checks that catch a bad model before a client or a site team opens it: coordinate base, live clashes and classification completeness.
How it works, step by step
3 steps across the platform - what you do at each one, and why it matters.
Check the coordinate base
FederationsConfirm the model sits on the shared project origin and grid before anyone downstream measures or clashes against it.
Why: A model that is a few centimetres off the shared base silently corrupts every clash test and quantity taken from it later.
Run a clash pass as a quality check
Clash detectionRun the clash test as a final quality gate rather than a coordination exercise, looking specifically for gross geometry errors rather than genuine trade conflicts.
Why: A clash run at issue time catches a model with parts floating in space or duplicated by accident, the kind of error a design review alone can miss.
Confirm classification is complete
ValidationRun the validation rules and confirm every element carries the classification and property set the next stage expects, with no unmapped category left behind.
Why: A model with a gap in its classification hands the next user, an estimator or a contractor, an element they cannot price or schedule without asking you first.