AUTODESK REVIT • VIEWS AND DOCUMENTATION

Tags — Add tags and understand tag families

Master annotation tags to communicate design intent clearly in every Revit view.

Historical Context & Motivation

Before the advent of Building Information Modeling, architectural documentation relied on hand-drafted annotations — small callouts, labels, and symbols drawn directly onto sheets of vellum or Mylar. Every time a door schedule changed or a wall type was revised, drafters had to locate and update each annotation manually, a tedious process that introduced significant risk of human error. The shift to computer-aided design in the 1980s digitized these annotations, yet the underlying problem persisted: labels and the objects they described remained disconnected, existing as independent geometry rather than as linked data. Autodesk Revit, introduced in 2000, fundamentally changed this paradigm by treating every building element as a data-rich object residing in a single, coordinated model. Within this framework, tags emerged as the primary mechanism for extracting and displaying element parameters directly in views, ensuring that annotations always reflect the current state of the model.

Pre-1980s
Hand-Drafted Annotations
Architects drew labels, keynotes, and callout symbols by hand on each sheet. Revisions required erasing and redrawing every affected note, making consistency across large document sets extremely difficult to maintain.
1982
AutoCAD and 2D CAD
The release of AutoCAD digitized drafting, but annotations remained simple text objects with no inherent link to the geometry they described. Updating a door number in a plan still required a separate manual edit of every schedule and detail.
2000
Revit Launches BIM-Based Tags
Revit introduced parametric, model-aware tags that read data directly from building elements. Changing a wall type automatically updated every tag referencing that wall across all views — a revolutionary leap in documentation accuracy.
2004–2010
Tag Families Mature
Autodesk expanded the Family Editor to support customizable tag families, allowing firms to define their own graphic standards, parameter displays, and conditional labeling rules for diverse element categories.
2020s
Cloud Collaboration & Smart Tags
Modern Revit versions integrate with BIM 360 and Autodesk Construction Cloud, enabling real-time tag updates across distributed teams. Shared parameter tags now feed directly into cost estimation, energy analysis, and fabrication workflows.

The central question that tags answer in the BIM workflow is deceptively simple: How do we display the right information, in the right place, at the right time, without ever letting annotation drift out of sync with the model? Understanding how tags work — and how tag families are structured — is essential for producing professional construction documents that meet industry standards while preserving your design narrative.

Core Principles & Definitions

Tags in Revit are a specific type of annotation element — view-specific 2D symbols that reference and display parameter values stored in model elements. Unlike model elements such as walls or furniture, tags do not carry geometric data that appears in 3D; instead, they exist only in the views where they are placed. Every tag is an instance of a tag family, which is a template file (with the .rfa extension) that defines the graphic appearance, label content, and display logic of the annotation. Grasping the relationship between tags, tag families, and the elements they annotate is foundational to producing coordinated documentation in any Revit project.

1

Tag vs. Text Annotation

A tag reads live data from a model element's parameters (e.g., a door's fire rating). A text annotation is static text you type manually. Tags update automatically; text does not.
2

Category Binding

Each tag family is bound to exactly one Revit category (Doors, Walls, Rooms, Furniture, etc.). A Door Tag family can only tag elements in the Doors category. This ensures parameter compatibility and prevents mismatched annotations.
3

Labels & Parameters

Inside a tag family, a label is the text placeholder that pulls values from element parameters. Labels can display built-in parameters (like Type Mark) or shared parameters you define for custom data.
4

Tag Families (.rfa)

A tag family is an .rfa file created or edited in the Family Editor. It defines the tag's shape (circle, rectangle, leader line, etc.), text formatting, and which parameter(s) appear. Firms maintain libraries of custom tag families matching their graphic standards.
5

View-Specific Behavior

Tags are view-specific annotations. A tag placed in a floor plan does not appear in a section or elevation unless you tag the same element again in that view. This gives you full control over documentation density per sheet.
KEY TAKEAWAY
Think of a tag family as a picture frame with a transparent window. The frame is the graphic border you design — its shape, line weight, and font — while the transparent window is the label that shows whatever content sits behind it, namely the live parameter value of the element it frames. Swap out the element, and the displayed information changes instantly. Swap out the frame (load a different tag family), and the visual style changes while the data link remains intact.

