Shared Coordinates (Revit)
Revit's mechanism for tying its internal coordinate system to a real-world site coordinate system shared across linked models and surveys.
🔗 Related Concepts
Deepen your understanding with these related topics:
Definition
Every Revit project has an internal origin (Project Base Point) and a survey origin (Survey Point). Shared coordinates establish a real-world reference (e.g., state plane, OS National Grid) that travels through linked models. Acquire Coordinates copies coordinates from a linked model into the host; Publish Coordinates writes the host's coordinate system into the link.
When shared correctly, every team's Revit model places at the same world position regardless of who is the host.
Why it matters
Without shared coordinates, linked models end up overlapping at internal origins (typically near 0,0,0) instead of at the building footprint. Aligning by visual snap is unreliable and breaks down on subsequent link updates.
Technical Deep Dive & Core Mechanics
Shared Coordinates (Revit) interacts with the model's phasing system, which assigns every element a "created in phase" and optionally a "demolished in phase" attribute. Views filter elements through phase filters that combine these phase assignments with graphic override rules (show as new, show as existing, show as demolished, or hide). This mechanism allows a single model to represent the building at multiple points in its lifecycle—existing conditions, demolition, new construction—without duplicating geometry.
The workset mechanism controls editing access to Shared Coordinates (Revit) in multi-user environments. When a team member takes ownership of a workset, the elements within it become editable only on that user's local copy until synchronized back to the central model. Conflicts arise when Shared Coordinates (Revit) references elements owned by different users—for example, a wall in one workset hosting a door in another—requiring careful workset organization to minimize synchronization conflicts and reduce the frequency of failed-to-save errors.
Step-by-Step Professional Implementation
Deploying Shared Coordinates (Revit) in a BIM production environment requires careful coordination of model integrity and data standards:
- Initialize from the BIM Execution Plan (BEP): Bind the model to the project template that defines levels, grids, shared coordinates, and workset structure. Confirm that the BEP's LOD requirements match the current design phase.
- Model Element Placement with Proper Classification: When configuring Shared Coordinates (Revit), assign correct IFC classifications (e.g., IfcWall, IfcSlab, IfcBeam) and ensure that type/instance parameters carry the required COBie or Uniclass data for downstream handoff.
- Coordination and Clash Resolution: Federate the model regularly with structural, MEP, and architectural disciplines. Run interference checks to identify spatial conflicts, and log resolution actions in a BCF-compatible issue tracker.
- Model Health Validation: Run model audit tools to detect warnings such as duplicate instances, room-bounding errors, or unjoined elements. Verify that schedules and quantity takeoffs reflect accurate, current model data before milestone submissions.
Advanced Troubleshooting & Error Diagnostics
Troubleshooting Shared Coordinates (Revit) in multi-user BIM coordination workflows:
- Synchronization failures with central model: Attempting to sync Shared Coordinates (Revit) changes produces "Can't find central model" or element ownership conflicts. Resolution: Verify network connectivity to the central file location. Check if another user holds editing permission on the affected workset. If the file server is unreachable, save the local changes as a backup before attempting to reconnect.
- IFC export produces generic proxy objects: Shared Coordinates (Revit) elements export to IFC as IfcBuildingElementProxy instead of their correct IFC class. Resolution: Review the IFC export mapping table and verify that Shared Coordinates (Revit)'s category maps to the appropriate IFC entity. Custom families may need their IFC Class parameter explicitly set in the family editor. Re-run the export after correcting the mapping.
- Linked model positions shift after reload: After updating a linked model, Shared Coordinates (Revit) elements in the link appear offset from their expected positions. Resolution: Verify that both the host and linked models use the same shared coordinate system. Check the link's positioning method (Auto - Origin to Origin vs. Auto - By Shared Coordinates). If coordinates were recently acquired or published, the link may need to be removed and reloaded with the updated coordinates.
Cross-Discipline Collaboration & Handoff
In federated BIM projects, Shared Coordinates (Revit) is an active element in multi-discipline model exchanges. During inter-platform handoff (for example, exporting to IFC for clash detection or converting native models for coordination):
- IFC Classification Mapping: Verify that Shared Coordinates (Revit) elements export with the correct IFC entity type and property sets. Unmapped or generic proxy exports lose their semantic identity, reducing the value of coordination reviews and quantity takeoffs.
- Shared Coordinates and Georeferencing: Confirm that all discipline models share the same project base point, survey point, and true north orientation. Misaligned shared coordinates produce multi-meter offsets in the federated environment, creating false clash results.
- Version and Phase Management: Stamp model exchanges with phase, revision, and LOD metadata. Coordinate on a common data environment (CDE) platform with clear status codes (work-in-progress, shared, published) to prevent teams from basing decisions on superseded model snapshots.
Common pitfalls
- Confusing Project Base Point and Survey Point — moving one without understanding the difference relocates the model.
- Publishing coordinates from the wrong host — locks the link into a coordinate origin nobody intended.
- Not documenting which model is the coordinate source — every subsequent linker has to guess.
- Acquiring coordinates from a CAD link without checking units — produces 304.8× scale errors (feet vs. inches).
Revit Ecosystem Context
This concept is a core structural element of the Revit drafting and engineering environment developed by Autodesk. Autodesk's flagship BIM authoring tool — the building model becomes the single source of truth for plans, sections, schedules, and clash detection.
Relevant Revit FAQs
❓ Is Revit available on macOS?
No. Revit is Windows-only. Mac users typically run Revit inside Parallels, VMware Fusion, or Boot Camp (Intel Macs). On Apple Silicon, virtualisation requires Windows-on-ARM and is officially unsupported by Autodesk. The closest cross-platform alternative is ArchiCAD.
❓ Can Revit open RVT files from older versions?
Yes — Revit can open any older RVT, upgrading it on open. Once upgraded, the file cannot be saved back to the older version. For cross-version coordination, export to IFC or DWG, or maintain a parallel older file.
❓ Why is my Revit project so slow?
Most common causes: too many in-place families, oversized linked DWG CAD files, raster image imports, links not workset-isolated, unused worksets visible in all views, view templates not used (so views render with unique graphics settings), and too many parameters in mass schedules. Use Manage > Purge Unused and Audit on open.
⚡ Concept Self-Test
Test your understanding of this concept to lock in your memory. Completing this quiz will automatically sync to your career learning progress.
🎓 Recommended Practice Lessons
Step-by-step practical exercises and certification-aligned paths chosen by our editors to master this concept:
Revit 2026 - 15 Minute Tutorial For BEGINNERS!
Autodesk Revit - Full Beginner Course | Complete Project - Start to finish
Revit on Coursera (beginner filter)
🌳 Semantic Crossroads & Navigation Pathways
Trunk-Branch-Leaf ModelExplore cross-referenced learning lanes. Connect this specific method back to macro CAD coordinate foundations, parent software environments, and sibling parameters in our shared taxonomy map.
Global Foundations
Core glossary, interactive graph, and domain-wide concept index.
Ecosystem Integration
Parent design environments and platforms implementing this method natively.
Active Context & Neighbors
Current active term and close sibling concepts:
Discover More
Practical Workflow Tips
Hard-won lessons from BIM projects involving Shared Coordinates (Revit):
- Build a project-specific parameter catalog early: Define all shared parameters at the project start, including naming conventions and data types. Attempting to standardize parameters for Shared Coordinates (Revit) after multiple team members have created variants leads to duplicates that never fully consolidate.
- Use phases consistently: Set up phasing (existing, demolition, new construction) before any elements are placed. Retroactively assigning phases to Shared Coordinates (Revit) elements is tedious, especially in renovation projects.
- Validate room boundaries floor by floor: After major model edits involving Shared Coordinates (Revit), run a room/area check on each floor. Unenclosed rooms produce incorrect area calculations that flow into schedules.
- Establish a design option strategy: If Shared Coordinates (Revit) will involve design alternatives, create design option sets at the project start rather than mid-project.