How to Link Session Notes Directly to the Next Music Cue

Read the previous session’s notes and your next-session prep. Mark only moments likely to need a deliberate audio change: an opening location, a new environment, a scene with a distinct tone, or a transition into a set-piece encounter. A cue is useful when it gives you a clear reason to change or start sound; routine conversation may need no change at all.

Planning likely locations and encounter types is a practical starting point for music prep, while unpredictable or improvised play makes precise advance selection harder. Boroughbound’s guide to preparing music for a tabletop session makes that distinction and recommends considering the kinds of scenes that may arise. Treat the list as possibilities, not a prediction of what players must do.

Write each moment as a short event or state: “party reaches the flooded stair,” “negotiation moves to the council chamber,” or “the chase begins.” Avoid assigning sound to every line of narration. The notes should help you notice a transition, not require you to interrupt play to manage a soundtrack.

Choose a compact ID format such as S03-A for session 3, moment A. Put that ID in both places: in the session note and in the cue name or soundboard label. Pair it with a human-readable scene name so the code remains useful when you are scanning quickly.

For example, a note might read: “At the first clear view of the flooded stair, offer the group a moment to react; if they descend, use S03-A — Flooded Stair.” The corresponding cue could be named S03-A Flooded Stair — low water ambience. The ID is the link; the scene phrase confirms you selected the right item.

If your sound tool supports groups, tags, or ordered scenarios, use those to make the cue easier to find, but keep the ID visible in the item name. Some TTRPG audio tools organize material into scenarios and scenes, and some let a note display or control playback. Those are optional conveniences: the matching label is the method, and it can work in a document alongside any player. DiceAudio’s feature overview describes scenario items, reusable presets, and an integration that places its player inside Trilium notes.

Place the cue reference beside the decision point in your notes, not in a separate music list you must remember to consult. Make the trigger observable: “when the group enters the chamber,” “after the door closes,” or “when the chase starts.” If timing is flexible, state whether to start the cue on the transition or wait until the table settles.

Distinguish the moment that calls for a cue from the story outcome. For instance, “If they enter the chamber, start S03-B; if they stay outside, keep the current ambience.” This prevents a prepared track from nudging you to steer the group toward a scene. If an expected event does not happen, skip its cue and continue from the notes the players actually create.

A small, ordered list can support a session with several planned moments:

Note trigger	Cue ID and label	Playback action
First view of flooded stair	S03-A — Flooded Stair	Start water ambience
Council chamber door closes	S03-B — Council Chamber	Replace current scene
Chase begins	S03-C — Rooftop Chase	Start brisk music; stop chamber ambience

Treat “replace,” “layer,” and “stop” as distinct actions. If the player supports fade or crossfade settings, decide in advance whether the old track should fade, stop, or continue under the new sound. Cue tools vary: for example, CueBard documents per-cue behavior for looping, transitions, and how a cue affects other playing cues. CueBard’s project documentation shows why stating the action can matter when several sounds may be active.

Use a naming pattern consistently, such as session ID — scene — sound type. Keep the part you need to identify first at the beginning of the name. If a cue is a one-shot effect rather than continuing music or ambience, mark it plainly, so you do not mistake a brief effect for a background bed.

Limit the prepared list to moments that are both plausible and meaningfully different in sound. A focused list reduces searching during play and is easier to revise when the group takes an unexpected route. For recurring scenes, reuse a stable cue ID or a named preset and change only the session-specific note reference. Avoid duplicating tracks under slightly different labels unless they need different playback settings.

If you run audio from a generic media player, create a short playlist or bookmark list using the same names. With a soundboard, put the most likely cues in reachable slots and leave less certain material searchable. The point is to reduce the steps between recognizing the trigger and finding the right control.

Before play, open the session notes and audio tool together. For each listed trigger, search or select its cue ID, confirm the label and listen briefly. Check that the cue starts at a useful point, that its volume fits beside speech, and that any intended fade, loop, or stop behavior is set. Then test that you can return to the note and find the next cue without losing your place.

Test the actual route you will use at the table: laptop speakers, room speakers, virtual tabletop, or voice-call audio routing. A music file playing locally does not by itself confirm that remote players can hear it. A general tabletop music-prep guide also recommends checking the playback setup before the session, rather than discovering connection problems at the table. Boroughbound’s preparation guide discusses testing tools in advance.

For each major planned transition, decide what to do if the cue is missing, late, or no longer fits. A simple fallback can be “leave the current ambience running,” “use the general exploration playlist,” or “play nothing.” Keep the fallback visible next to the cue reference. Silence is a valid choice when a track would distract from a conversation or when the group has moved into an unplanned scene.

After the session, update only what you learned: mark cues that were hard to locate, rename ambiguous items, and remove triggers tied to scenes that no longer matter. Notes and audio should describe the game as it developed, rather than preserve assumptions that the next session must follow the same path.

• How to Prep Music for a Tabletop Session — Boroughbound
• DiceAudio — project feature overview
• CueBard — project documentation