Family Types — Distinguish system families, loadable families, and in-place families (conceptual)

Historical Context & Motivation

Before the rise of Building Information Modeling (BIM), architects and designers worked primarily in two-dimensional drafting environments. Software like AutoCAD represented buildings as collections of lines, arcs, and hatches — geometry without intrinsic intelligence. A wall was simply a pair of parallel lines; it carried no data about material, height, or structural role. This paradigm made coordination between disciplines cumbersome and error-prone, because changes in one drawing rarely propagated to related sheets. The conceptual breakthrough that BIM introduced was the idea that every element in a digital model should be an intelligent, parametric object — one that knows what it is, how it behaves, and how it relates to other objects. Autodesk Revit, first released commercially in 2002, was designed from the ground up around this principle, and the family became its fundamental unit of content.

The central question this lesson addresses is deceptively simple: Why does Revit need three different kinds of families, and how does choosing the right one affect your design workflow? The answer lies in the tension between standardization and creative freedom — a tension that visual arts students navigate constantly. System families enforce consistency for elements like walls and floors; loadable families provide portability for furniture, fixtures, and specialty components; and in-place families allow unique, one-off sculptural geometry. Understanding when and why to use each type is the foundation of fluent Revit authorship.

Core Principles & Definitions

In Revit, every element you place — a wall, a chair, a custom light fixture — belongs to a family. A family defines the element's geometry, its adjustable parameters, and its behavior within the model. Families are organized into categories (such as Walls, Doors, or Furniture) and contain one or more types — predefined variants that differ in size, material, or other parameters. When you place a type into the model, the result is an instance, a specific occurrence with its own location and instance-level properties. This hierarchy — Category → Family → Type → Instance — runs through every element in the project, but the family classification (system, loadable, or in-place) determines how you create, edit, store, and share it.

Visual Explanation — The Family Taxonomy

The tree structure in this diagram is not merely organizational; it reflects how Revit's internal database stores and retrieves element data. When you select an element in a view and examine its properties, you are navigating this hierarchy in reverse — from a specific instance up through its type, its family, and ultimately its category. Each level carries parameters that cascade downward: category-level settings (like line weight defaults) apply to all families in that category, type-level parameters (like material assignments) apply to all instances of that type, and instance-level parameters (like exact location or individual dimensions) are unique to the placed element. Understanding this cascade is crucial because it determines where you go to make a change and how broadly that change will propagate throughout your model.

How Each Family Type Works

System Families — The Built-In Infrastructure

System families are hardwired into Revit's project template. They represent building elements whose behavior is tightly governed by the software's parametric engine — elements like walls, floors, ceilings, roofs, stairs, and railings. You never "load" a system family from an external file; rather, every new project already contains a set of system family types defined in the project template. To create a new variation, you duplicate an existing type and adjust its parameters (for instance, changing a wall's layer structure or total thickness). Because system families are embedded in the project, you cannot save them as independent .rfa files — though you can transfer them between projects using the Transfer Project Standards command. System families obey category-specific rules: a wall always joins to other walls, a floor always has a structural boundary, a stair always generates a railing host.

Loadable Families — The Portable Components

Loadable families are the most versatile and numerous family type in Revit. They are authored in a dedicated Family Editor — a separate modeling environment accessed via File → New → Family. In the Family Editor, you build geometry using extrusions, blends, sweeps, and swept blends; you assign parameters that control dimensions, materials, and visibility; and you define connector points for hosted elements (such as a door's relationship to a wall). The resulting file carries the .rfa extension and can be loaded into any project. This portability is what makes loadable families ideal for content libraries: a furniture manufacturer can distribute an .rfa file of their conference table, and any architect worldwide can load it into their Revit model. Common loadable-family categories include doors, windows, furniture, casework, lighting fixtures, mechanical equipment, and generic models.

In-Place Families — The Unique Sculptures

In-place families occupy a special niche. Created via Architecture → Component → Model In-Place (or Structure → Component → Model In-Place), they open a modeling environment inside the active project. This means the geometry you create can reference project-specific elements — snapping to existing walls, aligning to levels, or conforming to site topography. The trade-off is significant: an in-place family is permanently bound to the project in which it was created. You cannot export it as an .rfa file, and you cannot place multiple instances across different projects without recreating it. Overusing in-place families also degrades model performance because Revit must recalculate their non-standard geometry with every view regeneration. For these reasons, best practice reserves in-place families for truly unique conditions — a custom-shaped canopy, an irregular ceiling recess, or a site-specific art installation — where no standard or loadable family can achieve the required form.

Detailed Breakdown — When to Use Each Type

Choosing the correct family type is not a purely technical decision; it has direct consequences for your design agility, file performance, and collaboration workflow. The table below summarizes the key attributes that distinguish the three types, offering a quick-reference framework for the decisions you will make repeatedly as you develop Revit models for studio projects and professional work.

It is worth noting that the boundary between these categories is occasionally blurred by Revit's own nomenclature. For example, structural columns are loadable families, whereas architectural columns started as system families in earlier versions but are now often modeled as loadable families in practice. Similarly, curtain wall panels can be either system-defined or replaced with loadable families for custom panel designs. These edge cases reinforce the importance of understanding the underlying principles rather than memorizing a fixed list.

Worked Example — Selecting the Right Family Type

Suppose you are developing a Revit model for a contemporary art gallery. The project requires several distinct elements: a standard interior partition wall, a custom display case that will appear in multiple rooms, and a unique reception desk shaped to follow the building's curved entry wall. Walk through the decision process for each element to determine the appropriate family type.

Strengths, Limitations & Common Pitfalls

Connection to Advanced Concepts

The three-family taxonomy is the conceptual foundation upon which several advanced Revit topics are built. As you progress in BIM literacy, you will encounter shared parameters (which allow loadable families to contribute data to project-wide schedules), nested families (where one loadable family contains another, enabling modular assemblies), and adaptive components (a specialized loadable family type that can deform along complex surfaces — essential for parametric façades and freeform architecture). Understanding the family type distinction also prepares you for Dynamo scripting, where you programmatically generate and place family instances based on algorithmic logic.

For visual arts students in particular, the intersection of adaptive components and conceptual massing is especially relevant. These tools allow you to create parametric, pattern-based forms — think of Zaha Hadid's flowing façades or Toyo Ito's lattice structures — using loadable family logic rather than in-place family brute force. By mastering the distinction between family types now, you position yourself to use these advanced tools fluently later, bridging the gap between artistic intention and technical execution in BIM.

Practice Problems

Lesson Summary