Naming Conventions — Use naming conventions for views/sheets/worksets (conceptual)

Historical Context & Motivation

Before Building Information Modeling became an industry standard, architectural drawings were produced as isolated two-dimensional documents — each sheet a standalone artifact labeled by hand according to individual office customs. When Autodesk Revit emerged in 2000, it introduced a fundamentally different paradigm: every plan, section, elevation, and schedule lived inside a single, interconnected database. This meant that an inconsistently named view was no longer merely an annoyance in a flat filing system; it became a source of confusion that could ripple across an entire project, affecting coordination between disciplines and the integrity of construction documents.

The need for naming conventions — systematic rules governing how views, sheets, and worksets are labeled — arose directly from the collaborative nature of BIM. As project teams grew from a handful of drafters to dozens of specialists working simultaneously in shared models, the absence of a common language for organizing digital content led to duplicated views, misplaced sheets, and wasted hours searching for the correct drawing. Industry organizations responded by publishing standards, and firms developed internal protocols to manage the growing complexity of Revit projects.

The central question this lesson addresses is deceptively simple: How should you name views, sheets, and worksets so that any team member — today or years from now — can find, interpret, and trust what they are looking at? The answer involves principles drawn from information design, library science, and professional practice standards.

Core Principles of Naming Conventions

Effective naming conventions in Revit rest on a small number of interconnected principles. These are not arbitrary rules; each one solves a specific pain point that teams encounter when models scale beyond a solo practitioner's ability to remember where everything lives. Understanding these principles will allow you to evaluate any firm's standard critically and, when necessary, design your own.

Anatomy of a Naming Convention

The diagram below deconstructs a single view name into its component segments. Each segment carries a specific piece of information, and the segments are joined by a consistent delimiter — in this case, a hyphen. Understanding this anatomy allows you to read and construct names for any view type in a Revit project.

Notice how each segment answers a distinct question: What kind of view is this? (View Type), Where in the building does it show? (Level/Location), How much of the building does it capture? (Scope), and Why does this view exist? (Purpose). This four-part framework is flexible enough to accommodate any firm's specific vocabulary while preserving the predictability that makes the convention useful. When you scan the Project Browser, all floor plans cluster together because they share the FP prefix, and within that cluster they sort by level number, exactly as you would expect.

How Naming Conventions Work in Revit

Revit's Project Browser organizes views, sheets, and other project elements into a hierarchical tree. The default sorting groups views by type (Floor Plans, Ceiling Plans, Sections, etc.) and lists them alphabetically within each group. This alphanumeric sorting behavior is the mechanism that naming conventions exploit. By choosing prefixes, delimiters, and ordinal numbers carefully, you control exactly where every item appears in the browser hierarchy, transforming a chaotic list into a logically stratified navigation system.

Views: The Naming Engine

A view in Revit is any visual representation of the model — a floor plan, a 3D perspective, a schedule. Each view has a View Name parameter (which appears in the Project Browser) and a separate Title on Sheet parameter (which appears in the title block when the view is placed on a sheet). This distinction is critical: the View Name is your internal organizational tool and should be coded for sortability, while the Title on Sheet is a presentation-facing label that can be more descriptive and human-readable.

Sheets: The Document Backbone

A sheet represents a printed page of construction documents. Sheets have two naming components: a Sheet Number (e.g., A201) and a Sheet Name (e.g., "Floor Plan – Level 01"). The numbering system typically follows the CSI UniFormat or NCS convention, where the first letter denotes the discipline — A for Architectural, S for Structural, M for Mechanical, E for Electrical — and the subsequent digits indicate the drawing series and sequence.

Worksets: The Collaboration Partitions

A workset is a named subset of model elements that can be checked out by a single user during worksharing. Workset names serve a dual purpose: they organize who can edit what, and they control visibility in views. Common practice groups worksets by discipline and building system — for example, AR-Interior Walls, AR-Furniture, ST-Framing. Because workset names cannot be batch-renamed easily after creation, establishing the convention before the model is populated is essential.

Common Naming Patterns by Element Type

While every firm adapts naming conventions to its workflow, several widely adopted patterns have become de facto standards. The table below catalogs the most common naming structures for views, sheets, and worksets, along with the rationale behind each pattern. Use this as a starting point when developing your own project template or evaluating a firm's existing standard.

Sheet Numbering in Depth

The NCS-inspired sheet numbering system deserves closer attention because it encodes multiple layers of information in a compact string. The first character is the discipline designator: A (Architectural), S (Structural), M (Mechanical), E (Electrical), P (Plumbing), L (Landscape), and so on. The next digit (or pair of digits) represents the sheet type — 0 for general information, 1 for plans, 2 for elevations, 3 for sections, 4 for large-scale plans, 5 for details, and higher numbers for schedules and diagrams. The final digit is the sequence number within that series. Thus A301 decodes as: Architectural, Section series, first sheet in that series.

Worked Example: Naming a Mid-Rise Residential Project

Imagine you are setting up a Revit template for a six-story mixed-use residential building. The project involves architectural and structural disciplines, with plans for future MEP coordination. Walk through the following steps to establish a coherent naming convention from scratch.

Strengths and Common Pitfalls

Naming conventions are one of those practices that seem trivially simple until a project goes wrong. The table below contrasts the strengths of a well-implemented naming standard with the pitfalls that teams frequently encounter when conventions are absent, poorly documented, or inconsistently enforced.

Connection to Industry Standards and Advanced Workflows

The naming principles covered in this lesson are the conceptual foundation upon which more sophisticated BIM management frameworks are built. International standards such as ISO 19650 (Information Management Using BIM) and the UK's BS 1192 predecessor prescribe not only how files and views are named, but also how they are versioned, approved, and archived. Understanding the conceptual basis of naming allows you to step into any of these frameworks without being overwhelmed by their specificity.

As you advance in your BIM education, you will encounter tools like Autodesk Construction Cloud and BIM 360 that extend naming governance to the cloud, allowing project-wide enforcement across geographically distributed teams. The conceptual habits you build now — thinking in structured segments, documenting abbreviations, testing for predictability — will transfer directly into those advanced workflows.

Practice Problems

Lesson Summary