Skip to content

Ship the Revit template like software

Semantic versions, a changelog and a rollback path for the one file every project starts from.

SCAN_042 · 2,009 pts, coloured by heightfig. 1

Sample post. This copy is here to exercise the reading styles. Replace or delete it before launch.

Every project in the office starts from the same file. When that file changes, every project that starts afterwards inherits the change, whether anyone meant it to or not. Most firms still treat the template as a document someone tidies up on a Friday afternoon. It behaves much more like a dependency.

So treat it like one. Give it a version number, write down what changed, and always keep a way back.

Version numbers people can read

Semantic versioning maps onto a template cleanly. A major version breaks something a project relies on: renamed parameters, a restructured set of view templates, families swapped out. A minor version adds without breaking. A patch fixes a mistake.

The number goes in the file name and in Manage › Project Information, so anyone can check which version a model started from.

## 3.2.0 · 2026-11-03
### Added
- Fire separation line styles (1 h, 2 h)

## 3.1.2 · 2026-10-14
### Fixed
- Level heads clipped at 1:500

The changelog is the product

Nobody reads release notes until something breaks, and then they read nothing else. The format above follows Keep a Changelog, which is plain enough that nobody needs training to add to it.

Always keep a way back

Keep every released version where people can find it, and never edit a released file in place. Rolling back should be a decision, not an archaeology project.