It has been twenty-three days since the party entered the swamp. Somebody had a work trip, then somebody’s kid got the flu, and tonight, finally, five people are back at the table. Your paladin looks at the map, looks at you, and asks the question with total sincerity: “Why are we in a swamp?”

Nobody knows. The rogue thinks it involved a lizard. Your notes say “they follow Meren’s trail south,” which would be useful if anyone at the table, including you, could remember who Meren is.

If you searched “forgot what happened last dnd session,” here is the answer up front: this happens to every table, it says nothing about your players or your game, and you can make it stop mattering. Tonight there is a five-minute salvage protocol. Long term, there is a better idea: build the campaign assuming everyone forgets, because they will.

The gap is the villain

A weekly campaign is serialized fiction with the worst release schedule in media. A TV show gives you a week between episodes, a “previously on,” and a professional editing team making sure every important beat got screen time. Your campaign gives you two to five weeks, no editor, and an audience that was also eating tacos and rolling dice during the important beats.

Across a gap like that, human memory keeps a very specific residue. Your players will remember how the last session felt, roughly who was in it, and any moment that was funny. Dates, directions, names, amounts, the actual wording of the deal with the hag: gone. Memory holds on to stakes and feelings and quietly discards logistics, and almost everything a DM needs recalled is logistics.

Worse, everyone forgets differently. Six people walked out of the swamp session with six different swamps. Nobody is lying. Each of them rebuilt the night from their own fragments, filled the holes with plausible guesses, and is now sincerely certain. This is why the argument about whether the duke paid the party can run four minutes with everyone quoting a scene that, in their head, they can see.

Once you accept that the gap does this every single time, two things follow. You need a way through tonight, and you need to stop building sessions that the gap can kill.

Tonight: the five-minute salvage

You are at the table, nobody remembers anything, and the night is leaking. Do this, in order.

Reconstruct intent, no events. Go around the table, one sentence each: “What did your character want when we stopped?” Skip what happened. Wanting survives the gap much better than events do, and four sentences of intent will resurrect more of the session than any summary. The rogue may not remember the lizard, but she remembers she was angry at the smuggler, and that is the thread that matters.

Read the last thing written, out loud, verbatim. Your closing note, a player’s index card, the recap from the app, whatever exists. Read it exactly as written, even if it’s two lines. A written sentence from three weeks ago is testimony; everything anyone “remembers” is reconstruction. When the two disagree, the writing wins.

Canonize the reconstruction and move. Here is the arguable part, and I hold it firmly: if the table agrees it happened, it happened. When no record settles a dispute, take the version the group converges on in sixty seconds, declare it canon, and start the scene. You will occasionally canonize an error. Fine. A serialized story that contradicts itself in minor ways is a genre tradition older than the gap on your calendar, and it costs you nothing compared to a fifteen-minute continuity hearing that eats the energy the night arrived with.

Then open on motion, never on recap. After the salvage, do the thing I laid out in the recap guide: put people back in the emotional spot, in one minute, and cut to a scene where somebody has to act. A table that has just admitted it remembers nothing needs a decision to make, immediately. Nothing rebuilds a campaign in your players’ heads faster than having to care about it.

Long term: design for forgetting

The deeper fix is to stop writing sessions that require your players to remember things. Assume 80 percent of every session evaporates before the next one, and build so the surviving 20 percent is enough. Concretely:

Give everything a handle. A recurring NPC needs a hook the memory can grab: the smuggler who whistles, the baroness with the ledger, One-Eyed Sallow. Players who cannot retrieve a name for three weeks can retrieve “the whistling guy” for a year. (There’s a whole post on making names stick; the trick works on players even better than on you.)

Make stakes re-statable in one line. If the current situation cannot be said in a sentence (“we owe the smuggler a favor and the duke’s men are a day behind us”), the gap will destroy it. Complicated webs of leverage are wonderful in a novel, where the reader can flip back. Your players cannot flip back. One clean debt beats three subtle ones.

Quarantine the mystery plots. A whodunit that turns on a detail from four sessions ago is a bet that five adults will retain a clue across a month of mortgage payments and school runs. They will not, and then the reveal lands on blank faces. Run mysteries in tight arcs, one or two sessions, while the clues are still warm.

End every session with two lines for future you. What just happened, and what the table intends to do next. Ninety seconds, while everyone packs up. I made the full case in the post on ending sessions; those two lines are the cheapest insurance in this hobby.

The record beats the memory

Everything above works better with one boring foundation under it: an actual record of what was said at the table, kept by something other than a tired human.

I’ve written before that your players are the memory, and it’s true that the table collectively holds more of the campaign than any notebook. But the salvage protocol above has a step where writing beats testimony, and that step only exists if the writing exists. A DM scribbling during play is spending attention the game needs (that’s its own losing game), which is exactly why we built Loracle to sit in the Discord call, record the session, and turn it into a recap and a searchable record on its own. When the paladin asks why you’re in the swamp, the answer is one question away, in the exact words the table used twenty-three days ago.

With a record, the gap stops being scary. Sessions can be a month apart and open clean. Your campaign stops depending on anyone’s memory, including yours, and starts depending on something that never cancels, never fills the holes with guesses, and was paying attention the whole time.

The swamp, for the record, involved a lizard. The rogue was right.