Shared Parameters (Revit)

🔗 Related Concepts

Deepen your understanding with these related topics:

Definition

A shared parameter is defined in a shared-parameter file (.txt) external to the family or project. Both the family and the project (or another family) reference the same parameter GUID. Schedules can tag and report the same parameter across categories because all the families share the GUID.

Project parameters can be either non-shared (cannot be scheduled across categories) or shared (recommended for almost every project-level data attribute).

Why it matters

Without shared parameters, multi-discipline schedules — equipment lists, fire-rating reports, material inventories — cannot be produced because the parameters in different families are technically different parameters.

Technical Deep Dive & Core Mechanics

A shared parameter is defined outside any project or family — in a plain-text .txt file — and identified by a GUID (globally unique identifier). Because the GUID is stable, the same parameter can be attached to multiple families and to the project, and they all refer to the same data field. This enables cross-family scheduling and tagging that is impossible with project-only or family-only parameters.

The shared parameter file has a simple structure: groups (logical containers) and parameters within each group (name, GUID, data type, description). The data type is fixed at creation — you cannot change a text parameter to a number after creation. Always define parameters with the most specific type needed (Length, Area, Integer, Yes/No) rather than Text, because typed parameters can be used in formulas.

The critical limitation: shared parameters appear in schedules and tags only if they are added to the project as a Project Parameter (Manage → Project Parameters → Add → Shared Parameter). A parameter can exist in a family but remain invisible in schedules if this project-level binding step is skipped.

Step-by-Step Professional Implementation

Setting up shared parameters for cross-family scheduling:

1. Create the shared parameter file: Manage → Shared Parameters → Create. Save the .txt file in a location accessible to all team members (typically a project server path, not a local drive).
2. Define groups and parameters: Click Edit, add a Group (e.g., "Project Data"), then add parameters within it (e.g., "Fire Rating" as Text, "Load Capacity" as Number). Document each parameter purpose — the file is permanent and shared.
3. Add to families: Open each family in the Family Editor → Create tab → Family Types → Add Parameter → Shared Parameter. Browse to the file, select the parameter, assign it to the correct parameter group in the family (e.g., Identity Data). Save and reload the family.
4. Bind to the project: In the project, Manage → Project Parameters → Add → Shared Parameter → select the same parameter from the same file. Assign it to the relevant category (Doors, Windows, etc.). Now it appears as a schedulable column.
5. Tag the parameter: Create an Annotation Family using a Label that references the shared parameter. Because it is shared, the tag works across all families that have the parameter bound, with no additional setup.

Advanced Troubleshooting & Error Diagnostics

Issues commonly encountered with Shared Parameters (Revit) in BIM production environments, with resolution procedures:

• Element not visible in expected views: Shared Parameters (Revit) exists in the model but doesn't appear in a particular view. Resolution: Check the view's visibility/graphics overrides for the element's category and subcategory. Verify that the view range (cut plane and depth) encompasses the element's elevation. Confirm the element's phase is included in the view's phase filter settings.
• Warnings accumulate after model modifications: Editing Shared Parameters (Revit) generates persistent warnings about overlapping elements or invalid joins. Resolution: Use the Review Warnings dialog to identify the specific issue. For join-related warnings, unjoin and rejoin the elements. For overlap warnings, use the Interference Check tool to visualize the conflict geometry and determine which element should be adjusted.
• Schedule values don't match element properties: Quantities or parameters for Shared Parameters (Revit) in schedules differ from the values shown in element properties. Resolution: Verify that the schedule is filtering to the correct phase and design option. Check whether the schedule field uses a calculated value (which may round differently) versus the raw parameter. For type parameters, confirm that the schedule is grouping by type correctly.

Cross-Discipline Collaboration & Handoff

In federated BIM projects, Shared Parameters (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 Shared Parameters (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

• Keeping the shared-parameter file on a single user's machine — others can't load families that reference it.
• Recreating a 'lost' shared parameter with the same name — different GUID, schedule columns silently mismatch.
• Confusing shared parameter (GUID-keyed) with global parameter (project-wide expressions).

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

Practical insights from BIM coordination and delivery projects involving Shared Parameters (Revit):

• Create a family loading log: Track which families are loaded and their sources. Uncontrolled family loading is a common cause of model bloat—each loaded family adds to project size even if no instances are placed.
• Use scope boxes for large projects: On projects larger than ~10,000 sq.m., scope boxes control view extents and prevent Shared Parameters (Revit) elements from appearing at incorrect scales in sheets.
• Document linked model protocols: When Shared Parameters (Revit) involves linked models, establish a written protocol covering model origin, shared coordinates, file naming, and update schedules.
• Save local backups before synchronization: Before syncing to the central model, save a local copy as a recovery point for unexpected changes to Shared Parameters (Revit).

Sources & further reading

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