Let me deflate that dread right now, because most of it is aimed at the wrong job. You think you’re about to perform a one-person show, improvise a living world, and adjudicate a legal system you haven’t finished reading, all at once, for an audience. What you’re actually going to do on Friday is read a situation out loud, ask “what do you do?”, and then react to whatever your friends say. That’s the whole loop. Everything else in this post is just making that loop smoother, and none of it requires you to finish the rulebook, because I’m going to tell you which three rules carry a first session and which 290 pages can wait.

Run someone else’s adventure. This is the hill I’ll die on

Your first instinct is to homebrew. You have a world idea, you’ve had it since high school, and running D&D finally gives it somewhere to live. I’m asking you to save it for later, and I want to be honest about why, because “beginners should use published adventures” is standard advice and the standard reasons undersell it.

The real reason: a first-time DM has exactly one scarce resource, and it’s attention. On Friday night you’ll be tracking initiative, remembering an NPC’s voice, watching the quiet player, and deciding whether a goblin would really do that, all simultaneously. Every point of attention you spend remembering your own worldbuilding comes out of that budget. A published adventure moves the entire “what’s behind the door” question onto paper, so your live brain can do the only job that matters live: reacting to your players.

There’s a second reason nobody says out loud. Your homebrew world is precious to you, and precious is fragile. When your players ignore the lore hook and befriend the shopkeeper for an hour (they will), you’ll feel it in your chest. When they do that to a published module, it’s funny. First sessions go better when the DM has nothing to protect.

Pick a short published one-shot for your table’s system, read it twice, and you’re prepped. The classic starter sets are built for exactly this, run well straight off the page, and cost less than the pizza. If money is the concern, you need to buy even less than you think to get a first game to the table.

Prep nouns, not script

Here’s the mistake I made, and the mistake every new DM I’ve talked to made: writing prose. The opening narration, word for word. The NPC’s speech. The clever transition. It feels like preparation because it takes hours.

Then the session starts, a player asks the innkeeper a question your script didn’t anticipate, and the script is dead. Two paragraphs in. All that prose was prep for a session that was never going to happen, because sessions are conversations, and you can’t script the other side of a conversation.

What survives contact with players is nouns. Prep like this, one page total:

• Five names you can hand to anyone the players decide to talk to. Barkeep, guard, random farmer. Nothing derails a new DM faster than name-panic, and nothing sounds more like a real world than the farmer instantly being “Hedda.”
• Three scenes you expect: probably a social scene, an exploration scene, a fight. For each, one sentence of situation and one sentence of what the opposition wants. Not what happens. What’s true when the players arrive. They supply what happens.
• One secret the session is about, written at the top of the page, so that whatever chaos occurs, you always know what the night is secretly steering toward.
• The monster stats, printed or bookmarked, so combat never involves searching.

That page, plus a published adventure underneath it, beats ten pages of prose every time. The one-page DM walks into the session ready to react. The ten-page DM walks in with something to defend.

The three rules that run the whole night

You don’t need the rulebook read. You need three procedures cold, because between them they cover about 95% of a first session:

The core roll. A player wants to do something with an uncertain outcome: they roll a d20, add the relevant modifier from their sheet, and try to beat a number you pick. Easy thing, 10. Normal thing, 12 to 15. Hard thing, 18. That one sentence is the engine of the entire game. When in doubt, ask for a roll against 13 and narrate what happens. No table has ever noticed the difference between a DM who computed the exact right difficulty and a DM who confidently said “give me a 13.”

Advantage and disadvantage. Circumstances helping? Roll two d20s, take the higher. Circumstances hurting? Two d20s, take the lower. This one mechanism replaces a hundred fiddly modifiers, and saying “you know what, that plan’s clever, roll with advantage” is the single fastest way to make a player’s night.

The combat loop. Everyone rolls initiative once; on your turn you move and do one thing; the DM runs the monsters on their turns. Combat is just the core roll wearing armor. Keep it moving, describe hits with a little color, and let a dying goblin rout the survivors when the fight’s outcome is obvious, because the last two rounds of a decided fight are where session momentum goes to die.

Everything else, and I mean everything, gets this ruling: “Here’s what we’ll say for tonight; I’ll look it up after.” Say it in exactly those words, cheerfully, as many times as needed. A confident wrong ruling delivered in four seconds keeps the story alive. A correct ruling that took six minutes of page-flipping kills the scene it was meant to serve. Your players did not come over to watch you be right. They came to find out what’s behind the door.

