Levels, Grids, and Reference Planning: Building a Reliable Skeleton

Why Levels and Grids Matter (Your Model’s “Skeleton”)

Levels and grids are reference elements that control how the building is organized, coordinated, and documented. Think of them as the reliable skeleton that everything else can align to: levels define vertical organization (heights), and grids define horizontal organization (structural/coordination lines). When levels and grids are planned and managed well, you get predictable behavior in views, cleaner constraints, easier dimensioning, and fewer coordination mistakes.

• Levels: drive story heights, host elements (walls, floors, roofs), and control view ranges and plan generation.
• Grids: provide a consistent coordinate framework for columns, walls, structural framing, and dimension strings.
• Extents: determine how far levels/grids appear in each view; controlling extents prevents messy sheets.
• Scope boxes: allow you to control extents consistently across many views without manually stretching each line.

Step-by-Step: Create a Clean Level Structure in an Elevation

1) Start in an elevation view and set your “working elevation”

Levels are best created and edited in an elevation or section where you can see vertical relationships clearly. Open an elevation (e.g., East/West) that shows the full height of the building. If needed, adjust the crop region so you can comfortably see from below ground floor up past the roof/parapet.

2) Create the primary levels (Ground, Roof, Parapet)

Use Architecture > Datum > Level (or the equivalent Level tool). Place levels in this order to keep logic simple:

• Level 1 – Ground Floor: set at 0'–0" (or 0 mm) as your project baseline unless your office standard differs.
• Level 2 – Roof: set to your intended roof-bearing elevation (example: 12'–0" / 3650 mm).
• Level 3 – Parapet: set above roof (example: 13'–6" / 4100 mm).

Tip: Place levels roughly, then use temporary dimensions to set exact heights. Click the level line, then click the temporary dimension value and type the precise elevation.

3) Name levels with sheet-friendly conventions

Level names appear in the Project Browser and can drive plan view names. Use a consistent convention that sorts well and reads well on sheets:

Continue in our app.

• Listen to the audio with the screen off.
• Earn a certificate upon completion.
• Over 5000 courses for you to explore!

Or continue reading below...

Download the app

• 01 - Ground Floor
• 02 - Roof
• 03 - Parapet

This numeric prefix keeps levels ordered even when additional levels are inserted later (e.g., 01A - Mezzanine).

4) Decide which levels should generate plan views

When you create a new level, Revit may prompt you to create plan views. Create plan views only for levels that need documentation or modeling in plan. For example:

• Create plans for Ground Floor and Roof.
• Skip plan creation for Parapet if you don’t need a dedicated plan (you can still reference it in sections/elevations).

5) Control level extents: 3D extents vs 2D extents

Levels can display with different extents per view. This is a common source of “why is my level line too long/short on this sheet?” issues.

• 3D extents: the level line is consistent across views (useful for coordination).
• 2D extents: the level line can be adjusted per view (useful for sheet presentation).

In an elevation, select a level and look for the small control that toggles 2D/3D at the end of the level line. Use 3D extents while setting up the skeleton; switch to 2D extents later for sheet-specific cleanup.

6) Keep level heads readable and consistent

Level heads (bubbles) should be consistent across elevations/sections. As you adjust extents, ensure level heads align visually and don’t overlap. If you need a level head on only one side, you can toggle the bubble visibility per end.

Step-by-Step: Create a Grid System in a Plan View

1) Choose the right plan for grid creation

Create grids in a plan where the building footprint is clear, typically 01 - Ground Floor. Turn on a reasonable visual style (e.g., Hidden Line) so you can see references without clutter.

2) Establish a simple rectangular grid layout

Use Architecture (or Structure) > Datum > Grid. For a small rectangular building, start with a minimal, logical set:

• Vertical grids: A, B, C (left to right).
• Horizontal grids: 1, 2, 3 (bottom to top).

Place the first grid, then use temporary dimensions or the Move tool to set spacing precisely (example: 20'–0" between A-B and B-C; 15'–0" between 1-2 and 2-3). Keep the grid spacing aligned to your intended structural/module logic.

3) Use temporary dimensions to lock in spacing intentionally

When you place or move grids, Revit shows temporary dimensions. Use them to type exact values. Avoid immediately locking everything; instead:

• Set spacing accurately using typed values.
• Only lock constraints when you’re confident the grid is final or when it prevents repeated accidental edits.

4) Name grids with a convention that scales

Use letters in one direction and numbers in the other. For expansions, insert intermediate grids using suffixes rather than renaming everything:

• Between A and B, add A.1 or A1 (office standard dependent).
• Between 1 and 2, add 1.1 or 1A.

Consistency matters more than the exact format. The goal is to avoid renumbering grids later, which can break documentation and coordination.

5) Control grid extents and bubbles for clean sheets

Like levels, grids have extents that can be controlled per view. In plan:

• Use 3D extents while coordinating across multiple plans.
• Switch to 2D extents to fine-tune how far grid lines extend on a specific sheet view.
• Keep grid bubbles visible where dimensions will be placed; hide bubbles on the opposite end if they clutter the view.

Using Scope Boxes to Control Extents Across Multiple Views

Scope boxes are especially useful when you have multiple plans (e.g., Ground Floor and Roof) and want grids/levels to appear with consistent extents without manually adjusting each view.

1) Create a scope box around the building

