Game Master Tips: How to Pace a Session Like a Pro

Ask players why one session still gets retold years later while another was forgotten by Tuesday. Hardly anyone brings up the rules, and the lore barely gets a mention. They talk about how it felt: the knot in the stomach during the rooftop chase, or the laugh that cracked the whole table open after a dreadful pun. Most of that feeling comes down to pacing. And here's the cheerful part. Pacing isn't some gift a lucky few GMs are born with. You can learn it, the same way you once learned the grapple rules.

I've spent a slightly embarrassing amount of time thinking about tempo while building EchoQuest, because its Game Master is an AI that narrates every scene aloud. A slow scene on paper is a nuisance. A slow scene read out loud, at you, is a small form of torture. So these Game Master tips come from tabletop craft, filtered through the odd job of teaching that craft to a machine. Use them at a kitchen table full of friends. Use them too if you're writing a campaign for an AI Game Master, which can't see anybody yawning and needs the rules spelled out.

1. Frame Every Scene With a Question

Every scene should exist to answer one question. A few examples:

• Will they convince the smuggler to take them across?
• Can they escape the burning archive?
• Who is the stranger at the funeral?

Once the question has its answer, the scene is over. Cut to the next one. A scene that limps on after its question is settled drains the energy out of a room faster than anything else I know. Ever sat through ten minutes of haggling over rope after the plot had already moved on? Then you've felt it.

There's a handy side effect, too. If you can't name a scene's question, you probably don't need that scene at all.

2. Start Late, Leave Early

This one's pinched from screenwriting. William Goldman, who wrote Butch Cassidy and the Sundance Kid, put it bluntly: "You always attack a movie scene as late as you possibly can." So enter a scene as close to the interesting moment as you can manage, and get out the instant it's done.

• Don't narrate the whole walk to the tavern. Open with the players already at the table as the informant slides into the empty chair.
• Don't play out a goodbye to every NPC in town. Cut to the road.

Mike Shea, who writes as Sly Flourish, applies the same thinking to the first scene of the night and calls it a strong start. His favourite trick is blunt as well: "Starting with a fight gets everyone right into the game." I'd add that it beats twenty minutes of recap every time.

3. Alternate Tension and Release

Nonstop action wears players out, and nonstop calm sends them to sleep. So swing between the two:

1. Tension: a chase, a fight, a negotiation where nobody trusts anybody, a lock being picked while footsteps get closer
2. Release: a campfire chat, a hot meal, a quiet discovery, a joke between old friends
3. Rising tension: a new threat appears
4. Climax: the big confrontation
5. Release: consequences and reflection

Robin D. Laws wrote a whole book about this swing. Hamlet's Hit Points sorts stories into beats and tracks "their ups and downs from hope to fear and back", with Hamlet plus two films, Casablanca and Dr. No, as its worked examples. It's a useful lens at the table, honestly. If the last several beats all pushed fear up, your players are overdue a win.

Quiet scenes are where characters actually grow, so please don't skip them. Just keep them short.

4. Use Clocks and Deadlines

A deadline creates urgency without railroading anyone:

• "The ship sails at dawn."
• "The ritual completes at the third bell."
• "The guard shift changes in ten minutes."

A clock players can see lets them weigh real trade-offs. Search the study properly, or make the ship? John Harper's Blades in the Dark turned this into something you can literally draw. Its progress clock is a circle cut into segments (four for a complex obstacle, eight for a daunting one), and the GM ticks segments off as trouble closes in. The rules even suggest racing clocks, where the crew's "Escape" fills up against the constables' "Cornered". I adore that idea. You don't need the game to borrow it, either; a pie chart scribbled on an index card does the job.

Audio play has no index card, of course, so the clock has to live in the words. "Second bell. One more and the ritual's done." That line does the same work as the drawing.

5. Vary the Rhythm of Description

• Fast scenes: short sentences. Quick beats, with a sound effect or two.
• Slow scenes: longer, richer description that gives players time to breathe and notice things.

In audio play, rhythm matters even more. The speed of the narration and the gaps between lines do half the pacing work, and the ambient sound underneath does the rest. See How Ambient Sound Design Elevates RPG Storytelling.

