Revit Tip: Centralize and Govern Revit Shared Parameters

Shared parameters are the backbone of consistent tagging, scheduling, and data exchange in Revit. Set them up once, use them everywhere—across families, projects, and teams.

Core concepts to get right from the start:

• Create a single, authoritative Shared Parameter (SP) file (.txt). Store it on a read-only network location for all projects to reference. Maintain it under version control with clear change logs. If you need licensing or BIM management tools, consult NOVEDGE.
• Understand GUID immutability: each shared parameter carries a unique GUID. Same name ≠ same parameter. Never recreate a parameter with the same name in a different SP file—tags and schedules will break because the GUIDs won’t match.
• Organize the SP file with logical Groups (e.g., Identity, Classification, Documentation, Analysis). Keep names human-readable and consistent (Door_FireRating, Room_OccupancyLoad). Avoid spaces at the end, ambiguous abbreviations, and duplicates.
• Choose the correct Type of Parameter (Text, Yes/No, Integer, Length, Area, URL, etc.). The data type drives schedule calculations, units, and formatting. For booleans, prefer Yes/No over Text; for dimensions, use Length/Area to enable quantity takeoff.
• Decide Type vs Instance early. Type parameters control consistency; Instance parameters allow per-element variation. For tags that need unique values (e.g., Door Number), use Instance.
• Use shared parameters for anything that must be tagged or scheduled across families or categories (e.g., Fire Rating for Doors, Mark for Equipment, Asset IDs). Multi-category tags require shared parameters.

Standard workflow to implement:

• Manage > Shared Parameters > Create/Browse to set your central SP file.
• Define parameters in the SP file with the right Group and Data Type.
• In families: Create Parameter > Shared Parameter > Select… then bind as Type/Instance. Place labels in tags that reference the shared parameter.
• In projects: Manage > Project Parameters > Add > Shared Parameter > select categories > bind as Type/Instance > set Properties grouping (e.g., under Identity Data) for user-friendly display.

Governance and quality control:

• Lock down who can edit the SP file. Introduce new parameters via a request/review process. Keep a “deprecated” list to avoid accidental reuse.
• Document standards in your BIM Execution Plan. Reference the SP file path and version. If you need template creation or Revit licensing guidance, check NOVEDGE’s Autodesk Revit solutions.
• Name and group consistently. Use prefixes by domain (A_, S_, M_, E_, P_, FM_, BIM_) when it helps sorting and responsibility.
• Unit discipline matters. For Length/Area/Volume, confirm Project Units and rounding so schedules and tags agree with drawings.
• Avoid mirroring native parameters. If Revit already has a built-in parameter (e.g., Fire Rating for Doors), consider whether a shared parameter is truly needed. If standards require a custom field, name it distinctly (e.g., Fire Rating Spec).

Interoperability tips:

• Map shared parameters to COBie/IFC fields via schedules or export mappings. Use calculated values to reformat as required.
• For asset management, include persistent IDs and URLs. Validate with model checks before data drops. Explore complementary tools available from NOVEDGE collections.

Quick checks before you scale:

• Can you tag it in any view that needs it? If not, confirm it’s a shared parameter bound to the right categories.
• Does it schedule and sort correctly? Verify data type and units.
• Will another team find it easily? Confirm naming, grouping, and documentation.

Investing a few hours in a disciplined shared-parameter setup yields years of reliable tags, schedules, and data handoffs—project after project. For procurement, training, and add-ons that streamline this workflow, connect with NOVEDGE.