Keep your model’s vertical datums predictable by driving Levels from named Reference Planes. This simple constraint strategy prevents accidental shifts, streamlines redesigns, and supports clean handoffs.
Why it helps
- Prevents accidental nudges of Levels during busy coordination phases.
- Creates a single source of truth for FFL/SSL/TOS and other key datums.
- Enables controlled updates: move the Reference Plane, the Level follows.
- Supports parameter-driven workflows with Global Parameters for rapid scenario testing.
Setup (5–10 minutes per project)
- Open a clean elevation or section view dedicated to datum control.
- Create a horizontal Reference Plane at each critical datum (use RP). Name clearly, e.g., “L02_FFL – Control”.
- Select Align (AL). First select the Reference Plane, then the corresponding Level line. If the Lock icon appears, lock it.
- If no Lock icon appears in your context, place an Aligned Dimension between the Reference Plane and the Level, set it to 0, and lock the dimension.
- Pin both the Reference Plane and the Level. Keep them on the “Shared Levels and Grids” workset.
- Apply a View Template for your “Datum Control” elevations that:
- Turns on Reference Planes and Constraints for audit views.
- Turns off Reference Planes in production/documentation views.
- Optional: Dimension each Reference Plane from a known base (e.g., Level 0) and label with Global Parameters (e.g., L02_FFL_Elev). Adjusting a parameter moves the Reference Plane, which updates the Level via the lock.
Governance and collaboration
- Keep Levels and Reference Planes on “Shared Levels and Grids.” Assign a model lead as the Workset owner.
- Close the workset by default for most users to avoid incidental edits.
- Use Copy/Monitor to track Levels across linked consultant models; communicate changes proactively.
- Document naming standards: FFL, SSL, TOS, CL, etc., and include units and role suffixes where helpful (e.g., “L03_SSL – Struct”).
QA/QC and troubleshooting
- Use Reveal Constraints to verify locks after major coordination events.
- Avoid over-constraining: limit each Level to a single controlling Reference Plane.
- If you see “Cannot maintain constraints” warnings, unlock, resolve conflicts, and reapply the single authoritative lock.
- Pin, then test: try to move the Level slightly—Revit should block the action or move the paired Reference Plane.
Pro tips
- Centralize all datum controls in one or two dedicated “Datum Control” elevations and keep them off sheets.
- Include these settings in your office template so every project starts with protected datums.
- When upgrading or receiving external models, audit datums first—stability here saves hours later.
Need help implementing this in your standards or looking for Revit licensing and training? Partner with NOVEDGE. Their team can guide template setup, workset strategy, and best practices for datum management. Explore Revit solutions and expert services at NOVEDGE.