I learned this the hard way, because dead air is pacing too, just the wrong kind. At one point the browser narrator kept cutting off a few seconds into a scene, and nothing kills a tense moment like a voice that simply stops mid-sentence. Fixing that was only the start. Now narration begins speaking while the GM's reply is still being written, and the next premium-voice clip is fetched while the current one plays, so there's no awkward gap between one line and the next. Players never notice when that works. They notice right away when it doesn't.

6. Watch for Energy Drops

Signs that a scene is dragging:

• Players asking the same question twice
• Long silences that aren't the dramatic kind
• Side conversations (at a table), or one-word replies (in solo play)

When you spot one, reach for one of these levers:

• Introduce a complication. The rope frays, or a rival shows up early.
• Cut to a new scene. Nobody will miss the rest of this one.
• Ask a direct question, such as "What does your character want out of this conversation?"

That last lever is my favourite. A pointed question hands the spotlight back to the player, and most people answer it with more energy than they'd bring to "so, what now?"

7. Don't Let Combat Drag

Combat is where pacing most often goes to die. Keep it moving:

• Describe outcomes vividly so each turn feels like it counted
• Let enemies flee or surrender once the outcome is clear
• Change the battlefield: the fire spreads to the rafters, the floor gives way, more goblins pour in, the tide starts coming up
• End early: once the result is certain, narrate the rest

I tripped over this one in EchoQuest. A skill check used to need a whole extra exchange before you found out if your blade landed, and it sucked the momentum right out of a fight. These days skill checks resolve in the same turn, so you hear the result straight away. Losing a fight doesn't stall the story, either. Drop to 0 HP and the GM narrates a real setback instead of grinding everything to a halt. Maybe you're captured, or maybe you wake hours later with a price to pay.

8. End on a Hook

End each session on something that makes players itch to come back:

• A revelation: "The letter is signed in your father's hand."
• A threat: "Hoofbeats on the road behind you, a lot of them."
• A choice: "The prince offers you a place on his council, starting tomorrow."

Shea has a sneaky variation for ongoing campaigns: stop the session right before a big battle. As he puts it, "it builds Suspense", and as a bonus you already know exactly how next week opens. What's the best cliffhanger a GM ever left you on? I bet you still remember it.

How EchoQuest's AI GM Handles Pacing

When I rewrote EchoQuest's GM to talk like a human Game Master, pacing was the thing I fussed over most, and a good chunk of this list went straight into its instructions. Here's how it actually works:

• Every scene builds. The GM opens on one concrete sensory detail, tightens things with a complication (or a detail that doesn't fit and keeps nagging), then lands on a hook.
• Pace follows the moment. A sword swing gets two quick sentences. A reveal or a new place gets room to breathe.
• No padding. Four short paragraphs is the ceiling, and most scenes need fewer. The GM also stops on the hook instead of summing up or moralising, which is "leave early" in practice.
• One direct question closes each scene, and it changes from scene to scene ("Do you trust her?", "Left tunnel or right?"). The choices aren't listed in the prose, because the game reads them out separately once the narrator has finished.

That closing question has a pedigree, by the way. Dungeon World's GM rules say "Whenever you make a move, end with 'What do you do?'", and I think it's one of the best single rules a GM can follow. I didn't hard-code tension and release, though. Instead, the world's tone shapes it, so a horror world gets slow dread and a cinematic one gets dramatic pacing with emotional beats.

You can steer the tempo yourself, too. Type or say "let's skip ahead to the city", or "slow down, I want to explore this". The suggested choices are only suggestions, and the GM is told to follow your lead rather than herd you back onto its own path. On the listening side, Space or P pauses the narrator and R replays the last stretch of narration. If a scene drags or races, the [ and ] keys nudge the speech speed. Read more in Behind the GM: How We Prompt Claude to Run Your Adventures.

Quick Pacing Checklist

Copy this onto a sticky note and slap it inside your GM screen:

• Does every scene have a question?
• Am I starting late and leaving early?
• Have I alternated tension and release?
• Is there a clock or deadline?
• Is combat ending when the outcome is clear?
• Will the session end on a hook?

Try a well-paced adventure →