How to Make a Prepared Adventure Easier to Scan While Running It
To make a prepared adventure easier to scan during play, turn it into a compact table reference: put the next likely scene and essential reminders where your eyes land first, label each section consistently, and move full descriptions and rules to clearly marked pages you can find quickly. Before the session, rehearse finding a location, clue, NPC, and encounter. That quick check reveals whether your notes are usable under the interruptions of play.
Start with the decisions you need to make
A running reference should answer practical questions quickly: What is happening now? What can the characters notice or do? Which detail or rule do I need to check? These are different jobs, so give each one a predictable place. D&D Beyond’s 2024 Dungeon Master’s Guide separates preparation and session running from guidance on narration, exploration, combat, and encounters; that division is a useful reminder to organize around the work you do at the table, not just the story’s chapters. Dungeon Master’s Guide
Start by reviewing the adventure and listing the material you expect to need during this session: opening situation, likely locations, clues, important NPCs, encounters, and any unusual rules. Sly Flourish’s preparation guidance similarly calls out a strong start, possible scenes, clues, locations, NPCs, and monsters. Treat that list as a content checklist, not a required sequence of events. The Lazy GM’s Resource Document
Put a short session dashboard first
Make the first page or screen a dashboard, not a miniature rewrite of the adventure. Include the session’s starting situation, the party’s immediate goal if known, a short list of likely destinations or scenes, and references to the pages containing their details. Add names that are easy to forget and one or two important reminders, such as a time-sensitive event or a clue that could be missed.
Write in fragments rather than paragraphs: “East gate—guard wants a name; bell rings at dusk” is easier to skim than a block of prose that buries those details. Keep the adventure’s original page numbers or section labels beside each entry so the dashboard remains a map to the fuller material. The goal is quick orientation; if you find yourself reading a paragraph aloud to remember what happens, move the essential point into a shorter note.
Use labels that match what you will search for
Choose a small, consistent set of headings, such as Scene, Location, NPC, Clue, Encounter, and Rule. Use those labels in both the dashboard and detailed notes. If a clue can be found in multiple places, list it under Clues and note possible sources, instead of making the reader remember which character or room contains it. Sly Flourish recommends keeping clues short and flexible about where characters discover them; this also makes them easier to locate and adapt during play. The Lazy GM’s Resource Document
Use the exact names players are likely to say. If the adventure calls a place “The Sunken Archive,” do not label it only “basement” in the index. Add a plain-language alias if needed: “Sunken Archive (old records room).” A simple alphabetical list of people and places, with page references, helps when players ask about something unexpected from an earlier scene.
Separate table prompts from full descriptions
For each likely scene or location, put a short prompt in the running notes: what the characters first notice, what can change, and where the full description or map is. Keep boxed text or evocative prose in the adventure itself if you want to read it, but add a brief cue that tells you when it applies. For example: “Arrival: blue lamps still burning; read ‘Night Market’ description, p. 12.” This prevents a long passage from hiding the actionable detail.
For an NPC, note the name, role, what they want in this scene, and any immediately relevant information. For an encounter, note its trigger, participants, map or location reference, and any unusual mechanic. Avoid copying every statistic or rule into the dashboard. Copy or summarize a rule only when you need it often or the adventure’s explanation is hard to find; keep the edition and source reference with the reminder so you can verify it.
Make the page easy to scan at a glance
Use the same visual pattern for similar information: bold labels, short lines, and enough spacing to keep adjacent entries distinct. Put the most time-sensitive reminder at the beginning of its section. Color can help distinguish categories if you already use it consistently, but do not make meaning depend on color alone; readable labels still work in grayscale or on a small screen.
Keep each note focused on one idea. Break a long room description into separate bullets for entrance, notable features, and interactive details. On paper, use tabs or page flags for frequently visited sections; digitally, use headings and bookmarks that work in your chosen reader. The best format depends on whether you can navigate it with your hands free and your attention divided.
Build a fast route to details
Choose one route from the dashboard to each detailed reference: a printed page number, a stable heading, or a bookmark. Avoid vague notes like “see notes” or duplicate copies that can drift apart. If you change a page number or section, update the dashboard too. For a large adventure, maintain a short index of locations and NPCs, then group detailed entries in the order that makes sense for the session.
Keep supporting materials—maps, encounter statistics, handouts, and rules references—near the notes they support or linked from them. If an encounter has several moving parts, prepare a compact encounter card with only the current scene’s essentials and a pointer to the full stat block. Sly Flourish also lists tools such as notebooks, index cards, initiative cards, and a screen or cheat sheet among possible preparation aids; choose the few that match your table rather than adding a tool for every note. The Lazy GM’s Resource Document
Test the reference before play
Do a short retrieval drill using your own materials. Without reading through the whole adventure, find: the opening situation, one location’s key detail, an NPC’s current purpose, a clue, an encounter’s trigger, and a rule you expect to need. If any lookup takes several page turns or requires searching prose, add a clearer label or a dashboard pointer.
Then check for common failure points: Are names spelled consistently? Do page numbers still match? Can you distinguish a clue from a required event? Is the current version of a map or encounter obvious? Do your notes still make sense if players bypass the scene you expected? This last check matters because possible scenes are prompts, not a fixed itinerary; Sly Flourish explicitly cautions that a GM may need to discard prepared scenes when play moves in another direction. The Lazy GM’s Resource Document
Keep the reference lightweight as the session changes
During play, jot down only what will help you resume: a changed NPC attitude, an unresolved lead, a location the characters chose to visit next, or a detail you improvised and want to preserve. Mark completed or obsolete prompts clearly instead of deleting them in a way that leaves a confusing gap. At the end, update the dashboard for the next session and remove pointers to details that no longer matter.
A useful reference is not the shortest possible document; it is the one that helps you find the right information without losing the thread of the scene. If your group often explores off the expected route, prioritize reusable location, NPC, and clue notes. If your sessions follow a planned sequence more closely, a scene list with clear transitions may be enough. Keep the full adventure available for nuance, and let the scan-friendly layer handle orientation and retrieval.
