CYF BIM Studio

Auto Join Pro — Help

Version 1.0.0 · Autodesk® Revit® 2025, 2026, 2027

Auto Join Pro joins geometry and reports clashes across a whole model, a whole view, or a manual selection, with the join priority under your control.

Installation

  1. Close all running instances of Revit.
  2. Run the installer downloaded from the Autodesk App Store.
  3. Start Revit. A CYF tab appears on the ribbon with an Auto Join Pro panel containing two buttons: Batch Join and Clash Check.

The app is installed to %ProgramData%\Autodesk\ApplicationPlugins\Auto Join Pro.bundle.

The dialog

Both ribbon buttons open the same window; they differ only in which mode it starts in. The window is modeless, so you can keep it open while you work in the model.

Execution Scope

Active View cannot be used on a schedule, a sheet or a drafting view, because those cannot host model elements. Switch to a plan, section or 3D view, or use Project or Selection scope instead.

Action Mode

Categories

Move the categories your project uses from Available into Priority (High → Low) using the arrow buttons, or by double-clicking an entry. Use the up and down buttons to rank them.

Join works on Structural Columns, Architectural Columns, Structural Framing, Structural Foundations, Floors, Walls and Roofs.

Clash Check adds five more: Stairs, Toposolids, Ceilings, Generic Models and Slab Edges. The category list changes automatically when you switch modes. Those five are checked for overlaps but never joined, for two different reasons:

Both remain useful in a clash check — a beam running through a ceiling is a real coordination problem, and you still want to see it.

Priority order

Whatever sits higher cuts whatever sits lower, in every join the tool creates. A structural model usually reads top to bottom as:

  1. Structural Columns
  2. Structural Framing
  3. Structural Foundations
  4. Floors
  5. Walls

Columns run full height and cut the beams that frame into them; beams cut the slabs they support; slabs cut the walls beneath. If your office's take-off convention differs, reorder the list to match it — and keep the same order for every run on a project, so the quantities stay comparable.

Two elements of the same category are joined when they overlap, but no cut order is applied to them, because neither one outranks the other.

Concrete, not steel

Steel members are skipped in Join mode, even when they belong to a category you selected.

The reason is simply that joining them does nothing. Revit will record the join, but no geometry is cut — we measured the solid volumes before and after, and they are identical. Revit's own Join Geometry command will not even let you select a steel member. Steel connections in Revit are handled through the Steel tab, with plates, bolts and welds, not by joining geometry.

So rather than spend the time creating joins that have no effect, Auto Join Pro leaves them alone. Anything whose structural material is not steel is treated normally, including elements whose material has not been set.

Clash Check is not affected: a steel beam running through a concrete slab is still reported.

What the tool does not touch

Joins that already exist

Auto Join Pro adds joins. It does not remove one, and it does not change the cut direction of a join that is already there.

This matters more than it first appears. Revit joins some elements automatically as you model — a structural floor, for example, cuts what it meets as soon as it is created — and it does so using its own internal order, which is not necessarily yours. Those joins, and any you made by hand, keep the direction they were given. Auto Join Pro brings everything that is still unjoined up to your rule; it does not re-arbitrate what is already settled.

If the cut order on an existing join is wrong for your purposes, Revit's own Switch Join Order command will change it.

Elements that only touch

The tool joins pairs whose solids genuinely overlap, because overlapping volume is what a schedule counts twice. Two elements that share a face, with no overlapping volume, have nothing to resolve, so they are left alone and a result of No changes can be perfectly correct.

If you want those elements joined so that the line between them disappears in a drawing, use Revit's own Join Geometry command for that.

Before a large batch

When a run would carry out a large number of operations, the tool stops and shows you the exact count before it changes anything, so you can save your model, run a smaller scope, or go ahead.

At that moment nothing has been modified yet — the scan is read-only — so cancelling costs you nothing. Once you continue, Revit will not respond until the run finishes, which on a large model can take a while.

Recommended practice

This changes your quantities