You are the world’s biggest fan, and that’s the performance

The performance anxiety deserves its own section, because “am I entertaining enough?” is the fear under all the other fears, and it’s aimed at a job you don’t have.

Watch a great home game (a home game, and I mean this precisely, since the actual-play shows that inspired you are staffed by professional voice actors and edited for broadcast, and comparing your Friday night to them is comparing your jog to the Olympics). Mostly the DM is doing three small things on repeat: describing a situation in two or three sentences, asking “what do you do?”, and reacting with visible delight to whatever comes back. The players entertain each other. The DM deals them situations and then leans in.

Visible delight is the actual skill, and you already have it. When the bard proposes something unhinged, the table doesn’t need you to have a plan for it. The table needs your eyes to light up. “Oh no. Okay. Roll for it” is, word for word, the best line in DMing, and it requires zero preparation and no funny voices. Do voices if they’re fun for you. Skip them freely if they’re terror. Nobody has ever quit a campaign over an unvoiced innkeeper.

Friday night itself: a script for the first ten minutes

The hardest part of the first session is the first ten minutes, when the table is still a living room and you have to make it become somewhere else. So here’s a concrete opening, since this is the one place a little script genuinely helps:

Recap the premise in two sentences, even though there’s nothing to recap yet (“You’ve all taken the job. The pay is bad, the wagon leaves at dawn”). Then go around the table and have each player introduce their character with one look-and-vibe sentence, no backstory speeches. Then start in motion: the wagon is already rolling, the tavern door is already banging open, the first scene is already happening. Ask the player on your left the magic question. From there, the loop carries you.

If your players are also new, send them what a first session feels like from their side of the screen before Friday, and if this whole group is freshly assembled, a short session zero beforehand will save you from discovering mismatched expectations mid-scene. End the night ten minutes earlier than you want to, on an unresolved beat if you can manage it, and book the next date before anyone stands up. Scheduling, and I say this with the weariness of experience, is the boss monster of the entire hobby.

The mistakes you’ll make, pre-forgiven

You’ll make these. Everyone does. Knowing them in advance converts them from failures into checkboxes:

• You’ll get a rule wrong with total confidence. Fine. Ruling stands for the night, correct it next week.
• A fight will drag. Fine. End it early; routing enemies are more interesting than dead ones anyway.
• Your players will skip the content you were most excited about. Fine. Un-encountered content is reusable; next week it’s somewhere else, wearing a different hat.
• There’ll be a silence where nobody knows what to do, including you. Fine. “So, what’s the plan?” aimed at the whole table has broken ten thousand of those silences.
• You’ll finish the night certain you were mediocre. Almost every first-time DM reports this, and almost every one of their players reports having a great time, in the same conversation. The DM is the only person at the table grading the DM.

The one mistake worth actively guarding against is trying to hold it all in your head afterward. Who was Hedda, what did the party promise her, which goblin got away. Session one generates more canon than you expect, and by session three the details have gone soft, which is when a new DM starts quietly dreading prep. Write things down the same night, or let something else do the remembering: Loracle sits in your Discord voice channel, records the session, and turns it into the recap and the growing campaign wiki on its own, so the world you’re building keeps itself straight while you learn the fun parts of the job.

Because here’s the honest close. Your first session will be rough in spots, and it will also, very probably, work, because the game is built to work. The dice make drama on their own, your friends came wanting to have a good time, and the bar for a first DM is on the floor: deal situations, ask the question, delight in the answers. Read the one-shot twice, write your page of nouns, learn three rules, and go find out what your friends do when the tavern door bangs open. There’s a version of you three sessions from now who’s genuinely relaxed behind the screen, and the only route to them runs through Friday.

Notice what’s missing from that story: a bad plot. A rules argument. A player conflict. The campaign was good. Everyone liked it. It died anyway, of the most boring cause there is, and if you’ve played for a few years you have attended several funerals exactly like it.

Session zero is the meeting where you prevent that death, plus a few others, before the campaign starts. Most guides treat it as a character-creation workshop with a safety talk bolted on. Those things belong in it. But I want to convince you that the single most important thing you decide at session zero is the schedule, that it deserves more time than tone and setting combined, and that ninety minutes is enough for all of it if you know what you’re doing. By the end of this post you’ll have the full agenda.

What session zero actually is

