Levels — Create and modify levels; understand level-driven constraints

Before digital modeling tools reshaped architectural practice, designers communicated vertical organization through hand-drafted section drawings — laborious documents where each floor line had to be manually coordinated with plans, elevations, and structural details. A single change to a floor-to-floor height could cascade into hours of revision across dozens of sheets. The introduction of Building Information Modeling (BIM) fundamentally changed this workflow by embedding intelligence into every element of a digital building. At the core of that intelligence in Autodesk Revit sits the concept of levels — horizontal datum planes that define where floors, ceilings, roofs, and other story-based elements reside. Levels replaced the fragile, manually-drawn floor lines of CAD-era drafting with parametric references that propagate changes automatically, keeping an entire project coordinated in real time.

The central question this lesson addresses is deceptively simple: How does Revit know where a wall starts, where a floor sits, and what happens when a story height changes? The answer lies entirely in how you create, modify, and constrain elements to levels. Understanding levels is not merely a technical prerequisite — it is the conceptual foundation upon which every Revit project is built.

A level in Revit is a finite horizontal plane that acts as a reference datum for hosting building elements. Unlike a simple guideline, a level carries metadata — a name, an elevation value, and the ability to generate associated plan views. When you place a wall, Revit asks which level constrains its base and which constrains its top; when you lay a floor, Revit asks which level it belongs to. This hosting relationship is what the software calls a level-driven constraint, and it is the mechanism that makes parametric change propagation possible. Move a level, and every element constrained to it moves in lockstep.

The diagram above illustrates how levels function as organizational scaffolding within a Revit section view. Notice that each level appears as a dashed horizontal line with a circle head symbol on the left and an elevation callout on the right — this is precisely how levels render in Revit's elevation and section views. The two walls demonstrate the dual-constraint concept: Wall A is constrained between Level 1 (base) and Level 2 (top), so if you raise Level 2 by two feet, Wall A automatically stretches taller by two feet. Wall B extends from Level 1 to the Roof, spanning a greater height. The floor slabs, shown as thin rectangles at Levels 1 and 2, are hosted elements — they ride on their level and will shift elevation if that level moves. This kind of parametric dependency is what distinguishes BIM from simple 3D modeling.

The Constraint Graph

Behind the scenes, Revit maintains a constraint graph — a network of parametric relationships between elements and datums. When you assign a wall's Base Constraint to Level 1 and its Top Constraint to Level 2, Revit internally records two dependency edges in this graph. The wall's actual height is computed as the elevation difference between its two constraining levels, plus or minus any offset values you specify. This computation can be expressed as:

For example, consider a wall with its Base Constraint set to Level 1 at elevation 0′-0″ and its Top Constraint set to Level 2 at elevation 10′-0″. If the Base Offset is 0″ and the Top Offset is −6″ (meaning the wall stops 6 inches below Level 2 to leave room for a structural beam), the effective wall height is (10′-0″ + (−0′-6″)) − (0′-0″ + 0″) = 9′-6″. Now, if you move Level 2 up to 12′-0″, the wall height automatically recalculates to 11′-6″ — no manual editing needed.

Constraint Modes

Revit offers two primary constraint modes for vertical elements. In level-to-level mode, both the base and top are locked to specific levels, making the element fully parametric. In unconnected height mode, the base is constrained to a level but the top is defined by a fixed height value. The latter is useful for short partition walls or parapets that should not respond to floor-to-floor changes. Understanding when to use each mode is essential: if you assign an unconnected height to an exterior wall that should span to the roof, the wall will not grow when you increase a story height, creating a gap in the model that will go unnoticed until a section view reveals it.

Not all levels serve the same purpose. Revit distinguishes between story levels (sometimes called building stories) and non-story levels. A story level is flagged as a "Building Story" in its properties, which means it participates in Revit's area and volume computation schedules, appears in the Project Browser's plan view hierarchy, and is recognized by other Autodesk tools (like Navisworks) as a genuine floor of the building. A non-story level, by contrast, is a reference datum that may mark something like a window sill height, a mezzanine railing, or a structural beam soffit — it exists as a horizontal reference but does not generate plan views or participate in story-based scheduling. Understanding this distinction matters enormously for visual arts students working on exhibition design, gallery spaces, or theatrical set models where mezzanines and partial floors are common.

Imagine you are designing a two-story art gallery with a basement storage level. The program calls for a basement at −10′-0″, a ground-floor gallery at 0′-0″, an upper gallery at 14′-0″, and a flat roof at 26′-0″. You also need a non-story reference level at 4′-0″ to mark the top of a display wall rail system on the ground floor. The following steps walk through the complete setup.

As projects grow in complexity, the level hierarchy interacts with two advanced Revit concepts: worksets and phases. In a workshared environment, levels are shared across all worksets — they belong to a special "Shared Levels and Grids" workset that every team member can see. This ensures that the structural engineer, the architect, and the MEP designer all reference the same datum. However, it also means that moving a level in one user's local file propagates to the entire team upon synchronization, which can have dramatic consequences if done carelessly. In phased projects (such as a museum renovation where an existing building is being expanded), levels from the existing condition must be carefully matched to the new construction phase so that elements in both phases align correctly.

For visual arts students who may eventually work in exhibition design, theater production, or museum curation, these advanced concepts will become relevant the moment a project involves multiple consultants or a renovation of an existing space. Establishing a clean level hierarchy early — before walls and floors are placed — is the single most important step in ensuring long-term project health. The concepts of shared coordinates and workset management are explored in depth in later modules, but they all presuppose that your levels are correct and intentional.