Coulter BIM Information Management

A common challenge I encounter on projects is a reluctance to upgrade Revit models to newer years or versions. I do understand this hesitation—many remember older transitions that caused headaches, such as issues when moving from Revit 2014 to 2015 with structural columns (or similar examples). Stories like these often spread through word of mouth and become embedded in company standards, making teams wary of upgrading. However, the reality today is that holding on to outdated versions brings more risk than benefit. Pre-construction is often the best time to move models forward, before design information becomes heavily embedded across multiple disciplines.

The Autodesk “Previous Versions” Rule

Autodesk subscription customers are entitled to run the current release plus a limited number of previous versions. At present, that effectively means a four-year window of supported versions. These are the versions that Autodesk guarantees you can download, install, and activate, and they are also the only ones eligible for technical support, hotfixes, and updates.

Anything older than that may still run if it is already installed, but it is outside Autodesk’s entitlement rules. That creates risk: if a new member of staff joins, or if a machine needs to be replaced, reinstalling older software may not be possible. You could quickly find yourself locked out of a version you were relying on.

Why Staying Current Matters

Upgrading isn’t only about licensing—it’s also about project efficiency and risk management:

• Consistency across the team – All consultants, contractors, and internal staff need to work in the same model year to avoid compatibility problems.
• Smooth coordination – Coordination platforms, add-ins, and plugins are usually tested and certified against the latest releases, not legacy ones.
• Better support – Sticking to supported versions means Autodesk can help if something goes wrong.
• Future-proof handover – Deliverables such as COBie, IFC, and other data exports are cleaner and more reliable when produced from current versions.

Timing the Upgrade

The safest point to enforce upgrades is before detailed design starts. Once detailed design begins, models become the live production base for all subsequent drawings, schedules, and specifications. Having half the team on older software and half on newer versions is a recipe for disruption.

By setting a clear cut-off—all projects must be upgraded before entering detailed design—you protect the integrity of your models, simplify coordination, and future-proof your deliverables. Obviously we want to start in the latest stable year too.

Conclusion

The days of keeping projects on outdated software for years are behind us. Autodesk’s rules, combined with the practicalities of collaboration and handover, mean that standardising on the current four supported years is the only sustainable way forward. If you haven’t yet upgraded your projects, now is the time—before detailed design begins and the cost of changing later becomes too high.