Table improv
GM Improv Scene Checklist
Improvising a scene is easier when you only need a few answers. A generated venue already gives you atmosphere, people, rumors, and trouble. This checklist helps you turn that material into a playable scene in a few minutes, even when the players walk somewhere you did not expect.
The five-minute scene frame
Do not prep a full plot while everyone waits. Prep the next playable exchange: what someone wants, what blocks it, what gets worse, and how the characters can leave with a changed situation.
- Want: What does the party want from this room right now?
- Obstacle: Who or what makes the easy answer unavailable?
- Pressure: What changes if the party hesitates, argues, or fails?
- Face: Which NPC can speak for the scene?
- Exit: What new choice, clue, bargain, enemy, or deadline ends the scene?
Choose one pressure type
A scene without pressure becomes a conversation with no edge. Pick one pressure and let it show up visibly in the room.
Time
The gate closes, the ship boards, the keeper leaves, the guards arrive, or the storm cuts off the road.
Social
A rival is watching, a regular takes offense, a patron lies loudly, or a faction tests who belongs.
Material
A key is missing, a tab is unpaid, a pass is forged, a map is damaged, or supplies run out.
Information
A clue is hidden, a rumor is planted, a witness is leaving, or the wrong person knows too much.
Use one NPC as the scene handle
When improvising, one clear NPC is usually better than five vague voices. Give that NPC a role, mood, and leverage. They might be the keeper, a regular, a courier, a guard, a stranded pilot, a nervous informant, or the person pretending not to listen.
Ask what they can offer, what they want hidden, and what would make them act before the party is ready.
Add one useful clue or rumor
The scene should give the party something they can carry forward: a name, route, warning, debt, invitation, missing object, or contradiction. If the generated rumor is too broad, narrow it into a table-ready sentence and attach it to a source in the room.
If the party misses the clue, keep the consequence moving. The witness leaves, the rumor spreads, the rival gets there first, or the next scene starts with less time.
Example: unexpected tavern stop
Generated spark: a crowded roadside tavern, a keeper hiding a road token, and a rumor that the west bridge is closed for repairs.
Want: the party needs a safe route before nightfall. Obstacle: the keeper will not admit the bridge closure is fake. Pressure: a courier with the real route leaves in ten minutes.
Face: a regular recognizes the road token and asks the party who sent them. Exit: the party can buy the token, follow the courier, expose the keeper, or take the dangerous old ford.
Copy-friendly improv checklist
- Scene need: What are the players trying to get?
- Visible mood: What does the room feel like when they enter?
- Key NPC: Who can help, block, warn, or betray them?
- Pressure: What changes if they wait?
- Rumor or clue: What useful information can leave the room?
- Complication: What makes the straightforward option costly?
- Exit choice: What decision points toward the next scene?
Next reads
Encounter Prep Guide
Expand the checklist into a fuller scene with motives, entry paths, reactions, and consequences.
Random Tavern Rumors
Turn a quick rumor into a clue, job, warning, false lead, or personal hook.
Recurring NPC Guide
Keep improvised NPCs who worked and bring them back with changed pressure.
Open the Generator
Generate a scene, pick one pressure, and run the next playable exchange.