Shared vs. Project
Parameters
Understand how Revit stores and shares custom data across families, schedules, and tags: the essential difference between shared and project parameters.
What Are Parameters in Revit?
Parameters are named data fields attached to Revit elements. Every door's width, every wall's fire rating, and every room's name is stored as a parameter. They are the backbone of Revit's Building Information Model.
Two Kinds of Custom Parameters
Revit's built-in parameters cover common data, but real projects need custom fields. Revit gives you two main tools for this:
Why Does This Distinction Matter?
Choosing the wrong parameter type can cause hours of rework. If your team needs to tag or schedule custom data across multiple projects, a project parameter simply will not work.
How Shared Parameters Work
How Project Parameters Work
The Core Rule to Remember
Key Distinctions at a Glance
| Feature | Shared Parameter | Project Parameter |
|---|---|---|
| Storage location | External .txt file | Inside .rvt file |
| GUID-based identity | ✓ Yes | ✕ No |
| Schedulable | ✓ Yes | ✓ Yes |
| Taggable | ✓ Yes | ✕ No |
| Usable in family editor | ✓ Yes | ✕ No |
| Setup complexity | More steps | Fewer steps |
| Cross-project consistency | ✓ Guaranteed | ✕ Not linked |
Inside the Shared Parameter File
The .txt file has a simple structure. Each line defines a parameter with a GUID, name, data type, and group. Here is what that looks like conceptually:
Creating a Shared Parameter: Step by Step
Creating a Project Parameter: Step by Step
Example 1: Fire Rating Tag
Scenario: Your firm needs every door and wall to display its fire rating in both schedules and annotation tags on floor plans. Which parameter type should you use?
Example 2: Phase Tracking
Scenario: A contractor wants to track which construction phase each room belongs to. The data only needs to show in a schedule for internal use: no tags, no export to other projects.
Example 3: Multi-Project Equipment ID
Scenario: An MEP firm has three linked Revit models (Mechanical, Electrical, Plumbing). Every piece of equipment needs a consistent Equipment ID field that all three models recognize and can schedule together.
Common Mistakes to Avoid
Summary: When to Use Each
| Use Case | Best Choice | Why |
|---|---|---|
| Tag annotation | Shared | Tags are separate family files |
| Schedule-only data | Either | Both types are schedulable |
| Linked-model coordination | Shared | GUID ensures identity across files |
| Quick internal tracking | Project | Faster setup, no file management |
| Family-level parameter | Shared | Only shared params enter the Family Editor |
| Office-wide standards | Shared | Central .txt ensures consistency |
Question 1 of 5
Which parameter type stores its definition in an external .txt file?
Question 2 of 5
You need a custom "Maintenance Code" field to appear in a door tag on your floor plan. Which parameter type should you use?
Question 3 of 5
What ensures that two shared parameters with the same name in different projects are treated as the same field?
Question 4 of 5
A project manager wants to track room cleaning status in a schedule for internal coordination only. No tags, no export. What is the simplest approach?
Question 5 of 5
Which of the following is a common mistake when managing shared parameters?