D&D Session Notes Template for Dungeon Masters

Introduction

A D&D session notes template is not a diary.

It is a working surface.

It should help you remember what happened, prepare what might happen next, and find the one NPC name your players suddenly care about. If your notes are beautiful but impossible to use at the table, they are not doing their job. If your notes are messy but they help you run the next session with confidence, they are closer to what most Dungeon Masters actually need.

Separate three things that often get mixed together:

• prep before the session;
• notes during the session;
• cleanup after the session.

Each one needs a different shape. Prep wants prompts. Live notes want speed. Cleanup wants clarity.

This guide gives you a practical D&D session notes template you can adapt for homebrew campaigns, published adventures, one-shots, sandbox games, mystery campaigns, and long-running tables. It also explains what belongs in each section, what to leave out, and how to keep your notes useful after session five, session twenty, or session sixty.

Table of Contents

• What session notes are supposed to do
• The core D&D session notes template
• Prep notes before the session
• Live notes during the session
• Post-session cleanup
• How much detail to write
• Templates for different campaign styles
• Practical examples
• Common mistakes
• FAQs
• Final thoughts

What Session Notes Are Supposed To Do

Session notes should answer questions quickly.

Not every question. The useful ones.

Before a session, your notes should answer:

• where does play probably start?
• what unresolved pressure is active?
• who might appear?
• what clues, secrets, or consequences should be available?
• what scenes are likely, but not mandatory?
• what rules or stat blocks might you need close by?

During a session, your notes should capture:

• names the table invents;
• choices the players make;
• promises NPCs make;
• damage done to relationships, places, and plans;
• loot, clues, and information revealed;
• unresolved questions;
• anything you improvised and want to keep canon.

After a session, your notes should preserve:

• what actually happened;
• what changed because of it;
• what each faction, villain, or NPC does next;
• what the players seem interested in;
• what you need to prep before next time.

That is enough.

A lot of DMs make notes harder because they try to document the whole fictional world. You do not need a complete archive. You need continuity. You need the next session to feel like it remembers the previous one.

That is the standard.

The Core D&D Session Notes Template

Here is the plain version.

Use it in Google Docs, Notion, Obsidian, a notebook, markdown, or a campaign workspace.

# Session [Number]: [Title]

Date:
Party level:
In-game date:
Current location:

One-Sentence Recap

[What happened last time in one sentence.]

Strong Start

[The first image, situation, or decision of the session.]

Active Pressure

• [Villain/faction/threat]: [What they are doing if ignored]
• [Clock/timer/problem]: [What changes soon]

Likely Scenes

NPCs Likely To Appear

• [Name]: [Want], [mannerism], [secret or pressure]

Secrets And Clues

• [Truth the players can learn]
• [Truth the players can learn]
• [Truth the players can learn]

Encounters Or Obstacles

• [Combat, social, exploration, trap, chase, puzzle]

Rewards And Costs

• [Loot, favor, information, relationship, complication]

Live Notes

End Of Session Cleanup

What happened: What changed: Player interests: NPC/faction reactions: Next session starts with: Prep before next time:

That template is short.

A session template should not become homework you dread. If you want more detail, add it after the basics work. Do not start with a giant system and then feel guilty when you abandon it.

Prep Notes Before The Session

Prep notes are not predictions.

They are supports.

The players may ignore your expected scenes, interrogate the wrong person, befriend the enemy, burn the evidence, adopt an NPC you invented in six seconds, or spend forty minutes arguing over whether the suspicious well is too suspicious.

That is normal.

Good prep notes give you things you can move.

The One-Sentence Recap

Write the last session in one sentence.

Not a paragraph. One sentence.

Example:

The party exposed the priest's false miracle, rescued the missing apprentice, and learned that the silver bell was stolen before the fire.

This sentence reminds you what the players think the campaign is about right now.

It also makes your spoken recap easier. You can expand at the table, but the core is there.

The Strong Start

A strong start is the first playable moment.

It does not need to be dramatic every time. It just needs to put the table into a scene.

Weak start:

You wake up. What do you do?

Better start:

Rain hammers the chapel roof. The rescued apprentice is awake, terrified, and whispering the same phrase over and over: "The bell rang under the river."

Now the players have something to react to.

A strong start can be:

• an NPC demanding an answer;
• a visible consequence of last session;
• a new clue;
• an immediate danger;
• a quiet scene with emotional weight;
• a travel decision;
• a strange image that asks for investigation.

