With the advent of Revit Cloud Worksharing it became easier to share access to these 'common' models, however for a variety of reasons, common access to a single model is problematic particularly when there are multiple active projects with different timelines and multiple design and construction partners all accessing the data. Sometimes it is a selective copy/paste (or the equivalent using an API based tool) other times it may be a common model that 'everyone' works in while making use of the Phasing features in Revit, there are likely other approaches or variations to these common themes. A variety of creative solutions have and continue to be employed to allow the 'owners' of these 'source' models to keep these models up-to-date.
It is well established that a number of owner operators of buildings have elected to maintain 'up-to-date' Revit models (or their long term design partners choose to) in order to facilitate constant changes, upgrades and renovations to their properties. In software development circles the concept of source control is crucial to the development of any application, but even more so far large extensive applications that could have hundreds or even thousands of developers interact with the source code over many years.
