Understanding Revit Categories, Families, and Types

Revit is a database, not a drawing. Everything lives in a fixed hierarchy—Category → Family → Type → Instance—and almost every confusion new users hit comes from mixing those levels up. Get this straight and scheduling, visibility, and naming all click into place.

Category: Doors
├─ Family: Single-Flush
│  ├─ Type: 915 x 2134mm
│  │  ├─ Instance: door in Room 101
│  │  └─ Instance: door in Room 102
│  └─ Type: 800 x 2100mm
└─ Family: Double-Egress
   └─ Type: 1830 x 2134mm

Category

The top level. Categories are built into Revit—you cannot create or delete them. They control scheduling, cut/projection graphics, and Visibility/Graphics behavior. Two groups:

• Model categories — 3D physical elements (Walls, Doors, Furniture).
• Annotation categories — 2D documentation (Text Notes, Dimensions, Tags).

Rename Pro mirrors this split with separate Model and Annotation tabs in its Categories panel, so you build conventions for each independently. The annotation side is easy to forget but worth naming too: standardizing Text and Dimension type names (e.g., RP_Text_2-5mm_Arial, RP_Dim_Linear-3mm) stops the slow sprawl of near-identical annotation styles that bloat every dropdown.

Family

A family is a definition within a category that shares geometry and a parameter set. Three kinds, and the difference is practical:

Why it matters for naming: different family kinds expose different parameters. A Basic Wall (system family) has a Compound Structure parameter describing its layers; a Curtain Wall or a loaded family in the same Walls category does not. Rename Pro shows the Family group beside each category so you always know which parameter set you're naming against.

Type vs. Instance — The Distinction That Trips People Up

A Type is a specific variation (915 x 2134mm) shared by every instance of it. An Instance is one placed element, carrying its own instance parameters (Mark, Comments, Sill Height) on top of the type's.

The rule that matters for naming: only type-level and family-level data is consistent across every instance. Instance parameters vary element to element, so they can't drive a type name. Build names from type/family parameters only.

Two more common mix-ups:

• Type name ≠ Family name. Single-Flush is the family; 915 x 2134mm is the type. Rename Pro rewrites the type name.
• Type parameters change all instances. Edit a type's width and every placed instance updates—by design.

How to Tell a Type Parameter From an Instance Parameter

Quick check inside Revit: open an element's Properties palette and click Edit Type. Anything in the Type Properties dialog is a type parameter (safe to drive a name); anything that stays on the main Properties palette is an instance parameter (don't use it for type names). When you create a project or shared parameter, Revit asks "Type or Instance" at that moment—choose deliberately, because it decides where the value can be used later.

Why the Hierarchy Drives Good Names

A good name encodes position in the hierarchy:

In Rename Pro you pick the category in the Categories panel, pull type/family parameters from the Parameters panel, and assemble them in the Name Rules panel. For system families with layers, you can reach inside the compound structure to name by material build-up—see the Compound Name Rules dialog.

With the hierarchy clear, the next step is turning it into a written standard—see Best Practices for Revit Naming Conventions.