One Habit Stops Drift: Revit Shared Coordinates for Project Teams
Shared coordinates let multiple Revit and CAD files align to a single real-world origin, and the best practice is to derive coordinates from one authoritative source and use Acquire and Publish consistently. Autodesk recommends treating one model as the source of truth, with every other file acquiring coordinates from it rather than publishing in multiple directions.
TL;DR:
Establish one authoritative file, often the site or civil model, to serve as the sole source of shared coordinates for all linked models.
Always acquire coordinates from the source file rather than publishing into it, ensuring consistent one-way data flow.
Verify link positioning by reloading links, checking the Survey Point outside Revit, and reopening the project to prevent coordinate drift.
Use the Acquire and Publish commands in the Project Location panel to synchronize coordinates, especially when updating from site surveys or civil models.
Maintain a clear rule that only the source file publishes coordinates, with all others only acquiring, to avoid accidental misalignment during collaboration.
Table of Contents
How do you set up shared coordinates step by step?
Start by deciding which file is the source of truth. On most projects this is the site or civil model, since it typically carries the real-world survey data that building models need to inherit. Once that file is set, every other linked model should acquire from it rather than the reverse, so coordinates only ever flow one way through the project.
The practical sequence looks like this:
Open the site or civil file first and confirm its Survey Point reflects the actual site survey data.
Link the building model into the site file, positioned manually if needed for a first pass.
In the site file, go to Manage, then Project Location, then Coordinates, and select Publish to push coordinates into the linked building model.
Open the building model directly and use Acquire, pointing at the linked site file, to confirm it now reports the shared coordinate values.
Repeat the Acquire step for any additional discipline models (structure, MEP) that need to sit in the same shared system.
For DWG files from surveyors or civil engineers, the link method matters. Choosing Auto - By Shared Coordinates during the link process lets Revit read the DWG’s own grid or GIS coordinates and use them to establish the project’s shared system, rather than placing the file by guesswork.
After acquiring or publishing, verify the result before moving on:
Reload all links and confirm no warning appears about coordinate conflicts.
Open the linked file independently (outside the host) and check that its Survey Point still matches the published values.
Close and reopen the project in a fresh session, then confirm the link reloads in the same position without manual nudging.
Skipping verification is the most common reason teams discover a coordinate problem weeks into a project rather than on day one.
What are the Project Base Point, Survey Point, and internal origin?
Revit actually tracks three distinct reference points, and confusing them is where most coordinate mistakes start.
The internal origin is a fixed point Revit sets when the model is created; it never moves and is not visible by default.
The Project Base Point marks the origin of the project’s own coordinate system, used for construction documentation and typically near the building.
The Survey Point represents the real-world origin tied to a land survey, and this is the point that Acquire and Publish actually read and write when establishing shared coordinates.
True North is handled separately from these points. When a model acquires coordinates from a linked file, it pulls in that file’s True North angle along with the origin, which is why rotating a site plan after linking can throw off orientation if the acquire step runs again. Project North, by contrast, is a local setting used for convenient on-screen layout and has no bearing on the shared coordinate system.
Pro Tip: Keep Project North aligned to True North early in a project. It saves confusion later when you need to compare views, sections, or sheet annotations across disciplines.
For campuses or phased developments, a single model sometimes needs to appear in more than one location, such as a prototype building repeated across several sites. Named Positions let a model store multiple placements against the same shared coordinate system, which avoids repeatedly moving and re-acquiring the file by hand for each site.
Where do the Acquire and Publish commands live and how do they work?
Both commands sit in the same place: Manage tab, Project Location panel, Coordinates tool. From there you choose either Acquire or Publish depending on which direction the coordinate information needs to travel.
Acquire pulls the origin and True North angle from a selected linked file into the host model, overwriting the host’s own Survey Point position.
Publish does the opposite: it pushes the host model’s current coordinates out to a selected linked file, updating that link’s Survey Point to match.
Running Acquire or Publish again later re-syncs coordinates, which matters after a site survey update or a civil model revision.
For DWG links specifically, Auto - By Shared Coordinates reads the file’s embedded grid or GIS data and uses it directly, with the DWG’s origin becoming the shared origin and its Y axis becoming True North. When a DWG carries no usable grid data, or when mixed Revit and DWG links are not coordinated on a single shared position, Revit can fall back to a simple center-to-center placement, which silently breaks alignment unless someone checks it on first link.
Why do linked models shift, and how do you recover safely?
A model that was correctly positioned yesterday but loads in the wrong place today usually points to one of a few causes: a replaced DWG file with a different internal scale, a link instance accidentally moved and saved, or a team member running Acquire or Publish in the wrong direction. Warnings on load are the first clue, so never dismiss them without reading what changed.
Recovery generally follows this order:
Confirm which file is still the correct source of truth and has not been altered.
Re-run Acquire from that source file in any model that looks out of place.
Save the file immediately and tell the team which models were touched, so nobody overwrites the fix.
When coordinates are corrupted beyond a simple re-acquire, Reset Shared Coordinates is the last resort. It moves the Survey Point back to the internal origin, sets True North back to zero, and strips GIS data from the host model, but it does not touch the linked files themselves.
Keep in mind: resetting is one-directional and affects only the host file, which means every linked model will need to re-acquire coordinates afterward to restore alignment.
What habits prevent coordinate drift on a project?
A short list of habits accounts for most of the difference between projects that stay aligned and ones that need repeated fixes.
Commit to one source-of-truth file in writing, and make Acquire the only direction other models are allowed to use.
Keep all model geometry within roughly 32 kilometers (20 miles) of the internal origin, since placing elements farther out causes snapping errors and graphic instability.
Use spot coordinates on a verification sheet so anyone can check a point’s real-world value without opening the Coordinates dialog.
Save Named Positions for campus or phased work instead of moving the model’s origin by hand each time.
Pro Tip: Add a coordinate check to your BIM QA routine the same way you’d check for unresolved warnings, a quick reload and spot-coordinate comparison takes a minute and catches drift before it reaches a drawing set.
Regular link audits matter more on workshared, multi-user projects, where several people might touch the same linked files in a week. A reload at the start of every session, paired with a spot check against the known survey values, keeps the shared system trustworthy enough that coordinate reports and tags can be relied on without re-verifying them each time.
Why trust this guide on Revit shared coordinates?
This guide draws on official Autodesk documentation alongside practical workflow habits taught by Steve Fagan, an Autodesk Certified Trainer and founder of S15Studio. The steps above mirror what’s covered in S15Studio’s Revit: Worksharing course and the Setting Revit Site Coordinates post, both built around the same source-of-truth workflow used on real project teams. For a deeper look at coordinating linked disciplines, see Revit Coordination Model: A Guide for Architects.
Where to find official Autodesk documentation
For command-level detail beyond this guide, Autodesk’s own help topics are the primary reference:
About Shared Coordinates covers the concept and the single-source-of-truth recommendation.
Linking DWG files with grid coordinates explains Auto - By Shared Coordinates in full.
Shared positioning workflows walks through acquire, publish, and reporting in sequence.
Build these skills with guided Revit training
Reading about Acquire and Publish is one thing, practicing them on a live multi-discipline model is another. S15Studio offers a Worksharing Course that focuses specifically on collaboration and coordinate workflows, and a Revit Course Only package that develops these habits into a complete Revit curriculum. Current prices are available on the website.
Practice acquiring and publishing coordinates across linked site, building, and structural models.
Work through Named Positions on a sample phased project, with trainer feedback along the way.
Start with the Worksharing Course if coordinate setup is your immediate concern.
The one habit that stops most coordinate errors
Teams that struggle with shared coordinates almost always lack a written rule about who publishes and who acquires. Pick one file as the source of truth, document it, and forbid any other model from publishing into it. On your next project, say that rule out loud in the kickoff meeting before anyone links a file. For teams managing complex multi-building coordination, the process articles at The Intent Ledger are worth a look too.
— Steve
Sources
FAQ
What are shared coordinates in Revit?
Shared coordinates are a system that keeps multiple linked files, including Revit models, DWG files, and DXF files, positioned consistently relative to each other and to a real-world origin. Autodesk’s documentation recommends deriving them from one authoritative file rather than letting multiple files define their own.
How do I add shared coordinates to a Revit project?
Link the site or source file into your model, then use the Coordinates tool on the Manage tab, Project Location panel, choosing either Acquire to pull coordinates in or Publish to push them out. The Acquire and Publish workflow is the standard way to establish this connection between files.
What’s the difference between Acquire and Publish?
Acquire pulls the origin and True North from a linked file into your current model, while Publish pushes your current model’s coordinates out to the linked file. Both commands live in the same Coordinates tool, and a project should settle on one direction to avoid conflicting updates.
Does resetting shared coordinates affect linked models?
Reset Shared Coordinates changes only the host model, moving its Survey Point back to the internal origin and clearing True North and GIS data, but it does not alter the linked files themselves. After a reset, every linked model needs to re-acquire coordinates to restore alignment.
Why does my linked DWG file land in the wrong position?
This usually happens when the DWG lacks usable grid or GIS data, or when the link wasn’t set to Auto - By Shared Coordinates during import. Without that setting, Revit can fall back to a simple center-to-center placement, which rarely matches the real-world position.
Recommended
Comments