Visual Explanation — How Tags Connect to Elements

The diagram illustrates the three-part relationship: the model element (left) stores parameter data such as Type Mark and Fire Rating. The tag family (right) defines which parameter to display and how to style it. The result in view (bottom) is the visible annotation — here, a circled door number D-01.

As shown above, the tag acts as a conduit between the model's stored data and what appears on a printed or exported sheet. This linkage is what makes BIM documentation fundamentally different from CAD drafting: the annotation is never an independent object but rather a live viewport into the element's metadata. When you change the door type from D-01 to D-02 in the model, every tag referencing that element across every view updates simultaneously. This principle — often called single source of truth — is the conceptual backbone of all Revit tagging workflows and is what eliminates the coordination errors that plagued traditional documentation methods.

How Tags Work — The Mechanism in Detail

Placing Tags in a View

Adding a tag to a Revit view is a straightforward process, but understanding each step clarifies how the software resolves which tag family to use and which parameter to display. When you invoke the Tag by Category command (found under the Annotate tab, or via the keyboard shortcut TG), Revit enters a placement mode that is category-aware. As you hover over elements in the view, the cursor snaps to recognizable categories — Walls, Doors, Windows, Furniture — and Revit automatically selects the loaded tag family that matches the element's category. If no matching tag family is loaded in the project, Revit prompts you to load one from your library.

Tag Options Bar Settings

Before clicking to place, the Options Bar at the top of the canvas offers several critical settings. The Leader checkbox determines whether a line connects the tag to the element, which is especially useful when an element is partially occluded or distant from the annotation zone. You can also toggle Orientation between horizontal and vertical, and choose whether the tag attaches to the element's centerpoint or follows the cursor for free placement. For room tags and area tags, an additional Tag on Placement toggle automatically tags elements the moment you create them, streamlining the documentation of repetitive spatial layouts.

Tag All Not Tagged

For large plans with dozens or hundreds of elements, Revit offers the Tag All Not Tagged command (Annotate tab → Tag All). This batch operation scans the active view for all elements of one or more selected categories that currently lack a tag, and places tags on every untagged instance simultaneously. The dialog allows you to choose which tag family to apply per category, whether to include leader lines, and whether the tag orientation should be horizontal. This command is a major productivity tool, but its results often require manual adjustment to avoid overlapping or poorly positioned annotations — a process that, in a visual arts context, mirrors the compositional fine-tuning you would perform when arranging labels in an exhibition layout.

Inside the Family Editor — Building a Tag Family

Creating or modifying a tag family requires working in the Family Editor, Revit's dedicated environment for authoring component templates. You begin by selecting a tag family template from Revit's default library — for example, Generic Tag.rft or Door Tag.rft. The template pre-assigns the correct annotation category. Inside the editor, you draw 2D geometry (lines, arcs, filled regions) to define the tag's graphic border, then insert a Label element — the dynamic text placeholder that maps to one or more element parameters. You configure the label's font, size, justification, and which parameters it displays. When finished, you save the family as an .rfa file and load it into your project.

💡 Shared Parameters
If you need a tag to display a custom parameter that doesn't exist in Revit's built-in set — say, an artwork accession number for a gallery installation — you must create a shared parameter. Shared parameters are defined in an external .txt file and can be added to both the model element families and the tag families, ensuring the data path connects seamlessly from model to annotation.

Tag Family Classification & Anatomy

Revit ships with a default library of tag families organized by element category. Understanding this classification system, and knowing how to customize or replace default tags with your own, is essential for any firm that wants to maintain a consistent visual identity across its documents. The following diagram breaks down the anatomy of a tag family and shows how different tag types relate to the Revit category hierarchy.

This hierarchy diagram shows how a Revit project contains multiple tag family categories (Door Tags, Room Tags, Wall Tags, etc.), each of which can hold several family variants. The lower panel dissects the four core components of any tag family: graphic border, label, visibility rules, and font settings.
Common tag categories and their typical use in visual arts and exhibition design contexts
Tag CategoryTypical Parameters DisplayedCommon Use in Visual Arts Contexts
Door TagType Mark, Fire Rating, Frame MaterialGallery entry/exit labeling, accessibility notations
Room TagRoom Name, Room Number, Area, DepartmentExhibition hall naming, studio/classroom identification
Wall TagWall Type, Assembly Description, Fire RatingPartition types in gallery renovations, acoustic wall specs
Window TagType Mark, Sill Height, Width × HeightDaylighting studies for studios and exhibition lighting
Generic TagAny shared parameter you assignCustom artwork labels, installation hardware callouts

