ArchHubBABOOMDownload

Software supported releases

BBM-STD-91 · V0.1 · The Manual V0.5 §11.3, BEP V0.5 §9.2/9.2.1, BBM-STD-65, BBM-STD-69, BBM-STD-70, BBM-STD-73 and BBM-STD-74 keep a pointer to this matrix and their own project/asset records only.

Download WordAll standards

BBM-STD-91-SOFTWARE_SUPPORTED_RELEASES-V0.1 | Office standard | 4 November 2026 | V0.1 | Private controlled WIP draft for office review

VersionDateChange
V0.12026-11-04First issue: closes rows,,,,,,,,,,, and top-gap 12 / §1.3 "Software lifecycle and supported-release matrix" + template alignment (..148)

1 Purpose and owner#

This standard is the one owner of the office supported-release matrix for Revit and its companion tools. The Manual V0.5 §11.3, BEP V0.5 §9.2/9.2.1, BBM-STD-65, BBM-STD-69, BBM-STD-70, BBM-STD-73 and BBM-STD-74 keep a pointer to this matrix and their own project/asset records only. The BIM Manager owns the matrix; the IT owner records installed builds; licences are in BBM-STD-94.

Support status comes only from the Autodesk previous-versions list: a release not listed there has neither support nor downloads. Hardware follows the Autodesk system requirements published for the qualified build, not an office legacy inventory.

2 Revit supported-release matrix (checked 2026-11-04)#

The office template BBM-ARC-TMP-R23 is authored in the oldest Revit release in office use (currently Revit 2023) and must open and upgrade cleanly in Revit 2023–2027; a new project starts in a supported release by upgrading the template and recording the §5 upgrade test; the qualified build per release is a recorded field.

ReleaseAutodesk support statusNew projectsQualified build (record field)IFC exporter lineIFC 4.3 RVSeed / template
Revit 2027Supported (listed)Allowed after the §5 upgrade test of the template passesRecord exact build; latest update 2027.3 (15 Sep 2026)revit-ifc 27.x; latest 27.4.0.30 (30 Oct 2026), which exports IFC4x3Only after a test export from the project build passes the project IDSProject seed upgraded from the office template per §4, upgrade test and hash recorded
Revit 2026Supported (listed)Allowed after the §5 upgrade test passesRecord exact buildLatest revit-ifc release for 2026, recorded with build and hashSame ruleSame
Revit 2025Supported (listed)Allowed after the §5 upgrade test of the template passesRecord exact buildLatest revit-ifc release for 2025, recorded (25.4.40 added the IFC4.3 Reference View exchange requirement)Same ruleSame
Revit 2024Supported (listed)Allowed after the §5 upgrade test of the template passesRecord exact buildLatest revit-ifc release for 2024, recordedSame ruleSame
Revit 2023Not supported: not on the Autodesk previous-versions listNot allowedExisting projects only: frozen build recordedFrozen exporter build recorded; no changeNot usedAuthoring release of the office template BBM-ARC-TMP-R23 and the library; legacy, recorded risk

Default IFC profile stays IFC 4.0.2.1 Reference View. IFC 4.3.2.0 (ISO 16739-1:2024) is used only by recorded approval when the sender build and receiver both pass a test exchange; IFC2x3 only when an appointment or authority profile requires it; authority submissions use the schema stated by the authority (BBM-STD-85).

2.1 Legacy rule (Revit 2023)#

A project already running on Revit 2023 may continue only with: a recorded risk acceptance (project lead + BIM Manager), the frozen build and exporter recorded in BEP §9.2.1, and an upgrade plan naming the target supported major and the trigger (next stage gate or appointment change). No new project and no new appointment runs in Revit 2023. The office template and library stay authored and saved in Revit 2023 as the oldest release in office use; this is a recorded legacy risk.

2.2 Companion tool fields#

Each release row in the register workbook also records:

FieldRule
DynamoVersion bundled with the qualified Revit build, exact build recorded from the installed product. Graphs saved in Dynamo 2.x need a migration test in the target Dynamo before use (BBM-STD-73)
AutoCADRelease and build used for DWG exchange and CAD standard work (BBM-STD-66); DWG save format recorded per appointment
Add-ins and checkersName, version, hash, compatible Revit majors; admission per BBM-STD-73
IFC exporterPackage version, release date, hash, schemas/MVDs it supports, receiver verified (per BBM-STD-65 §4 compatibility sheet)
System requirementsLink to the Autodesk system requirements for that build; office hardware is checked against it
Help linksCite the Autodesk help for the qualified release, not an older release

3 Library save version#

Families, detail libraries, materials and templates are saved in the office template's authoring release, the oldest Revit release in office use (today Revit 2023; as refined by). No upgrade happens inside the library: a newer project opens and upgrades a copy on load. Revit cannot save an upgraded file back to an earlier major, so a library item is never saved in a newer major and then shared to older projects. When the office stops using its oldest release, the template and library move together: the curator releases a tested upgraded copy at the new oldest release and records the upgrade build and hash; the old copy is archived, never edited.

4 Seed and legacy library upgrade#

The office template BBM-ARC-TMP-R23, R23 detail collections and other Revit 2023 library assets stay in Revit 2023. To bring one into a project: copy it, upgrade the copy in the qualified build of the project's major, run the BBM-STD-65 §5 fixtures and the §5 upgrade test, and record the build and new hash. Never save an upgraded copy back into the template or library.

5 Upgrade test#

A release is qualified for new projects or for an in-project upgrade only after these steps pass on a copy, in the exact build:

StepPass condition
OpenSeed/project opens without blocking errors; warnings counted against the previous build
UpgradeUpgrade completes; links, families and add-ins listed with any failures
SyncWorkshared model synchronises with central / cloud model; worksets and permissions intact
IFC exportExport with the controlled preset; file passes the buildingSMART IFC Validation Service (schema)
IDS passExport passes the project IDS in the named checker and version (BBM-STD-89)

Record build numbers, preset IDs, hashes, results and the tester; independent check by QA; BIM Manager decision. An appointed project keeps its major release until an authorised upgrade; no "or later" permission.

6 Lifecycle review#

Review this matrix when Autodesk publishes a new Revit major, when a release leaves the previous-versions list, and at least every 12 months. The review updates support status, qualified builds, exporter lines, the library save version (§3) and the legacy list (§2.1), under one ChangeID in BBM-STD-51.

References#

  • Autodesk, previous versions available to subscribers: https://www.autodesk.com/support/account/manage/versions/previous-versions, checked 2026-11-04.
  • Autodesk, support lifecycle policy: https://www.autodesk.com/support/account/manage/versions/support-lifecycle, checked 2026-11-04.
  • Autodesk, Revit 2027 updates release notes: https://help.autodesk.com/view/RVT/2027/ENU/?guid=RevitReleaseNotes_2027updates_html, checked 2026-11-04.
  • Autodesk revit-ifc releases (27.4.0.30, 30 Oct 2026; 25.4.40, 14 Jan 2026): https://github.com/Autodesk/revit-ifc/releases, checked 2026-11-04.
  • ISO 16739-1:2024 (IFC 4.3.2.0): https://committee.iso.org/standard/84123.html, checked 2026-11-04.
  • buildingSMART IDS 1.0 (June 2024): https://github.com/buildingSMART/IDS/releases, checked 2026-11-04.
  • buildingSMART IFC Validation Service: https://technical.buildingsmart.org/services/validation-service/, checked 2026-11-04.