Revit Shared Parameters and Nested Families: A Complete BIM Workflow

A poorly structured family may look correct in a 3D view but fail when a project team attempts to schedule its properties, tag its components or exchange information. The underlying problem is often not geometry; it is the way family parameters are defined and connected.

1. Revit Parameter Types

Revit uses several parameter types to control geometry and store information. Instance parameters apply independently to each placed element, while type parameters are shared by all instances of the same family type.

Project parameters can be assigned to categories within a project. Family parameters control behavior inside a family but are not automatically available as shared identifiers for project-wide tagging and scheduling.

Shared parameters are definitions stored in an external shared parameter file and identified by unique GUIDs. Their stable identity allows the same parameter definition to be reused in multiple families and projects.

2. Why Shared Parameters Matter

Consider a door family containing fire rating, acoustic rating, manufacturer and asset identification data. If every family uses unrelated parameter definitions, schedules and tags become difficult to standardize.

A shared parameter definition provides a common identifier. When the same shared parameter is used consistently across families, project schedules can collect the corresponding values from different family types.

A shared parameter file should be managed carefully. Changing or recreating a parameter with a different GUID does not necessarily preserve its identity, even if its displayed name is identical.

3. Creating a Shared Parameter

Open Revit's shared parameter management interface and create or select a shared parameter file. Organize definitions into logical groups, such as architectural, structural, mechanical and asset information.

Define each parameter with an appropriate data type. For example, a fire rating may use text, an installation date may use a date-compatible parameter type where supported, and a physical dimension should use a suitable length parameter.

Add the shared parameter to the family through Family Types. Decide whether it should be an instance or type parameter according to the intended behavior. Load the family into a test project and confirm that its value can be scheduled or tagged as expected.

4. What Are Nested Families?

A nested family is a family placed inside another family. Instead of modeling every component as one large collection of geometry, a complex object can be assembled from smaller reusable components.

A window assembly, for example, may contain a frame family, glazing component, handles and opening elements. A lighting fixture may contain a housing, lamp and mounting component.

This modular approach improves reuse and makes complex family behavior easier to maintain. The main family controls the overall assembly, while nested components represent individual parts.

5. Associating Nested Family Parameters

A nested family's parameters can be associated with parameters in the host family. This creates a control layer through which users can change nested component dimensions or properties from the main family interface.

For example, a host family can expose a frame width parameter and associate it with the corresponding nested frame parameter. Changing the host parameter then drives the nested component, provided the family constraints and parameter types are compatible.

Parameter association is particularly useful for configurable products. It reduces the number of controls users must understand and keeps the main family interface organized.

6. Shared vs. Non-Shared Nested Families

Revit allows nested families to be configured as shared or non-shared. This setting affects how nested components are represented and selected in the project environment.

A shared nested family can be independently identified and scheduled in the project under appropriate category and schedule conditions. A non-shared nested component is generally treated as part of its host family for project-level selection and scheduling.

Use shared nested components when individual parts need independent tagging, selection or data reporting. Use non-shared components when they only contribute to the geometry or behavior of the host object.

7. A Practical Family Architecture

Door_Assembly.rfa
├── Frame_Nested.rfa
│   ├── Frame_Width
│   └── Frame_Depth
├── Leaf_Nested.rfa
│   ├── Leaf_Thickness
│   └── Material
└── Hardware_Nested.rfa
    ├── Handle_Type
    └── Hardware_Code

Host Parameters
├── Overall_Width
├── Overall_Height
└── Fire_Rating

The host family should expose only the parameters required by the project user. Internal construction parameters can remain inside nested components unless they are needed for scheduling or configuration.

8. Common Problems and Validation

Parameters do not appear in schedules

Confirm that the parameter is shared where required, assigned to the correct category and available in the relevant schedule context. Also check whether the nested family needs to be configured as shared.

Nested geometry does not respond

Check parameter associations, reference planes, dimensional constraints and formulas. A parameter can exist without controlling the intended geometry if the family constraints are incomplete.

Duplicate parameter definitions

Two parameters can have the same displayed name but different GUIDs. Maintain a controlled shared parameter file and avoid recreating definitions unnecessarily.

Family becomes difficult to maintain

Avoid exposing every nested parameter in the host family. Keep the interface focused, use clear naming conventions and test type changes as well as instance changes.

9. BIM Data Quality and Interoperability

Shared parameters are useful for maintaining consistent information across Revit projects, but they do not automatically guarantee correct IFC mapping or compliance with an information delivery specification.

Parameter names, data types, units, property-set mapping and export configuration should be checked against the project's information requirements. A parameter that appears correctly in a Revit schedule may still require explicit mapping to an IFC property.

For large BIM libraries, establish a naming convention, parameter owner, GUID registry and validation procedure. This turns family creation into a controlled data-management process rather than an isolated modeling task.

Frequently Asked Questions

What is the difference between shared and family parameters?

Family parameters control behavior inside a family. Shared parameters have unique GUID-based definitions and can be reused for project tagging and scheduling workflows.

Can nested Revit families be scheduled?

Shared nested families can be independently represented in suitable project schedules, subject to category and schedule configuration.

Should every nested family be shared?

No. Use shared nested families when independent identification or reporting is required. Non-shared nested families are often preferable for internal geometry and components that do not need separate project-level management.

Do shared parameters automatically map to IFC?

No. IFC property mapping and export settings must be configured and validated separately.