GM Scenario Prep for Sci-Fi Games

Core Approach

Good scenario prep is genre-agnostic in structure but genre-tuned in surface texture. The same progression that works for dungeon referees works for cyberpunk run GMs — just swap rooms for compartments, monsters for corporate security, and treasure for data/gear.

The progression below applies to any sci-fi or cyberpunk game. Examples use generic cyberpunk run framing throughout.

Stage 1: Single-Site Runs

Start with a compact, contained location. One building, one facility, one corporate node.

Map the location with a handful of distinct zones (floors, wings, vaults)
Key each zone with a primary challenge or object of interest
Add one notable NPC with a clear role and reaction disposition
Keep notes short and table-facing — one line per room is enough

This mirrors the five-room dungeon structure: entrance/guardian → challenge → complication → climax → payoff. The structure is not mandatory, but compact maps benefit from the rhythm.

Do not write a story. Write a location with content.

Stage 2: Active Defenders

Once single-site play is comfortable, animate the opposition.

Use an adversary roster: list who is where at session start, then let them react to noise, alarms, and player choices
Security does not wait in rooms to be killed. It responds to incursion
Separate awareness levels: unaware → suspicious → alerted → hostile
Key decision: what does security do when alerted? Lockdown, call in backup, evacuate the target?

Cyberpunk adjustment: security response and escalation timers are a genre expectation. Players know that time is a resource. Build that in from Stage 2 onward.

Stage 3: Clue-Based Investigation Arcs

Once operational play (entry, execution, exit) is stable, add investigation depth.

Apply the Three Clue Rule: every critical piece of information has at least three independent paths to discovery
Do not construct linear clue chains where missing one clue blocks progress
Think in nodes, not sequences: each discovered clue opens new questions; some paths converge, some branch

Cyberpunk adjustment: investigations often precede the run. The session may be a recon job, a data-mining op, or a social infiltration that feeds into the next session's action. Treat investigation arcs as run-enabling, not separate from operational play.

Build linear investigation first (to understand the shape of the mystery), then deliberately add redundant paths.

Stage 4: Linked Scenarios and Conspiracy Arcs

Once single-run investigation structure is stable, connect sessions.

Runs that surface new questions feed into follow-up jobs
Introduce a conspiracy layer: a faction or system that appears across multiple runs in partial view
Use callbacks: NPCs from past runs, references to past events, consequences of past choices
Do not pre-script the arc's conclusion — maintain multiple possible outcomes based on player actions

Cyberpunk adjustment: corporations, fixers, and underground movements have institutional memory. If the party damaged one faction, that faction has a position on them. Consistency is the tool; tight plots are not.

Prep Discipline (Applies at All Stages)

Keep notes short and table-facing (one line per obstacle, one line per NPC motivation)
Separate what must be explicit from what can be improvised
Avoid prep-to-play time imbalance — more prep time than play time is a warning sign
Reusable context beats over-scripted tactics: a GM who understands the location improvises better than one who memorized specific responses
Prep the situation, not the plot: who wants what, who is where, what happens if PCs never arrive