Structured, discipline-by-discipline clash rounds run to a documented resolution log — not a raw report handed back unresolved.
Clashes are grouped by discipline and severity, hard clashes separated from soft clearance issues, and every item tracked to resolution — so each round shrinks the list instead of just re-reporting it.
The same four-stage delivery model, applied to clash detection.
Clash test rules configured by discipline pair, tolerance and severity in Navisworks or Revizto.
Clash results grouped by location and discipline rather than reviewed as a flat list.
Each clash assigned an owner and priority in a joint review session.
Resolution tracked round over round until the model reaches clash-free status.
Navisworks and Revizto, matched to what your team already uses for review.
A hard clash is physical overlap between two elements; a clearance issue is a maintenance, access or code clearance violation without physical overlap. We track them separately since they're resolved differently.
Both — we flag, group and assign clashes, and can also make the model-side fix where the resolution sits within our scope.
On construction-ready engagements for contractors, yes — resolution is tracked to a documented, clash-free sign-off. On design-stage consultant engagements, the same structured process applies without the formal guarantee, since the design is still being developed.
