Framework
How do you run a heist in a tabletop RPG?
Structure the score into four phases: casing the target, engagement with flashback tokens, an active alarm track, and a chaotic getaway. That way players react in the moment instead of planning for every hypothetical complication up front. Give the party flashback points to retroactively reveal preparations when obstacles emerge during the infiltration, and pair it with a visible heat counter that climbs on failed checks, so infiltration becomes a tense back-and-forth rather than a stalled planning session.
The fatal planning paralysis trap
Traditional tabletop heists frequently stall because players spend two to three real-world hours arguing over theoretical contingencies. They debate guard shift rotations, buy fifty feet of silk rope, and plan escape routes for scenarios that will never happen. The moment the first stealth roll fails in room two, that exhaustive plan collapses, leaving players frustrated and the Game Master scrambling.
Borrowing the flashback structure from narrative systems like Blades in the Dark cuts most of that debate out. By assuming the characters are competent scoundrels who planned off-screen, you can drop the party straight onto the rooftop or into the ventilation duct, and deal with obstacles as they come up instead of arguing about them in advance.
Systems worth studying for heist mechanics
If you want the rules to carry more of the heist structure, these games offer useful mechanics to borrow or play as written:
- Blades in the Dark: flashbacks, stress, and clocks Flashbacks let players establish preparations when they become relevant, while stress gives those preparations a cost. Clocks make guards, alarms, and rival crews advance in visible steps. Together, the mechanics turn a failed roll into a new pressure rather than a request to restart the plan.
- Leverage: assets, complications, and reversals Leverage builds the caper around changing advantages. Players can establish useful assets through flashbacks, while complications keep a successful approach from becoming automatic. This suits groups who want the feel of a television con job, with regular reveals and reversals.
- The Sprawl: legwork, mission moves, and threat clocks The Sprawl separates investigation and preparation from the action phase, then uses mission and threat clocks to make earlier choices matter once the operation starts. It is a strong model for cyberpunk or criminal campaigns where the team needs to manage both the target and the organisations reacting to them.
- A bolt-on for traditional fantasy systems You do not need to change systems. Add one flashback resource per character, one clock for detection, and a consequence table for failed checks. Charge the resource when a preparation is especially unlikely, expensive, or powerful, so the mechanic creates decisions rather than free solutions.
The important design choice is deciding what the rules should protect: character competence, escalating pressure, or the surprise of a well-timed reversal.
The four-phase heist structure
Organise your heist session around these four distinct operational beats:
- Casing the target Give players three concrete pieces of intelligence: an entry vector, a security obstacle, and the exact physical vault location. Allow two quick reconnaissance checks, then cut directly to the infiltration.
- Engagement with flashback tokens Grant each player two flashback tokens. When a locked reinforced door or unexpected patrol appears, a player spends a token to declare how their character prepared for this obstacle hours earlier.
- The escalating alarm track Track discovery with a five-state alarm track visible on the table: Quiet, Suspicion, Alert, Lockdown, and Lethal Response. Failed skill checks or loud spells tick the counter forward, triggering reinforcements, lockdown gates, or ward dispels.
- The compromised getaway Once the prize is secured, shift the tempo into high gear. The original entry route should be sealed or crawling with guards, forcing an improvised chase scene through rooftops, sewers, or canal barges.
The structure keeps the table moving: players react to what is actually in front of them instead of debating hypotheticals.
Example
Worked example: Infiltrating the High Vault of House Vane
Observe how replacing three hours of upfront planning with retroactive flashback mechanics transforms a typical vault infiltration scene.
- The rigid upfront planning approach
- The table spends ninety minutes debating whether to pose as wine merchants or scale the laundry chute. When they finally pick the laundry chute, the rogue rolls poorly on an agility check, falls into the courtyard, and the entire infiltration devolves into an unplanned frontal melee.
- The flashback and alarm track approach
- The Game Master opens the session with the team already perched above the courtyard skylight. When the party encounters an arcane glyph lock on the treasury door, the wizard spends a flashback token: Yesterday afternoon, I bribed the head archivist apprentice to trace the glyph sequence onto parchment. The wizard rolls to decipher the ward, but rolls a partial success. The GM ticks the alarm track from green to amber as bells toll in the guardhouse, immediately escalating table tension.
- Why it works
- The competence of the characters is preserved through the flashback, while the mechanical failure still produces real, escalating stakes without derailing the score into a total restart.
See a table-ready score in action
A finished score shows how concentric security rings, escalating alarm states, and compromised getaways connect during play without endless pre-planning.
The table-ready heist prep checklist
Before your players roll initiative on the score, confirm you have these structural elements written down:
- A clear target prize with a tangible physical weight, size, or volatile magical aura.
- Three distinct security rings: perimeter patrol, access barrier, and inner vault lock.
- A visual alarm track with five states: Quiet, Suspicion, Alert, Lockdown, and Lethal Response.
- Two flashback tokens allocated to each player character.
- One unexpected wildcard complication that triggers automatically when the prize is lifted.
Was this useful?
Systems built for this
- Blades in the Dark
Flashbacks let a player establish a preparation retroactively, and its clocks give the alarm track a ready-made mechanic rather than a house rule.
- Scum & Villainy
The same flashback and clock engine as Blades in the Dark, reskinned for a starship crew running jobs across a sector.
- Leverage: The Roleplaying Game
Built around a heist's planning montage: players narrate flashback preparations during the job itself, and complications create reversals rather than dead ends.
Tracking heist contacts in Codex Cryptica
The generator doesn't build any of this for you automatically, but once you have named guards, fences, and rival crews, Codex Cryptica lets you save them as entities and link them with typed relationships — which corrupt guard owes a debt to which underworld contact, held once and shown on both sides.
That means a flashback token can spend an existing campaign relationship instead of an ad hoc contact invented on the spot, because the connection is already on record from a previous session.
Explore the RPG knowledge graphRelated
Tools
- Heist topic hub The complete RPG heist cluster: core running frameworks, target design checklists, worked examples, and generation tools.
- Heist generator Turn this framework into a score: prize, casing intel, three security rings, alarm track, complications, and a compromised getaway.
- Dungeon generator Generate multi-room vaults, fortified subterranean complexes, and security checkpoints.
- Quest hook generator Create high-stakes patron contracts, heist objectives, and rival crew complications.
- NPC generator Quickly produce corrupt vault wardens, nervous lookouts, and rival fence contacts.
Other answers
- What makes a good heist target in a tabletop RPG?
- How do you run a mystery without railroading?
- How do you design RPG puzzles that do not stall the game?
- How do you prep a weekly RPG session quickly?
- What makes a good random encounter?
- How do you keep track of time in a tabletop campaign?
- How do you write a one-shot adventure?
- How do you run a chase in a tabletop RPG?
- How do you run character roles in a cyberpunk RPG?
- How do I run spies and infiltrators in an RPG?
- How do I run a rogue or scout without splitting the party?
- How do I run common character roles in a fantasy RPG?
- How do I run a stealth mission in a tabletop RPG?