Workflows  ›  Auto-Tagging

Auto-Tagging

Workflow 1 phases Composed from Adelphos skill

Adelphos tags every room, space and MEP element across your views — placing tags with smart collision avoidance that evaluates multiple positions around each element and picks the clearest one, then untangles leaders so nothing overlaps.

Before you start

How it flows

You ask for tags — "tag all rooms on this plan" or "batch tag every view on Level 01".

flow screenshot 1

Adelphos checks which rooms, spaces and elements exist in the target views and whether any are already tagged. It won't double-tag anything.

For each untagged element, the smart placement engine evaluates multiple positions around it. Each candidate is scored for visibility, overlap with existing tags, proximity to other elements, and readability. The best position wins.

flow screenshot 3

Tags are placed in a single pass across the whole view. If leaders are needed (tag can't sit directly on the element), they're routed to avoid crossing other leaders — the untangling algorithm runs after placement to clean up any overlaps.

You can also set up auto-tag rules in JSON that run automatically when you open a view or at a scheduled interval. Rules specify which categories to tag, which tag family to use, and any exclusion filters.

Settings & options

Per-workflow toggles. Defined in the skill markdown so the page and the live behaviour stay in sync.

OptionDefaultWhat it does
Include linked rooms On Tag rooms from linked architectural models as well as host model rooms.
With leader Off Place tags with leader lines. When off, tags sit directly on the room centroid.
Tag type selection Auto if one, ask if multiple If one room tag family is loaded it is used automatically. If multiple are loaded the user picks.
Batch scope Current view Tag the current view only, or batch across all plan views in the project.