It’s September. The campaign stopped in June, for no reason anyone can name. A wedding, a vacation, two soft cancellations in a row, and then the Thursday slot just quietly stopped being a thing. Last night somebody typed “we should play again” in the group chat, four people reacted with emojis, and now you, the DM, are staring at your notes from three months ago wondering how you get six people back into a story none of them remember.

If you searched “how to restart a dnd campaign after a break,” here is the promise up front: the campaign is almost certainly still alive, the way back in takes one short meeting and one good session, and the biggest mistake you can make is the one most DMs reach for first. I’ll give you the whole restart, in order.

The mistake: trying to recap your way back in

The instinct is to treat the break as a memory problem. Write a heroic summary of sessions one through eleven, read it at the table, and resume as if the gap never happened. I’ve watched this fail at my own table and I understand exactly why it’s tempting: it feels responsible. You’re the keeper of the story, the story got dropped, so you pick it up and hand it back.

But a three-month break does something a three-week gap doesn’t. Across a normal gap, players forget logistics and keep stakes, which is why the salvage protocol for a missed session works at all. Across a whole summer, the stakes go too. Your rogue doesn’t just forget the smuggler’s name; she forgets being angry at him. The emotional threads that made the campaign feel urgent have gone slack, and no summary, however well written, can re-tension them by being read aloud. A recap assumes an audience that still cares and has merely misplaced the details. After a long break you have the opposite: people who remember they loved this, in the abstract, and feel almost nothing about the duke, the debt, or the door you left dramatically unopened.

So treat the restart as what it actually is: a re-onboarding. You are re-recruiting five people into a story they already said yes to once, which is a much easier sell than the first time, as long as you run it like a sell.

Step one: a twenty-minute session zero point five

Before you prep a single scene, get the table together for twenty minutes. Voice call is fine. This is a miniature version of session zero, and it answers two questions.

“Are we still these characters?” Ask each player, directly: are you still excited to play this person? Three months is long enough for the answer to change, and it’s enormously better to hear “honestly, I was getting bored of the barbarian” now than to watch someone sleepwalk through four sessions. Offer the cheap fixes out loud: a retooled subclass, a new personal hook, or in the extreme case a new character written into the story. A player who chose their character again five minutes ago plays differently than one who got handed their old sheet.

“What do we still owe each other?” This is the scheduling conversation, and it’s the actual reason the campaign stopped. Campaigns die of calendars, and a campaign that has already died of one once will do it again unless something changes. Re-pick the slot with calendars open. Re-agree the quorum rule. If the old slot was the problem, say so and move it. Skipping this step because it’s awkward is how you end up writing this same group-chat message in January.

Twenty minutes, both questions, done. Do it days before the first session back, so the anticipation has somewhere to build.

Step two: canonize a “story so far,” don’t perform one

You still need the table to share a version of what happened, and here is the arguable position: write it as two paragraphs, send it in the chat before game night, and declare it the official record. Two paragraphs, maximum, and the ceiling is doing the work: whatever survives the compression is, by definition, what the campaign is actually about, and whatever gets cut is stuff the story can live without.

Write the first paragraph as the situation: who the party is, what they want, and the one debt or threat that defines the current moment. Write the second as the cliff edge: where they were standing when the music stopped, and the question the next scene has to answer. If you have real records, mine them for the details your memory has sanded off. This is where months-old session recaps stop being an archive and start being a rescue: when we built Loracle’s campaign memory, the case we kept designing for was exactly this one, a table coming back after a gap long enough that even the DM needs the record. The recordings and recaps don’t fade in June. You can ask the campaign what the hag’s deal actually was, in the words the table used, and put the true version in your two paragraphs instead of the version you’d have sincerely misremembered.

Then, at the table, read it once and rule that it’s canon. Somebody will remember events differently. Across three months, everyone’s memory is reconstruction; the written version wins, the table nods, and you’ve spent ninety seconds on what could have been a half-hour continuity hearing.

Step three: restart on a hard hook, not an admin session

The first session back must be a real session, and it should be the most playable one you’ve run all year. There’s a strong pull toward an easing-in night: level up the characters, redo the shopping, “get our feet back under us.” Resist it with everything you have. An admin session confirms every quiet doubt in the room that the campaign is a chore you all used to do. Handle the bookkeeping asynchronously in the chat during the week, and spend the actual slot proving the game is alive.

Open in motion. First scene, somebody has to make a decision with a consequence hanging off it. The door you left unopened in June gets kicked in by someone else. The debt gets called. The NPC the party trusts sends word that things went badly while they were away, because time passed in the world too, and a world that moved without the party is instantly more real than one that waited politely under a tarp. You want a player leaning in by minute ten, texting the group something in character by the next morning. That text is the campaign restarting; everything before it was setup.

And when the night ends, end it the way that would have saved you in June: on a live question, with the last five minutes spent booking the next session before anyone logs off. The restart is finished the moment session thirteen happens on schedule, and no sooner.

The campaign was never dead

Here’s the exit thought, and I believe it literally: a campaign with no scheduled session is paused, and a paused campaign holds its value for a shockingly long time. The characters keep meaning something to the people who played them. The goose oath stays funny. What decays is the connective tissue, the names and debts and unopened doors, and that decay is only fatal if nobody kept a record.

So keep one, starting now, whichever way you keep it. Loracle does it by sitting in the Discord call and turning each session into a recap and a searchable campaign memory, which means the next break, and there will be a next break, because you are adults with jobs, costs you nothing but the time off. The story waits, in full, exactly where you left it. Three months from now, “we should play again” can be a plan instead of a wish.