01 / 21

Project
Parameters

Learn how to create and bind project parameters to element categories for consistent, project-wide data tracking in Autodesk Revit.

Autodesk Revit

What Is a Parameter?

In Revit, a parameter is a named field that stores a single piece of data about an element: a dimension, a text label, a yes/no flag, or a material reference. Every wall, door, room, and sheet already carries dozens of built-in parameters that Revit uses internally.

The Three Parameter Types

Built-in
Pre-defined by Revit. Cannot be renamed or deleted. Examples: Width, Height, Level.
Project
User-created, stored in the .rvt file. Bound to categories for project-wide data tracking.
Shared
Defined in an external .txt file. Can appear in tags, schedules, and be shared across projects.

Why Project Parameters Matter

Revit's built-in parameters cover geometry and system data, but real-world projects need custom metadata: cost codes, installation phases, warranty dates, fire ratings, and more. Project parameters let you attach this data directly to elements so it flows into schedules and filters.

Scheduling
Custom parameters appear as schedulable fields, enabling quantity takeoffs and data exports.
Filtering
Use parameter values in view filters to color-code or hide elements by phase, status, or trade.
Consistency
One parameter definition applied to a category ensures every element in that category carries the field.

How Parameters Bind to Categories

Project Parameter Category Binding Walls Doors Windows W-01 W-02 D-01 D-02 WN-01 WN-02

The Fundamental Rule

Miss any one of these four and the parameter either won't appear where you need it or will store data in the wrong scope. The next slides walk through each property.

Instance vs. Type Parameters

Instance
Each placed element gets its own value. Example: a specific door's installation date.
Type
All elements of the same family type share one value. Example: a door type's fire rating.
Instance Parameter Install Date Door D-01 2024-03-15 Door D-02 2024-06-01 Different values per element Type Parameter Fire Rating Door D-01 60 min Door D-02 60 min Same value for all of that type

Project vs. Shared Parameters

Project Parameter Shared Parameter
Storage Inside the .rvt file External .txt file
Taggable No Yes
Schedulable Yes Yes
Cross-project No Yes
Setup Speed Fast Moderate
Best For Quick, single-project data Tags, multi-project standards

Choosing a Data Type

When you create a project parameter, Revit asks for a discipline and a type of parameter. The discipline (Common, Structural, Electrical, etc.) filters the list of available data types. Here are the most frequently used:

Text
Free-form string. Use for notes, codes, phase labels.
Integer
Whole numbers. Use for counts, sequence numbers.
Yes/No
Boolean checkbox. Use for flags like "Is Demolished".
Length
Dimensional value. Revit respects project units and converts automatically.

How to Create a Project Parameter

1
Open the dialog: Go to Manage tab > Settings panel > Project Parameters.
2
Click Add: This opens the Parameter Properties dialog.
3
Select "Project parameter" (not Shared parameter) at the top of the dialog.
4
Name it: Enter a clear, descriptive name (e.g., "Cost Code").
5
Choose discipline and data type: Pick Common > Text, or the appropriate combination.
6
Group under: Select a parameter group (e.g., "Identity Data") for where it appears in Properties.
7
Choose Instance or Type and check the categories to bind (Walls, Doors, etc.).
8
Click OK: The parameter now appears in the Properties palette for every element in those categories.

Example 1: Fire Rating

Scenario: Your firm needs to track fire ratings for all walls and doors in a hospital project. This value is the same for every instance of a given family type.

Fire Rating Type : Text : Common Walls Doors Basic Wall "60 min" Curtain Wall "0 min" Single Flush "60 min" Double Flush "90 min"

Example 2: Installation Date

Scenario: A construction manager wants each placed mechanical unit to record the actual date it was installed on-site. Every unit may be installed on a different day.

1
Name: "Installation Date"
2
Data type: Common > Text (Revit has no native date type, so text is standard practice)
3
Scope: Instance (each unit has its own date)
4
Categories: Mechanical Equipment
5
Group under: Identity Data

Example 3: Phase Code in a Schedule

Scenario: A project manager needs to assign a construction phase code ("PH-1", "PH-2", "PH-3") to every structural column, then generate a schedule that groups columns by phase.

Mark Phase Code Level C-01 PH-1 Level 1 C-02 PH-1 Level 1 C-03 PH-2 Level 2 C-04 PH-3 Level 3 Schedulable

Where Parameters Appear

Project Parameter Properties Palette Schedules Fields list View Filters Filter by value Tags ✕ NOT available

Common Mistakes

✕ Wrong Scope
Choosing Type when values should differ per element (e.g., installation dates). Results in all instances sharing one value.
✕ Missing Categories
Forgetting to check a category in the binding dialog. The parameter silently does not appear on those elements.
✕ Expecting Tags
Creating a project parameter and then trying to tag it. Project parameters are not taggable: use shared parameters for tags.

Summary Reference

Property What to Decide Example
Name Clear, descriptive label "Cost Code"
Discipline Common, Structural, HVAC, etc. Common
Data Type Text, Integer, Yes/No, Length Text
Scope Instance or Type Instance
Categories Which element types receive it Walls, Doors
Group Where it appears in Properties Identity Data

Question 1 of 5

Where do you access the Project Parameters dialog in Revit?

Question 2 of 5

A project parameter is NOT available in which of the following?

Question 3 of 5

You need every individual door instance to record its own delivery date. Which scope should you choose?

Question 4 of 5

After creating a project parameter as an Instance parameter, you realize it should have been a Type parameter. What must you do?

Question 5 of 5

Which of the following best describes the difference between a project parameter and a shared parameter?