Session zero is a get-together before the campaign begins where the table decides, out loud, what game you’re playing and how you’re going to sustain it. No dungeon, no initiative. You’re answering two questions: what are we playing (tone, setting, content, characters) and how are we playing it (schedule, attendance, table norms). Everything worth covering falls under one of those two, and the second one is the one that kills campaigns, so we start there.

The scheduling contract comes first

Campaigns die of scheduling. Say it out loud at session zero, because your players have all watched it happen and naming it gets everyone on the same side. Then negotiate the following, for real, with calendars open:

A recurring slot, not a rolling negotiation. “Every other Thursday, 7 to 10” is a campaign. “We’ll find a time each week in the chat” is a countdown timer. If I could know only one thing about a table and had to bet on whether it’s still playing in a year, I’d want to know whether the slot is fixed, sitting in everyone’s calendar like a standing meeting. Pick it together at session zero while everyone’s motivated, because you will never again have this much collective goodwill to spend on calendar Tetris.

The quorum rule. Decide now, while it’s hypothetical and nobody’s feelings are involved: how many players can be missing and we still play? I push hard for “we play unless two people are out.” One absence cancelling the game hands every single player a veto over everyone else’s Thursday, and the reschedule spiral from the opening of this post is what that veto costs. Playing with someone missing is mildly awkward. It is enormously better than the alternative. Agree on how absent characters are handled (they fade into the background, someone else runs them, the party leaves them guarding camp) and move on.

What “can’t make it” means. A campaign slot is a commitment to five other people, and it’s fair to say so. The norm that works: you show up unless something real comes up, you give notice as early as you can, and “I’m kind of tired” gets you sympathy and an expectation that you show up anyway. This sounds strict written down. In the room it takes thirty seconds and everyone nods, because everyone has been the person who dragged themselves to game night tired and was glad they came by the second scene.

Who owns the calendar. One person sends the “we’re on for Thursday” message. Usually the DM, but honestly the best pick is your most organized player, who has been waiting their whole life for this assignment.

That’s the contract. Ten minutes of conversation, and it does more for your campaign’s life expectancy than anything else in this post.

What game are we actually playing

Now the fun half. The goal here is to surface mismatched expectations while they’re still cheap to fix. A player who wanted grim political intrigue and a player who wanted to befriend every monster can absolutely share a table, but only if they find out about each other at session zero instead of session three.

Pitch the campaign like a TV show. Two or three sentences: genre, tone, what the party does. “Low-magic mercenary company, war-torn borderlands, morally gray, think Black Company” sets completely different expectations than “high-magic heist romps in a wizard city.” Your players cannot read your mind, and the campaign lives in your head in far more detail than in theirs. Say the elevator pitch out loud and watch their faces.

Set the rating and the lines. Decide together what’s on screen, what happens off screen, and what stays out of the story entirely. You don’t need formal terminology for this. “Anything anyone doesn’t want in the game?” asked sincerely, with the DM offering one of their own first to make it safe (“I don’t do harm to kids in my games”), gets you ninety percent of the value. Write the answers down. And agree on a mid-session mechanism, any mechanism, for “I’m actually not okay with where this scene is going,” because it’s much easier to invoke a rule you set up at session zero than to interrupt a scene cold.

Build a party, together, that has a reason to stay together. Characters made in isolation produce the classic session-one problem: five strangers in a tavern, each waiting for a reason to care about the other four. Make characters in the same room, and require two things of every sheet: a reason this character stays with the group when things get hard, and one connection to another player’s character. Siblings, old war buddies, debtor and creditor, anything. Two sentences per player, established in ten minutes, and your party enters session one already tangled together in a way that would otherwise take a month of play to grow. This is also your best insurance against the lone wolf who works alone (great in a novel, poison at a table, and completely fixable at session zero by just asking for a different concept).

The boring house rules. Phones at the table, how rules disputes get settled mid-session (DM rules now, look it up after, I’m right sometimes), who’s hosting, how food works. Two minutes each. Deciding them now means never having a tense version of the conversation later.

Play something before you leave

A session zero that’s pure meeting sends everyone home having done paperwork about a game instead of playing one. So end with dice. Run one short scene, twenty or thirty minutes: the party’s first job interview with their patron, a bar brawl, the last fight of the war that ended yesterday. New players get their first taste of how the game flows before the campaign has any stakes, and everyone drives home having actually played, which is the feeling that carries a table to session one.

If you have brand-new players at the table, this scene matters even more. I’ve written about what a first session actually feels like from the player’s side, and about getting a group together in the first place if you’re reading this without one yet.

The 90-minute agenda

