Revit Tip: Revit Shared Parameter Standards and Governance

Implement company-wide parameter standards to make data predictable, taggable, and exchange-ready across projects and families.

What “standard” means in Revit

• One master Shared Parameters file (.txt) that issues the only valid GUIDs.
• Clear naming, data types, and groups so parameters appear consistently in Properties, tags, and schedules.
• Governance: roles, change control, and documentation everyone follows.

Build a single source of truth

• Create a master Shared Parameters file on a controlled, read-only location (ACC Docs, network share, or PDM). Do not keep duplicates.
• Assign an owner (BIM Manager) and a simple request process for new/changed parameters. Log changes with versioning.
• Distribute read-only access to users and editors; keep a single editor copy under change control.
• Store a copy in your project and family templates for resilience, but never replace the master’s GUID source.

Naming, grouping, and data types

• Use concise, unambiguous names with discipline prefixes and purpose suffixes (e.g., A_FireRating_Type, M_Airflow_cfm).
• Choose the correct Parameter Type: Length, Number, Integer, Yes/No, Text, URL, Material, etc. Never store numeric values in Text.
• Group parameters where users expect them (e.g., Identity Data, Dimensions, IFC Parameters). Consistency beats preference.
• Document units, allowed values, and formatting in a “Parameter Dictionary” distributed with templates.

Shared vs Project vs Global

• Shared Parameters: Use when you must Tag, Schedule, or export to IFC/COBie across categories. They carry GUIDs that tools recognize.
• Project Parameters: Use for project-only metadata that never needs tagging or external exchange.
• Global Parameters: Use for design constraints and formulas; do not store deliverable data here.

Binding strategy and performance

• Bind Shared Parameters only to the categories that need them. Avoid “catch-all” bindings that clutter UIs.
• Prefer Type parameters for values that rarely vary (performance and data hygiene). Use Instance only when required.
• Yes/No toggles are efficient for visibility and options logic; avoid overly complex formula webs.

Template-first deployment

• Embed approved parameters in office project templates and family templates (.RTE/.RFT) so teams start compliant.
• Add QC schedules and view filters that highlight missing or invalid values (conditional formatting for blanks/zeros).
• Provide sample tags and legends so users can verify parameter behavior immediately.

Interoperability and classification

• Align with a classification system (OmniClass, UniClass, MasterFormat) via standardized parameters.
• Map parameters for IFC export using the official IFC exporter mapping. Keep an export mapping file under version control.
• If owners require COBie, define fields and validation rules in your Parameter Dictionary and QC schedules.

Migration and QA/QC

• Legacy families: Replace ad-hoc parameters with approved Shared Parameters. Data can be transferred via schedules or Dynamo.
• Avoid renaming parameters to “match” a standard—rename in UI changes the label, not the GUID. Replace to truly standardize.
• Audit regularly: a Dynamo script can report missing parameters, invalid types, and empty required fields across models.

Deliverables to publish

• Master Shared Parameters file (.txt) and readme.
• Parameter Dictionary (PDF/HTML) with naming, type, units, allowed values, and examples.
• QC schedules, view filters, and sample tags within templates.

Need help selecting add-ins or shaping your standards playbook? Consult the experts at NOVEDGE. If you’re building out new seats or templates, explore Autodesk Revit licensing and ecosystem options with NOVEDGE for guidance and procurement.