Write one or two sentences. Do not script a speech unless the exact words matter.

Active Pressure

This is the section that keeps campaigns alive.

If the party does nothing, what moves?

Examples:

• The cult relocates the prisoners before dawn.
• The duke blames the wrong village for the assassination.
• The rival adventuring party reaches the ruin first.
• The plague spreads to the river district.
• The dragon's agent buys the last map.

Active pressure prevents the campaign from becoming a waiting room.

You do not need ten active pressures. One to three is enough for most sessions.

If you use SessionRoll, this is where generated factions, campaign clocks, villains, and secrets become useful. Instead of starting from a blank page, you can turn one generated faction goal into a pressure line: what will they do next if the party ignores them?

Likely Scenes

Write three likely scenes, each with a purpose.

Do not write a plot chain.

Use this shape:

Scene: purpose

Examples:

• Chapel cellar: reveal the bell was stored below ground, not in the tower.
• Market square: show public anger turning against the wrong suspect.
• River shrine: offer a dangerous route to the hidden chamber.

The purpose matters more than the location. If players skip the chapel cellar but investigate the old sexton, the clue can move. The purpose survives.

NPCs Likely To Appear

Most session notes need fewer NPC details than DMs think.

For each likely NPC, write:

• name;
• want;
• one table-facing detail;
• one hidden truth, pressure, or limit.

Example:

Mara Vell, chapel clerk. Wants the scandal to end before her brother is blamed. Keeps rubbing ink from her thumb. Knows the stolen bell was copied, not taken.

That is enough to run her.

You do not need her full childhood unless the campaign already cares.

Secrets And Clues

Secrets and clues are the backbone of flexible prep.

Write truths, not locations.

Instead of:

The bloody glove is in the stable.

Write:

Someone from the chapel handled the murder weapon after the fire.

Now that truth can appear as a glove, a witness statement, ash under fingernails, an anxious confession, or a divine vision.

For most sessions, prepare three to seven truths the players might learn.

For mysteries, prepare more. For combat-heavy sessions, prepare fewer.

Encounters Or Obstacles

Do not limit this section to combat.

An encounter can be:

• a locked archive;
• a hostile witness;
• a collapsing bridge;
• a patrol with orders;
• a negotiation;
• a monster;
• a cursed object;
• a moral decision;
• a chase through crowded streets.

Write the obstacle and what makes it interesting.

Weak:

Bandits attack.

Better:

Bandits stop the party at the old toll road, but they are hungry villagers wearing stolen masks. Fighting them solves the ambush but worsens the village problem.

Now the encounter has a campaign connection.

Rewards And Costs

Rewards are not always loot.

Useful rewards include:

• information;
• safe passage;
• faction favor;
• a new contact;
• a map;
• a public reputation shift;
• a rescued NPC;
• access to a restricted place;
• an owed favor;
• a clue that changes the players' theory.

Costs matter too.

If the players choose one lead, what worsens elsewhere? If they save one NPC, who remains in danger? If they spend resources here, what becomes harder later?

Session notes should remind you that choices echo.

Live Notes During The Session

Live notes must be fast.

Do not write polished prose while players are waiting.

Use fragments.

Good live notes look like this:

- promised Mara protection
- Toren insulted Captain Vel, captain now hostile
- players suspect river shrine, not duke
- improvised tavern: Glass Heron, owner Pela, owes tax debt
- gave party silver key from apprentice
- wizard cast detect magic on bell fragment: necromancy and illusion
- end: party entering river tunnel

That is all you need.

You can clean it later.

Mark Canon Immediately

The most dangerous improvisations are the ones you forget.

If you make up:

• an NPC name;
• a shop name;
• a price;
• a relationship;
• a rumor;
• a faction symbol;
• a rule ruling;
• a clue;
• a promise;

write it down.

Players will remember the tiny detail you invented while reaching for a drink.

Your notes need to remember it too.

Use Tags If They Help

You can use simple tags:

• NPC: Pela owns Glass Heron
• CLUE: bell fragment has necromancy
• RULING: climbing wet chain DC 14
• PROMISE: party owes dockworker 20 gp
• INTEREST: players loved river shrine

Do not build a complex tag system before you know you need one.

Start simple.

Write Player Interest

This is one of the most valuable note types.

If players lean forward, laugh, argue, get suspicious, protect someone, or ask three follow-up questions, write it down.

Examples:

