- Home
- How it works
How it works
Report in. Five steps. Resolved model out.
ClashFree is AI-native: the AI is not a chat box on the side but the engine that weighs every fix. You stay where judgement matters, at the start (your trade, your clashes) and at the end (Keep).
Step 01
Import the clash report.
Open the ClashFree pane from the ribbon and import one or more Navisworks XML clash reports or BCF files. Run your clash tests where you always do; ClashFree starts from their output.
- Matched to both elements in your model and its loaded links; fittings and accessories resolve to their run.
- Duplicates merged across tests and files; what needs no action goes to Ignored with its reason.
- Grouped by root cause: one group per culprit run, ranked by priority, each with a stable G-id.
- Re-tested straight away: clashes already apart in the model go to Cleared.
What an import does to a report
Illustrative example of two reports on one project.
Step 02
Choose your trade.
ClashFree asks once which trade you are and remembers it. Everything after is filtered to what your trade may move, because the rule is simple: you fix your runs; other trades' runs and linked models are obstacles.
- Counts per trade come from your model: groups your trade can fix, and groups that involve it.
- Change it any time with the trade pill at the top of the list.
- When the cheaper change is another trade's, the clash goes to Coordination, with the reason for its owner.
Step 03
Pick the clashes.
The work list is one list with four tabs. Start with To fix, highest priority first. A row click shows the clash in Revit; › opens it. Tick what you want the AI to work on.
- To fix · Coordination · Ignored · Cleared, each with its reason under the title.
- Search, Level and Filters by priority, strategy, AI status, change and related groups.
- Groups or clashes: the list icon switches to a flat list of clashes.
- Shift-click selects a range, Space toggles, Esc clears.
Step 04
Send to AI. See the cost first.
Send to AI adds the selection to the AI queue and tells you how many items, which model and about how much, before anything runs; no API key is needed to queue. Run works one clash at a time in the background with your API key, or Claude over MCP takes the queued items.
- a
Context
Both runs through their fittings, every clash on them, free space, walls, precedents, access zones, the profile and the clash test.
- b
Options and choice
Every feasible fix scored, hard limits removed; the AI picks and explains.
- c
Build and verify
Applied in Revit, checked, rolled back. A failure tries the next option, up to three, then flags with a reason.
- d
Ready
The row shows verified, failed, flagged or stale. Stop any time.
Step 05
Keep, reject or revise.
Open a verified fix. The clash page shows both elements, the AI's proposal and why, Revit's verification with a snapshot, and what the fix changes on the run. Preview fix draws its route in Revit as a ghost.
- Keep applies it as one undo step. Next opens the next clash your trade can fix.
- Reject leaves the model exactly as it was.
- Revise in plain words: "go over the beam", "keep 100 mm from the wall".
Under the hood
Every proposal makes the same round trip.
Choose
A scored option by id, or its own with millimetres, degrees and a logged reason.
Build
Split and offset, move, drag or reroute the run, or slide or tilt a tee; 45° or 90° fittings; every joint reconnected.
Verify
Cleared at the test's clearance, joints connected, no new clash in host and links.
Roll back
Transaction group rolled back; the fix is kept as a ghost route and a snapshot.
Keep
Re-applied as one undo step, or rejected with the model untouched.
Cleared
Fix one, and watch the others clear.
A fix often clears more than its own clash, and other people's fixes clear yours. After an import, when the pane opens and after each Keep or Reject, ClashFree re-tests the To fix clashes in Revit in the background: geometry only, no AI, skipping elements that have not changed. Those apart move to Cleared.
- The header shows Checking n/N while it runs; the list updates as clashes clear.
- Opening a clash re-checks it first: if a kept fix already cleared it, the page says so and offers Next, and no AI is asked.
- Move back returns any clash to To fix, Coordination or Ignored; moves survive a reload and the next import.
The same workflow, with Claude
Or let Claude drive, on your Claude plan.
Connect Claude Desktop or Claude Code from the installer. Ask Claude to work through a trade or a level: it lists the groups, opens each clash, reads the context and the scored options, proposes fixes through the same checks and moves on. The pane shows a toast when Claude opens a clash and a banner with its budget and Stop. Keep stays your click.
› Work through the Plumbing groups on Level 2. ● get_status report set loaded · trade Plumbing ● list_groups level=L2 → 7 groups ● open_clash G-014 · Pipe Ø100 DCW × Beam (linked) ● get_options 5 scored · 2 removed (column, slab) ● propose_fix option=best ✓ verified o1 offset down 300 mm, 45° ● open_clash G-021 · Pipe DN65 HWS × Duct 600×300 ● get_clash_context 2 more clashes on the run ● propose_fix option=o2 (drag) ✓ verified · also cleared #22, #23 Two fixes ready in the pane for your Keep.
Public beta
Five steps. Try them on your own report.
Free 15-day trial, Revit 2023–2027. Your invite and the installer arrive as soon as you confirm your e-mail.