Growth Tracker
PremiumTrack element counts over time to detect model bloat. · Explore the live interface below - every control works exactly as it does inside Revit®.
Architecture
Structure
Steel
Precast
Systems
Insert
Annotate
Analyze
Massing & Site
Collaborate
View
Manage
Add-Ins
NexionTools
Select
Highlight
Rooms
Parameters
Sheets & Views
Data
Manage
QC
Test it Live - exactly as if you are in Revit
Loading interactive demo…
Get Started in Minutes
Four simple steps to bring Growth Tracker directly into your Revit® environment.
1
Create Account
Sign up for a free NexionTools account - no credit card required.
2
Download Installer
One installer, 52 professional Revit® tools. Under 15 MB.
3
Open Revit
Growth Tracker appears in your ribbon automatically - ready to use.
4
Activate License
Enter your Premium key to unlock full features.
Ecosystem · QC
Try NexionTools completely free.
Get full access to all 40 premium Revit® plugins. No credit card required.
Why Growth Tracker exists
A model that opens in forty seconds today opened in fifteen last spring, and nobody can say what changed. The usual explanation is "it got bigger", which is true and useless. Without a record of what the element counts were three months ago, there is no way to tell whether the furniture library tripled, someone exploded a CAD import, or it is just normal progress.
How Growth Tracker works
Take a snapshot and the tool records categorised element counts plus the numbers that actually drive model weight - file size, views, sheets, groups, CAD imports, Revit links, family types, and the warning count broken down by warning text.
Every snapshot is scored out of a hundred with a letter grade, weighted across six things that make models heavy: file size, CAD imports, groups, the family catalogue, the views-per-sheet ratio and warnings. Bloat warnings name the specific offenders - exploded CAD lines, hundreds of groups, thousands of generic models.
Snapshots are kept as a per-project history, so the second time you run it you already have something to compare against.
Pick a baseline - or two - and compare. Growth is shown per category, so you see which part of the model actually expanded, with a sparkline across recent snapshots for the trend.
Snapshots can be renamed, so "before furniture load" is a meaningful baseline months later, and the snapshot or the comparison exports to CSV or Excel.
Before
Model bloat is noticed as a feeling about speed, with no data behind it.
After
You can point at a category and a date and say what grew, which turns a vague performance complaint into a specific one.
When to reach for it
- Establishing a baseline at a project milestone so later growth is measurable.
- Investigating a model that has become slow, to find which category is responsible.
- Tracking whether a cleanup effort actually reduced anything.
What it does not do
- It counts elements and records the file size at each snapshot. What it cannot tell you is open time - that depends on hardware, links and views as much as on what is in the model.
- History starts when you take the first snapshot. It cannot reconstruct what the model looked like before you began tracking.
- It reports and compares; it deletes nothing and never opens a transaction, so a run leaves nothing on the undo stack. Acting on a finding means going to the relevant cleanup tool.
- On a non-English Revit the imported-line detection mis-reads native lines as exploded CAD, which produces a false critical warning about CAD lines.
- If the history file cannot be written - a locked profile folder, no disk space - the snapshot is lost when you close the dialog, and nothing tells you at the time.
Questions
- Why is my Revit model getting slower?
- Usually accumulation - more elements, more families, more views, often in one specific category rather than evenly. Element counts over time are the fastest way to find which one, which is what the snapshot history is for.
- Where are the snapshots stored?
- In a JSON file on your own machine, one per project, named after the document title. It is not stored in the model - a colleague opening the same central file starts their own history - and two files that happen to share a title will share one interleaved history. The last two hundred snapshots are kept; older ones drop off.
- Can I compare against two different points in time?
- Yes. A second optional baseline lets you see a change against both a milestone and the most recent state at once.