- ClashFree
- Blog
The ClashFree blog
How the AI thinks, one clash at a time.
Worked examples from MEP coordination: which service gives way and why, how a fix is scored, the limits no AI may break, and what every change asks an engineer to re-check. Drawings included.
AI-native clash coordination: the whole loop, from report to Keep
Import, choose your trade, pick, send to AI, keep. The whole loop, and why each part sits where it does.
What a fix changes
The bill every fix carries, and the airflow, hydraulic, fall and firestop checks it triggers. ClashFree simulates nothing.
Learning from the neighbours
Nearby runs, twin rooms on other levels, access zones and the wall a run was dragged into: evidence, never a rule.
One fix, many clashes
Duplicates, ignorable clashes and the culprit run chosen by cost per clash cleared. Fix the cause once.
Hard limits the AI cannot break
Falls, ceiling lines, structure, risers and other trades' runs: enforced by the validator, not requested in a prompt.
Five valid fixes, one right answer
Fittings, length, distance, class factors, walls and precedents: a worked example of the scorer, term by term.
Why the pipe moves, not the duct
Both reroutes are feasible. Only one is cheap. How ClashFree prices a change by system class and size.
The real cost of a clash
Ten small jobs and one decision per clash. Where the hours go, the arithmetic, and what software should and should not take.
Public beta
Try it on your next clash report.
Sign up, confirm your e-mail and get your invite code and the installer straight away. Free 15-day trial, Revit 2023–2027.