It’s 7:09 on a Tuesday. The pizza’s late, somebody’s dog is barking on the call, and your rogue is asking — completely sincerely — whether they still have the cursed amulet.

They do. They’ve had it for four sessions. They were there when they picked it up.

This is the moment the recap was invented for. Not the wiki, not the binder, not the forty-page campaign bible nobody reads. The two minutes at the top of the night where five distracted adults put down their phones, climb back into people who can cast spells, and remember that last week they swore a blood oath to a goose.

Most tables wing it. “So, uh… where were we?” Someone half-narrates the boss fight. Someone else is sure there was a door. The energy that should be building toward adventure instead drains into a group-therapy session about continuity. By the time you actually start, you’ve spent fifteen minutes and a good chunk of everyone’s enthusiasm just getting back to even.

It doesn’t have to go like that. The recap is a tiny, gorgeous, wildly underrated piece of craft, and once you start treating it like one, your sessions open with a snap instead of a shrug.

So let’s get into it. All of it.

First, throw out the idea that a recap is a summary

A summary is a list of things that happened. You fought the bandits, found a map, went to town, bought rope. Accurate. Thorough. The narrative equivalent of a receipt.

A recap is not a receipt. A recap is an on-ramp. Its job isn’t to inform — it’s to transport. You’re not reminding people what occurred; you’re walking them back to the exact emotional spot they were standing in when you all said goodnight last week. The fear. The grudge. The dumb plan they were one round away from executing.

Get that distinction and everything else falls into place. You stop reading minutes from the meeting and start re-opening a story.

The single best trick: leave the pen down

Here’s a thing Hemingway did, and it’s the most useful recap advice I know even though he never ran a dungeon in his life.

He refused to write a scene all the way to the end. He’d stop while it was still flowing — sometimes mid-sentence — at a point where he knew exactly what came next. Then he’d cap the pen and walk away. The next morning there was no terrifying blank page waiting for him. There was a half-finished sentence with an obvious ending, practically begging to be picked back up.

“The best way is always to stop when you are going good and when you know what will happen next.”

A campaign is the same idea, just stretched over a week instead of a night. End your session on a comma, not a period. Don’t button everything up. Leave a door un-opened, a question un-answered, a sword raised and not yet swung. Stop while it’s still going good.

Then your recap isn’t a chore. It’s you walking back to the page and picking the pen up mid-stroke — and because your players were the ones who helped leave that sentence dangling, they remember precisely where the ink stopped. You don’t have to drag them back into the story. You just finish the sentence, and they’re already inside it.

It’s a beautiful trick. It also has one fatal dependency, which we’ll get to. (Foreshadowing. Leaving the pen down. See what I did there.)

A whole tackle box of recap styles

There is no one right way to do this. There are about fifteen, and the fun is in mixing them. Here’s the menu.

The “Previously, on…” — The classic for a reason. Channel a prestige-TV cold open: three or four punchy beats, present tense, scored by whatever’s dramatic on your playlist. Lead with names. “Kira, your hand is on the vault door. Bram, you’re still bleeding from the thing in the cellar. And nobody has mentioned the letter you all decided not to read.”

Hand the mic to a player. Make recapping a rotating job and pay for it — a point of inspiration to whoever recaps last week. Suddenly someone else is responsible for remembering, they pay closer attention all night to earn it, and you get to learn which moments actually landed (it’s never the ones you’d guess).

Recap in character. This is where it gets delicious:

  • The bard’s song. Four lines, badly rhymed, sung off-key. Comedy gold and a genuinely efficient recap.
  • The tavern rumor. Two NPCs gossip about “those adventurers” — which lets you recap and foreshadow and slip in misinformation all at once.
  • The letter home. A player writes three sentences to their character’s mother. Tells you everything about what mattered to them.
  • The villain’s status report. The big bad updates their dark master on the heroes’ annoying progress. Players love hearing themselves described as a threat.

The headline. Recap the session as a newspaper front page. “LOCAL HEROES INSULT DUKE, ADOPT GOOSE, FLEE.” Story on page 4. Whimsical, fast, weirdly memorable.

The open-loops board. Keep a running list — physical index cards are great — of every dangling thread: unkept promises, unanswered mysteries, NPCs who owe the party a favor or a knife in the back. Your recap is just you reading the three or four cards that are about to come due. Players feel the plot tightening.

The cliff. The purest version of leave-the-pen-down: end so abruptly that the recap writes itself, because everyone’s been thinking about it all week anyway.

The map pin. For the visual table — drop a pin on the map, slide the tokens to where they stood, and narrate from there. Spatial memory does half the work for you.

The 80-word straitjacket. Constraint as a feature. Force the whole recap into eighty words and you’re physically incapable of rambling about the rope you bought. Only the load-bearing beats survive.

Mix these. Sing one week, hand off the next, run a villain’s report when the campaign goes dark. Variety keeps the ritual from going stale, and the ritual is the point — same beat every week and your players learn to drop into character the instant it starts.

A small confession

That's a lot of homework for a goose joke. Picking the right four beats, remembering the NPC's name, tracking which threads are about to snap — that's real work, and it all happens after a four-hour session when your brain is a wrung-out sponge.

What if it just... showed up in your inbox? Loracle records your session and writes the recap for you — the beats that mattered, the names you'll fumble, the loops still open. See how it works →

The boring mechanics that make it sing

Style is the fun part. Logistics are what make it actually happen every week instead of just the weeks you remember to prep.

When. Top of the session, full stop. A recap at the end of last week is a nice idea that nobody’s brain absorbs while packing dice. Do it cold, at the start, when it’s load-bearing.