Worked Example — Creating and Placing a Custom Door Tag

In this worked example, imagine you are documenting a contemporary art gallery. The gallery has twenty doors, and each must be tagged with both a type mark and a fire rating inside a rounded rectangular border, matching your firm's graphic standards. We will walk through creating the custom tag family and placing it in a floor plan view.

Custom Door Tag — From Family Editor to Floor Plan
1
Step 1 — Open the Family Editor with the Correct TemplateGo to File → New → Family. In the template browser, navigate to Annotations and select Door Tag.rft. This template automatically assigns the family to the Door Tags annotation category, ensuring it can only be placed on Door elements.
A blank annotation family canvas opens with reference planes at the origin.
2
Step 2 — Draw the Graphic BorderUsing the Create tab → Line and Arc tools, draw a rounded rectangle approximately 12 mm wide × 6 mm tall (in annotation scale). Set the line subcategory to Medium Lines so the border prints at an appropriate weight. Center the shape on the intersection of the reference planes.
A centered rounded rectangle defines the tag's visible outline.
3
Step 3 — Insert the LabelGo to Create tab → Label. Click inside the rounded rectangle to place the label. In the Edit Label dialog, add two parameters: Type Mark (first row) and Fire Rating (second row). Insert a line break between them. Set the font to Arial Narrow, size 2.0 mm, bold for the Type Mark and regular for the Fire Rating.
The label shows placeholder text: <Type Mark> on the first line and <Fire Rating> on the second.
4
Step 4 — Save and Load into the ProjectSave the family as Door Tag - Gallery Standard.rfa in your firm's family library. Then click Load into Project on the Family Editor ribbon. If prompted about overwriting an existing family, choose to overwrite if you want this to replace the default door tag.
The custom tag family is now available in the project's loaded families.
5
Step 5 — Place Tags Using 'Tag by Category'Return to your gallery floor plan view. Go to Annotate → Tag by Category (shortcut TG). In the Type Selector, confirm that Door Tag - Gallery Standard is selected. Enable the Leader checkbox in the Options Bar. Click on each door in the plan — the tag appears showing the live Type Mark and Fire Rating from each door instance.
All doors display custom tags reading, for example, D-01 / 90 min inside a rounded rectangle with a leader line.
6
Step 6 — Batch Tag Remaining DoorsTo catch any doors you missed, go to Annotate → Tag All Not Tagged. In the dialog, check only the Doors category, select your custom tag family, and click OK. Review the view and adjust any overlapping tags by dragging them or bending the leader elbows.
Every door in the active view is now tagged with the Gallery Standard tag. The documentation is complete and coordinated.

Tags vs. Other Annotation Methods — Strengths & Limitations

Tags are not the only way to annotate elements in Revit. Understanding how they compare to text notes, keynotes, and schedules helps you decide which tool is appropriate for each documentation scenario. The following table provides a systematic comparison.

Comparison of Revit annotation methods
FeatureTagsText NotesKeynotes
Data SourceLive element parametersManually typed static textExternal keynote table (.txt file)
Auto-UpdateYes — changes propagate automaticallyNo — requires manual editingYes — if keynote table is updated
CustomizationFamily Editor (graphic + parameter control)Font, size, justification onlyLimited — standard keynote appearance
Best ForIdentifying specific elements (doors, rooms, walls)General notes, disclaimers, clarificationsMaterial callouts, specification references
LimitationRequires matching tag family loaded per categoryNo model connection — prone to coordination errorsDepends on external file management
KEY TAKEAWAY
Choose tags whenever the information you need to display already lives inside the model as a parameter — they are the only annotation type that guarantees a live, unbreakable link to element data. Use text notes for freeform commentary that doesn't correspond to any element property. Use keynotes when you need to reference a centralized specification database. Think of tags as your model's name badges, text notes as sticky notes, and keynotes as index cards pointing to a filing cabinet.

