Wow, there is a lot of rhetoric and misinformation in this thread. First of all, there are a few completely DIFFERENT concepts that are getting conflated or confused, in terms of whats possible and whats not:
Shared Coordinates (with a simple single system): 100% possible, and usable, and functional, on both C4R and BIM360 Design.
Multiple Named Places (multiple Shared Coordinate systems): 100% possible, and usable, and functional, on both C4R and BIM360 Design.
Multiple Named Places in both the Linked files AND the Host File: 100% possible, and usable, and functional, on both C4R and BIM360 Design.
Specifically using ACQUIRE or PUBLISH Coordinates, when models have Multiple Named Places: Doesnt work in C4R, or BIM360 Design, but it also doesnt work in basic Revit, and its always been that way. AND, it doesnt stop you from accomplishing the goal, because: If you have multiple Named Places, you need to use Specific Coordinates at a Point ANYWAY, which is the workflow that always works, 100% of the time.
So, lets cover a few topics, if i may:
1. Originally setting up Shared Coordinates. A lot of people and project teams prefer to have this done using the PUBLISH or ACQUIRE workflows, which is fine when the project models only have one Shared Coordinate System, aka One Named Place (that teams typically leave called Internal, which is a lousy and confusing name). If you hapeen to do any work with both the 3D Coordination Team and the Construction Team, you may discover they want different coordinate systems. For instance, if the 3D coordination team wants the model to be orthagonal to "North" and to be close to 0,0,0, so they can pull straight dims when they have clashes, that will end up needing to be a Coordinate System (Named Place). But the Model will also have its REAL coordinates, which will be another.
My only point in saying all of that, is the ONE workflow that works in all cases (and always has) is using Specify Coordinates At A Point, instead of Acquire or Publish. I also prefer this, as i can then set the coordinates by the exact benchmark location Civil has used. In fact, i dont EVER use Acquire, or Publish, or or unclip/clip/move the Survey point of Project Base Point. There simply isnt a need.
Now, to the last question that was asked: What happens when the building has to move five feet? No issues at all. Go in the Linked Model, and use specify Coordinates at a point AGAIN, and change the coordinate to move the five feet. Whats even better about this, is: Unlike with Acquire/Publish, where you have to use the "sacrificial link" to reset the Coordinates as mentioned above, using Specify at a Point, you dont have to do that. Here is a comparison:
Sacrificial Link method (what you need to use to "move the building five feet" if you used Acquire/Publish... Also which doesnt work with multiple named places: https://youtu.be/UFngm-dGsEQ
(Note: In that video we are "fixing" coordinates for another reason, but its the same workflow.
Moving the building with Specify at a Point: https://youtu.be/TegBE-SSOd8
That workflow always works, with the exception of needing to quickly unload the link, and reload it (NOT remove). There are no downsides to this, frankly.
Ive been using Revit since 2006, and this all works the same as it always has, assuming you use Specify as your means to determine the original coordinates. And- given that i do a LOT of Field Layout collaboration DIRECTLY with staff on jobsites, and ive seen the many different ways coordinates can be set up, IMVHO its insane to use Publish or Acquire, without then putting a Spot Coordinate down to back check yourself versus civil. And if you are taking the time to put the spot coordinate down, why not actually just type in the coordinate value, and then not have to worry about it?
I have no need to address the other "commentary" on the Revit Coordinate System, nor the Revit Ideas page. Since the former has resulted in 100% usable data for construction teams in the field, and the latter has resulted in new features being added to the program that started out as Revit Ideas posts, the facts speak for themselves.