Home

Let’s make this concrete.

Imagine you’re running a modern-fantasy game where the crew has to steal a cursed painting from a private museum before it’s shipped to a buyer who knows exactly what it does.

Here’s what prep might look like with The Heist Tool Kit open on your desk.

Start with the Job Brief & Crew Angles (01A–B)
You define the score in one sentence: “Steal the cursed painting before it leaves the city.” You list constraints: must avoid public scandal, must not destroy the painting, must not trigger a particular ward. Then you give each character a line: who’s in this for money, who has a personal history with the curator, who has a fear that might surface during the job.

Already, you know which levers to pull when things get tense.

Build the Target Profile & Blueprint (02A–B)
You break the museum into zones: street and plaza, lobby, public galleries, restricted wing, security nerve center, rooftop. You jot notes about access points, cameras, and the path the painting will take from display to crate. You sketch just enough layout that you can answer “what’s around that corner?” without freezing.

Now, when the crew says “we’ll get in through the loading dock and cut across the storage corridor,” you know what that actually means.

Map the Security & Defenses Grid (03A–B)
For each zone, you log physical defenses (locked doors, reinforced glass), technological ones (cameras, sensors), social ones (docents, donors), and personnel (guards, night crews, external contractors). You add one or two non-obvious threats: a warded frame, a rival crew with partial access.

During play, this grid tells you exactly what reacts when the painting disappears or when someone hits the wrong door.

Fill the Intel stack (04A–D)
You write down what the crew truly knows (documented shipping time, security firm name), what they think they know (which entrance is “lightly guarded”), what’s false on purpose (a decoy shipping schedule), and what you’re keeping off-screen (the buyer’s personal agent already on-site).

As you run the session, you cross items between columns. A “suspected” detail becomes “known.” A hidden factor is revealed at the worst possible moment. A planted lie meets reality in the middle of the job.

Prep Surveillance & Legwork (07A–B)
You frame three casing scenes: attending a public gala, posing as contractors, and watching the plaza overnight. Each has a clear goal, a couple of clues, and an attention cost if the crew pushes too hard.

Legwork stops being aimless speculation. It becomes a series of real choices: which questions matter, how much risk they’ll take to answer them, what they’re willing to leave unknown.

Lay out the Operation Plan & Heat (05A–D)
You break the heist into phases: Entry, Approach, Swap, Extraction, Exit. For each, you note the main tactic, a backup plan, and a heat trigger that will bump the response if things get loud. You seed one pivot option per phase—places where the plan can bend instead of just snapping.

At the table, you always know what phase you’re in, how much heat is on the crew, and where they might pivot when the painting isn’t where they thought it was.

Tie in Factions, Complications, and Fallout (06–08–09)
You give the museum, the buyer, and the rival crew each a timer. You preload a handful of complications tied to intel gaps and faction moves. When things inevitably go wrong, you don’t have to invent “something interesting” from a blank page—you pull from the engine and attach it to something already in motion.

By the time the job is over, the Fallout sheets tell you exactly what changed: who’s furious, who owes the crew, who got hurt, and what the next job might be.

The difference isn’t that you suddenly have more ideas. It’s that the ideas have somewhere to live.

Next post, we’ll zoom in on the pieces that make heists feel alive: factions, complications, and fallout.

Find out more here: https://games.akapplegarth.us/comingsoon.html

ttfn,

aka

The Heist Tool Kit isn’t just “18 pages of stuff.”

It’s a stack.

Each worksheet is designed to feed the next one, so you can move from “we have a cool heist idea” to “we have a living, trackable situation” without scattering notes across three different notebooks and a dozen sticky notes.

Here’s the arc.

01A–B: Job Brief & Crew Angles
This is the table’s shared starting point. You define the score in plain language, clarify what success actually means, list constraints, and write down why the job matters to each crew member. At the table, this gives everyone the same picture of the job and keeps personal stakes visible when things get messy.

02A–B: Target Profile & Blueprint
These sheets turn the target into a real place with people in it. You break the location into zones from entry to prize, note important features, and log key personnel. In play, this lets you answer “where are we right now?” and “who’s nearby?” without stopping to invent the building from scratch.

03A–B: Security & Defenses Grid
Here you map out defenses by zone: physical, technological, magical, social, and personnel. Instead of a loose list (“guards, cameras, wards, alarms”), you get a grid you can scan in seconds. When the crew does something loud on the loading dock, you already know what reacts and how fast.

