Setup, Rule Logic, and Batch Tagging

Before You Start

• Install the TagSuite add-in for the Revit version you are using.
• Open Revit and confirm the TagSuite command is available in the TiMBIM ribbon.
• Check that the tag families and types you plan to use are already loaded in the project.
• Review the active view or target view templates before running large batches.

Main Workflow

1. Open TagSuite from the TiMBIM ribbon.
2. Use the rule list to add, duplicate, enable, disable, or reorder rules.
3. For each rule, choose the tag mode, family, type, leader behavior, and placement anchor.
4. Add element filters to narrow the rule to the intended categories or parameter values.
5. Add view filters when a rule should only run in certain view types, disciplines, scales, or templates.
6. Review the shared apply settings for linked models, already tagged elements, and spacing defaults.
7. Apply to a small test scope first, then move to active-view or selected-view batches when the results look right.

Saving and Reusing Rules

TagSuite supports save, save as, import, and append actions for rule sets. TagSuite stores the default rules file locally as %AppData%\TiMBIM\TagSuite\TagSuiteRules.xml, and you can also save additional XML files wherever you want for team standards, project templates, or backup copies.

• Use Save to update your current local rules file.
• Use Save As to create a separate XML file for a project, team, or test setup.
• Use Import to replace the current rule list with rules from another file.
• Use Append when you want to add saved rules to the existing list without starting over.

Alignment Tools

After tags are placed, you can use TagSuite's alignment tools to improve readability. TagSuite includes shared spacing defaults for fast alignment and an advanced alignment command in the tag context menu.

• Select one or more tags in a view.
• Use the context menu option for Advanced Tag Alignment....
• Adjust spacing and leader behavior when a quick alignment pass is not enough.

Best Practices

• Start with a short ruleset and confirm the results before adding more exceptions.
• Use descriptive rule names so it is easy to maintain large saved rule libraries.
• Test new rules on a selection first before running them across multiple views.
• Keep the loaded tag families in the project aligned with the rules you plan to reuse.
• Save a separate XML file before large edits if you want an easy rollback point.

Frequently Asked Questions