Steal this outright:

That last row is real, by the way. Momentum is worth protecting, and the strongest opening move a campaign can make is the date of session one going into the chat while everyone’s still in the room.

The part everyone forgets by session twelve

One more thing, from someone who builds campaign-memory software for a living. Everything you decided at session zero (the tone, the lines, the quorum rule, why the ranger owes the warlock money) lives in exactly one place: your table’s collective memory. That memory is five busy adults, and it leaks. By session twelve, nobody’s sure what was agreed about character death, two players remember the patron’s deal differently, and the ranger’s debt has been silently forgotten by everyone except the warlock’s player, who is waiting.

Write session zero down. One page, pinned in the group chat, is plenty. The campaigns that go multi-year keep their agreements and their history somewhere outside their heads. That’s the actual job of my product, for what happens after the dice start rolling: Loracle sits in your Discord voice channel, records the session, and keeps the recaps and the growing campaign wiki so the story’s memory stops depending on anyone’s Tuesday brain. Session zero is the one session it can’t keep for you, because session zero happens before there’s anything to record. So bring a notebook to this one.

Then pick a Thursday, hold the meeting, play the scene, and post the date. Campaigns that get a real session zero start better, and a year from now they’re the ones still meeting, because the thing that kills the others got handled in ninety minutes, back before it ever had a chance.

You get a list. Buy these three books. Consider these seven alternate systems. Here are twelve ways to find a group, four virtual tabletops, a character creation walkthrough, and a paragraph about how the most important thing is to have fun. Somewhere around option thirty you close the tab, and eight months later you still haven’t played.

You have plenty of information. What you’re missing is somebody willing to tell you what to actually do.

So this guide has an opinion. Answer two questions and you’ll get exactly one recommended path — the specific next thing to do this week, and permission to ignore everything else.

Every path below is written out in full, so if you’d rather just read the whole thing, read the whole thing. The buttons only decide which one gets emphasized.

If you’ve never played, and you know people who’d try it

Run a one-shot.

This is the single highest-leverage decision on this page, and almost everyone gets it backwards by reaching straight for a campaign. A campaign is a months-long commitment from five adults with jobs. A one-shot is one evening. You’re asking people to watch a movie together that happens to have dice in it, and that’s an easy yes.

Here’s your week:

1. Text four people. Four players plus you is the sweet spot — enough that the table has energy, few enough that everyone gets to do things. Invite seven and three of them will spend the night on their phones.
2. Pick a night, three weeks out. Far enough that nobody has a conflict yet, close enough that it stays real.
3. Skip the books. The basic rules are free. The three-hundred-dollar shelf can wait until you know you like this.
4. Use a pre-written one-shot. Somebody has already done the hard part. Writing your own adventure for your first session is like building a bike before your first ride.

A successful first session ends with somebody saying we should do that again. That’s the whole bar.

If you’ve never played, and you don’t know anybody

Play online, and join a game as a player before you try to organize one.

The instinct is to recruit strangers into a group you run. Don’t. You’d be learning the rules, learning the tools, and managing five people you’ve never met, all at once.

Instead:

1. Find a beginner-friendly game with an experienced GM. Look for the words “new players welcome” and take them literally — those GMs are volunteering to teach.
2. Expect to bounce off the first group. This is normal and not a referendum on you. Tables have chemistry or they don’t, exactly like any other set of five humans.
3. Play something short. A published one-shot or a short adventure. Somebody’s four-year homebrew epic, where everyone already shares five hundred inside jokes, is a hard room to walk into cold.

One honest warning: online text games move at a pace that feels glacial if you were imagining a lively table. If you want the thing you’ve seen on podcasts, you want voice.

If you’ve played once or twice and want it to become a real thing

Commit to four sessions.

“Campaign” is a scary word that means indefinite, and nobody wants to sign an open-ended contract. Four sessions is a season of television — a real arc, a real ending, and a natural moment to ask whether everyone wants more.

Then do the two things that actually determine whether a group survives:

• Have a session zero. Twenty minutes before anyone rolls anything. What kind of game is this — heroic, grim, silly? What’s off the table? How do we handle someone missing a week? Most groups that fall apart do it over a mismatch nobody said out loud, while the plot was going fine.
• Pick the night and defend it. Every other Tuesday, always. The groups that survive treat the calendar slot as the real commitment. The groups that “find a time that works” every week quietly stop playing by session five.

If you want to be the one running it

Run a published one-shot for three people, and leave the worldbuilding for later.

