Who gives way
The small pipe moves, not the duct
Both reroutes are feasible. Two elbows on a DN50 water pipe cost 0.5; on an 800 mm supply duct they cost 6 and need an airflow re-check.
pipe movespressure_loss avoided
AI-native clash resolution for Revit
MEP clashes, resolved by AI. Verified in Revit.
Import your Navisworks or BCF report, choose your trade, send the clashes to AI. ClashFree weighs every feasible fix the way a senior coordinator would: who gives way, what each change costs, which limits are hard. It applies the best one in your model, verifies it against host and linked models, and waits for your Keep.
- Free 15-day trial
- Revit 2023–2027
- Nothing changes until you Keep
Works with
Revit 2023 · 2024 · 2025 · 2026 · 2027
Navisworks XML clash reports
BCF 2.1 and 3.0
Claude Desktop and Code over MCP
Windows 10 and 11
Inside one fix
Every feasible fix, weighed.
ClashFreeReading both runs, the free space around the clash, the coordination profile and the clash test…
The workflow
From clash report to resolved model in five steps.
No scripting, no rules to set up. ClashFree lives in a pane beside your model and does the routine of every fix, so your time goes to the decisions.
Not just routing. Judgement.
Five valid fixes. One right answer.
A route that clears the clash is the easy part. ClashFree lists every feasible fix, prices each change by what it costs on that system, removes what breaks a hard limit, and only then lets the AI choose and explain. Pick a scenario.
Why this fix
fittingslength added or moveddistance movedsystem classwallsprecedent bonus
Lower is better. Scores use ClashFree's base weights; a project profile can change the soft weights, never the hard limits.
Built-in coordination knowledge
The rules of thumb a senior coordinator carries in their head.
They are data, not prompt tricks: system classes, a coordination profile in three layers (base, project, you) and checks Revit runs. The AI cites them by name; you can read and tune them per project.
Hard limit
Gravity drainage never climbs
A sloped drain is hands off: ClashFree never moves it up or down, and it says so. The tray or pipe that crosses it gives way.
drain: never movedtray moves
Project profile
The ceiling line is never crossed
A project's ceiling height is a hard constraint. The drop that would break it is removed before scoring, so the AI cannot pick it, even by override.
drop removedsideways in zone
Hard limit
A beam is never the fix
Structure is a read-only obstacle. When nothing else clears, the flag says "beam opening, structural approval" with the size needed, for a person to decide.
no beam openingflag with size
Root cause
One move clears five clashes
Clashes are grouped by the run that causes them, and the run whose change costs least per clash cleared moves first. Fix the culprit once, not five times.
grouped by culprit5 cleared
Precedent
The neighbours show the way
Runs of the same system and size already pass this beam at one height. An option at their level earns a bonus: evidence, never a rule.
precedent −800
Corridor
Access zones stay clear
Valves, dampers, terminals and equipment carry access zones. A fix that would block one costs more, and the context tells the AI why.
access kept
Finding
Dragged into a wall? Drag it back.
A run lying inside a wall along its length was usually dragged there. ClashFree says so first and proposes the drag that undoes it, stretching the neighbours.
dragneighbours stretch
Import and grouping
A thousand clashes are rarely a thousand problems.
ClashFree matches every clash to its two elements in your model and links, merges duplicates across reports, sets aside what needs no action, and groups the rest by the run that causes them. Each group is one decision.
- Duplicates merged across Navisworks tests and BCF files.
- Ignored, with a reason: approved or resolved in the report, within tolerance, or a copy of your own run in another trade's model.
- Coordination for what your trade may not move: another trade or a person decides.
- Cleared as soon as Revit finds the elements apart, after your fix or someone else's.
Two reports, one week of a hospital project
Illustrative example of an import. Your numbers show in Report details after each import.
Raw clashesStruct vs MEP + Arch vs MEP1 284
After duplicatessame pair, two tests948
Needs actiontolerance, approved, copies set aside671
Root-cause groupsone culprit run each176
To fix for Plumbingruns your trade may move58
Verified, then yours to keep
Nothing reaches your model unverified.
The AI never writes coordinates. It chooses; deterministic code builds the geometry; Revit checks it. Every step runs inside one transaction group, so Reject leaves the model exactly as it was.
01 · AI
Choose
Picks a scored option by id, or its own with millimetres, degrees and a reason that is logged and shown to you.
02 · CODE
Build
Splits, offsets, drags or reroutes the run, adds 45° or 90° fittings and reconnects every joint.
03 · REVIT
Verify
Clash gone, the clash test's clearance kept, joints connected, no new clash against host and links.
04 · PREVIEW
Roll back
The fix is rolled back and drawn as a ghost route with a snapshot. Your model is untouched.
05 · YOU
Keep
Keep re-applies it as one undo step. Reject restores the model. Or ask for a change in plain words.
A failed check sends the reason back: the next-best option is tried, up to three, before a person is asked.
Time saved
Ten small jobs per clash. ClashFree leaves you one.
By hand, every clash is the same routine: find it, judge it, cut the run, offset, fit, reconnect, re-check, undo when it fails. ClashFree does the routine for the whole list while you review the decisions.
By hand ≈ 15 min per clash
findjudgespacesplitoffsetfitjoinre-checkundo, retry
With ClashFree ≈ 2–3 min of your time
AI + Revityou: Keep
Where it fits
Clash detection finds the problem. ClashFree resolves it.
Keep running your clash tests in Navisworks or your coordination platform. ClashFree takes the report from there to a fixed, verified Revit model.
| Step | By hand in Revit | Clash detection tools | ClashFree |
|---|---|---|---|
| Find clashes | Visual checks | Yes | Imports their report |
| Merge duplicates, group by root cause | Spreadsheets | Partly, by rules you set | Automatic, by culprit run and cost |
| Decide who gives way | Experience | No | System class × size, cheaper change moves |
| Compare fixes | One at a time | No | Every feasible option, scored |
| Respect ceilings, falls, walls, access | If remembered | No | Hard limits and costs from the profile |
| Model the fix | Split, offset, fit, reconnect | No | Built by code, in your model |
| Check it clears, with no new clash | Re-run the tests | Next test run | Verified in Revit before you see it |
| Say what must be re-checked | Often missed | No | Airflow, hydraulics, falls, firestops listed |
Works with Claude
Bring Claude into your Revit model.
ClashFree ships an MCP server, and the installer connects it to Claude Desktop or Claude Code. Claude reads the clash, both runs, the free space and the scored options, looks around with sections and nearby elements, and uses the same verbs as the pane: drags that undo a modeller's move, tee slides and tilts, shift and stretch, reroutes and area fixes, all through the same checks, on your own Claude plan. Keep is always your click.
› Fix the Plumbing groups on Level 2. ● list_groups trade=Plumbing level=L2 → 7 groups ● open_clash G-021 · Pipe DN65 HWS × Duct 600×300 ● get_clash_context run 14.2 m · 2 more clashes on it ● get_options 6 scored · 2 removed (ceiling line) ● propose_fix option=best ✓ verified o2 drag 320 mm up · neighbours stretch ✓ also cleared #22, #23 0 new clashes The pipe gives way: 2 elbows on DN65 hot water cost 0.5, on the 600 mm supply duct 6 (pressure_loss). Ready in the pane for your Keep.
Your model, your call
Built so nothing happens behind your back.
Nothing commits without you
Every fix is a preview inside one Revit transaction group until you Keep it.
Reject means restored
The model returns exactly to how it was. Keep is one undo step.
Links are never edited
Structure and other trades are obstacles, not targets. When the fix is theirs, it is flagged with the reason.
The AI never draws
It chooses from a fixed list with millimetres and degrees; code builds the geometry; Revit verifies it.
Your model stays on your PC
No model, report or name is ever sent. The AI gets a text description, straight to your AI provider.
It says what to re-check
Airflow on a duct, the hydraulic calculation on a sprinkler, the fall on a drain: listed with every fix, never claimed fine.
From the blog
How the AI thinks, one clash at a time.
Who gives way
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.
Scoring
Five valid fixes, one right answer
Inside the scorer: fittings, length, distance, class factors, walls and precedents, and the limits that remove options before any score.
Time saved
The real cost of a clash
Fifteen minutes, ten small jobs and one decision. Where the hours go in clash resolution, and which of them software should take.
Questions
Before you install.
What is ClashFree?
ClashFree is an AI-native clash resolution add-in for Autodesk Revit. You import a Navisworks XML or BCF clash report, choose your trade and send clashes to AI. For each clash ClashFree lists every feasible fix, scores it, applies the best one in your model, verifies it against the host and linked models, and waits for your Keep or Reject.
Does the AI draw the geometry?
No. The AI never outputs coordinates. It picks one of the scored options, or a strategy with millimetres, an angle and a direction, and explains why. Deterministic code builds the geometry and Revit verifies it before you see it.
How does ClashFree decide which service moves?
By the cost of the change. Every run has a system class (supply duct, sprinkler, gravity drainage, domestic water, cable tray and more) with change costs scaled by size. The cheaper change gives way: a 50 mm water pipe moves before an 800 mm supply duct, whose reroute would need an airflow re-check. Gravity drainage is never moved.
How much does the beta cost?
The beta is a free 15-day trial per e-mail address, counted from your first activation in Revit. The AI runs on your own Anthropic API key, or on your own Claude plan when you drive ClashFree from Claude Desktop or Claude Code.
Which Revit versions are supported?
Revit 2023, 2024, 2025, 2026 and 2027 on Windows 10 or 11. One installer finds the versions on your PC and you tick the ones that get ClashFree.
Does my model leave my computer?
No. Your Revit model, clash reports and project, file, user and machine names are never sent. The AI gets a text description of the clash and its surroundings, straight from your PC to your AI provider. Details.
Public beta
Your next clash report, resolved.
Sign up, confirm your e-mail and get your invite code and the installer straight away. The 15-day trial starts when you activate in Revit.