Home / Guides / Ledger
Data panelLedger

The keynote file, finally managed.

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 2024–2027Edits stay drafts until you saveKeeps working when the .txt is offline
Why Ledger exists

Your keynote library is a text file from 2004.

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 ?.

Revit on its own
  • The keynote file is edited in Notepad, in the right tab-format, or it breaks.
  • A tag whose key was renamed prints ? on the client's sheet — silently.
  • Nobody knows which of 1,000 keynotes the model actually uses.
The same library, in Ledger
  • Every keynote shows a dot: tagged, assigned, or never used at all.
  • Every tag that would print ? is listed — one click opens its view, one click deletes the strays.
  • Bulk edits go via Excel, and every add, change and delete is reviewed before the file is touched.
How Ledger works · one afternoon with the library

Open it. See the truth. Fix it. Prove it.

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.

The truth, first

Every keynote, with a dot that tells you if it earns its keep.

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.

New to Revit: a usage answer per keynote — Revit's own dialog cannot say if a key is used at all.
BIMIO · Ledger — Keynote managerBIMIO
Ledger
1197 keynotes · 214 tagged · 356 used in this model.
Save to fileNew file…Route keynote…Export…Import…Reload
K:\Standards\Keynotes\office-keynotes.txt
Search the library by code or text…
ShowTaggedAssigned, not taggedUnusedIn this viewMaster…Prune…HistoryReport
F30Masonry12 tags · 31 elems
F30/110Facing brickwork, stretcher bond2 tags · 5 elems · 3 types
Tagged in2 tags in 1 view · on 1 sheet: A431
VIEWLevel 02 — Detail at parapet · 2 tagsOpen view
Carried by5 elements · 3 types
TYPEBasic Wall : FAC Brick 102 — 3 instances · WallsSelect
F30/115Blockwork, fair-faced8 elems
F30/190Glazed brick special
Tagged — a keynote tag is placedAssigned — elements carry it, no tag yetUnused — not in this model
The ? on the sheet

The tags that print as ? — found, named, and one click from fixed.

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.

New to Revit: the ? found before the client does.
BIMIO · Ledger — Keynote managerBIMIO
Keynote tags that print as ?7
3 with no key · 4 showing a key this file doesn't have · 2 of these are on a sheet right now — those print as ? for the client.
Select allSelect none3 of 7 selected · 2 on a sheetDelete 3 tags
Empty(no key)Level 02 — Detail at parapet · sheet A431Go to Level 02 — Detail at parapet
Not in fileM40/021Roof plan — Membrane upstand · sheet A502Go to Roof plan — Membrane upstand
Not in fileF30/112Level 05 — Core wall junctionGo to Level 05 — Core wall junction
Edit without fear

Change anything. Nothing is written until you say so.

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.

New to Revit: keynote editing with a draft state and one deliberate save — not a live wire into the .txt.
BIMIO · Ledger — Keynote managerBIMIO
Ledger
1197 keynotes · 214 tagged · 356 used in this model.
● Unsaved changes — click “Save to file” to write the keynote .txt.
Save to fileNew categoryNew keynoteEditDeleteFrom selectionShow in modelRename key…Audit
Search the library by code or text…
ShowTaggedAssigned, not taggedUnusedIn this viewMaster…Prune…HistoryReport
F30Masonry12 tags · 31 elems
F30/110Facing brickwork, stretcher bond
F30/115Blockwork, fair-faced — edited
F30/191New keynote — glazed special (draft)
Tagged — a keynote tag is placedAssigned — elements carry it, no tag yetUnused — not in this model
Excel, round trip

Bulk edits belong in Excel — the review belongs here.

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.

New to Revit: a keynote import that shows its plan — instead of replacing the file and hoping.
BIMIO · LedgerBIMIO
Import & reconcile
office-keynotes.xlsx — nothing touches the keynote file until you commit.
Show unchanged rows
1 add · 1 modify · 1 delete (1 in use) · 1192 unchanged
ADDF30/191Glazed brick special — new entry under F30
MODIFYF30/115Blockwork, fair-faced → Blockwork, fair-faced both sides
DELETE · IN USEM40/021Removed in the workbook — 'M40/021' is used in this model (1 tag); deleting it leaves its tags and elements with a broken key.
I understand 1 placed keynote will be deleted — its tags keep showing a key the library no longer defines.
CancelCommit 3 changes
The office standard

Pull from the master. Never push to it.

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.

New to Revit: an office keynote standard that flows one way — into projects, never out of them.
BIMIO · LedgerBIMIO
Compare with the office master
Marina Tower — Block A ← office-master-keynotes.txt
Hide identical
The master is only ever read. Nothing here can write to it — changes go one way, into this project. Keynotes that exist only in your project are listed for review and cannot be removed from here.
1 only in master · 2 text differs · 0 moved
Select allSelect none2 of 3 selected · 1 placed in the model
TEXT DIFFERSF30/110Master wording differs
Placed in the model — this changes what prints on the sheets.
IN MASTER ONLYF30/120In the master, not in this project
TEXT DIFFERSM40/050Master wording differs
I understand 1 of these is placed in the model, so its text changes on the sheets showing it.
CancelBring in 2 keynotes
Memory and proof

It remembers what changed — even what changed behind its back.

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.

New to Revit: a keynote library with a history and an audit — for a file format that has neither.
BIMIO · LedgerBIMIO
History
office-keynotes.txt — every change Ledger committed, newest first. Pick two days to see the net difference between them.
EDITEDF30/115Text changed2026-08-28 17:41 · fmartinez
ADDED · XLSXF30/191Added via Excel import2026-08-27 12:03 · fmartinez
EDITED · FILEM40/050Changed outside Ledger — detected on load2026-08-25 09:12 · outside Ledger
Close

Stop editing keynotes in Notepad.

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.

← PreviousInlay