- Home
- About
About ClashFree
Coordinators should spend their time on decisions, not on fittings.
Every week, BIM coordinators and MEP modellers lose days to the same routine: find a clash, judge who moves, cut the run, offset it, fit it, reconnect it, re-check it, undo it when it fails. We build ClashFree so software does the routine and people keep the judgement calls that matter.
Mission
AI that knows MEP coordination, and knows its limits.
Clash detection has been solved for years. Clash resolution has not: a report with a thousand clashes is still worked through by hand, one at a time, by people who know far more than any rule set.
ClashFree is AI-native. The AI reads each clash the way a senior coordinator would: both runs, the space around them, the system each one belongs to, what a change on each would cost and which limits are hard. But it never touches geometry directly. It chooses; deterministic code builds; Revit verifies; you decide.
That split is the whole product. It is why a fix can be explained, checked, rejected without a trace, and improved for everyone when it goes wrong.
Principles
Seven rules we do not bend.
They are written into the code and the way we work, and every feature has to respect all seven.
- 01
The AI never draws
It picks a strategy from a fixed list with millimetres, degrees and a direction, and says why. Code turns that into geometry, so a fix is never a guess.
- 02
Nothing commits without you
Every fix is a preview inside one Revit transaction group. Keep makes it one undo step; Reject restores the model exactly as it was.
- 03
Other trades are read-only
Linked models and other trades' elements are obstacles, never targets. When the right fix is theirs, ClashFree flags it with the reason.
- 04
Exact units, every time
Everything ClashFree reasons about is in millimetres and is converted exactly at Revit's boundary, so 300 mm means 300 mm.
- 05
Revit stays in charge
The AI works in the background and never blocks Revit; changes to your model only go through Revit's own safe channel.
- 06
Your keys stay yours
Your AI key is stored encrypted for your Windows user and goes only to your AI provider. We never see it.
- 07
Fixes are general, never one-offs
When a clash goes wrong, we fix the missing capability for every model and project, never a rule shaped around one clash.
Our story
Built by people who have resolved clash reports by hand.
ClashFree is made by a small team of BIM practitioners and software engineers. We started where most coordinators start on a Monday: a fresh Navisworks report, hundreds of clashes, and the knowledge that most of them would be fixed the same way, by the same people, one by one.
We did not want a black box that rewires a model. We wanted something a coordinator could trust: a tool that lists the options it considered, says why one won, names the project rule it respected, and proves in Revit that the fix clears without creating a new clash.
The beta is the next step. Every Keep and Reject that testers choose to share teaches us where the judgement is right and where it is not yet, and every improvement ships to every user.
What's next
Where ClashFree is heading.
These are plans, not promises or dates. The beta's data and your feedback decide the order.
Hand-offs to the right trade
When the cheaper change is another trade's run, a ready-made hand-off for its owner: the best option as advice, its cost and what to re-check.
Reshape a duct
The coordinator's classic: keep a duct's area and change its shape, flatter and wider, with transitions at both ends.
Team coordination profiles
One shared set of ceiling lines, zones, clearances and system rules per project, for the whole coordination team.
Moving the other run
When your run has no room, propose the move on the other side, within the same trust rules.
Overnight batches
Send a whole report in the evening and review verified fixes in the morning.
Measured numbers
Real beta figures on this site: time per clash, first-try Keep rate, new clashes per fix.
Help us shape it
Bring your hardest clash report.
The beta is where ClashFree learns what coordinators really need. Try it on a real project and tell us what it got wrong.