Documentation is the unsung hero of great roleplaying games. I've been running campaigns for decades, and this is the hill I'll die on — writing down what happens at the table and sharing it with your players transforms scattered memories into a story everyone can trust. It also, occasionally, makes you look like a genius. But we'll get to that.
Your Players Have Already Forgotten
Your players are going to forget. Not because they're careless, but because they're human. What was "five minutes ago" for their characters might have been three weeks ago in real life. By the time they're back at your table, that crucial clue you dropped has been filed away next to last night's dinner order.
That mismatch creates friction. I've seen it turn into arguments: the DM knows the story one way, while players insist on their version of events. And sure, you can roll with it, let the winnebago stand in for the wendigo, but each compromise chips away at the foundation of your plot. Soon the whole story risks wobbling like a Jenga tower.
DMs rarely face this problem. Most of us keep careful notes: binders, spreadsheets, digital files. The disconnect isn't in the DM's preparation, but in the gap between clear notes and hazy player memory.
The Dragon's Hoard Problem
Most DMs already document obsessively. Character sketches, half-finished maps, lore fragments. We hoard them like dragons on piles of paper and pixels. The trick is simple: make those notes shareable.
When I hand my players the same descriptions I wrote for myself (places, NPCs, fragments of history), suddenly we're all working from the same page. No more arguments about whether the innkeeper's name was Darion or Darius. No more second-guessing the last session's choices.
The result? A more consistent world, where players use the material to deepen their decisions and catch connections they'd otherwise miss. They stop being passengers and start being co-authors of the shared story.
Spoilers Are a Feature, Not a Bug
A fair concern: "If I hand out my notes, won't players learn things they weren't supposed to know?"
Sometimes, yes. And that can be a strength, not a flaw.
Take Lira, a half-elf fighter/wizard in my home game. At the table, the players met her as the first mate of a sailing ship. My notes, however, also revealed that she grew up in Waterdeep, grew restless with wizard training, and took to the sea to build her career. None of that came up in play. But when the players read it later, it added richness to the character.
Think of it like the back matter in a published adventure: pages of lore about NPCs and places that rarely surface during the session. Rather than locking that information in the DM's binder, why not give players access? They don't need it, but it gives them hooks to think about between sessions. Like a Marvel credits scene, it rewards those who want more without demanding it from everyone.
Write It Down Before You Forget It Wrong
Memory is unreliable. One player swears the goblin chieftain wore a red cloak, another remembers it as blue. Without documentation, that becomes a debate. With documentation, you have a clear record: the recap everyone can agree on.
I write recaps after every session. Sometimes they're straightforward summaries. Sometimes they're in-character, more like a bard's dramatic retelling. Either way, they give players a reliable anchor for what happened. I even invite players to fact-check me. Because occasionally it's me who misremembered.
The result is continuity, sanity, and a story that doesn't collapse under "didn't we already kill that guy?" Players revisit the notes between sessions, theorize about story threads, and stay immersed in the world even when the dice are packed away.
The Secret Bonus: Accidental Genius
Here's the secret: documentation can make you look brilliant.
Writing down the connective tissue of your world forces you to see patterns you might otherwise miss. Suddenly two unrelated threads line up like they were destined to meet. To players, it looks like masterful foreshadowing. To you, it's often a happy accident discovered while rereading your own notes.
In one of my campaigns, I realized a character's parents were lighthouse keepers tied to the larger plot, not just background detail. Which meant that a simple childhood song they once taught her became the key to reactivating a magical beacon. I hadn't planned that twist from the start. But when the dots connected, it landed like a carefully orchestrated reveal.
You don't need to start big. Write a recap. Share a single NPC backstory. Build from there. The world gets more consistent, the players get more invested, and every now and then, when the threads you forgot about line up perfectly, you get to look like you planned the whole thing.
