Revit Family Naming Conventions & Shared Parameters Checklist

Family Naming Checklist

Lead with the manufacturer or brand so your products group together in the project browser.
Follow with product line, then product type, in that order – general to specific.
Keep separators consistent across the entire library; pick one and never mix.
Avoid version numbers, dates, and internal SKUs in the family name; those belong in parameters.
Never encode size in the family name when size is a type or parameter.
Keep names short enough to read in a truncated browser column.
Make the name guessable: someone who has seen one of your families should predict the next.

Type names should distinguish types on the attributes a specifier actually chooses between – size, configuration, finish.
Use consistent unit formatting, and the units your primary market uses.
Order attributes the same way in every type name across the library.
Match the type name to the model number where a real model number exists.

Maintain one shared parameter file for the whole library; never regenerate it per project.
Back it up and version it – regenerating it creates new GUIDs and silently breaks schedules downstream.
Group parameters logically (identity, dimensions, performance, sustainability, links).
Use the correct data type for every parameter; a length stored as text cannot be sorted or totaled.
Set instance versus type correctly – anything that varies per placement must be an instance parameter.
Reuse the standard built-in parameters where they exist instead of inventing duplicates.

Manufacturer name and model number.
Product URL and a link to the current cut sheet or specification.
Key dimensions, including required clearances.
Performance values relevant to the category (flow, acoustic, thermal, fire, load).
Finish or material options.
Certifications and sustainability data specifiers filter on.
Classification codes used in your market.