Worldbuilding is the most fun part of DMing and the worst possible place to start. You will spend six weeks drawing maps of a continent your players will never visit, and by the time you’re done the excitement has drained out and nobody’s played anything.

The reverse order works:

1. Take a published adventure. All the prep is done. Your job is to read it.
2. Three players. Fewer people means fewer rules questions, fewer things happening at once, and much less to hold in your head while you’re still learning.
3. Say yes more than you think you should. A player wants to try something the module didn’t anticipate? Let them, and figure it out. “Sure, roll for it” is the most powerful phrase you have.
4. Let the rules be wrong. You will get things wrong all night. Nobody at the table knows. Make a call, keep moving, look it up afterward if you care.

The world you build after four sessions with real players in it will be better than anything you’d have invented in a vacuum, because it’ll be built out of the moments that actually landed.

The thing every path has in common

Here’s how it actually falls apart. You schedule one session. It goes fine — better than fine, everyone laughs, somebody does a voice. Then the week gets away from you, and the second session requires a specific person to open the group chat and propose a date, and that person turns out to be nobody.

Be the person who sends the text.

A note on remembering any of it

Something nobody warns you about: three sessions in, the texture starts evaporating.

The big beats survive. Everyone remembers the dragon. What goes is the innkeeper’s name, which one of you promised what to the guard captain, whether the amulet was cursed or just ugly. Four weeks pass between sessions, real life happens in between, and you open the night with fifteen minutes of “wait, who was that guy?”

Every group solves this eventually. Some tables have one person who takes notes, which works right up until that person wants to actually play. Some keep a shared doc that’s beautifully maintained for three weeks and abandoned by week five.

That gap is the reason Loracle exists — it sits in your Discord voice channel, and turns the session into a recap and a searchable wiki afterward, so nobody has to be the scribe. But that’s a problem for session four. Right now you have a more important job.

Text the four people. Pick the night.

Four faces turn to you, waiting. You have no idea who Garrick is.

You invented him three sessions ago—a blacksmith, a grudge, a limp—and the table loved him so much they wrote his daughter into their backstories. He’s the best NPC you never planned. And right now, in front of everyone, you’re about to retcon him into a stranger.

That’s improv at the table. It’s the heart of running D&D—you can prep a dungeon, but you can’t prep the moment a player asks your throwaway shopkeeper what he thinks about the war. So you riff. You invent a name, a grudge, a limp. The table leans in. It’s great.

And then, three sessions later, it quietly falls apart—because the best thing you made, you made on instinct, and nothing was there to catch it.

Here are the improv mistakes that do the most damage—and the one that does the quiet damage no one notices until it’s too late.

Mistake #1: Not writing anything down

This is the big one. The silent campaign-killer—and it’s exactly how you ended up blanking on Garrick.

In the moment, you are certain you’ll remember. The name is obviously Garrick. The daughter ran off with a smuggler. He hates the baron. It’s vivid. It’s burned in.

It is not burned in.

So next session, when the player walks back into the forge, you improvise again—and now the daughter is a son, the grudge is against the church instead of the baron, and Garrick has picked up a completely different accent.

The players notice. They always notice. And now you’re doing an awkward retcon in real time, breaking the fiction to patch a hole you made yourself.

The character stops meaning anything. Not because the idea was bad—because the why got lost. An NPC is only as real as the throughline you can remember.

Mistake #2: Railroading the improv

The opposite failure. You improvise an NPC, but secretly you’ve already decided what they’ll do. The players push, negotiate, get clever—and it doesn’t matter, because the NPC was always going to hand over the quest / refuse the bribe / die in the ambush.

That’s not improv. That’s a cutscene with extra steps. Players can feel the rails under the wheels even when they can’t see them, and it teaches them the worst lesson: their choices don’t move anything.

Mistake #3: Trying to fix mush with “no”

Improv comedy gives us “yes, and”—accept what’s offered, build on it. Most DMs absorb this as gospel. And taken too literally, it curdles.

If the answer to every player request is yes, and here’s more, the world goes soft. No friction, no scarcity, no stakes. The party asks the harbormaster for the fastest ship and gets it. Asks the duke for an army and gets it. Nothing is earned because nothing was ever in doubt.

So DMs reach for the obvious antidote: start saying no. Block the request. Soften it to “no, but” and call it nuance.

