Revit Tip: Revit View Naming Convention: Discipline-ViewType-Level-Zone/Scope-Phase-Status-Purpose

Clear, consistent view names save clicks, reduce coordination errors, and accelerate onboarding. Use the convention below to make your Project Browser instantly navigable.

Core pattern (recommended):

Discipline-ViewType-Level-Zone/Scope-Phase-Status-Purpose

• Discipline: A, S, M, E, P, C (e.g., A)
• ViewType: FP, RCP, SEC, ELE, DET, 3D, SCD (schedule), LEG (legend)
• Level: L00, L01, L02, B01 (zero-pad for natural sort)
• Zone/Scope: CORE, EAST, ZN-A, GRID-A1–A5 (keep it short and consistent)
• Phase: EX, DEM, NEW
• Status: WIP, COORD, ISSUE
• Purpose: PERMIT, IFC, EXPORT, PRESENT, DETAILING

Examples:

• A-FP-L02-ZN-A-NEW-COORD-PERMIT
• A-RCP-L01-CORE-NEW-WIP-DETAILING
• S-SEC-L00-GRID-B1–B6-NEW-ISSUE-IFC
• 3D-COORD-ZN-B-OVERALL (prefix 3D for quick filtering)
• SCD-ROOM-FINISHES (use SCD- for schedules) | LEG-SYMBOLS (for legends)

Key practices:

• Zero-pad numbers (L01, L02…) to avoid L1/L10 sorting issues.
• Keep View Name browser-focused; use “Title on Sheet” for readable print titles.
• Avoid special characters that can break exports; stick to A–Z, 0–9, hyphens, and underscores.
• Standardize abbreviations in your BIM Execution Plan and post the list in your Revit template.

Set up Browser Organization (instant win):

• Create a project parameter for Views: Zone/Scope, Status, Purpose (Instance, Text).
• Manage > Browser Organization: Group by Discipline > View Type > Level, then sort by View Name.
• Add a second scheme for Production (e.g., group by Sheet Number for placed views).

Automation and QA:

• Use Dynamo to batch-rename: concatenate Discipline + View Type + Level + custom parameters into View Name.
• Protect “Title on Sheet” from bulk renames; ensure it remains human-friendly.
• Create view templates that write known values (Phase, Detail Level) and drive consistent naming inputs.
• Run periodic audits: filter for views with blank Zone/Scope or missing Level and correct in bulk.

Rollout tips:

• Embed the pattern in your project template and starter views.
• Train teams to use the same shortcodes; pin a cheat sheet in the template’s “Start Here” drafting view.
• Apply exceptions sparingly (e.g., LEG-, SCD-, 3D-) and document them.

Need add-ins, training, or Revit licenses to standardize this across your firm? Explore NOVEDGE for Autodesk Revit and ecosystem tools: NOVEDGE Revit solutions and NOVEDGE.com.

Pro tip: Bake the convention into scripts and templates once, then scale it across projects. The payoff is immediate—faster navigation, cleaner exports, and fewer coordination misses.

If you’re refreshing standards or building automation, connect with the experts at NOVEDGE for Revit training and add-ons.