BIM Teams: Avoid Broken Tags with Revit Shared Parameters & Service
A shared parameter is a parameter definition stored in an external text file so it can be used across multiple families and projects with one consistent identity. You need one whenever you tag elements from different categories or build a multi-category schedule, and whenever you want a parameter to survive a family transfer intact.
TL;DR:
Shared parameters are stored externally in text files, making them reusable across multiple families and projects, unlike project parameters which are stored within a single project file.
To avoid conflicts, team members should store the shared parameter file on a stable server and manage it centrally, preferably using an organization-wide Parameters Service.
Creating a shared parameter involves defining it in the shared file with clear naming, grouping, and proper data type, then adding it to families or projects through the Manage tab.
Converting a project parameter to a shared parameter requires defining it externally first and then recreating it as a shared parameter, as no direct conversion exists.
Proper governance, including version control, proper storage, and disciplined editing of the shared parameter file, is essential to prevent widespread issues across projects.
Table of Contents
What shared parameters are and how they differ from project parameters
Where the shared parameter file lives and modern alternatives
Create a shared parameter file, groups, and parameter definitions
Convert an existing project parameter into a shared parameter
Best practices and common pitfalls for managing shared parameters
S15Studio perspective: training to implement shared-parameter governance
What shared parameters are and how they differ from project parameters
A shared parameter lives outside any single family or project, in a text file that Revit reads from and writes to. Because the definition is external, the same parameter can appear in a door family, a wall type, and a project schedule without being recreated three different ways. A project parameter, by contrast, is created directly inside a project file and stays there: it cannot be shared with other projects or pulled into a family. A family parameter lives inside one family and cannot be scheduled across categories at all.
The practical difference shows up fast, as outlined in this construction project planning and scheduling sample, illustrating why consistent shared parameters matter in project workflows.
Project parameters work fine for single-category schedules and simple project-only data.
Family parameters work for formulas and type/instance logic inside one family.
Shared parameters are the only option when you need a tag that spans multiple categories or a schedule that pulls from more than one category, because tags and multi-category schedules require a shared parameter definition underneath.
If you are not sure which to pick, ask whether the data needs to leave this one project file. If the answer is yes, it has to be shared.
Where the shared parameter file lives and modern alternatives
The shared parameter file is a plain text file, and Revit can only point to one of them during a session. The file path is a session setting, so switching files midway through work risks losing track of which definitions a project actually used. Autodesk’s own guidance is blunt about this: Revit uses one shared parameter file at a time, and that file should sit on a stable server location rather than a personal drive, so every team member points to the same source.
Autodesk’s Parameters Service offers a cloud-based alternative to the local text file. It lets administrators manage parameter definitions centrally and lets designers pull them into Revit with an Add From Service action, which removes the single-file bottleneck entirely.
Local text file: simple, free, but fragile if stored inconsistently.
Network-hosted text file: better for teams, still vulnerable to accidental overwrites.
Parameters Service: centrally managed, supports searching and filtering parameters across an organization.
Centralizing storage, whether through a managed file or the service, is what prevents two offices from building incompatible versions of the same parameter.
Create a shared parameter file, groups, and parameter definitions
Building your own shared parameter file takes a few minutes once you know the path. Start from Manage, then Shared Parameters, then Create to make a new file or Browse to point at an existing one.
Open Manage > Shared Parameters and either create a new file or browse to your team’s existing one.
Under Groups, add a new group to organize related parameters, such as “Door Hardware” or “MEP Identity Data.”
Click New under Parameters, give it a clear name, assign a discipline, choose a data type (text, integer, length, yes/no, and so on), and add a tooltip description.
Save the file and confirm it sits in the shared network location your team actually uses.
Revit Help documents these exact dialog paths for creating files, groups, and parameters, along with the fields each dialog expects.
Pro Tip: Write the tooltip description the moment you create the parameter, not later. You will not remember what “DR_Type_02” meant six months from now.
Never open the .txt file in a text editor to add entries by hand. The format uses structured META, GROUP, and PARAM blocks that the Revit API reads programmatically, and a stray character can break the structure for every file that references it.
Add shared parameters to families and projects
Getting a shared parameter into a family and into a project are two separate steps, and the sequence matters.
For a family:
Open the family in the Family Editor.
Go to Modify tab > Properties panel > Family Types, then click New Parameter.
Select Shared parameter, click Select, and choose the definition from your file.
Set it as Type or Instance depending on whether the value should vary per placed instance.
Choose the parameter group so it sits logically in the Properties palette.
For a project:
Go to Manage > Project Parameters > Add.
Select Shared parameter, then Select to choose from the shared file.
Pick the categories that should carry the parameter.
Set Type or Instance, and choose a grouping for the Properties palette.
Revit’s documented workflow for adding shared project parameters follows this same Manage > Project Parameters path.
A few things trip people up here:
Type parameters apply to every instance of that type; Instance parameters can differ element by element.
A parameter assigned to the wrong categories will not appear where you expect in schedules.
Once added to categories, the parameter shows up as a column in multi-category schedules and becomes available to tag families built for those categories.
Get the category list wrong at this stage and you will be back in this dialog within the week.
Convert an existing project parameter into a shared parameter
There is no toggle in Revit that flips a project parameter into a shared one. The two live in different storage locations, so the only path is to recreate the definition properly: define it in the external shared parameter file, then add it through Project Parameters using the Shared parameter option instead of the plain Parameter option.
After mapping:
Confirm the categories selected match what the old project parameter covered.
Check whether Type or Instance behavior matches what your schedules expect.
Open a sample tag and a multi-category schedule to confirm the new shared version populates correctly before you delete the old parameter.
Skipping that last check is how teams end up with blank schedule columns two weeks into a project.
Best practices and common pitfalls for managing shared parameters
Most shared parameter problems trace back to one habit: editing the text file by hand. Manual edits frequently corrupt the file structure and can break parameter functionality across every model that references it, so additions should always go through the Revit UI or the API.
Keep one authoritative shared parameter file on a managed server, or move to Parameters Service with admin-controlled access.
Use consistent naming and grouping conventions so nobody creates a duplicate “Fire Rating” parameter under a different name.
Back up the file before major changes and keep a simple change log noting who added what and when.
When importing from Parameters Service, confirm category and type/instance settings: parameters without defaults require manual assignment during import.
Pro Tip: Store your shared parameter file in the same version-controlled folder as your templates, so a rollback on one restores the other.
Clear naming and centralized access solve most governance headaches before they start. Our guide to Revit project parameters covers the companion workflow for data that should stay local to one project.
S15Studio perspective: training to implement shared-parameter governance
Reading the dialog sequence is one thing, building the habit of checking categories and tooltips every single time is another. Hands-on practice catches the mistakes that documentation cannot, like forgetting to set Instance when a schedule needs instance-level data, or loading a stale shared parameter file into a new project.
Family editing, Project Parameters setup, and worksharing habits are exactly what our Worksharing Course and broader Revit training work through, with real project files rather than isolated examples. If you are mapping project parameters for the first time, our piece on Revit worksharing explains why this governance matters once more than one person touches the model.
What the documentation gets wrong about shared parameters
Most tutorials treat shared parameters as a one-time setup task: create the file, add a few parameters, move on. That framing undersells the ongoing discipline the system actually demands. A shared parameter file is a living document that an entire office depends on, and the real failure point is not the initial creation, it is six months later when someone opens the file on a laptop that was never pointed at the network copy.
The conventional advice to “just create a shared parameter file” skips the governance question entirely: who owns it, where does it live, and what happens when two people add conflicting definitions in the same week. Teams that treat the file like source code, with a single owner, a backup habit, and a change log, avoid the duplicate-parameter mess that plagues larger offices. Teams that treat it like a throwaway setup step end up with three versions of “Fire Rating” scattered across projects within a year.
If you take one thing from this, prioritize storage discipline over feature knowledge. Knowing which dialog box to click matters far less than knowing where the one authoritative file lives.
— Steve
How S15Studio courses help you apply this
Family editing and parameter mapping get easier once you have done them inside a real project rather than a sample file. The Revit Course Only walks through family creation, project parameter setup, and the worksharing habits this article covers, with lifetime access to the materials so you can revisit a step whenever a project calls for it.
FAQ
What is the difference between shared and project parameters?
A shared parameter is stored in an external file and can be reused across multiple families and projects, while a project parameter exists only inside one project file. Shared parameters are required for tags and multi-category schedules, which project parameters cannot support.
Where are shared parameters saved in Revit?
Shared parameters are saved in an external plain text file rather than inside the Revit project or family file. Revit uses one shared parameter file at a time, and that file’s location is set as a session preference under Manage, Shared Parameters.
How do I add a shared parameter to a family?
Open the family in the Family Editor, go to Family Types, and click New Parameter, then choose Shared parameter and select the definition from your shared file. From there you set whether it behaves as Type or Instance and assign it to a grouping, following the documented Revit workflow for parameter creation.
How do I turn a project parameter into a shared parameter in Revit?
There is no direct conversion option. You need to define the parameter in the shared parameter file first, then recreate it in Project Parameters using the Shared parameter option so it points to that external definition.
Sources
Recommended
Comments