That’s the trap. Blocking is the original sin of improv. “No” negates what the player just put on the table—it stalls the momentum and quietly teaches them that offering anything is pointless. And “no, but” is just a block wearing a coat: the player still hears the thing you wanted didn’t happen. You haven’t cured the mush. You’ve traded a world with no stakes for a scene with no air.

Here’s the part everyone misses. The mush was never caused by “yes, and.” It was caused by a toothless and—an “and” that only ever adds gifts. A good “and” adds a complication. You keep saying yes to the player’s reality—their competence, their want, their contribution—and you let the world push back through cost, consequence, and its own agenda.

Yes, the ship exists. And it’s short two crew after a brawl, so passage will cost you sweat, not coin. Nobody got told no. The friction lives entirely in the “and.”

A worked example: “yes, and” with teeth

Here’s the situation. The party needs to leave the city tonight, and there’s exactly one ship sailing before dawn: the Gull’s Mercy. As DM, I want them on that ship—the next chapter happens at sea. But if I just hand it over, the scene is mush. So I never say no. I keep saying yes, and—and I let the “and” do all the work.

Player (Vth, the rogue): We need passage on the Gull’s Mercy. Tonight. Whatever it costs.

DM (as Harbormaster Oluf): He doesn’t look up from his ledger. “Aye, she sails before dawn—and she’s chartered full, grain to the last berth. And Reyes came in two hands short after a brawl at the Drowned Crow last night. She won’t sail undermanned, and she won’t wait.” He finally glances up. “So. Depends what those hands of yours are good for.”

I never told them no. Passage exists—yes. The “and” just keeps stacking the world on top: full ship, and a brawl opened two berths, and those berths are work, not coin. Every clause accepts the scene and tightens it. The players didn’t hit a wall; they got handed a lever.

Player (Vth): We can crew. We’re stronger than we look, and the half-orc could haul cargo all night.

DM (as Oluf): “I believe it.” He taps the ledger. “And Reyes won’t sign strangers on my word alone—last lot I vouched for walked off with the cargo. So you’ll be wanting to give me a reason. There’s a crate going aboard that nobody signed for. Tell me where it ends up, and your names go down as vouched.”

Still no “no.” I yes-and their competence—I believe it—and then the “and” raises the cost and, this is the important part, smuggles in the plot hook (the unsigned crate) as something they’re choosing, not something I’m imposing. No rails. They reached for it.

Player (Vth): Done. We watch your mystery crate, you get us aboard.

DM (as Oluf): He stamps the ledger and slides a chit across the desk. “Yes. And tell Reyes that Oluf says you’re worth your salt—she’ll take it from me. And—since you’re already curious—the man who dropped that crate paid in old crowns. Pre-siege coin. Nobody’s spent those in twenty years. Make of that what you will.”

Once they’ve bought in—paid a cost, made a choice—the “and” pays them back with interest: the vouch, and a thread that deepens the mystery they just signed up for. The scene accelerates instead of going slack.

Same NPC, same goal, three turns, and not a single “no.” The friction never came from refusing the players—it came from the world having its own weight, delivered through the “and.” Nobody got railroaded, nobody got blocked, and the party walked onto exactly the ship I needed them on—thinking it was their idea. Because it was.

The part where it all comes back to memory

Here’s the catch that ties every one of these mistakes together.

That scene only matters if Oluf shows up again. If the unsigned crate pays off. If, ten sessions from now, a player says “old crowns—wait, like the harbormaster mentioned?” and you can actually run with it.

Improv that no one remembers isn’t worldbuilding. It’s a really good campfire story you’ll never tell the same way twice.

You can do everything else right—friction that never blocks, a hook they reached for, zero railroading—and still lose it all to Mistake #1. The complication you built, the thread they took, the name of the NPC who handed it over: gone by next session unless something catches it.

Let Loracle remember the why

This is the gap Loracle fills.

You run the game. You riff, you improvise, you let the “and” carry the friction so the scene never goes soft or slams shut. Loracle records the session, transcribes it, and pulls out the entities—every NPC, the promises they made, the threads they dangled.

So when a player asks Garrick about his daughter, you search and you know: her name, where she went, why he’s angry. No retcon. No “I think it started with a G?”

The improv stays yours. The remembering stops being your job.

Riff fearlessly. We’ll keep the throughline.

Meanwhile, the best hook for that arc has been sitting in a shared doc since session zero. You read it once. You don’t remember what it said.

Every player handed you a backstory. A dead mentor. A sister who vanished. A debt, a betrayal, a home they can’t go back to. Then the campaign started, the dice came out, and those pages went quiet.

