You ran a great session. Real drama, good rolls, an NPC death nobody saw coming. You stayed up afterward and wrote a detailed recap in the Discord. You are a good GM. A responsible GM. A GM who genuinely cares about their players’ experience.

Next session rolls around. You open with “so, picking up from last time…” and one of your players goes: “Wait, who’s Velindra again?”

Velindra. The villain. That they’ve been chasing for four sessions. The one with the dragon.

The problem isn’t your players (whaaaaaa?). The problem isn’t even your recap. The problem is that you wrote it for the wrong audience, in the wrong format, with the wrong goal. And until you fix that, it doesn’t matter how thorough your session summaries are. They’ll keep going unread.

Let’s talk about why, and what to actually do instead.

---

The Real Reason Recaps Don’t Get Read (It’s Not Laziness)

Here’s a very easy thing to believe: your players skipped the recap because they’re checked out, or they don’t care enough, or they’re just not the kind of people who engage with campaign prep. And maybe one of them is a little bit of all of those things. But that’s not why recaps get ignored.

Recaps get ignored because most of them are written for the GM, not the player.

Think about it this way. Your session recap is, in structure, a project management document. It tracks what happened, what information was revealed, which plot threads advanced, and what the party needs to know going into next session. That’s useful to you. To your players, it reads like meeting notes for a meeting they were already at.

The thing is, players can care deeply about campaign events. The same players who blank on Velindra’s name will spontaneously, unprompted, remember a ridiculous moment from eight sessions ago where someone rolled a natural one at the worst possible time. They remember the things that were about them — their character’s failure, their group’s inside joke, the consequence that landed on their lap. They remember the parts of the story where they felt like the protagonist.

Your recap, written from a plot-management perspective, is usually not about them in that way. It’s about things that happened around them. And things that happened around people don’t stick — things that happened to people do.

---

The Science Part (Stay With Me for Two Minutes)

In 1885, a psychologist named Ebbinghaus memorized lists of nonsense syllables and recorded how quickly he forgot them. The resulting “forgetting curve” has been replicated hundreds of times since, and the finding is always the same: without reinforcement, people lose roughly half of newly learned information within a few days.

Your players aren’t immune to this. Two weeks between sessions is a long time. A week is long enough.

But here’s the more useful piece: memory isn’t one uniform thing that fades at the same rate across all information. Researchers studying narrative comprehension have found that what they call the event model (the big-picture structure of what happened, who did what, why it mattered) decays far more slowly than surface-level detail. The exact wording of the merchant’s threat. The specific name of the street the fight took place on. The year the war ended.

What this means practically: your players aren’t forgetting that there was a tense confrontation with a mysterious courier. They’re forgetting that the courier was working for the Merchant Council, and the Council is the same faction that burned Mira’s village, and that’s the thread that makes the next session make sense.

A good recap doesn’t retell the whole session. It re-attaches the details the forgetting curve ate to the events the players still remember. That’s a much smaller, much more achievable document than what most GMs are writing.

---

Four Things That Actually Fix This

These aren’t tips so much as ways of thinking about the recap differently.

1. Make the characters the subject of every sentence.

Go pull up your last recap. Find every sentence where the main actor is “the party.” Rewrite it so it names the character who actually did the thing.

“The party discovered a vault beneath the temple” becomes “Mira’s paranoia finally paid off since she’s the one who found the vault, and she is going to make everyone aware of this for the rest of the campaign.” “The party learned about the Merchant Council’s involvement” becomes “They all know now. The Merchant Council is funding the cult. Which means Councilor Fen, who hired them, might be dirty too.”

It sounds like a small change. It isn’t. When a player opens the Discord recap and the first sentence contains their character’s name doing something specific, they read it differently than if the first sentence begins with “the party.” They read it the way you read a text message when you’re the one being talked about. Fully, and immediately.

Do this throughout the whole recap. Every session beat should have a character’s name attached to it. Your players are the protagonists of your campaign. Make sure the recap writes them that way.

2. Structure it in three parts — and keep it short.

Most recaps fail on length before they fail on anything else. The forgetting curve applies to the recap too: the longer it is, the less of it gets read, which means the most important information, usually buried at the end, is the information that gets skipped.

