Dungeon Master & Game Master Guides

Running a game is a skill you can practice, not a talent you either have or lack. The difference between a session that drags and one players talk about all week usually comes down to a few repeatable habits: preparing the right things, keeping scenes moving, and making combat fast enough that nobody reaches for their phone.

Prep the Situations, Not the Script

Most new game masters over-prepare plot and under-prepare material they can use when players go off script. Instead of writing what will happen, prepare what exists and what people want. A useful prep list for a single session fits on one page:

• A strong start: the opening scene, ideally already in motion (an ambush, a messenger, a door being kicked in).
• Three to five scenes or locations the party is likely to visit, each with one interesting feature.
• NPCs with a want: name, one mannerism, and what they want from the party. That last line does most of the roleplaying work.
• Secrets and clues: a short list of facts the players could learn, not tied to any single scene, so you can drop them wherever they fit.
• One or two encounters built and balanced in advance, plus loot.

If your prep time is tight, the 30-minute prep framework turns this list into a timed routine.

Structure a Session Like a Three-Hour Show

A typical home session runs three to four hours. Treat it as having a shape rather than a list of events.

Phase	Rough time	What you do
Recap	5 minutes	Ask a player to summarize last session. You learn what they remember and care about.
Opening scene	15 to 30 minutes	Start with momentum. Avoid opening on shopping or a long rest.
Rising action	Most of the session	Alternate exploration, social scenes, and challenges so no single mode runs too long.
Climax	30 to 60 minutes	A big fight, a revelation, or a hard choice.
Wrap-up	10 minutes	End on a hook, hand out XP or milestones, ask what players enjoyed.

If the climax is not going to fit, cut a middle scene rather than rushing the ending. Stopping on a cliffhanger is also fine; it gives players something to argue about until next week.

Pacing at the Table

Pacing problems usually show up as energy problems: side conversations, long planning debates, one player dominating. A few techniques help:

• Cut to the next interesting moment. Travel with nothing at stake can be one sentence: "Three uneventful days later, you reach the ford."
• Use a clock. When planning drags, introduce pressure: the guards change shift in ten minutes, the ritual finishes at dawn.
• Spotlight rotation. Track who has not acted in a while and ask them directly: "Ilsa, what are you doing while they argue?"
• End scenes early. Leave a conversation once its key information has landed. Players rarely miss the extra five minutes.

Run Combat Faster

Slow combat is the most common complaint at D&D tables. Most of it is lost time between turns, not on turns. In 5e you can trim a lot without changing the game:

1. Roll initiative for groups. The rules already let the DM make one initiative roll for a group of identical creatures, so six goblins act together.
2. Use average damage. Monster stat blocks list an average next to each damage roll. Using it saves dice-counting.
3. Announce who is on deck. "Mara, you're up; Tom, you're next." The next player plans during the current turn.
4. Track initiative visibly. A shared list or an initiative tracker ends "wait, whose turn is it?"
5. Let monsters retreat or surrender. The DMG includes an optional morale rule; even without it, cowardly bandits fleeing at half strength ends the fight when the outcome is already clear.
6. Build tighter encounters. Fewer, more interesting monsters beat a swarm of identical ones. The encounter builder helps you check difficulty before the session.

Give every fight a second objective (hold the bridge, grab the idol, save the hostage) and it stops being a slugging match even when the dice are cold.

Guides Worth Reading Next

• Session Prep in 15 Minutes: the shortest workable prep loop, for weeks when life gets in the way.
• How to Run a Session Zero: the checklist that prevents most mid-campaign table conflicts.
• How to Keep Track of NPCs: a system so recurring characters keep their names and voices.
• How to Handle Player Backstories: weaving PC history into the plot without letting it take over.
• How to Write a One-Shot Adventure: the best practice ground for a new DM.
• Mystery Adventure Design for D&D: redundant clues so the case never stalls.
• Plot Twists for D&D Campaigns: seeding reveals that feel earned instead of arbitrary.
• NPC Generator: instant names and personalities for the shopkeeper you did not plan.

Keep Notes You Will Actually Use

After each session, take five minutes to write down names you invented, promises NPCs made, and unresolved threads. Those notes are what make a campaign feel consistent months later. Whether you use a notebook or a tool such as Anima, a free in-browser app with a linked wiki and a live DM screen for initiative, dice, and the session log, the habit matters more than the format. For broader GM resources, browse the Dungeon Master Toolkit Hub.

Frequently Asked Questions

How long should a D&D session be?

Three to four hours is the most common length for home games, with a short break in the middle. Shorter two-hour sessions work well online or for groups with busy schedules; plan one main scene plus one smaller one.

How much prep does a DM need per session?

Many experienced DMs prep 30 minutes to an hour once a campaign is running. Prep NPC motivations, a few locations, secrets, and one or two encounters; skip scripting dialogue or plot outcomes.

How do I make combat in D&D 5e go faster?

Roll one initiative for groups of identical monsters, use the average damage listed in stat blocks, tell the next player they are on deck, and let enemies flee or surrender once a fight is decided.

What should a new DM run first?

A short published adventure or a one-shot designed for a single session. It lets you practice pacing, rulings, and combat before committing to a long campaign.