Revit's keynotes live in a bare .txt file nobody dares touch — edited in Notepad, broken on sheets, full of entries no one uses. Ledger puts a real manager over it: see what's actually used, fix what prints as ?, and take the whole library to Excel and back — with nothing written until you've seen the change.
Revit gives keynotes one dialog and no answers: no usage, no history, no safe way to edit. So the .txt gets edited raw — and the mistakes surface on printed sheets, as a ?.
Ledger reads the model's linked keynote file and holds every edit as a draft — the .txt is written once, when you say so, and Revit's keynote table reloads in the same gesture.
Ledger opens on the linked keynote file as a tree. Green: a keynote tag is placed. Amber: elements carry the key, but no tag yet. Grey: never used in this model. A category's dot and counts roll up its branch, and expanding a keynote shows the evidence — which views tag it, which family types and materials carry it; views and family types each with a button to go and look. Search by code or text; the filter chips are the same filters as the typed search tokens.
Revit cannot create a keynote file at all — Ledger writes the .txt and links it. Start from Uniclass 2015's eleven tables, MasterFormat's divisions, OmniClass's fifteen tables, GuBIMclass's functional groups, or empty. And when a file is linked but unreadable, Ledger names the actual obstacle — a disconnected drive, a moved folder, a permission — instead of claiming none is linked. Route keynote… re-points the model at the real file; a new file is never offered as the fix.
The active MasterFormat divisions (North America). Fill in sections under each. © CSI.
A card at the top lists every placed keynote tag with no key, and every tag showing a key the file no longer has. It says how many are on a sheet right now — those print as ? for the client — opens the view each one lives in, and bulk-deletes the ticked strays. The library itself is untouched; this is tag surgery, not file surgery.
Audit grades the whole library in three tones. Red: tags showing a key the file lost, a parent that no longer exists, a hierarchy that loops back on itself, the same code entered twice. Amber: elements carrying a key nobody defined, and the fault a shared library really accumulates — two codes holding the identical sentence, which print the same on a sheet and cannot be told apart. Grey: the housekeeping totals. Copy report hands the findings to whoever owns the fix.
New categories and keynotes, edits, deletes, drag onto another entry to re-parent — Tab and Shift+Tab do it from the keyboard. Every change is a draft: a banner flags them, Save to file writes the .txt once and reloads Revit's keynote table in the same gesture, Reload throws the drafts away. And Rename key… rewrites the model's tags and elements along with the key, so nothing is left pointing at a code that no longer exists.
Ledger remembers the exact text its library came from. When the .txt has moved on since — a colleague edited it on the share while your drive was down — Save to file refuses to overwrite. The same reconcile preview opens with the direction reversed and says so: “Someone edited office-keynotes.txt since Ledger loaded it. This is what saving your version would do to the file — rows shown as DELETE are theirs, not yours.” Nothing reaches the file until you commit.
Export the library, renumber and rewrite it comfortably in Excel, and import it back: Ledger shows every add, change and delete before the file is touched. Broken rows block the commit; repaired ones are noted rather than refused; and deleting a keynote still shown by placed tags demands an explicit tick. Ledger also remembers every workbook it exported — Up to date, Library changed, Excel pending, Conflict or File missing.
Compare the project's library against the office master keynote file — read-only by construction, and the window says so. Tick what to bring in, with a warning wherever a pulled change rewrites text already placed on sheets, and a confirm gate before anything placed is rewritten. Prune reviews the never-used entries the same way.
History shows every change committed through Ledger, and the net difference between any two days. Edits made to the .txt outside Ledger are detected against the copy the model keeps, and recorded too. That same copy keeps you working when the network drive is down — the save simply waits for the file to come back. And one button exports a self-contained HTML report: summary, integrity audit, recent changes and the full library with its dots, openable on any laptop without Revit.
Click any element in Lens and its keynote code resolves to the sentence it prints, with its type and its parent. Click a keynote tag and Lens says outright whether it prints as ?. It reads Ledger's own store — the resolved library held for thirty seconds so a click stays instant, and dropped whenever the document changes — and classifies with the same rule the panel's list uses, so the two surfaces can never disagree about what counts as broken. The coordinator who never opens Ledger still sees the keynote truth on the element in front of them.
This is an actual HTML report Ledger exports — self-contained, works offline, shareable as one file. Scroll it right here, or open it full-screen.
Ledger ships on the Data panel of the BIMIO tab. Open the library, see what's really used, and never let a ? reach a printed sheet again. Revit 2024–2027, full trial, no card.