Heist Structure

Who it’s for

• Crime, caper, thriller, fantasy, and science fiction novels built on planning and execution.
• Writers who want to emphasize team dynamics, banter, and specialized skill interplay.
• Stories where the appeal is watching a dangerous job unfold despite (or because of) complications.
• Narratives that use misdirection and information asymmetry to surprise the reader.
• Character ensembles where the crew is as important as the individual protagonist.

The beats

1. The score – Target + payout established. Why this heist? What makes it worth the risk?
2. Team assembly – Specialists recruited. Each member brings a skill; introduce their personality and prior relationship to the leader or crew.
3. The plan – Layout + steps detailed. Walk the audience (and the reader) through the operation. This is the promise of the premise: how will this actually work?
4. Execution begins – Plan moves into motion. First stage feels clean; crew works in sync. Show competence and trust.
5. Complication – Plan breaks under reality. Security is tighter, a mark doesn't cooperate, or an outside force intervenes. The crew pivots on the fly.
6. Betrayal or twist – Inside threat surfaces: a crew member has another agenda, or a detail the leader didn't know changes everything.
7. Resolution – Score won, lost, or transformed. The job succeeds, fails, or succeeds in an unexpected way.
8. Fallout – Consequences and theme. Who got caught? Who left with the money? What fractured within the crew? What did they learn about themselves?

Worked example

A crew of five is hired to steal an encrypted hard drive from a corporate vault on the 47th floor. The job pays half a million. The leader is a mastermind who hasn’t failed in fifteen years; the team includes a hacker, a lockpick, a con artist, and a driver. The plan is meticulous: they’ll impersonate maintenance workers, loop the security feed, and extract the drive in under six minutes.

But on execution day, a corporate security sweep happens an hour early. The team pivots: the con artist delays an elevator; the hacker reroutes the alarm. They get the drive. As they leave, the driver realizes the hacker has a copy. The hacker had a side deal with a rival syndicate. The crew splinters in the final moments. The leader gets the original drive to the client and disappears. The hacker sells the copy and vanishes into a new life. The lockpick and con artist are arrested. In the epilogue, the leader encounters the hacker years later, and neither knows if they’ll work together again or if trust is broken for good.

Strengths

Propulsive pacing. The heist scaffolds a clear three-beat rhythm: plan, execute, implode. Readers stay engaged because they’re invested in the crew and curious how the job will actually go. Competence porn and banter create satisfying interludes between action beats. The structure naturally accommodates ensemble casts without sidelining any character.

Weaknesses

Can devolve into pure plot mechanics if character stakes are thin. Readers stop caring about the score if they don’t care about the crew. The pleasure also lives in information management: if the reader feels the writer is holding back crucial information just to pull off a twist, trust erodes fast.

Pendraic notes

Pendraic seeds Heist as an eight-beat Engine. Use the Heavy structure preset to keep the beats and crew relationships visible. The team-assembly beat is a natural anchor for character introductions: give each crew member a beat inside the Engine if the cast is large. Consider pairing the primary storyline (the main heist) with a subplot Engine for crew friction, betrayal prep, or the personal stakes of the leader. The Complication and Betrayal beats are the core of the dramatic tension; don’t rush them. Seed the reader with the crew’s plan explicitly so that when reality breaks it, the reversal hits harder.