Annotation Families & Tags

Definition & Context

Annotation families in Revit are 2D view-specific elements that scale with the sheet rather than the model. They include tags (door tags, window tags, room tags), symbols (north arrows, section markers), detail components (steel sections, insulation hatching), and title blocks. Created in the Family Editor with dedicated annotation templates (.rft).

Tags pull parameter values from model elements via label parameters: a door tag displays the door's Mark, Width, Height, and Fire Rating by referencing Shared Parameters. Custom annotation families support: visibility controls, conditional formatting (Yes/No parameter toggles), nested shared families, and formula-driven label text. Annotation scaling is automatic per view scale when using annotative behavior.

Key concepts: label vs. text (labels link to parameters, text is static), masking regions (white-fill backgrounds), symbolic lines (view-dependent line work), and shared annotation families (usable in tags AND schedules).

Why It Matters

Annotation families are what make a Revit model read correctly on a printed sheet: because they scale with the sheet rather than the model, the same tag or symbol stays legible at any view scale. Tags that pull live parameters (Mark, Width, Height) also keep drawings coordinated — change a door in the model and its tag updates automatically.

Investing in good annotation families and title blocks pays off across every sheet in a set, since consistent, data-driven annotation is what turns a 3D model into a compliant, issuable drawing package.

Best Practices

• Use Shared Parameters (not Project Parameters) in annotation families so values appear in both tags and schedules
• Set annotation family category correctly (Generic Annotations, Detail Items, Tags) to control visibility filter behavior
• Build tag families with multiple label types: create variants for plan, elevation, and enlarged plan display
• Use Yes/No visibility parameters to create one family with optional detail levels instead of multiple separate families
• Test annotation families at multiple view scales (1:50, 1:100, 1:200) to verify readability before deploying to templates

Common Pitfalls

• Creating text-only tags instead of label-based tags — text doesn't update when model parameter values change
• Forgetting to load the Shared Parameter file before editing families that reference shared parameters
• Annotation families placed in wrong category won't appear in correct subcategory visibility toggles
• Nested annotation families lose their label connections if the host family's category doesn't support the nested category

References & Further Reading

• https://help.autodesk.com/view/RVT/2025/ENU/?guid=GUID-C0D103D6-E2EB-4C53-B5D3-42DC59B00F5F

Related Concepts

Explore more Revit topics in our Revit knowledge base, or browse the full terminology index.

For structured learning, see our Revit learning path.

Enterprise Production Implementation & GstarCAD 2027 Workflow

• Database Serialization & Binary Fidelity: Ensure all entities and symbol table records associated with Annotation Families & Tags are authored on standardized ISO 13567 layers rather than Layer 0 or Defpoints, and verify lossless round-trip persistence in native DWG (AC1032) format.