04A–D: Intel – Known, Suspected, False
This stack is the information backbone. One page is for confirmed facts, one for working assumptions, one for planted lies, and one for things the crew doesn’t even know exist yet. During play, you can see at a glance where the gaps are and what happens when a false belief collides with reality.

05A–D: Operation Plan, Phases & Heat
These sheets run the job itself. You break the operation into phases, track rising heat, and note pivot options when a phase fails or ends early. At the table, this is your control panel for the score: what phase we’re in, what’s at risk, and where the next safe handhold is when the plan shreds.

06A–B: Factions, Stakeholders & Timers
Heists feel dead when only the PCs move. These pages track everyone else who cares about the prize: rival crews, security firms, bosses, victims, and wildcards. You give them goals, resources, and clocks. Between scenes, you advance those clocks and decide who intersects the crew next.

07A–B: Surveillance & Legwork Scenes
Casing can be the best part of a heist or the slowest. These sheets structure legwork into concrete scenes with clear questions, stakes, and an attention track. Instead of free-floating speculation, you get a series of focused opportunities for the crew to learn something or push their luck.

08A–B: Complications & Twist Engine
When things go sideways, this is where you go. The engine is built around preloaded complication bands and link prompts: small wrinkles, serious problems, and worst-case twists, each tied back to something already on your other sheets. Twists feel like consequences, not surprises from nowhere.

09A–B: Fallout, Payoff & Future Hooks
Heists matter when they leave marks. These pages record what the crew gained, who lost what, which consequences stick, and what new pressure they created for themselves. By the time you’re done, you have a clear picture of how this job changed the campaign and what trouble it sets up next.

You can run a one-shot with a minimal stack or lean into the full pipeline for a long campaign. Either way, you’re not improvising the scaffolding under your heist. You’re building it on purpose.

Next post, we’ll walk through a concrete example: one job, one table, and what it looks like to actually fill these out.

Find out more here: https://games.akapplegarth.us/comingsoon.html

ttfn,

aka

“System-neutral” is one of those phrases that can mean almost anything.

Sometimes it’s a polite way of saying “we stripped out the mechanics and left you with something vague.” Sometimes it means “we secretly had one system in mind the whole time; good luck bending it to yours.”

For The Heist Tool Kit, “system-neutral” means something more specific: every page is built around questions, structure, and pressure, not rules. You bring the mechanics. The toolkit brings the scaffolding.

That starts with language.

Instead of saying “clock 4-segment,” a field might say “clock size.”
In your Blades in the Dark game, that might be a literal four-tick clock. In your trad fantasy game, it might be a rough countdown of failed stealth rolls, mounting suspicion, or how long the guards will tolerate a distraction before they shut things down.

The sheet doesn’t care what dice you’re rolling. It cares that:

• You know there is a clock.
• You know what it represents.
• You decide in advance how big it is and what moves it forward

Same with “heat.” In one table, that’s a proper mechanical track. In another, it’s an abstract measure of how much attention the crew is drawing and what kind of response they’re about to trigger: more security, a rival crew, the boss coming down in person, or the cops finally being called.

Every sheet in the kit is built around that pattern:

• Job Brief & Crew Angles doesn’t assume playbooks or playbooks. It just asks why this job matters to each character and what they are not willing to risk.
• Target Profile & Blueprint doesn’t prescribe grid maps or theater-of-the-mind. It asks you to define zones and important features in whatever mapping style you already use.
• Intel: Known, Suspected, False doesn’t care whether intel is gathered with Investigate checks, flashback scenes, or divination magic. It cares that you clearly separate “true,” “probably,” “someone wants you to think this,” and “you don’t know this exists.”

ttfn,

aka

Because none of the pages rely on a particular rule set, you can drop the kit into:

Blades scores, Shadowrun operations, and cyberpunk infiltrations.
Fantasy burglaries, artifact thefts, and prison breaks.
Modern crime campaigns and spy thrillers.
Weird occult heists where the alarms are more metaphysical than physical.
You keep using the mechanics your table already knows. The Heist Tool Kit sits underneath that, giving you a consistent way to think about pressure, information, and consequences no matter what you’re rolling.

Next time, I’ll open the cover and walk through the full sheet stack, from the first job brief to the last fallout note.

Find out more here: https://games.akapplegarth.us/comingsoon.html

ttfn,

aka