Revit Tip: Standardize Spot Elevations and Coordinates in Revit

Today’s tip: use Spot Elevations and Spot Coordinates properly to prevent downstream field errors and RFIs.

Decide your coordinate strategy first:

• Establish whether deliverables must reference Project Base Point (PBP) or Survey/Shared Coordinates. Civil and site packages almost always expect Shared Coordinates.
• Acquire/Publish coordinates once from the civil model, then Pin both the Survey Point and Project Base Point. Do not move them after you start annotating.
• Document the decision in your BIM Execution Plan and in your Revit template notes so every view and sheet stays consistent. If your team needs licensing or template help, consult NOVEDGE for Revit standards support: NOVEDGE.

Configure annotation types for clarity and control:

• Create dedicated Spot Elevation types: one for Project Elevation and one for Shared/Sea Level. Set the Elevation Base, unit format (override to mm/ft as required), rounding, and prefixes/suffixes (e.g., +/−, “EL=”).
• Create Spot Coordinate types for Easting/Northing. Choose orientation (Project or True North), define unit precision, and optionally add “E:” / “N:” prefixes for legibility.
• Standardize tick marks, text size, and leader styles via your View Templates so all plans, sections, and details read the same across sheets. Need a jump start on templates? See NOVEDGE.

Place spots accurately and predictably:

• Ensure the host face is visible in the view. For sloped slabs/roofs, set the spot to read the surface (not the reference plane) and confirm the leader landing is on the intended point.
• Use a section box in 3D to isolate and place precise Spot Elevations on complex geometry, then reference those values on plan/section for consistency.
• For grids and site benchmarks, place Spot Coordinates at known control points (grid intersections, survey monuments) and lock their visibility via View Templates.
• When working with links, verify all models share the same Shared Coordinates before placing spots. If your firm tags/annotates in the host, confirm “tagging linked elements” is supported in your Revit version and workflow.

Quality assurance checks that catch costly mistakes:

• Create a dedicated “Coordination – Benchmarks” view set with bold graphics to compare spot-read values against civil benchmarks and datum callouts.
• Audit unit overrides: mismatched rounding between views can make elevations appear inconsistent.
• Compare values under Project North vs True North views to ensure orientation settings don’t shift reported coordinates.

Troubleshooting tips:

• Spot won’t place? Check the category’s visibility (host must be visible), detail level, and your active workplane. Try On Face vs On Workplane placement.
• Numbers look wrong? Confirm Elevation Base, Shared Coordinates status, and that the Survey Point hasn’t been moved. Re-Acquire/Publish coordinates only if absolutely necessary.
• Inconsistent on sheets? Lock annotation types via View Templates and avoid per-view unit overrides unless documented.

Done right, spot annotations make your documentation unambiguous and construction-ready. Establish the base, standardize the types, place with intent, and verify early—your field team will thank you. For Revit licenses, add-ons, and expert guidance, visit NOVEDGE.