The temptation to maintain a transfer log in Google Sheets or Excel is understandable. Spreadsheets sort, filter, and calculate totals instantly. But for holders who deliberately keep signing devices offline, a cloud-connected ledger introduces the very exposure they are trying to avoid.
The Minimum Viable Paper Log
We recommend a bound ledger—not loose sheets—with numbered pages. Each entry should capture:
- Transfer date (local time, with timezone noted)
- Source vault label
- Destination vault label or external address (last four characters only)
- Transaction identifier (if available from a block explorer printout)
- Amount and asset type
- Signers present (for multisig)
- Your initials and date signed
Why Bound Books
Loose pages get misfiled. A bound ledger creates a chronological record that is harder to alter without leaving evidence. When we reconcile client records, the physical integrity of the notebook often tells us whether entries were made contemporaneously or reconstructed later.
Pairing Paper with Printed Confirmations
Every transfer should have a companion document: an exchange withdrawal email, a printed block explorer page, or a signed memo from a co-signer. We staple these behind the corresponding ledger page during reconciliation sessions.
When to Start Fresh
If your current notes are scattered across sticky notes, phone photos, and half-filled spreadsheets, do not try to patch them. Begin a new bound ledger with a cross-reference table mapping old labels to new vault names. We cover this in our Cold Wallet Documentation session.