Families (Revit)

🔗 Related Concepts

Deepen your understanding with these related topics:

Definition

Revit families come in three categories: system families (built into Revit: walls, floors, roofs, stairs, ducts, pipes — type properties only, no .rfa file), loadable families (.rfa files loaded into a project: doors, windows, furniture, fixtures, structural connections, plumbing fixtures — fully parametric, can be shared), and in-place families (one-off geometry created inside the project for unique situations).

Each family has parameters (instance or type), reference planes, host behaviour (level-based, face-based, wall-hosted), and a category (which controls behaviour, filtering, and tagging).

Why it matters

Almost every Revit limitation traces back to a family-authoring decision. A door family without proper reference planes resists scheduling. A door family hosted to a face instead of a wall fails to relocate when the wall moves. Family discipline is what separates productive Revit from frustrating Revit.

Technical Deep Dive & Core Mechanics

Revit families divide into three fundamental categories. System families (walls, floors, roofs, stairs, ceilings) are defined within the project and cannot exist as external files — they are edited through Type Properties and duplicated with "Duplicate Type". Loadable families (doors, windows, furniture, structural columns, annotations) live as .rfa files, can be shared between projects, and are edited in the Family Editor. In-place families are unique geometry created directly in the project context — use sparingly because they bloat file size and cannot be reused.

Within loadable families, the distinction between Type parameters (shared by all instances of a type, e.g., nominal width) and Instance parameters (individual per placed element, e.g., sill height) directly governs scheduling and tagging. A parameter that users need to change without duplicating a type must be an Instance parameter.

Family template choice is permanent — a door template has host behavior baked in (cuts the host wall, manages the rough opening), while a furniture template does not. Choosing the wrong template and trying to work around it creates fragile workarounds. Match the template to the real-world behavior of the element.

Step-by-Step Professional Implementation

Creating and loading a custom loadable family:

1. Choose the right template: File → New → Family, select the template that matches the element behavior (e.g., Door.rft for wall-hosted openings, Generic Model.rft for non-hosted geometry, Structural Column.rft for base-point hosted structure). Template choice determines hosting rules and cannot be changed later.
2. Model with reference planes: Draw named reference planes (not model lines) as the skeleton. Lock geometry to these planes with the padlock icon. This ensures the family stretches correctly when type parameters change.
3. Add parameters: In Family Types dialog, add parameters and assign them to dimensions that are locked to reference planes. Mark as Instance if users need per-placement control; Type if the value defines the type.
4. Create multiple types: In Family Types, click New and enter values for each standard size (e.g., 800mm door, 900mm door, 1000mm door). Each size becomes a type in the project.
5. Load into project: Click Load into Project (or Load into Project and Close). Revit places the family and all its types in the project. Find it in the Properties palette or Project Browser under Families.

Advanced Troubleshooting & Error Diagnostics

Troubleshooting Families (Revit) in multi-user BIM coordination workflows:

• Synchronization failures with central model: Attempting to sync Families (Revit) changes produces "Can't find central model" or element ownership conflicts. Resolution: Verify network connectivity to the central file location. Check if another user holds editing permission on the affected workset. If the file server is unreachable, save the local changes as a backup before attempting to reconnect.
• IFC export produces generic proxy objects: Families (Revit) elements export to IFC as IfcBuildingElementProxy instead of their correct IFC class. Resolution: Review the IFC export mapping table and verify that Families (Revit)'s category maps to the appropriate IFC entity. Custom families may need their IFC Class parameter explicitly set in the family editor. Re-run the export after correcting the mapping.
• Linked model positions shift after reload: After updating a linked model, Families (Revit) elements in the link appear offset from their expected positions. Resolution: Verify that both the host and linked models use the same shared coordinate system. Check the link's positioning method (Auto - Origin to Origin vs. Auto - By Shared Coordinates). If coordinates were recently acquired or published, the link may need to be removed and reloaded with the updated coordinates.

Cross-Discipline Collaboration & Handoff

In federated BIM projects, Families (Revit) is an active element in multi-discipline model exchanges. During inter-platform handoff (for example, exporting to IFC for clash detection or converting native models for coordination):

• IFC Classification Mapping: Verify that Families (Revit) elements export with the correct IFC entity type and property sets. Unmapped or generic proxy exports lose their semantic identity, reducing the value of coordination reviews and quantity takeoffs.
• Shared Coordinates and Georeferencing: Confirm that all discipline models share the same project base point, survey point, and true north orientation. Misaligned shared coordinates produce multi-meter offsets in the federated environment, creating false clash results.
• Version and Phase Management: Stamp model exchanges with phase, revision, and LOD metadata. Coordinate on a common data environment (CDE) platform with clear status codes (work-in-progress, shared, published) to prevent teams from basing decisions on superseded model snapshots.

Common pitfalls

• Using in-place families when a loadable family would be reusable.
• Not setting type catalog data for families that come in 20+ size variants.
• Mixing host categories — a generic-model 'door' that doesn't trigger door-related behaviours.
• Constraining geometry to reference lines instead of reference planes (lines don't constrain inserts properly).

Relevant Revit FAQs

Direct answers from our technical editorial desk concerning related workflows.

🎓 Recommended Practice Lessons

Step-by-step practical exercises and certification-aligned paths chosen by our editors to master this concept:

Practical Workflow Tips

Lessons from BIM production workflows involving Families (Revit):

• Establish view templates before modeling begins: Create and assign view templates for plan, section, elevation, and 3D views at the project start. When working with Families (Revit), consistent view settings prevent confusion in review meetings.
• Address warnings as they appear: Each warning related to Families (Revit) (overlapping walls, duplicate instances, room boundary gaps) should be resolved promptly—warnings compound over time and degrade model performance.
• Use worksets strategically: Organize worksets around editing ownership rather than element categories. This minimizes synchronization conflicts when multiple team members work with Families (Revit).
• Test IFC export early in the project: Run a trial IFC export and validate the output in an IFC viewer during the first project week. Catching mapping issues with Families (Revit) early is far easier than correcting them after months of modeling.

Sources & further reading

• Autodesk Help & Technical Documentation portal · Autodesk Inc.
• Revit Product Support Portal · Autodesk Inc.