• players love Mara;
• suspicious of duke, even without evidence;
• want more about old river gods;
• cleric interested in bell curse;
• group bored during tax negotiation;
• combat with masks worked well.

This tells you what to prep next.

Great campaigns often come from noticing what the table already cares about.

Post-Session Cleanup

Cleanup should take ten minutes.

Do it soon after the session if you can. The next morning is fine. Two weeks later is where details start vanishing.

Use five prompts.

What Happened?

Write three to seven bullets.

Example:

• The party questioned Mara and learned the bell was copied.
• They angered Captain Vel by accusing him in public.
• They found necromancy on the bell fragment.
• They chose the river tunnel over the duke's invitation.
• They ended outside a sealed shrine door.

This is your durable recap.

What Changed?

This is more important than what happened.

Examples:

• Captain Vel is now hostile.
• Mara trusts the party.
• The public rumor shifts toward the chapel.
• The villain knows someone is investigating the bell.
• The river shrine is now the next active location.

Campaigns feel alive when the world changes.

Who Reacts?

List NPCs and factions that respond before next session.

Example:

• Duke sends polite invitation with hidden threat.
• Bell cult moves the real relic.
• Mara hides her brother.
• Captain Vel posts guards near the river.

If nobody reacts, the session may feel isolated.

What Do Players Care About?

This is your compass.

Players may care about:

• a clue;
• an NPC;
• a theory;
• a joke;
• a place;
• an enemy;
• a mystery;
• a moral question;
• a magic item;
• a personal connection.

Write it.

Build toward it.

What Starts Next Session?

End cleanup by writing the next strong start.

Even if you change it later, future-you will be grateful.

Example:

Next session starts with the river shrine door opening from the inside. Someone has been waiting for them.

That one line removes a lot of blank-page stress.

How Much Detail To Write

Use less detail than you think.

The more words you write, the harder it becomes to find the right sentence during play.

For most sessions, use:

• one sentence of recap;
• one strong start;
• three active pressures or fewer;
• three likely scenes;
• three to seven secrets or clues;
• three to six NPC notes;
• one to three encounters or obstacles;
• live notes in fragments;
• cleanup in bullets.

If you are running a dense mystery or political intrigue campaign, you may need more relationship notes. If you are running a dungeon crawl, you may need room details, traps, treasure, and wandering pressure. If you are running a light one-shot, you may need far less.

The template should serve the campaign.

Do not serve the template.

Templates For Different Campaign Styles

The core template works, but different campaigns need emphasis in different places.

For mysteries, add the known truth, suspects, clue paths, false theories, and what happens if players accuse the wrong person. Never make one clue carry the whole session.

For sandbox campaigns, add available leads, nearby locations, faction clocks, travel procedures, rumors, and what changes if the party goes elsewhere. Sandbox notes should help you react, not force a route.

For urban campaigns, add district mood, current rumors, law or social pressure, faction presence, and what the city watch cares about. Cities become easier to run when each district has pressure, not just scenery.

For dungeon sessions, add room purpose, sensory cues, wandering pressure, locked paths, treasure, rest consequences, and what players can learn. Dungeon notes should answer what players notice, what can hurt them, and what can change.

For political sessions, add public goals, private goals, leverage, rumor, debt, scandal, and who benefits if talks fail. Political notes should keep motives visible. Names alone are not enough.

Practical Examples

Example: Notes Before A Session

# Session 8: The Bell Under The River

Date: July 18
Party level: 4
Current location: Stoneford

One-Sentence Recap

The party exposed the false miracle, saved Mara's apprentice, and learned the stolen bell may still be inside the city.

Strong Start

Rain lashes the chapel roof while the apprentice wakes and whispers, "The bell rang under the river."

Active Pressure

• Bell cult: moving the real relic before dawn.
• Captain Vel: posting guards after being publicly accused.
• Duke: trying to invite the party away from the investigation.

Likely Scenes

1. Chapel recovery room: learn what the apprentice saw.
2. Market square: hear public blame shifting toward Mara.
3. River tunnel: find the shrine door and old bell marks.

NPCs

• Mara Vell: wants her brother safe, ink-stained thumb, knows the bell was copied.
• Captain Vel: wants order, clipped speech, angry at public embarrassment.
• Oren Pike: ferryman, wants payment, saw lights under river at midnight.

Secrets And Clues

• The bell fragment is a copy.
• The real bell was moved below the river.
• Someone in the duke's house paid for silence.
• The cult needs the bell rung during rainfall.
• The apprentice saw a blue handprint on the shrine door.

