A Player's Bullet Journal for Your TTRPG Campaign (The Table Historian Setup)

You're the one who takes notes because nobody else will. Here's a bullet journal system built for the player at the table, not a wiki nobody reads. Most note systems assume you can write full sentences between turns. At the table, you can't. This one is built for how live play actually works.

A player bullet journal for your TTRPG campaign is a retrieval system, not a record: the kind of setup you can scan in ten seconds when your party stops mid-scene to ask who that smuggler from session three was. You flip open your notebook, find the name, and read it out loud.

This is a guide for the player who's been there with a pen since session one: the table historian, the one who wants a lightweight structure that holds up under the chaos of live play.

Why Most Note Systems Fail Players

It plays out the same way every time. A player, engaged and organized, sets out to write everything down properly. A paragraph on every NPC, a prose recap after every session.

By session three, they've stopped filling it out.

At the table, you're managing HP and spell slots, watching for your turn, keeping your character sheet straight. Writing prose is a completely different task. It doesn't fit alongside everything else you're doing.

Scriv the Bard puts a name to the result: a "play-by-play, chronological account of what happened", choc full of underlining, asterisks, and side notes in margins. A play-by-play log and a retrieval-optimized log are two different objects. Confusing them is what most engaged players do.

TrailsWeaver captures the failure in one note, written mid-session and found weeks later:

"What the fuck does grumpy guy, hates guards, map?? even mean?"

That note isn't a failure of effort. It's a failure of retrieval.

The Two Modes Every Player Lives In

Fiona Hopkins describes TTRPG note-taking in four phases: worldbuilding, prep, at-the-table, and reflection. As a player, two of those phases are where you live: at the table and after the session. Each needs something different from you.

At the table, the goal is fast capture. Hopkins puts it directly: "I want as few barriers to writing things down as possible." You're leaving breadcrumbs for future-you, who will be sitting in a different chair four weeks from now trying to remember why that locked door mattered.

After the session, you have five or ten minutes to clean up the chaos. Add context and apply tags; follow the loose ends that branched. This is also where callbacks happen: you write "that's the third time they mentioned the harbor" and circle it.

A fast-capture method with no structure falls apart at retrieval; a prose-heavy one falls apart during live play. A bullet journal, done right, handles both.

Three Sections and One Key

Sly Flourish says it plainly: "Our notes are just for us. They don't have to carefully capture and record every aspect of our campaign as though we were going to hand it to someone else." He's talking about GMs, but players are the same. Your notebook is a memory aid for future-you, not a wiki. Three sections and one shared key cover almost everything.

The Key (One Page, Up Front)

You define a small set of symbols, one per category, and use them consistently. That's the whole system:

• @, NPC name
• !, rumor or unconfirmed information
• ?, open question or unresolved thread
• #, location
• *, important item or object
• >, action you need to take (ask the GM, follow up, investigate)
• underline proper nouns inline (NPC names, place names) as you write them, so they pop on a fast scan
• box location names if you want to distinguish them from NPCs at a glance
• [ ], quest or task checkbox; check it off when resolved

Six symbols is plenty. The goal is to scan a page of session notes and pull out every @ name or ! rumor in ten seconds. If your key requires a decoder ring, it's already too complicated.

The Session Log (Most of the Notebook)

Each session gets a dated page. Fast capture, one-line entries, tags applied as you write them.

Session 14, [date]
! The harbormaster is taking coin from someone outside the city
@ Mireille, fence at the Broken Compass, nervous, knows more than she says
? Why did Orren leave town three days before the fire?
# The Copper Vault, underground, two exits, third implied by the smell

Four entries, each retrievable, none more than five seconds to write.

After the session, close the ? entries that got answered and write a one-line summary at the top: "We found Mireille, confirmed the Vault exists, Orren is still missing." That's what you'll read three weeks from now.

The NPC Quick-Reference Section

Two facing pages near the front of the notebook for the @ names. When a name appears in your session log, add a one-liner here: name, role, one distinguishing detail, and the session number.