That’s the most underused resource at your table.

Backstories are hooks with names attached

A good plot hook makes a player care. The hard part is manufacturing that caring—why should the rogue risk her neck for a town she’s never heard of?

A backstory solves the problem before you start. The player already told you what their character loves, fears, and owes. They wrote you a list of buttons to press. You don’t have to invent stakes. You have to remember them.

The wizard’s backstory mentions the academy that expelled him. Six sessions later, the villain turns out to be a professor from that academy. That’s not a coincidence the players write off as lazy—it’s a payoff they’ll swear you planned from day one.

Mining the page

Read every backstory with a highlighter and pull out four things:

• People. Named NPCs—mentors, rivals, family, exes. Each one is a guest star waiting for an entrance.
• Wounds. The unresolved thing. The death they blame themselves for. This is the emotional engine of an entire arc.
• Loose ends. “I left in the night and never looked back.” Great—so what’s chasing them?
• Contradictions. A noble’s son with a thief’s skill set. The gap between those two facts is a story.

Most backstories give you three to five of these. With four players, that’s fifteen-plus hooks you didn’t have to write.

The reincorporation move

Improv has a principle called reincorporation: bring back something from earlier and the audience feels the whole thing was designed. Backstories are reincorporation on a campaign scale.

The trick is timing. A backstory beat lands hardest when the player has half-forgotten they wrote it. Sister vanished in the first paragraph of their bio? Don’t open with it. Let them adventure for two months—then have a prisoner pull back her hood. The table will lose its mind.

But that only works if you remember the detail when the moment arrives. And the moment almost always arrives mid-session, while you’re juggling six other things.

The catch (and the fix)

Here’s why this resource stays buried: backstories are long, you read them once, and the relevant line is never the one on top of your mind when you need it.

So you default to generic hooks. The town needs saving. A stranger offers gold. Functional, forgettable.

This is one of the things Loracle is quietly good at. Keep your players’ backstories alongside your session records, and every name, wound, and loose end becomes searchable. When the party captures a cultist mid-session, you can check in seconds whether anyone has history with that cult—and turn a random encounter into a personal one.

The campaign your players actually want is the one they already described to you.

Go read what they wrote. Then make it come true.

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.

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.

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.

“Wait — that’s the guy from Thornwood. We were supposed to bring his son back.”

You stare at her. You glance at your notes. The name you just said is not the name on the page. She is right. You are wrong.

This used to mortify you. After enough campaigns, it stops.

The myth

There’s a fiction at the heart of how DMs talk about the craft. The DM is the keeper of the world. You arrive at the table with the canon — notebook, binder, wiki, whatever — and the players show up empty-handed to be told things.

It has never been true.

In a campaign long enough to matter, your players hold as much of the world as you do. More, usually. They remember the NPC you invented at eleven PM and forgot by Tuesday. They quote dialogue you have no memory of writing. They argue about what really happened in session nineteen, and you nod along, because you don’t know who’s right and it would be impolite to admit it.

You’ve been running on borrowed memory for months. You just haven’t said so out loud.

What it really is

Here’s the part that took me a long time to see: this is fine.

The instinct is shame — that you should have written it all down, that you’ve failed your players. But the campaign was never a thing you held in your head and dispensed. It was a thing you all made, in the room, together. They kept their parts. You kept yours. The whole only existed when you sat down at the table.

Your players have always been the memory.

They just had no way to look at it without you.

The campaign lives in a dozen places — your prep, their notes, the scene Mike still talks about, the offhand line that became Sarah’s character’s whole arc. You’re the one with the binder, so you’ve been treated like the one with the truth. But the truth was distributed all along. Your binder is just the bit you wrote down.

What we shipped

A read-only link you can send to your players. They open it — no account, no app — and there’s the world. The characters they’ve met. The places they’ve been. The threads, sourced to the sessions where they happened.

A note on what this is. It’s not a database for your players to study so they can quiz you. It’s not a “player engagement tool.” Most players do not want homework, and a campaign that demands homework is asking the wrong thing.

It’s an acknowledgment.

For years your players have been doing the memory work — keeping notes you couldn’t, remembering scenes you forgot. The share link makes that work visible. It says: this campaign isn’t a story I’m telling you. It’s a story we’re keeping. You should be able to see what we have.

The room you’re already in

Some of your players will browse it. Most won’t. That’s fine. The point isn’t that everyone reads the wiki — the point is that the wiki is theirs. The world that exists between you isn’t locked in a DM’s binder anymore. It can be looked at. By the people who helped build it.

