Revit Add-ons: AutoJoin Manager: Automates Revit’s Join Geometry and Unjoin Geometry Workflows

Executive Overview

AutoJoin Manager is a professional productivity add-in developed by DesignLab for Autodesk Revit. It automates Revit’s Join Geometry and Unjoin Geometry workflows across multiple element categories and gives users explicit control over cutting priority. Instead of joining intersecting elements one pair at a time—and then correcting join order where the wrong element cuts—the user creates an ordered list of categories, optionally narrows each category to chosen element types, and runs the operation across the model in one batch.

The add-in is primarily a model-cleanup and standards-enforcement utility. It is intended for architectural and structural teams that repeatedly coordinate walls, floors, columns, framing, ceilings, foundations, and other joinable categories. Its main advantage is not merely speed; it makes join precedence repeatable. A saved rule set can express a firm or project convention for which categories should cut others, reducing inconsistent results created by manual selection order.

How the Workflow Operates

Build the category list. Add the Revit categories that should participate in the operation. Published examples include structural columns, structural framing, walls, floors, ceilings, foundations, and other categories that Revit permits to be joined.
Set the cutting hierarchy. Arrange the categories in priority order. The category in the first row has the highest priority and is intended to act as the cutting element when it is joined to categories listed below it.
Refine by type when necessary. Any category row can be restricted to selected element types rather than applying to every type in that category. This allows different treatment for items such as particular wall, floor, framing, or column types.
Run Join or Unjoin. One command processes the configured categories in batch rather than requiring individual element-pair selections.
Monitor progress. A progress window reports processing status and percentage completion while Revit evaluates the model.
Review the outcome. A results report separates successful operations, skipped pairs, and failures, including reasons where available.
Reuse the setup. The priority list is automatically retained between sessions, avoiding repeated configuration when Revit or a project is reopened.

Core Capabilities

Priority-Controlled Join Geometry

Revit’s native join result can depend on the category combination and join order. AutoJoin Manager formalizes that behavior through an ordered hierarchy. If a project standard requires structural framing to cut walls, or columns to take precedence over floors, the hierarchy provides a repeatable rule rather than relying on each modeler to select the correct element first.

Batch Unjoin

The same category-and-type framework can be used to remove existing joins in bulk. This is useful before rebuilding relationships under a revised hierarchy, correcting legacy models with inconsistent joins, or preparing a controlled model-cleanup sequence.

Optional Type Filtering

Type filtering limits a category rule to specified Revit types. This is important where a broad category contains elements that should behave differently—for example, where only selected wall constructions, floor assemblies, or framing types should participate.

Large-Scale Processing

The Marketplace description positions the add-in for hundreds or thousands of element pairs. Revit processes the relationships in batches while the plugin reports progress. Actual duration will depend on model size, geometric complexity, category count, type filters, and the number of intersecting or nearby candidates.

Persistent Configuration

Settings are remembered between sessions. This supports repeatable execution but also creates a governance requirement: teams should confirm that the stored hierarchy is appropriate for the current project before running it.

Progress Tracking and Results Reporting

Real-time status: The processing window displays an accurate percentage indicator so users can follow long-running operations.
Successful joins or unjoins: Completed relationships are counted and summarized.
Skipped element pairs: Pairs that are too far apart or otherwise do not qualify are reported rather than silently presented as successful.
Failed operations: Errors are identified with the available reason, helping users isolate problematic geometry or unsupported relationships.
Operational transparency: The report provides a review point after bulk modification, which is essential because a large join operation may change many view graphics, material intersections, quantities, and model relationships at once.

The report should be treated as the beginning of QA rather than proof that every resulting join is correct. A technically successful join may still conflict with design intent, detailing standards, quantity requirements, or downstream model uses.

Deployment

Operating model: The add-in is described as fully offline; no Internet connection is required during use or activation.
Configuration persistence: Priority settings remain available across sessions on the machine, supporting repeatability but requiring local standards control.
Network and privacy implications: Offline operation reduces reliance on cloud availability and limits routine transmission of project geometry.

