Bnotes—Advanced Keynote Manager is a Revit add-in from BREVIT LLC that provides a visual interface for searching, editing, organizing, and maintaining keynote text files. It retains Revit’s external .txt keynote-file workflow while reducing the need to maintain that file manually in a separate editor. Its main capabilities combine hierarchical browsing, usage indicators, inline editing, reference updates, file recovery, and coordination tools for cloud-hosted keynote files.
Keynote Browsing and Editing
- Hierarchical tree view: Keynotes appear in a collapsible parent/child structure. The Marketplace listing identifies blue entries as used, red entries as unused, and black entries as parent or category headings. This makes project usage visible without reviewing a flat text file.
- Live search: Entering part of a keynote key or description filters the tree. The listing describes debounced searching intended to remain responsive with thousands of entries.
- Inline editing: Users select an entry and change its key or description in the detail panel. Changes can be written back to the keynote file and applied to Revit. The guide distinguishes Update Selected, Reload From File, Refresh, and Save & Apply to Revit controls.
- Adding and reorganizing notes: Users can add child or sibling entries, edit a parent key to move an entry within the hierarchy, and delete entries with confirmation. New keys are automatically numbered to follow the existing scheme, according to the listing.
- File-wide text-case tools: Descriptions can be converted to Title Case, UPPERCASE, or lowercase. These are broad standardization operations across the file, rather than selective editorial corrections.
Usage Checking and Reference Coordination
- Usage navigation: Users can click usage indicators to reach the sheets and views where a keynote is used. This provides a connection between library maintenance and placed documentation.
- Bulk reference updates: Renaming a keynote key updates placed references across sheets in one Revit transaction. The precise coverage of element assignments, annotations, and project-specific conditions should be verified in a trial.
- Orphan detection: Identification of missing-key references and entries no longer referenced. These conditions should be treated differently: an unused library note may be intentional, whereas a placed reference with a missing key requires investigation.
- Keynote types: The product page explicitly identifies element and user keynotes. The reviewed material does not clearly establish equivalent material-keynote support; firms requiring that workflow should confirm it directly.