@ Mireille, fence, Broken Compass, nervous, first: S14
@ Orren, missing cartographer, connected to the fire?, first: S11
@ The Bailiff, name unknown, works for Harbormaster, hostile, first: S14

When the table asks "wait, who was the fence?", you find it in ten seconds. Skip the backstory, the stat block, and the portrait. The one-liner is what jogs your memory.

Don't worry about writing the "correct" one-liner for an NPC. What you notice is shaped by who your character is. Advanced RPGs makes this concrete: at the same table, a bard's entry for an NPC reads "Vellin laughed too long at the 'warehouse fire' joke" while the paladin writes "Vellin avoided oath language; eyes flicked to dock guards." Your one-liner will look like yours. That's useful: it tells you what your character thought, which is exactly what you need when you're roleplaying the follow-up six sessions later.

The Rumor Log

A running collection for the ! entries. Write the rumor, note who said it and when, and put a [ ] checkbox next to it. When it gets confirmed or debunked, check it off and write one word next to it: confirmed, false, complicated. Quests and tasks work the same way: [ ] open, [x] done. If your party picked up a job in session eleven and closed it in session fourteen, the checked box tells you without rereading both sessions. Unconfirmed information is the texture of a campaign, and the checkbox is how you keep the live list clean.

Names First, Everything Else Second

The most important thing to capture at the table is also the thing most players most often forget: names.

MinvarPG identifies NPCs, quests, and storylines as the core tracking targets. At the player level, simplify further. Capture:

• Names. Every named NPC, location, and item. Names are what you most often need and most often forget.
• Anything framed as a secret, a rumor, or an unconfirmed claim. If the GM lowers their voice to tell you something, it goes in the rumor log.
• Your character's emotional beats. If your character had a meaningful moment, a revelation or a choice that cost something, one line. It pays off when you're roleplaying the callback six sessions later.
• Open questions. Anything that felt unresolved.

Combat blow-by-blow, rules lookups, flavor text: let it go.

The Ten-Minute Cleanup

Right after the session, before you close the notebook, do five things:

1. Write the one-line session summary at the top of the log.
2. Check ? entries from tonight. Close the ones that got answered; open new ones if they branched.
3. Add new @ entries to the NPC section.
4. Move new ! entries from the session log to the rumor log.
5. Write one or two lines about what the party is doing next session.

That last step is easy to skip, and skipping it costs you every single week. The note isn't a summary of what happened. It's a door back into the fiction for next-week-you, who opens the notebook cold. Advanced RPGs calls this the pre-next-session anchor: "Next: stake out Warehouse 9 after sundown; if no ship, question Vellin with the green-wax crest." Written last. Read first. You enter the next session already inside it.

Gnome Stew puts the stakes plainly: notes that are too sparse cause "discomfort that can shake the confidence of the note-taker and can disrupt the mood of the game." Fifteen minutes of cleanup is the insurance against that.

The Retrieval Problem the Notebook Can't Solve

A physical notebook works for this. The tactile engagement and the table presence are real, and nothing breaks mid-session.

The retrieval problem is also real. Paging through a physical notebook to find a rumor from session seven takes time, and cross-referencing across sessions means flipping back and forth.

Inkless uses the same bullet-journal-style tagging logic: tag an NPC name once and every mention across the campaign connects to it. You're not flipping through a physical notebook looking for session seven. The tags build a campaign index as you play, so you can pull up every mention of Mireille or the harbormaster without remembering which session they first showed up in. The rumor log lives alongside your session notes. Your whole table can see each other's notes in real time, which means you're not the only one keeping track anymore.

If you're the player who takes notes because nobody else will, that last part is worth something.

Start Small. Grow as You Play.

A notebook with a key, one session log, and three NPC entries is more useful than a polished prose recap you abandon by session three. Start with the key. Write your first session log tonight.

Future-you, the one who remembers the smuggler's name at the exact right moment, will thank you.