Practical BIM Assessment

Where It Adds Value

Model cleanup: Quickly standardizes large numbers of geometric joins that would otherwise require repetitive pair-by-pair work.
Consistent cutting precedence: Converts an informal modeling convention into an explicit category hierarchy.
Architectural–structural coordination: Helps regularize interfaces among walls, floors, columns, beams, foundations, and ceilings after coordination changes.
View and material cleanup: Correct joins can improve displayed intersections, remove unwanted lines, and produce cleaner sections, elevations, and details.
Quantity and layer behavior: Join order can affect how overlapping geometry is resolved. A controlled process can reduce arbitrary results, provided quantities are checked afterward.
Legacy-model remediation: Batch unjoin followed by a controlled rejoin can be useful when inherited models contain inconsistent or incorrectly ordered relationships.
Standards-driven workflows: Type-level filters provide more precision than category-only automation and can support project-specific exceptions.

Best-Fit Users and Projects

The add-in is most relevant to BIM coordinators, architects, structural modelers, VDC teams, and model-health specialists working with join-intensive Revit projects. Large concrete, steel, institutional, healthcare, commercial, and multidiscipline models are likely to see the greatest time savings. Small models with few intersections may not justify a model-wide operation.

Limitations and Governance Considerations

Joinability remains governed by Revit: The add-in automates native join and unjoin operations; it cannot create a valid relationship where Revit does not support the category pair or geometry condition.
Geometric proximity is not design intent: Intersecting elements are candidates for joining, but not every intersection should be joined. Movement joints, finish layers, embeds, openings, stacked assemblies, phasing conditions, and discipline ownership may require exceptions.
Cutting priority requires careful definition: A hierarchy that works for one project, material system, or level of development may be inappropriate elsewhere. The top-listed category should not automatically be assumed to cut every lower category.
Model-wide operations can affect performance: Evaluating large numbers of element pairs and creating many join relationships may increase processing, regeneration, opening, synchronization, or editing time.
Downstream effects require review: Joins can change visible edges, wall and floor cleanup, hosted-element behavior, material takeoffs, calculated quantities, analytical interpretation, and exported geometry.
Worksharing risk: Bulk changes may require ownership of many elements. Run the tool in a controlled worksharing state and coordinate with other users before synchronization.
Groups, design options, phases, links, and special elements: Public descriptions do not fully document behavior for every Revit context. These conditions should be tested rather than assumed.
Limited independent evidence: Public information is dominated by the publisher’s Marketplace description and demonstration.
No substitute for clash detection: Automating joins does not identify all spatial conflicts, coordinate linked disciplines, or replace formal interference-checking and issue-management workflows.

Recommended Evaluation Before Production Deployment

Confirm the current installer, supported Revit build, license scope, machine-transfer policy, refund terms, and update process with DesignLab.
Install the trial in a controlled test environment and verify compatibility with enterprise security, antivirus, and software-deployment standards.
Use a detached or copied model containing representative walls, floors, columns, beams, ceilings, foundations, groups, phases, design options, and worksets.
Document the intended hierarchy in plain language before configuring it—for example, which structural and architectural categories should cut others and where exceptions apply.
Test category-only rules first, then apply type filters to isolate assemblies that require different behavior.
Run Join on a limited scope and inspect plans, sections, elevations, details, material boundaries, hosted elements, and quantities.
Compare successful, skipped, and failed report entries with a manual sample to confirm that the result categories are understood.
Test Unjoin and rejoin sequences to determine whether the tool restores the intended priority without creating new graphical or data issues.
Measure processing time, model-size change, regeneration time, synchronization time, and editing responsiveness before and after a large run.
Test worksharing ownership and synchronization behavior with more than one user in a nonproduction environment.
Establish exclusions for elements, types, phases, design options, or worksets that should never be processed automatically.
Require model review and backup or version control before committing bulk geometry changes to a production central model.

Sources Consulted