How do you structure a heist in DnD?

Run it in six stages: the hook and target, casing the location, planning and acquiring what they need, infiltration, the complication where it goes wrong, and the escape. Each stage is a different kind of play, from investigation to social to combat, which is what makes a heist feel different from a dungeon crawl.

How do you stop a DnD heist plan from being boring?

Don't make the players write a perfect plan. Let them gather an advantage, then introduce a complication during infiltration that no plan accounts for: a guard rotation changes, a face is recognised, the vault has a second lock. The fun of a heist is improvising when the plan breaks, not executing a flawless one.

Should I use a battlemap for a heist?

Yes, but reveal it gradually. Use a map of the target location and uncover rooms as the party scouts or enters them, marking guard patrols, cameras or wards as they're discovered. The shared map becomes the planning tool, and the moment of revealing a room the players didn't expect is where the tension lives.

How long should a DnD heist take to run?

A focused heist fits in one long session of three to four hours if you keep the planning stage tight. Cap the casing and planning at the front, then spend the bulk of the time on infiltration and the escape. Multi-session heists work for big targets but risk losing momentum if the planning drags.

Where can I get maps for a DnD heist?

MakeMythic on Etsy includes mansions, vaults, banks, temples, guild halls and noble estates in its 250,000+ battlemap bundle, all high resolution and gridless for VTT or print. One bundle covers almost any heist target you can dream up for your players to break into.

How to run a heist in DnD: a step-by-step guide

TL;DR: Run a heist in six stages: hook, casing, planning, infiltration, the complication, and the escape. Let players gather an advantage rather than write a perfect plan, then break the plan during infiltration. Reveal the target map gradually to keep the tension high.

The heist is one of the most satisfying things you can run in DnD and one of the least supported by the rulebooks. There’s no “heist” chapter, no subsystem, no neat table to roll on. So a lot of DMs either avoid them or run them as a dungeon crawl with extra sneaking, which misses what makes a heist special. With a clear structure, a heist becomes a showcase for the whole party: the face, the sneak, the planner and the muscle all get their moment. Here’s the structure that works.

Why heists need their own structure

A dungeon crawl is reactive. The party moves forward and deals with what’s in front of them. A heist is the opposite: it’s about preparation, knowledge and a plan, right up until the plan collapses and everyone improvises. That inversion is the whole appeal, and it’s why running a heist like a dungeon falls flat.

The structure below splits the heist into stages that each reward a different kind of play. That’s deliberate. It means the player who loves investigation gets the casing stage, the talker gets the social infiltration, and the fighter gets the moment it all goes loud. Nobody sits idle for an hour while one character does everything.

The six stages of a DnD heist

DnD heist battlemaps: vaults, mansions and banks in the 250k bundle

From the shop

250,000+ RPG Battlemaps Mega Bundle

£30 £9

Browse on Etsy →

1. The hook and the target. Establish what’s being stolen, from where, and why it has to be the party. Give the target a clear defining feature: the vault is warded, the mansion has a private guard, the artefact is behind a face only the owner can open. That feature is what the players will spend the heist trying to beat.

2. Casing the location. The party scouts. They watch the guard rotation, befriend a servant, sketch the layout, bribe a clerk. This is where you feed them information, and where a gradually revealed map starts to fill in. Reward thorough casing with real intelligence, because the better they understand the target, the more clever their plan, and the more the eventual complication lands.

3. Planning and acquisition. The party turns information into a plan and gathers what it needs: forged papers, a uniform, a key, a distraction. Resist the urge to demand a perfect plan. Instead, let each piece of preparation become an advantage they can spend later. This keeps the stage from dragging into an hour of arguing around the table.

4. Infiltration. The plan goes into motion. Stealth checks, disguises, picked locks, the slow creep through the target. Use the map here, revealing rooms as they reach them. Keep the tension by tracking something: a guard’s patrol, an alarm threshold, the time before the owner returns.

5. The complication. This is the heart of the heist. Something the plan didn’t account for goes wrong. A guard rotation changed. A face is recognised. The vault has a second lock nobody saw. The complication should not be unfair, it should be something the casing could have caught but didn’t, and now the party has to improvise. This is the moment players remember.

6. The escape. Getting in is half the job. Getting out with the prize, while the place is now alerted, is the climax. This is often where the combat finally happens, and where a chase can break out into the streets. Make the escape its own scene rather than a formality.

The golden rule: don’t reward the perfect plan

The single most common way heists fail at the table is the DM insisting the players produce a flawless plan before anything happens. Hours pass, the energy drains, and the players become paralysed by the fear of missing a detail.

Flip it. Tell the players that their preparation buys them advantages, not certainty. A good plan means they go in with the upper hand. But the heist is designed to break, and the fun is in how they react when it does. Once players understand that improvising through a collapse is the point, the planning stage gets tighter and the whole heist gets better. The complication in stage five is your promise that no plan needs to be perfect, because you were always going to throw a curveball.

Use the map as a planning tool

A heist is one of the few encounters where showing the players a map up front helps rather than spoils. Reveal the target’s layout as they case it, and the shared map becomes the surface they plan over: marking guard routes, circling the vault, arguing about whether to go over the wall or through the kitchen.

Then, during infiltration, keep one or two rooms hidden. The pantry that turns out to hold a sleeping guard, the gallery with a wardstone nobody scouted. Revealing a space the players didn’t expect is exactly where the tension spikes, and a battlemap delivers that beat far better than narration alone.

The MakeMythic heist map collection

The 250,000+ RPG Battlemaps Mega Bundle (~~£30~~ £9) covers practically any target your players might rob: noble mansions and estates, bank vaults, temples and reliquaries, guild halls, warehouses and the sewers running underneath them all. Because the bundle is so deep, you can match the map precisely to the score, and reveal it room by room as the heist unfolds.

Everything is high resolution and gridless, ready for Roll20 or Foundry, or printed out so the party can lean over the table and plot their way in.