Managing multiple Revit builds

[Mbruno-JDB]

We consult with a number of different architects on many different projects.

Some simply state the base version of Revit for their projects, i.e. Revit 2019.

Some are very precise, i.e. Revit 2019.1.3

Sometimes we've applied more hotfixes than the architect has and need to roll back to get to the version they want.

My question is, if we have one project using Revit 2019.1.3 and we get a new project that wants to use Revit 2019.3.2 (number is random, don't stress).  Would we need to maintain different versions of Revit, or just tell the higher version that we can't accomodate.   Are the build numbers that critical?

[RSomppi · Accepted solution]

---

@Mbruno-JDB wrote:

Are the build numbers that critical?

---

If you are linking models and not actually working within the same files, I think that most of the time it is not that critical. If push comes to shove, the default should be that everyone is on the latest build.

[Mbruno-JDB]

Most models are all shared and linked through BIM360.  It's rare that we exchange models anymore.

[RSomppi]

My response applies to network and cloud based projects.

[MarkNoble-WPM]

Can you roll back to a previous build?  The structural engineering team has one build but a new engineer who got a new computer has a newer build of R22.  Can we roll her build back to match the rest of the team or does the whole team have to now update to the newer build?

[RSomppi]

It's usually best to update.

[Mbruno-JDB]

I had the same thing happen.  Architect had request Revit 2019.2.3.  However, after a couple of years, I couldn't give that build to a new person.  That project is still ongoing.