The structure that works is: what happened, what it means, and what’s unresolved. Three parts. The first part covers the session’s key beats in two or three player-centric sentences. The second part is one sentence that states the stakes clearly. “They’re not just chasing a cult anymore. They might be working for the people who started it.” The third part is the thing that’s still hanging.

That third part is the most important one nobody talks about. You’re borrowing a technique from serialized television: you end on something unresolved. Not a cliffhanger, necessarily, but an open question. “And there’s still the matter of the letter Dax pocketed from the cultist’s body. He hasn’t shown anyone. Yet.” A recap that ends on an unresolved thread isn’t just a summary of the past, it’s a trailer for the next session. People read trailers. People skip meeting notes.

3. Write it within twenty-four hours.

This sounds like logistical advice but it’s actually creative advice. Your memory of the session’s best moments, the things worth including, the line of dialogue that landed, the player decision that surprised you, is sharpest the day after. By the following Thursday, when you’re building next week’s encounters, you’ll be reconstructing half of it from vibes and hoping you got it right.

Writing fast also forces you to be brief. When the session is still clear in your head, you know instinctively what mattered and what was filler. A week later, everything feels equally important and the recap balloons. Twenty-four hours in, you’ll write a tighter document almost by accident.

4. Format for the channel, not for yourself.

A Discord channel is not a Google Doc. People read text differently in Discord. They skim, they scroll fast, they process in short chunks between other messages. A six-paragraph wall of text dropped into a channel that also contains session scheduling debates and memes about critical failures is not going to get read. It’s going to get scrolled past and quietly never mentioned.

Short and scannable wins. Bold the character names and the proper nouns players need to recognize at a glance. Break every two or three sentences with a line break so there’s no unbroken wall of text. And start, not with “Session Recap” as a header, but with the most interesting single thing that happened, written like you’re texting a friend about it. The hook matters. If the first sentence doesn’t earn a reaction, the rest of the recap doesn’t get read.

If your group uses something other than Discord (group chat, email, a campaign wiki), the principle is the same; the execution adjusts. Email needs a subject line that someone would actually open: “Session 12 Recap” is not that, and “Dax is sitting on a secret and Mira is going to lose her mind” is. A wiki is a reference document, not a recap. It’s where players go when they need to look something up, not what gets them excited for next week. Keep both, but know which is which.

---

The Recap That Gets Ignored Isn’t Wasted

When your players skim the recap, forget Velindra’s name, and show up next week asking what they were doing, the work you put into that summary didn’t disappear. The act of writing it clarified the session in your own head. You know what mattered. You know which threads are live. You know what Dax’s secret is and why it’ll matter later. That clarity makes you a sharper GM at the table, even on the nights when nobody read the homework.

And the recaps that do land, the ones that get reactions, that prompt in-character Discord speculation, that make one player text another about what Mira is going to do when she finds out, those recaps build something real. They keep players emotionally in the campaign between sessions. They remind people why they’re coming back.

You don’t need your players to memorize your recap. You need it to do one thing: make them want to play again. Every word that doesn’t serve that goal can be cut.

So stop writing the project management document. Write the thing that makes one of your players put down their phone and say oh no into a quiet room on a Tuesday night. That’s the recap. That’s the one they’ll read.

---

Now Go Rewrite Last Session’s Recap

If this clicked and you want somewhere to start, go find the recap you wrote most recently. Find the first sentence that begins with “the party.” Rewrite it with a character name. Then do that for the rest of them.

Then cut the document in half. Keep the event model — the what-happened-and-why-it-matters — and cut the surface detail. End on an unresolved thread. Post it somewhere people will actually see it.

Then read it out loud at the start of next session anyway, because written recaps supplement a verbal recap, they don’t replace it. Both. You want both.

Your players will remember. And then nobody will ask who Velindra is, and you will feel the specific satisfaction of a GM whose work is landing exactly the way it was supposed to.

---

Want to go deeper? The Angry GM’s piece on the art of the verbal recap is essential reading — aggressive as always, but correct. Roleplaying Tips’ bullet-to-mini-story method is a great companion system for the verbal side. Both will make your session starts faster and your players sharper — and significantly less confused about the dragon.