D&D Session Notes Template: Turn Table Notes Into Next-Session Prep

You finish a great session. The party made a deal with a suspicious guide, gave a cursed ring to an NPC, angered a local guild, and announced that they are sailing north next week.

guide = 40 gp? knows smugglers / ring to Ilyra / guild mad / NORTH

That is not bad note-taking. It is exactly what a live game produces: useful fragments written while you are listening, ruling, roleplaying, and keeping the table moving.

The problem begins later. If those fragments stay as fragments, next week's prep starts with reconstruction: What did Ilyra promise? Which guild? Was north a plan or a joke? After enough sessions, the campaign becomes a pile of recaps that is technically complete but difficult to use.

This template gives every session three outputs:

1. Record: what became true at the table.
2. Pressure: what is still moving, unresolved, or likely to react.
3. Prep: the few things worth making ready for the next session.

You can use it in a notebook, a document, a wiki, or on index cards. The format matters less than the separation.

Why a recap alone is not enough

A recap answers, “What happened?” That is essential, but it asks one question too few.

Good campaign management also needs to answer:

• What changed because of it?
• Who knows, wants, fears, or owes something new?
• What has a clock on it?
• What did the players say they want to do next?
• What can I prepare without deciding the players' choices for them?

If you mix all of those into one running paragraph, future-you has to interpret every line again. The Record → Pressure → Prep method gives each kind of information a home and makes the next decision easier.

The 15-minute post-session workflow

Do this after the session or the next morning, while the table is still fresh. Set a timer. The goal is not perfect documentation; it is a usable handoff to your future self.

First, save the notes exactly as they were written. Do not clean them up while you are trying to remember the whole night. Raw notes contain timing, wording, and uncertainty that a polished recap can accidentally erase.

Then write a four-to-six-bullet factual recap. Use past-tense verbs and include only things that happened or were established at the table.

Example: factual recap

• The party accepted guide Mara Venn's offer to take them through the Salt Marches for 40 gp and safe passage.
• Tovin gave the black ring to Ilyra at the Lantern House.
• Guild factor Harrold publicly blamed the party for the warehouse fire.
• The party learned that a smuggler vessel leaves Greywake in six days.
• The group ended the session intending to find passage north.

List only the things whose current state changed. This is the part most recaps bury, and it is why a returning NPC or location can feel inconsistent months later. Use five headings and leave any empty.

This is not a full encyclopedia. Capture only changes that could matter later. A tavernkeeper's name can stay in the raw record until it matters; the identity of the person holding a dangerous artifact should not.

The pressure list contains things that may move if the players do nothing: unresolved questions, promises, threats, opportunities, and consequences. Keep it short, active, and testable.

When a pressure belongs to a character concern, the player spotlight tracker helps turn it into an optional, group-friendly invitation.

Example pressure list

The phrase likely move matters. It lets the world react without promising a single scene. Players can negotiate with Harrold, flee town, frame someone else, or ignore him; your preparation should support consequences, not force a route.

Prep only the next useful layer. A strong brief gets you to the table with direction while leaving players room to surprise you.

SESSION [number] — NEXT-SESSION BRIEF

Where play resumes:
[Place, immediate situation, and who is present.]

Opening pressure:
[One sensory or social signal that makes the current situation move.]

What the players said they may do:
1. [Intention]
2. [Intention]
3. [Intention, if any]

Three prepared responses (not required scenes):
1. [If they pursue the most likely direction...]
2. [If they investigate or negotiate...]
3. [If they change direction...]

People/places to have ready:
- [Name]: [current goal, leverage, or attitude]
- [Location]: [what has changed or what it can reveal]

One reveal or decision point:
[Information that becomes available if the players earn, notice, or ask for it.]

Stop prep here:
[The boundary that prevents you from writing the party's choices in advance.]

Filled example

SESSION 19 — NEXT-SESSION BRIEF

Where play resumes:
Outside the Lantern House at dawn. Ilyra has not come downstairs.

Opening pressure:
Saltwater drips from beneath Ilyra's door while two Dockside Guild agents question the innkeeper.

What the players said they may do:
1. Check on Ilyra.
2. Find a ship north.
3. Deal with the guild before leaving town.

Three prepared responses:
1. The ring's influence has pulled Ilyra toward the flooded cellar; it offers clues, not a mandatory fight.
2. The smuggler captain wants a favor or a false manifest before offering passage.
3. Harrold will accept restitution, a scapegoat, or useful information; violence is his costly option.

People/places to have ready:
- Mara Venn: wants the job but will not cross the Guild for free.
- Greywake docks: departure board, a nervous deckhand, Guild eyes.

One reveal or decision point:
The ring belonged to a drowned customs officer who investigated the smuggler route.

Stop prep here:
Do not decide whether the party boards the ship, gives up the ring, or fights the Guild.

The complete session-notes template

Use this as a standing page for every session.

# Session [number]: [short title]
Date played: [date]

## Raw table notes
[Keep the messy notes, initiative scraps, and exact wording worth preserving.]

## Record: what became true
-
-
-

## Change log
### People
-
### Factions
-
### Places
-
### Things
-
### Knowledge
-

## Pressure list
| Pressure | Source | Clock | Likely move | Next evidence |
|---|---|---|---|---|
| | | | | |

## Player-facing recap (optional)
[What the characters would reasonably know; omit GM-only causes, clocks, and future moves.]

## Next-session brief
### Where play resumes

### Opening pressure

### Player intentions
1.
2.
3.

### Three prepared responses
1.
2.
3.

### People/places to have ready
-

### One reveal or decision point

### Stop-prep boundary

## After the next session
[Move resolved pressures to the record; update only what changed.]

Keep facts, interpretation, and prep separate

This is the rule that protects both continuity and player agency.

If an interpretation later proves wrong, nothing has been retconned—you simply had a possibility, not a fact. If players change their minds, you still have a prepared response instead of a wasted script.

Common mistakes that make notes harder to use

If you missed a few updates

Do not begin with the entire campaign. Pick the last session you can confidently reconstruct, run the template for it, and work forward only until you have a usable current brief. Then use the 30-Minute D&D Campaign Continuity Audit to find the important threads and state changes that deserve backfilling.

The goal is not an immaculate wiki. It is a campaign you can resume with confidence.

Make the second pass the useful one

The notes you take during play do not need to be elegant. They need a short second pass that separates what happened, what is now moving, and what you will prepare next. Make that pass a 15-minute habit, and every session leaves the campaign easier—not harder—to run.