Connection to Advanced Workflows

Once you are comfortable creating and placing basic tags, a range of advanced workflows opens up. These extend the tagging concept into parametric design, automation, and interoperability contexts that are increasingly relevant in professional practice and in the intersection of visual arts with architectural technology.

Progression from basic to advanced tagging workflows
Basic Tagging ConceptAdvanced Extension
Single-parameter label (e.g., Type Mark)Multi-parameter labels with conditional formatting — show fire rating only if the value is not empty, using visibility-controlled nested labels
Manual tag placement with Tag by CategoryDynamo-driven batch tagging — use visual programming to place tags at precise offsets, filtered by parameter values, across dozens of views automatically
Standard built-in parametersShared parameter ecosystems — create custom parameters (e.g., artwork medium, exhibition title) shared between model families, tag families, and schedules for comprehensive data coordination
Static tag family appearanceType-driven tag families with multiple family types that switch graphic appearance (e.g., circular vs. rectangular border) based on context, controlled through the Type Selector
Tags visible only in placed viewView templates with tag filters — configure which tag categories appear per view template, ensuring consistent annotation visibility across document sets

For visual arts students working on exhibition design, installation documentation, or museum renovation projects, the advanced extension of shared parameter ecosystems is particularly powerful. By defining a shared parameter like Artwork_Accession_Number and embedding it in both your furniture families (representing display pedestals) and a custom Generic Tag family, you can tag every pedestal in a gallery floor plan with the accession number of the artwork it holds. That same parameter can appear in a schedule on your sheet set, creating a complete, coordinated exhibition inventory — a workflow that traditional 2D drafting could never achieve with comparable reliability.

Practice Problems

PROBLEM 1CONCEPTUAL
Explain the fundamental difference between a tag and a text note in Revit. Why does this distinction matter for maintaining accurate construction documents in a project with hundreds of annotated elements?
PROBLEM 2BASIC
You need to tag all windows in a floor plan view with their Type Mark. Describe the exact sequence of steps in Revit to accomplish this, including the ribbon tab, the command name, and the key Options Bar setting you should verify before clicking on elements.
PROBLEM 3INTERMEDIATE
You are creating a custom Room Tag family that displays the Room Name on the first line and the room's Area on the second line, with the area value rounded to one decimal place in square meters. Outline the steps you would take in the Family Editor, including which template to start from, how to configure the label, and how to control the number format.
PROBLEM 4APPLIED
You are documenting a university art gallery renovation with 40 rooms, 60 doors, and 25 custom display pedestals (modeled as Generic Model families). The client requires each pedestal to be tagged with a custom 'Artwork_ID' parameter that does not exist in Revit by default. Describe the complete workflow — from parameter creation to final tagged floor plan — including how shared parameters, model families, and tag families must be coordinated.
PROBLEM 5CRITICAL THINKING
A colleague argues that using Text Notes for all annotations is faster and more flexible than creating custom tag families, especially for one-off projects with tight deadlines. Construct a counterargument that addresses workflow efficiency, error prevention, downstream data use (schedules, exports), and the long-term value of a tag family library. Under what narrow circumstances, if any, might your colleague's approach be justified?

Lesson Summary

Tags are parametric annotation elements in Autodesk Revit that display live parameter data from model elements directly in views — ensuring that every label, callout, and identifier remains perfectly synchronized with the building model. Each tag is an instance of a tag family, an .rfa file created in the Family Editor that defines the tag's graphic border, label mapping, font settings, and visibility rules. Tags are category-bound — a Door Tag can only annotate Door elements — which prevents mismatched annotations and enforces data integrity across the document set.

Key commands include Tag by Category for individual placement and Tag All Not Tagged for batch annotation. Tags differ from text notes (static, unlinked) and keynotes (linked to an external table rather than element parameters). For visual arts applications — gallery design, exhibition documentation, museum renovations — custom shared parameters extend tags beyond standard building data to include project-specific metadata like artwork identifiers and installation specifications, making the Revit model a true single source of truth for both architectural and curatorial documentation.

Varsity Tutors • Autodesk Revit • Tags — Add tags and understand tag families