What changes when you send the link isn’t really their experience. It’s yours.

You stop pretending to be the source. You stop carrying the campaign like a secret you have to dispense correctly. You stop the small, exhausting performance of always knowing — because the binder is open, and what’s in it is what’s in it, and what isn’t is something you’ll figure out together, the way you always have.

You’re not the keeper of the world. You’re the one with the dice.

The world belongs to the room.

I’ll bet you anything: it wasn’t the one they prepped the most.

It was the one where everything went sideways. Where the players ignored the dungeon and befriended the monster. Where an NPC invented in desperation became the campaign’s heart. Where the story went somewhere no one—including the DM—expected.

The best sessions emerge. They can’t be planned.

The improv paradox

Here’s the tension every DM lives with:

You prep because you care. You build the world, design the encounters, write the dialogue. That’s craft.

But the magic? That happens when you throw it away. When you riff. When the players surprise you and you surprise yourself.

The barbarian adopts the goblin. The wizard makes a deal with the wrong god. The party decides to open a tavern instead of saving the kingdom.

And you roll with it. You invent. You discover the story alongside your players.

These moments are gold. They’re also the first thing forgotten.

The memory gap

Prepped content survives. It’s in your notes. The dungeon map, the NPC backstory, the plot outline—you wrote it down before the session.

But the improv? The stuff that actually made the session great?

That exists only in the moment. In the memory of everyone at the table. And memory fades.

Three sessions later, someone asks: “What was the name of that goblin the barbarian adopted?”

Silence. Nervous laughter. “I think it started with a G?”

The magic is gone.

Catching lightning

This is what Loracle is for.

Not to replace your prep. Not to generate your story. But to catch the lightning.

Record the session. Let us listen. We’ll find:

• The NPC name you invented at 11 PM when your brain was fried
• The promise made in the heat of roleplay
• The plot twist that emerged from a joke
• The lore you improvised and immediately forgot

All searchable. All sourced. All yours.

So next time someone asks about the goblin, you don’t guess. You know. And you can build on it—because nothing was lost.

Keep riffing

The best DMs aren’t the ones who prep the most. They’re the ones who can let go—who trust the improv, who play to find out what happens.

Loracle lets you do that without fear.

Riff harder. Go off-script. Let the story emerge.

We’ll remember it for you.

Session logs. NPC lists. Relationship maps. Plot thread trackers. The advice is everywhere—buy a nice notebook, develop a system, write everything down.

And it makes sense. When you’re running a campaign that spans months or years, memory fails. Players ask about the shopkeeper from session 12. They want to know what the prophecy actually said. They remember making a deal with someone, but not who.

So you write it all down. Or you try to.

The problem with notes

Here’s what actually happens:

1. You run an incredible session. The players go off-script. An NPC you invented on the spot becomes their favorite character. Someone makes a promise that will matter later.

2. The session ends. Everyone’s tired but happy. You clean up, maybe have a drink, decompress.

3. You think: “I should write this down.”

4. You don’t. Or you write half of it. Or you write it but forget the important part.

5. Three sessions later: “Wait, what was that guy’s name?”

The notes you take are filtered through exhaustion, through what you thought was important, through the limits of memory. They’re incomplete by definition.

Your notes are what you remembered to write. Not what happened.

A different philosophy

What if the expectation is wrong?

What if you shouldn’t have to take notes?

Your brain is for storytelling—for voices, for drama, for thinking on your feet when the players do something unexpected. That’s the hard part. That’s the art.

Why should you also be the stenographer?

The camera, not the canvas

Think about it this way: you’re creating something at the table. A living, improvised story. Your notebook is your canvas—where you build your world, prep your encounters, sketch your ideas.

But the session itself? That’s a live performance. And live performances need a camera, not a canvas.

Something that captures what actually happened. The NPC name you invented. The promise the rogue made. The plot twist that emerged from chaos.

Not what you planned. What happened.

Loracle’s bet

This is why we built Loracle.

Record your session. We’ll transcribe it, extract the characters, locations, quests, and items. We’ll remember what you forgot to write down.

Then, when you need it: ask. “What did the oracle say about the sword?” “Who was that merchant in Waterdeep?” “What did we promise the dragon?”

Sourced answers. In seconds.

Your brain stays free. For the next voice. The next twist. The next moment of magic at the table.

Because you shouldn’t have to take notes.