Unique Numbering
PremiumMulti-parameter sequential numbering with rule builder and preview. · 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 Unique Numbering 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
Unique Numbering appears in your ribbon automatically - ready to use.
4
Activate License
Enter your Premium key to unlock full features.
Ecosystem · Parameters
Try NexionTools completely free.
Get full access to all 40 premium Revit® plugins. No credit card required.
Why Unique Numbering exists
Numbering is the job that looks like it should take ten minutes. Doors need marks in a sensible order. The order needs to follow the building - level by level, left to right - not the order Revit happened to create the elements. And the numbers have to be unique, which you only discover they are not when a schedule shows two of the same.
How Unique Numbering works
Pick a category and a sort order - level, then left-to-right and top-to-bottom, is usually what a drawing set expects. There is a scope-to-selection option when you only want to renumber the elements you have already picked in the model.
Build a numbering rule: prefix, separator, start number, step, zero padding, suffix, and whether the count restarts per level. A live sample shows the result as you type.
Add more than one rule if a single pass needs to write to several parameters - a mark and a comment, for example, each with its own format.
Generate a preview showing the old and new value for every element, with counts for what will be assigned and what will be skipped.
Assign, and everything is written in one transaction.
Before
Numbers are typed by hand in whatever order elements were selected, and duplicates surface in the schedule.
After
Numbering follows a rule and a spatial sort order, and you see every value before it is written.
When to reach for it
- Door, window and room numbering that has to run in plan order rather than creation order.
- Renumbering after a layout change has made the existing sequence meaningless.
- Writing a mark and a secondary reference in one pass, each formatted differently.
What it does not do
- It writes to parameters that exist and are writable. It does not create them.
- There is a Clear All Values button that empties every target parameter on every element in scope. It runs immediately, without asking - Ctrl+Z is the only way back, so be sure of the category and the scope before you press it.
- Skipping already-numbered elements is a toggle. Check where it is set before running on a partly numbered model.
- Writing a formatted value to a whole-number parameter scrapes the first run of digits out of it, so "D-001" lands as 1, and a value with no digits at all lands as zero.
- The preview table shows the first fifteen hundred rows on very big categories; the counts cover everything.
- Sort order is spatial and level-based. A sequence that has to follow a circulation route rather than a grid is not something a sort can infer.
Questions
- How do I renumber doors in Revit in plan order?
- Revit numbers by creation order, which almost never matches the order a drawing needs. Here you choose a spatial sort - by level, then left to right and top to bottom - and the numbering follows that instead.
- Can it restart numbering on each floor?
- Yes. Reset-per-level is part of the rule, so the counter starts again from the rule's start number on each floor rather than continuing from the ground floor. If you want level two to begin at 201, that is the start number you set.
- Can it write to two parameters at once?
- Yes - add a second rule targeting a different parameter with its own prefix and padding, and both are written in the same pass.
- What stops it creating duplicates?
- The preview shows every value before anything is written and flags any that collide - though a flagged duplicate is still written if you go ahead, so the preview is the check rather than a gate. Skipping already-numbered elements is an option too, so a second run does not renumber what is already correct.