01 / 21

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.

Autodesk Revit

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:

Shared Parameters
Defined in an external .txt file. Can appear in schedules, tags, and across multiple projects and families.
Project Parameters
Defined inside a single project. Quick to create, but cannot be tagged or shared to other files.

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.

1
Tagging: Only shared parameters can be placed inside annotation tag families.
2
Multi-project consistency: Shared parameters use one source-of-truth file, keeping data definitions identical.
3
Speed: Project parameters are faster for one-off data that never leaves a single file.

How Shared Parameters Work

SharedParams.txt Family A (.rfa) Project (.rvt) Family B (.rfa) Schedule Tag Family One .txt file feeds all projects, families, schedules, and tags

How Project Parameters Work

Project File (.rvt) INTERNAL ONLY Walls Doors Schedule: ✓ Tag: ✕ Project parameters live and die with their project file

The Core Rule to Remember

Shared ✓ Schedules ✓ Tags ✓ Multi-project ✓ Family editor Project ✓ Schedules ✕ Tags ✕ Multi-project ✕ Family editor

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:

GROUP
Organizes related parameters (e.g., "Structural", "MEP Data", "Custom Tags").
GUID
A unique identifier ensuring the parameter is recognized across all files, even if renamed.
Data Type
Text, Integer, Number, Yes/No, Length, Area, URL, and more: determines what values are valid.

Creating a Shared Parameter: Step by Step

1
Open the Shared Parameters dialog: Manage tab → Shared Parameters. Point to your team's .txt file (or create one).
2
Create a group (if needed) to organize your parameter logically, e.g., "Fire Safety".
3
Add the parameter: Name it, choose a data type (Text, Yes/No, Length, etc.), and click OK.
4
Bind it to your project: Go to Manage → Project Parameters → Add, select "Shared parameter", pick your new parameter, and assign it to element categories.
5
Use in tags or families: Open the tag/family, add the same shared parameter by GUID. The data now flows between elements and annotations.

Creating a Project Parameter: Step by Step

1
Open Project Parameters: Manage tab → Project Parameters → Add.
2
Choose "Project parameter" (not shared). Name it and select a data type.
3
Assign categories: Check the element categories this parameter should apply to (e.g., Doors, Windows).
4
Choose Instance or Type: Instance = different per element; Type = same for all elements of that type.

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?

Door Fire Rating = 1HR Schedule ✓ Tag ✓ SHARED parameter

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.

Room Phase = 2 Schedule ✓ PROJECT parameter

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.

SharedParams.txt Mechanical.rvt Electrical.rvt Plumbing.rvt Same GUID → Same Parameter → Consistent Data Only shared parameters can guarantee cross-model identity

Common Mistakes to Avoid

✕ Multiple .txt Files
Using separate shared parameter files per user creates duplicate GUIDs and broken schedules. Always share one file.
✕ Tagging a Project Param
Trying to display a project parameter in a tag: it won't show. You must recreate it as shared and rebind.
✕ Overusing Shared Params
Making every parameter shared adds setup complexity. Use project parameters for internal-only data to keep things simple.

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?