Why managing a Revit family library is slow
Anyone maintaining a family library at scale hits the same wall: the work is per-file. A parameter that needs renaming across four hundred families is four hundred files opened, changed, saved and closed. Checking that those families meet the standard before they go out is the same loop again, by eye.
It is not difficult work. It is work that does not fit in a day.
Batch processing and QA tools for Revit families
A full toolkit for running a family library, every tool working across a whole set of families at once:
- Library upgrades: whole folders of families upgraded to a new Revit version in one run, with a scanner showing which version every file was saved in.
- Family housekeeping: preview images set and categories changed across a whole set of families.
- Family Grid: an entire library laid out in a project, to review it at a glance.
- Materials: materials exported from one family or a whole folder, and consolidated across the library.
- Parameters: parameters edited in batch across hundreds of families, and exported for review.
- Lookup tables and schedules: lookup tables exported, and schedules sent straight to Excel.
- Quality assurance: automated checks across a folder of families, with a review step before anything is published.