Obstacles

• River tunnel has rising water.
• Guards patrol the old quay.
• Shrine door opens only when the copied bell is struck.

That is not a script. It is a tool.

### Example: Live Notes

```markdown
- cleric healed apprentice, apprentice trusts him
- rogue stole captain's warrant
- players ignored duke invitation
- invented NPC: Oren Pike, ferryman, bad knee, afraid of bells
- wizard identified bell copy
- party thinks duke is too obvious
- ending: shrine door opens, blue hand visible

Ugly notes. Useful notes.

Example: Cleanup

What happened:
- Party confirmed the bell fragment was a copy.
- They avoided the duke and entered the river tunnel.
- Rogue stole Captain Vel's warrant.
- Oren Pike became a useful contact.

What changed:
- Captain Vel has legal reason to pursue them.
- Duke knows they refused him.
- Bell cult accelerates the ritual.

Player interests:
- They liked Oren.
- They are suspicious of the duke but unsure.
- They care about the apprentice.

Next start:
- The shrine door opens from inside. A blue hand gives the rogue the stolen warrant back.

That cleanup is enough to prep the next session.

Common Mistakes

Writing Too Much Lore

Lore belongs in campaign notes, not every session note.

If the lore matters this session, include the part that can appear in play. If not, leave it in the larger campaign file.

Hiding The Useful Information

Some DMs write long recaps and then cannot find the one thing they need.

Use headings. Use bullets. Use bold if your tool supports it. Put important NPCs and clues where your eyes can find them.

Treating Expected Scenes As Required Scenes

Likely scenes are not a railroad.

If the players solve the problem another way, move the important clue or consequence. Your notes should bend.

Forgetting What Was Improvised

Improvised names and promises become canon fast.

Write them during play. Even one ugly bullet is enough.

Skipping Cleanup

The session is not really prepped for next time until you know what changed.

Cleanup is where continuity happens.

Keeping Separate Notes That Never Meet

If your NPC notes, session notes, clue notes, faction notes, and quest notes all live in different places, you need reliable links between them.

This is where a structured campaign workspace helps. SessionRoll's Workspace keeps sessions, notes, quests, NPCs, factions, locations, lore, encounters, and generated campaign material in one place, which is useful once the campaign grows beyond a single document.

FAQs

What should be included in D&D session notes?

Include a short recap, strong start, active pressures, likely scenes, NPCs, secrets and clues, obstacles, rewards, live notes, and cleanup prompts. You can add rules references or stat blocks when they are likely to matter.

How long should D&D session notes be?

Most session notes can fit on one to three pages. Mystery or political sessions may need more. If you cannot quickly find NPCs, clues, and consequences during play, the notes are probably too long or poorly organized.

Should I write session notes before or after the game?

Both. Before the game, write prep notes. During the game, capture quick live notes. After the game, clean up what happened and what changed. Those are three different jobs.

What is the best app for D&D session notes?

The best app is the one you will actually use. Google Docs, Notion, Obsidian, OneNote, markdown files, paper notebooks, and campaign workspaces can all work. Retrieval matters more than fancy formatting.

How do I take notes while DMing without slowing the game?

Write fragments, not sentences. Capture names, decisions, clues revealed, promises, rulings, and player interests. Clean the notes after the session instead of trying to make them pretty during play.

Should players see the DM's session notes?

Usually no. Keep GM-only secrets separate from player-facing recaps. You can share a public summary, known NPC list, quest log, or discovered lore, but private motives and unrevealed clues should stay hidden.

How do I organize notes for a long campaign?

Separate session logs from durable campaign records. Session notes answer what happened in a specific game. Campaign records track NPCs, factions, locations, quests, lore, items, and unresolved threads across many sessions.

Can SessionRoll help with session notes?

Yes. SessionRoll can generate campaign foundations, NPCs, factions, clues, encounters, prophecies, and campaign pressure, then Pro users can organize that material in a GM Workspace. You still decide what happened at your table and what changes next.

Final Thoughts On D&D Session Notes Template

A D&D session notes template should make running the game easier.

That is the whole point.

You do not need perfect notes. You need notes that remember what the table cares about, what changed, and what might happen next. Keep the structure simple. Write active pressure. Capture improvised details. Clean up after the session while the game is still fresh.

Do that, and your campaign starts feeling less like a stack of disconnected episodes and more like a world that remembers the players were there.