Your cart is currently empty!
Good Revit naming conventions are the cheapest BIM standard you can adopt. They cost nothing, they make every schedule and browser list readable, and clients notice them at handover. This article gives a practical standard for families, types, views, sheets and worksets, with examples you can copy.

A model is read by many people: modelers, coordinators, the client’s facility team and the next consultant. When names follow one pattern:
Keep a few rules for every name in the project:
A family name should say what the object is, not who made it. A common pattern is:
Category_Description_Variant
Examples:
Door_Single-Flush_GlazedWindow_Casement_2-PanelColumn_Concrete_RectangularIf your client follows a classification such as Uniclass or OmniClass, put the classification code in a shared parameter instead of the name. Names stay short and the code is still schedulable.
Type names carry the size or the build-up that makes a type different. Put the defining dimensions in a fixed order:
Width x Height, for example 900x2100mm.200mm_Concrete or Int_100mm_Plasterboard.300x600mm or UB 305x165x40.For scan-to-BIM work this is where most clean-up happens: every measured opening becomes a new size, so type names drift fast. Renaming types by hand from their parameters is slow; Rename Types renames every type of a family from a pattern such as {Width}x{Height}mm in one step.
View names should tell the level, the purpose and the discipline:
Discipline_Level_Purpose
ARC_L01_Floor PlanARC_L01_Working (for modelers, not for sheets)STR_Section_A-AARC_3D_CoordinationKeep working views clearly separate from sheet views, for example with a "Working" suffix or a browser organization by view purpose. Then nobody edits the view that is placed on a sheet by mistake.
Sheet numbers usually follow the client’s document standard. When there is none, use discipline plus a running number: A-101, A-102, S-201. The sheet name says what is on it: Ground Floor Plan, Sections A and B.
Worksets are for splitting work and controlling visibility, not for categories. A short list is enough for most scan-to-BIM projects:
Point CloudShared Levels and GridsArchitecture_ExteriorArchitecture_InteriorStructureMEPLinksPutting the point cloud on its own workset lets the team close it when they don’t need it, which also keeps Revit faster (see point cloud slow in Revit).
Naming is one part of a good BIM standard. Read how LOD and LOA define what you deliver from a scan, or see the full Revit point cloud plugin workflow for modeling faster from laser scans.
ZetaBIM is a Revit plugin for scan-to-BIM teams. See the complete guide to the Revit point cloud plugin workflow. Download ZetaBIM to try it, browse more ZetaBIM tutorials, or watch the videos on the ZetaBIM YouTube channel.