Joining changes how Revit assigns shared volume between elements. That is what joining is for — it removes the double-counting caused by overlapping solids. But it means the numbers in your schedules, and in any quantity take-off built on them, will be different afterwards.

This is expected behaviour, not a defect. Run the tool on a copy of the model first, note your schedule quantities before and after, and confirm the change is in the direction you expect. Auto Join Pro automates a repetitive operation consistently; it does not verify that the outcome is correct for your project.

The status line

When a run finishes, the status line lists only the things that actually happened, separated by ·, with the elapsed time last. For example:

74 joined · 16 reordered · 0.66s

Its colour tells you whether you need to do anything: green means the run completed with nothing outstanding, red means something needs your attention, and orange means the tool is busy or the run was cancelled.

What "reordered" means

This is the part worth reading once.

When Revit joins two elements it decides for itself which one cuts the other. For some pairs it has a fixed rule — a floor cuts a column, for instance, whichever way round you ask — and for others it simply follows the order the request was made in.

reordered counts the joins where Revit's own choice did not match your priority list, so the tool switched it. They are part of the joined count, not additional to it: 74 joined · 16 reordered means 74 joins were created, and 16 of those 74 needed correcting.

A high number is not a problem. It simply means Revit's defaults differ from your convention in a lot of places — which is the whole reason for setting a priority list. A count of zero means Revit happened to agree with you everywhere.

Result parts

PartWhat it means
N joinedNew joins the tool created.
N reorderedHow many of those joins had to be switched to match your priority list. See above.
N skippedOperations Revit would not accept. See the next section.
No changesNothing within the scope needed joining. Everything was either already joined, or not actually overlapping.
N clashes · M elementsClash Check only. M elements are involved in N overlapping pairs, and are now selected in the model.
No clashesClash Check only. No unjoined overlaps were found within the scope.

Other messages

MessageWhat it means
ReadyIdle, waiting for you to press Start Process.
Working — Revit won't respond
Scanning — Revit won't respond
Running. Revit stays busy until it finishes.
CanceledYou cancelled element selection, finished without picking anything, or declined the confirmation before a large batch. Nothing was changed.
Open a project first.No project is open. The window stays open when you close a project — reopen one and try again.
Not available in the Family Editor.The active document is a family. Switch to a project.
Active View cannot be used here.The current view is a schedule, sheet or drafting view. Switch views, or use Project or Selection scope.
Please select at least one category.The priority list is empty. Move at least one category into it.
Revit is busy, please try again.Revit could not accept the request, usually because another command is active. Finish or cancel it first.
Error: …Something unexpected. Please send us the exact wording.

If an operation is skipped

This is uncommon, but worth knowing about.

A dimension, or anything else that references the geometry, is attached to a particular face. Most of the time a join only moves that face, and Revit quietly re-attaches the reference. Occasionally a join removes the face altogether, leaving nothing to re-attach to, and Revit refuses the change.

Rather than stopping the batch, Auto Join Pro skips that operation and carries on. When the run finishes:

Nothing is ever deleted. To resolve it, look at what is selected — usually moving or deleting the dimension is enough — and run the tool again.

Undo

However many passes a run takes internally, the whole thing is a single undo step. One Ctrl+Z restores the model to the state it was in before you pressed Start Process. In Revit's undo list it appears as Auto Join Pro: Batch Join.

Limitations

Uninstalling

Close Revit, then use Windows Settings → Apps → Installed apps, select Auto Join Pro and choose Uninstall. You can also remove it from the Autodesk App Manager. Uninstalling removes the bundle folder; your Revit models are not affected.

Auto Join Pro does not write settings to your file system or to the Windows registry, so nothing is left behind.

Support

Email cyfang.studio@gmail.com. We are based in Taiwan (UTC+8) and will get back to you as soon as we can.

When reporting a problem, please include your Revit version and build number, the version of Auto Join Pro, what you had selected, what you expected, and the exact wording of any message. Please do not send project files containing confidential or client information — a cut-down sample that reproduces the problem is usually more useful.

Version history

1.0.0 — First public release. Supports Revit 2025, 2026 and 2027.