In plan view, use View > Create > Scope Box and draw a rectangle that encloses the building with a small margin. Name it clearly, for example:

• SB - Overall Building

2) Assign grids to the scope box

Select all grids (use a window selection carefully), then in Properties set Scope Box to SB - Overall Building. This makes grid extents consistent across views that reference the same scope box behavior.

3) Assign levels to the scope box (when appropriate)

Levels can also be controlled via scope boxes in many workflows. If your elevations/sections are inconsistent, assign the same scope box to levels to standardize how far they extend. If you find it reduces flexibility in a particular elevation, remove the scope box assignment for that view and use 2D extents there.

Aligning Modeled Elements to Levels and Grids (Without Over-Constraint)

1) Prefer “real” constraints over manual nudging

Whenever possible, let elements reference levels and grids rather than relying on eyeballing or repeated manual adjustments. Examples:

• Walls: set Base Constraint to 01 - Ground Floor and Top Constraint to 02 - Roof (or to 03 - Parapet if the wall forms the parapet).
• Floors: set the floor’s level to 01 - Ground Floor and use offsets only when needed.
• Columns: set base/top levels explicitly (e.g., Base: Ground Floor, Top: Roof).

2) Use Align (AL) + Lock only when it protects intent

The Align tool is powerful for snapping geometry to grids or reference planes. Use it intentionally:

• Align a wall centerline or face to a grid when the grid is intended to control that wall location.
• Lock the alignment only if the wall must always remain on that grid (e.g., structural grid controlling column line).
• Avoid locking every alignment “just in case.” Too many locks can create constraint conflicts later.

Rule of thumb: Constrain the minimum number of relationships needed to preserve design intent.

3) Use offsets instead of locks for controlled flexibility

If a wall should be consistently offset from a grid (e.g., exterior face 6" from Grid A), consider:

• Align the wall to the grid, then set a consistent Location Line and use a dimensioned offset.
• Or use a reference plane at the offset distance and align/lock to that reference plane (cleaner than locking directly to the grid if the grid is purely structural).

4) Temporary dimensions: treat them as a precision tool

Temporary dimensions are ideal for quick, accurate placement without creating permanent annotation clutter. Use them to:

• Set grid spacing precisely.
• Place walls at exact distances from grids.
• Verify symmetry (e.g., centered core between grids).

If a relationship needs to be documented or maintained, convert it into a permanent dimension and (optionally) lock it. If it’s only for initial placement, rely on temporary dimensions and avoid extra constraints.

Verification Workflow: Check Consistency Across Views

1) Confirm levels appear correctly in all elevations/sections

• Open at least two elevations (e.g., East and North).
• Verify level names and elevations match exactly.
• Check that level lines are not unintentionally at 2D extents in one view and 3D in another (unless you intended that).

2) Confirm grids align and extend consistently in multiple plans

• Open 01 - Ground Floor and 02 - Roof plans.
• Verify grid labels are identical and in the same order.
• Check that grid extents are consistent (use scope box assignment if needed).

3) Spot-check element constraints

Select a few key elements and verify their constraints in Properties:

• Walls: base/top constraints and offsets.
• Columns: base/top levels.
• Floors/roofs: associated level and offsets.

If something is “floating” (unconstrained) or “fighting” (over-constrained), fix it now before adding more model complexity.

Exercises: Build the Skeleton for a Small Rectangular Building

Exercise A: Create and name levels

Goal: Create three levels and ensure they are consistent in at least two elevations.

• In an elevation, create levels at: 0'–0", 12'–0", 13'–6" (or metric equivalents).
• Name them: 01 - Ground Floor, 02 - Roof, 03 - Parapet.
• Create plan views for Ground Floor and Roof only.
• Open a second elevation and verify the same level names/elevations appear.

Exercise B: Create a 3x3 grid system and set spacing

Goal: Create grids A–C and 1–3 with precise spacing and clean extents.

• In Ground Floor plan, place three vertical grids and label them A, B, C.
• Place three horizontal grids and label them 1, 2, 3.
• Set spacing: A–B = 20'–0", B–C = 20'–0"; 1–2 = 15'–0", 2–3 = 15'–0".
• Adjust grid bubbles so labels are readable and not overlapping.

Exercise C: Use a scope box to standardize grid extents

Goal: Make grids look consistent in Ground Floor and Roof plans.

• Create a scope box around the building area and name it SB - Overall Building.
• Select all grids and assign them to the scope box.
• Open the Roof plan and verify grid extents match Ground Floor.

Exercise D: Align a few elements to the skeleton (light constraints only)

Goal: Practice aligning without over-locking.

• Place a few exterior walls roughly forming a rectangle inside the grid.
• Set wall Base Constraint to 01 - Ground Floor and Top Constraint to 02 - Roof.
• Use Align to align one wall to Grid A and another to Grid 1. Lock only one of these alignments (your choice) and leave the others unlocked.
• Move a grid slightly and observe what updates; then undo and decide which relationship truly needs a lock.

Exercise E: Consistency checklist across views

• In Ground Floor and Roof plans: confirm grid labels and order match.
• In two elevations: confirm level names and elevations match.
• Select a wall: confirm base/top constraints reference the intended levels (not “Unconnected”).
• If something looks different between views, check: 2D/3D extents and Scope Box assignments.