How long. Ninety seconds to two minutes. If you’re past three you’ve stopped recapping and started re-running. Trust the eighty-word instinct even when you’re speaking off the cuff.

What to cut. Almost everything. The shopping, the travel montage, the long rest — gone. Recap only what tonight’s opening scene actually leans on. A recap is defined by what you leave out.

Where to keep it. Have something — a pinned Discord message, a running doc, the back of a napkin. Not because you’ll read it aloud, but because Tuesday-you needs a place to find out what Saturday-you thought was important. The gap between those two people is where campaigns quietly fall apart.

How it goes wrong (and it goes wrong the same five ways)

  • The data dump. Every detail, no shape. Players glaze. You’ve recapped your way out of momentum.
  • The DM monologue. Twelve unbroken minutes. Hand the mic out before it becomes a TED talk.
  • The wrong altitude. You recap the lore and skip the feelings, or recap the feelings and skip the one fact tonight depends on.
  • The confident lie. You misremember the NPC’s name, say it with total authority, and now it’s canon. Your players will remember the wrong name forever, and it’s your fault.
  • The skip. “We all remember, let’s just go.” You don’t. You really don’t.
Still a lot of work

Notice how many of these failures are really just memory failures? The wrong altitude, the confident lie, the skip — they all come from a tired human trying to reconstruct four hours of improv from a smudge.

Loracle remembers the session exactly, so your recap starts from what was actually said instead of what you think you recall. Let it keep the record →

The catch nobody mentions

Here’s the fatal dependency I promised you.

Every technique above — the leave-the-pen-down comma, the open-loops cards, the in-character bard song, all of it — quietly assumes one thing: that you can remember the session well enough to recap it.

And a week is long. Between Saturday’s session and Tuesday’s recap there was work, and sleep, and laundry, and a whole other show you watched, and an argument about something unrelated. The dangling sentence that was so vivid when you packed up the dice is now a blur. Was the captain alive or dead? Did the NPC actually ask that question or did you just mean to have them ask it? What in the nine hells was his name?

You left the pen down on purpose. Then you lost the page.

This is the quiet tragedy of the recap as a craft: the better the unfinished beat, the more it hurts to misremember it — and you will, because you are a person, and people forget. The recap depends on a perfect record of the session, and your memory is the least reliable place to keep one.

So keep it somewhere else.

Where Loracle comes in: from raw transcript to a memory that recaps itself

This is the part we actually built, so let me show you what’s under the hood — because “AI takes notes” undersells it by a mile. The interesting work isn’t the transcription. It’s everything that happens after.

It starts simply. Loracle sits in your Discord voice channel and records the session. When you’re done, it transcribes the whole thing — every name, every aside, every “wait, say that again.” That alone solves the smudge problem: there’s now a perfect record of what was actually said. But a four-hour transcript is its own kind of useless. Nobody reads a wall of text before game night. So the real pipeline begins.

The first pass reads the session like a DM would. It writes your Quick Replay — a tight two-or-three-paragraph recap built for exactly the on-ramp job we’ve been talking about — and even gives the session a punchy episode title. Then it goes looking for things: it pulls out the characters, locations, quests, items, spells, and monsters and files each one under its canonical name with a one-line description drawn from what happened. Your raw audio becomes a cast list.

Then it maps how everyone’s tangled together. A second look extracts relationships — who killed whom, who betrayed whom, who traveled where, who quietly acquired the cursed amulet. Not a list of nouns; a graph of a living world. This is the open-loops board, built for you, automatically.

And then the enrichment passes start — and this is the good part. A single session is just one data point. A campaign is the through-line. So Loracle runs a series of passes across your whole history:

  • An entity-merge pass notices that “the captain,” “Captain Voss,” and “that guy from Thornwood” are all the same person, and quietly stitches them into one character — descriptions, relationships, and all — so your cast doesn’t fracture into a hundred half-remembered duplicates.
  • A timeline pass synthesizes each entity’s appearances across every session into something that reads like a wiki article. Click Voss and you get his whole arc, not just last Tuesday.
  • A relationship pass infers the connections that span sessions — the grudge that started in session three and pays off in session nineteen.
  • A consistency pass plays continuity cop: it flags contradictions, orphaned threads, and the duplicate NPCs you didn’t catch. (It’s the friend who says “wait, didn’t he die?”)
  • A theme-and-arc pass steps all the way back and watches for the shape of the thing — quest progressions, faction dynamics, the narrative arcs you’re weaving without realizing it.

All of that pours into a World Feed — first appearances, NPC deaths (rip), relationship shifts, campaign milestones — so the story’s evolution is something you can actually scroll. And when you edit something by hand, the system marks it as canonical and the enrichment passes leave it alone. You’re always the DM. It just never forgets.

Here’s what that does for your Tuesday. You leave the pen down on Saturday — a comma, a raised sword, a question left hanging — and you walk away without a shred of anxiety about losing the page. Because the page is kept. Three days later the Quick Replay is sitting there waiting, the captain’s name spelled right, the open loops listed, the exact unfinished sentence ready to pick back up. You read it, you feel the session click back into place, and you start the night on a snap.

Your players climb back into people who can cast spells. The rogue, you can now confirm, still has the amulet. And the goose oath remains, as ever, fully canon.

Leave the pen down. We'll hold the page.

Run the session. Loracle records it, writes the recap, builds the cast, maps the threads, and quietly keeps your whole campaign straight — so the only recap work left for you is the fun part: deciding how to tell it.

It's the campaign memory you don't have to build. Try Loracle free →