Revit Levels and Grids: A Trainer’s Sequence for Fewer View Errors
Levels are horizontal datum planes that mark stories and reference heights, while grids are the vertical planes that organize columns and structural layout. If a grid refuses to show up in a plan view, the fastest fix is checking that its 3D extents intersect the level datum, then using 2D extents, scope boxes, or view templates for view-specific control.
TL;DR:
Create story levels before grids, set each level’s Plan View Type first, and add reference levels only for secondary heights such as parapets or mezzanines.
Use 3D extents for changes that should affect every view, and 2D extents for view specific adjustments; scope boxes and templates standardize visibility.
Revit numbers grids by creation order, not screen position, and renaming a grid does not reorder later labels, so establish a naming convention before placement.
Deleting a level also removes associated floor and ceiling views and hosted elements; inspect the Project Browser and back up the model first.
Table of Contents
Create and Manage Levels: Add, Rename, Move, and Delete Safely
Create and Manage Grids: Place, Copy, Shape, and Name Grid Lines
How 2D vs 3D Extents, Scope Boxes, and Templates Control Visibility
Quick Fixes for Grids Not Showing and Missing Levels in the Project Browser
Trainer-Backed S15Studio Workflow: A Short Checklist to Avoid Errors
Why the “Levels → Grids → View Control” Order Matters in Real Projects
Create and Manage Levels: Add, Rename, Move, and Delete Safely
Levels only make sense in an elevation or section view, since that is the only place you can see them as horizontal lines rather than abstract settings buried in a dialog box.
Open an elevation or section view and select the Level tool from the Datum panel.
Sketch the level line at the height you need. When “Make Plan View” is checked in the options bar, Revit generates a matching floor plan and ceiling plan automatically. Clear this option when you only need a reference height, such as a sill or a structural datum, without a new plan view.
Create one story level for each floor, then add reference levels for secondary heights like parapets or mezzanines.
Rename levels directly in the Project Browser or by double-clicking the level label. Revit will ask whether to rename the corresponding plan views to match, which keeps your browser tidy.
Adjust elevation by selecting the level and typing a new value, or drag the level line in the view. Offset the label from the line when levels sit close together, so text doesn’t overlap.
Deleting a level is not reversible in a casual sense. It removes the associated plan and ceiling views along with anything hosted on that level, so check the Project Browser for dependent views before you confirm, and keep a backup copy of the model when the level carries real content.
Create and Manage Grids: Place, Copy, Shape, and Name Grid Lines
Grids give every column and wall a shared reference, which is why getting their shape and spacing right early saves redrawing later.
Switch to a plan view and select the Grid tool, then choose a straight, arc, or multi-segmented line depending on the building footprint.
Place the first grid, then use the Copy tool with the Multiple option to generate the rest. Typed distances or temporary dimensions keep spacing exact instead of relying on eyeballed drags.
Edit a grid’s extents in an elevation or section view by dragging the endpoint bubble; this is also where you set a grid to 2D when you want it to appear differently in one view without changing the model everywhere else.
Name or number grids as you place them. Revit’s automatic numbering follows the sequence of creation, not the order grids appear on screen, and renaming one grid does not shift the numbering of the ones placed after it.
Locking in a naming convention before you start placing grids avoids the confusion that comes from manual renames drifting out of sync with the automatic sequence.
How 2D vs 3D Extents, Scope Boxes, and Templates Control Visibility
Every level and grid carries two separate extent settings, and mixing them up is the single most common reason datums behave unpredictably across views.
3D extents apply model-wide: stretching or shrinking them changes how the grid or level behaves in every view at once.
2D extents are view-specific: they let you shorten a grid line’s visible length in one plan without touching the model.
A grid’s 3D extents must intersect the level datum for that grid to appear in the corresponding plan view at all.
Scope boxes clip grid planes across a defined set of views, and including datum visibility in a view template keeps that standard consistent across the whole team.
Reach for 3D extents when the change is permanent and should ripple through the project; reach for 2D extents when you’re making a one-view presentation tweak.
Pro Tip: Before adjusting any extent, check whether the fix needs to apply everywhere or just in the view you’re looking at, since that decision determines which extent you touch.
Quick Fixes for Grids Not Showing and Missing Levels in the Project Browser
A grid that vanishes from one plan view almost always traces back to one of a short list of causes.
Open the view in elevation and confirm the grid’s 3D extent line actually crosses the level datum; if it stops short, drag it through.
Toggle the grid between 2D and 3D in the view that’s misbehaving, since a leftover 2D edit from another view can hide the line unexpectedly.
Right-click the grid in a plan view and open Show Grids to see exactly which levels that grid is set to display on.
If a level’s plan view is missing from the Project Browser, it may have been deleted without a replacement plan; use Make Plan View from the level’s properties to recreate it.
Check the view range, Visibility/Graphic Overrides, and whether grid annotation categories are switched off in that specific view.
Trainer-Backed S15Studio Workflow: A Short Checklist to Avoid Errors
We teach a fixed order for setting up datums because the sequence itself prevents most of the rework learners run into: establish every story level first, place grids second, then apply scope boxes and view templates last to lock down how everything displays.
Settle on a grid and level naming system before you start placing anything, and avoid renaming mid-layout, since Revit’s automatic grid numbering won’t retroactively reorder items you’ve already renamed. Lock critical level lines once they’re confirmed, build view templates that carry datum visibility settings, and keep a model backup before deleting any level.
Pro Tip: Set every story level’s Plan View Type before placing a single grid, so grids show up correctly in the right views the first time.
For guided, project-based practice on this exact workflow, our course library walks through full setups step by step.
Why the “Levels → Grids → View Control” Order Matters in Real Projects
Fixing levels before placing grids keeps the coordinate system stable, which prevents the slow drift that shows up later as mismatched views and columns that land on the wrong floor. The biggest time-sink we see in training sessions is learners placing grids first, then fighting extents and visibility settings for the rest of the project. A few extra minutes spent locking down levels early saves hours during documentation and coordination.
— Steve
S15Studio Courses That Help You Master Levels and Grids
Getting datums right the first time is a skill worth practicing deliberately rather than relearning on a live project. Our Revit Introduction course for €20 one-off covers the fundamentals of setting up levels and grids for beginners, and our Revit Course Only program for €79 one-off builds on that with a full structured progression through real workflows.
Project-based exercises built around the kind of setups you’ll actually model at work.
Support when a workflow question comes up mid-course.
Access to course materials, with certificates provided on completion.
Start with whichever entry point matches where you are, and work through the lessons at your own pace from our course catalog.
FAQ
What are levels and grids in Revit?
Levels are horizontal datum planes that mark story heights or reference elevations like sills and parapets. Grids are vertical planes used to organize columns and structural layout across the building.
Why are grids not showing on all levels in Revit?
A grid only appears in a plan view when its 3D extents intersect that level’s datum line in elevation. If the extent stops short of the level, switch the grid between 2D and 3D or check the Show Grids dialog to confirm which levels it’s set to display on.
What is the point of grids in Revit?
Grids give every column, beam, and structural wall a shared reference so elements line up consistently across every floor of a project. They serve as the primary organizational framework for aligning structural elements throughout a multi-story building.
How do I see a list of levels in Revit?
Open the Project Browser and expand “Floor Plans” or “Ceiling Plans” to see every level with an associated view. Levels without a listed plan view may still exist in elevation but lack a corresponding plan, which you can add back with Make Plan View.
Authoritative Links and Documentation
The Revit mechanics covered here draw on official Autodesk Help documentation on levels, grids, and datum visibility. For structured, guided practice applying these workflows to real projects, our Revit training courses walk through the same setup sequence step by step.
Recommended
Comments