Revit Naming Conventions

Consistent naming keeps models navigable and automatable. These conventions apply to all firm projects unless a project BEP specifies otherwise.

View Naming

Use the pattern: {Level} - {Discipline} - {Type}

Rules:

• Abbreviate disciplines to a fixed set: Arch, Struct, Mech, Elec, Plumb, FP, Coord.
• Spell out the view type: Floor Plan, Ceiling Plan, Section, Elevation, 3D View, Detail.
• Drafting views use: Detail - {Description} (no level prefix).

Sheet Naming

Use the pattern: {Number} - {Name}

• Sheet numbers follow the NCS or firm-specific discipline code: A101, S201, M301.
• The name should be title-case and concise: A101 - First Floor Plan, S201 - Foundation Plan.
• Do not duplicate the discipline in the name if the number already implies it.

Family Naming

Families follow: {Category}{Manufacturer or Type}{Description}_{Size}

Rules:

• Use underscores to separate segments, PascalCase within segments.
• Omit manufacturer for generic/in-house families.
• Include size only when multiple sizes exist as separate families.

Parameter Naming

• Shared parameters: PascalCase with no spaces - RoomDepartment, SheetIssueDate.
• Project parameters: match the shared parameter name when possible.
• Avoid abbreviations unless universally understood (HVAC, ID, URL).
• Prefix custom parameters with a firm code to avoid collisions: PV_CustomField.

Enforcement

Pyvoid's Conform Names tool can audit views and sheets against these patterns and batch-rename non-conforming elements.

Last updated: 2026-03-20