Your party is standing at the mouth of the barrow you spent four hours mapping. The fighter looks around the table and says, "Actually, can we go back to town first? I want a better shield." Nobody argues. The cleric wants incense. The rogue wants to fence a ring. Your carefully trapped corridors are suddenly a long way off.
Most GMs would call this a derail. We think that word causes half the trouble. The players haven't wrecked anything. They've shown you that the prep only worked along one path. The fix is scenes that can follow the table wherever it goes.
Derailing is feedback about your prep
"Derail" assumes there was a track. There wasn't. There was a scene you liked, in a place you liked, and the players chose a different place. That stings. It also tells you something specific: your content was glued to a location when it should have been glued to a purpose.
The SRD's own definition of an encounter helps here:
An encounter is a scene in an adventure that is part of at least one of the game's three pillars: social interaction, exploration, or combat.
SRD 5.2.1, "Encounter"
There's no room number in that sentence, and no map. An encounter is defined by the kind of play it delivers. A nervous informant works just as well in a crypt antechamber as behind a fishmonger's stall. Three hired knives can jump the party on a stair or in an alley. If your scene boils down to "the party talks to someone who knows something," you can set it down almost anywhere.
So when the table veers, ask which of your scenes can travel. Usually more of them than you'd guess.
The 'yes, and' reflex buys you thirty seconds
"Yes, and" gets pitched as a generous improv philosophy. At a real table it's mostly a stall, and a good one. Saying yes costs nothing. The "and" is where you get time to think.
There are two moves. Accept the action out loud, so the players hear that their choice counts. Then ask a question that makes them talk for a while. While they answer, you're flipping through your notes in your head.
"Sure, you can skip the dungeon. Tell me how you're getting to the market from here."
That line never breaks tone. It sounds like you care about the fiction, because you do. Most groups will cheerfully spend half a minute arguing over the river road versus the shortcut through the orchards. That half minute belongs to you.
It has limits, though. If the detour comes out of nowhere (the party wants to sail to another continent), thirty seconds won't cover it. Call a five-minute snack break. A calm GM after a break runs a better scene than a flustered one who pushes through.
Reroute your prep, don't improvise from zero
This is the habit that does most of the work. Stop treating NPCs, clues and set pieces as fixtures bolted to one room. Think of them as furniture you carry to wherever the party actually sits down.
Say the villain's agent was going to confront the party in the dungeon's shrine. The party is in town now. Fine. The agent still exists, still wants the same thing, and still has the lines you wrote. Put them in the new scene. You lose a backdrop, and backdrops are the cheapest thing in your notes to replace.
This only works if the agent's goal doesn't depend on the location. "Guard the shrine" describes a place. "Recover the amulet before anyone connects it to the magistrate" is a want, and wants follow the party around. If your agents keep falling apart whenever the map changes, build their motivation around something the players can believe instead of a post they stand at.
Moving prep is faster than inventing it. The dialogue and the secret are already written, and the stat block is ready. Relocating all of that takes one sentence of description. A brand-new NPC on the spot needs a name and a voice and a motive, and then you have to remember them next month.
Rerouting also protects continuity. A clue invented in a panic tends to contradict the clue you prepped, and the contradiction surfaces three sessions later when the players try to assemble the picture. Moving the prepped clue keeps your reveals consistent. It's the same reasoning behind planting a clue twice in different places: if the players miss it in the shrine, they can spot it on the agent's sleeve.
The other classic derail, killing the wrong NPC, works the same way. Suppose the rogue knifes the informant before she talks. Her information survives her. It moves into her coded ledger, or to her sister who runs the ferry, or into the letter tucked in her coat.
Three redirect lines to say out loud
These work word for word. Put them on a sticky note.
- "Sure, what's your plan?" This accepts the detour and makes the players get specific, and specifics give you something to hang prep on. "We go shopping" gives you nothing. "We go to the spice market because Brann wants to sell the pepper we looted" gives you a location and a merchant to work with.
- "As you're doing that, something catches your eye." This is where you move the furniture, dropping a prepared clue or NPC into the scene they picked. The phrasing rewards their choice instead of interrupting it.
- "Before you go, one more thing happens." This closes the scene with a hook back toward the main thread: a messenger, a stranger trailing them, a bell ringing somewhere out toward the barrow. It's an invitation. They can refuse it.
Accepting shows the table their choices matter. Injecting keeps your story alive inside their choice, and the hook offers a way back. Players who feel free to ignore a hook are far more likely to take it.
If they ignore the third line too, let them. The hook can come back later in a sharper form. Dragging them toward it now only teaches them that their choices were never real.
Worked example: they skip the dungeon to go shopping
Here is a hypothetical setup. Magistrate Orsolya Venn is the villain. She wants the Gallows Amulet, a cursed pendant hidden in an old barrow outside town, because it holds the confession of a man she had hanged for her own crime. Her agent, Brother Callum Reye, is a soft-spoken man in grey robes. He was supposed to ambush the party inside the barrow, try to buy the amulet off them, and turn violent if they refused. Three sessions back, the party heard a tavern rumor about "a pendant with a rope carved around it."
Then the derail. The party reaches the edge of the barrow and decides to spend the afternoon shopping in town.
First, accept it. "Sure, what's your plan?" The warlock, Ilse, wants a new focus. The fighter still wants that shield. Someone mentions spices. Now you have a market.
Next, look for furniture you can move. Callum's want hasn't changed. He's hunting the amulet and anyone who knows about it. He has no idea the party skipped the barrow, so as far as he knows, they already have it. That gives him a better reason to be in the market than he ever had in the dungeon.
Now inject him. "As you're doing that, something catches your eye." A robed buyer at the saffron stall is haggling in a low, patient voice. When Ilse describes the rumored pendant to the jeweler next door ("rope carved around it, she said"), Callum goes still. His hand stops on the merchant's scale. He doesn't look over. Any player who notices will start asking questions, and that's all this scene needs to do.
Then step back and let the players decide what to do about him. If they approach him, he plays the scholar, using the dialogue you already wrote for the barrow: "A rope pendant? Morbid. I collect morbid things. If you ever find one, I'd pay well." If they ignore him, he follows them. If they attack him in broad daylight, they now have a problem with the town watch, which Venn happens to control.
Finally, the hook. "Before you go, one more thing happens." As the party leaves, the saffron merchant presses a scrap into the fighter's hand: "He paid me in coin from the magistrate's mint. Fresh-struck. Thought you'd want to know." The barrow matters more now, because someone dangerous wants what's inside it.
You lost the shrine ambush. In return, the villain has a face before the fight, and we'd take that trade nearly every time. The motive and the eventual confrontation stay exactly as you planned them.
If you need more market texture fast, borrow a beat or two from these market day encounters and slip Callum into one. In the middle of an investigation this rule matters even more, because every clue has to survive the detour. That requirement is the backbone of running a mystery players can actually solve.
A checklist for modular encounters that survive any direction
Run through this before each session. Ten minutes now is cheaper than a mid-game panic.
- Build each encounter around a want before you give it a location. Write "Callum wants the amulet" before "Callum waits in the shrine."
- Give every important NPC a motive that can surface in any scene. If the motive only makes sense in one room, rewrite it.
- Make each key clue findable at least two ways, such as a document plus a witness, or an object plus an overheard argument.
- Tie combat triggers to a condition. "The knives attack when the party is seen with the amulet" travels. "The knives attack in room 4" doesn't.
- Fill one index card with reusable props and lines: a distinctive coin, a symbol, a phrase the villain's people always use. They make any scene feel connected to the plot.
- Mark the one scene you'd hate to lose and decide where else it could happen.
Modular encounters also cut your prep. You stop writing three versions of a scene for three possible routes, because one version handles all of them.
Reroutes are easy to forget by the next session. If you keep a running record of them, LorePanic can post the session straight to your Discord, so you can scroll back and check exactly how Callum ended up at the saffron stall.
Start with this tonight. Take your next session's main NPC and write their want on one line at the top of the page, above any location. If you can't write that line without naming a room, that NPC will break the first time your players turn left.