D&D Campaign Journal: Free Template + What to Track

A D&D campaign journal is the page you open when someone asks, "What is happening in this campaign right now?" It tracks the party's current situation, active quests, open mysteries, important people and places, and the consequences still following them.
That makes it different from a stack of session notes. Notes tell you what happened. A good journal tells you what remains true because it happened.
Once a campaign gets past ten or fifteen sessions, history starts crowding out the information you need tonight. The dragon the party fought eight months ago may be a fond memory. The dragon's surviving cult, which now knows the party's names, belongs in the journal.
The free template below is built for DMs, but players can use a spoiler-free version too. Copy it into any document or notebook. You can also print the headings and fill them in by hand.
What is a D&D campaign journal?
A campaign journal is a compact record of the campaign's present state. It sits between your raw notes and your next session plan.
The official 2024 Dungeon Master's Guide campaign-journaling advice treats a journal as something a DM can use before, during, and after a game. That is a useful starting point. The mistake is letting all three stages pile into the same undifferentiated document.
Plans are not canon. Table notes are messy. The journal should contain the cleaned-up truth after the dice stop rolling.
Suppose you planned for the party to bargain with Captain Veyra, but they exposed her smuggling ring and burned her ship instead. Your prep notes still contain the bargain. Your table notes contain fragments such as "Veyra angry," "ship fire," and "Milo owes dockmaster 200 gp."
The journal records the new state:
Captain Veyra has lost her ship and knows the party exposed her. Milo owes Dockmaster Rusk 200 gp for the damaged pier. The harbor watch is searching outgoing vessels.
That paragraph can drive next week's prep. The abandoned bargain cannot.
How is a campaign journal different from notes, recaps, and a wiki?
These documents solve different problems. Combining them is how one file turns into a 70-page attic.
| Document | Question it answers | Best audience | What belongs there |
|---|---|---|---|
| Session notes | What happened at the table? | DM or note taker | Rough events, names, rulings, improvised details |
| Session recap | What does the group need to remember? | Players | Major events, decisions, discoveries, cliffhanger |
| Campaign wiki | What do we know about this person, place, or faction? | DM and players | Separate linked pages for world entities and lore |
| Campaign journal | What is true and active now? | Primarily the DM | Current situation, quests, mysteries, consequences |
For the first row of that table, see our guide to D&D session notes, which covers what belongs in them and how to get them written for you. If you need help choosing how to capture events during play, the D&D note-taking apps comparison covers that decision. If you want a reference organised around NPCs and locations, read the campaign wiki guide. This article stays with the journal: the short document that carries campaign state from one week to the next.
A D&D campaign journal template you can copy
The best template is short enough to update while the session is still fresh. Start with this version and remove any section you repeatedly leave blank.
# Campaign name
Last session:
In-game date:
## Current situation
Where is the party? What just changed? What immediate pressure are they under?
## Active quests
- Quest:
Status: New / Advanced / Blocked / Failed / Complete
Next known step:
Stakes:
## Unresolved mysteries
- Question:
What the party knows:
Last relevant clue:
## Important people and places
- Name:
Current role or condition:
Relationship to the party:
Last change:
## Consequences and obligations
- Decision, debt, promise, enemy, deadline, or lost resource:
## Party state
- Important resources:
- Conditions or injuries:
- Reputation changes:
## Next-session starting point
The exact scene, decision, or threat waiting when play resumes:
You do not need a page for every shopkeeper. You need the shopkeeper who saw the rogue hide the murder weapon. A journal earns its space by changing what you prepare or how you run the world.
The official D&D campaign journal tracking sheet is another useful format, especially if you prefer a one-page printable. Its session-based layout works well for planning and quick notes. The template above adds a current-state layer so unresolved material survives beyond one session.
What does a completed entry look like?
Here is a fictional example from session 24 of The Ash Lanterns. Notice how little of it reads like a story. It is meant to make session 25 easier to run.
Current situation
The party is hiding beneath Saint Orra's abandoned hospice after escaping the city archive. Magistrate Veyra has blamed them for the fire. The eastern gates are closed until dawn, and the watch has sketches of Brann and Sella.
Active quests
Clear their names
Status: Advanced
Next step: Find Archivist Pell, who copied the original shipping ledger.
Stakes: If the party leaves the city as fugitives, the Crown will seize their property.
Find the Glass Saint
Status: Blocked
Next step: Decode the phrase "where the river remembers."
Stakes: The cult reaches the reliquary in three days.
Unresolved mysteries
Who removed page 47 from the shipping ledger?
The party knows the missing page listed cargo from Veyra's ship. Pell signed the archive register that night.
Why did the hospice bell ring after midnight?
The building has no bell. Sella heard it immediately before the hidden stair opened.
Important people and places
Magistrate Veyra: Now openly hostile. Lost control of the ledger but controls the city watch.
Archivist Pell: Missing. Possible witness or accomplice.
Saint Orra's Hospice: Current refuge. Contains a hidden stair descending below the old chapel.
Consequences and obligations
- Brann promised Dockmaster Rusk 200 gp for the burned pier.
- The party left Captain Veyra alive, so she can identify them.
- Sella used the last charge in the mirror key.
Next-session starting point
Boots stop directly above the hidden room. Someone tries the chapel door while a voice below the party whispers Sella's name.
That is enough. You can prep the search above, whatever lives below, and Pell's current location. The journal has narrowed an entire campaign to the decisions that matter on Tuesday night.
How do you update the journal in ten minutes?
Update it as soon as practical after the session. Waiting three days turns clear memories into confident guesses.
1. Replace the current situation
Do not append another paragraph beneath last week's situation. Rewrite it. This section should describe now, even if that means deleting a scene you loved.
2. Move every active quest
Give each quest one status: new, advanced, blocked, failed, or complete. Then write the next step the party currently understands. If there is no next step, that is useful information. They need a clue.
3. Keep unanswered questions, not every secret
An unresolved mystery is a question the party might reasonably pursue. "Why did the hospice bell ring?" belongs. Forty pages of hidden cosmology do not.
4. Record changed facts
Update loyalties, locations, injuries, deadlines, ownership, and reputation. These are the details most likely to cause continuity errors later. If an NPC switched sides, write who knows and why.
5. End at the next playable moment
Write the first pressure the players will face when the next session begins. This can be a threat, a decision, or a question. It should be specific enough that you could start running after reading one sentence.
Mike Shea's guide to organizing RPG prep notes makes a related point: the system should stay simple and adapt to the way you run games. If your journal takes an hour every week, the problem is the journal, not your discipline.
Kelsey Dionne from The Arcane Library shows a practical paper setup here:
What should you leave out?
The campaign journal is not the place for material you can retrieve elsewhere.
- Full monster stat blocks belong with encounter prep.
- Detailed biographies belong in character or NPC pages.
- Read-aloud descriptions belong in the session where you expect to use them.
- Complete transcripts belong in an archive.
- Finished quests belong in campaign history unless their consequences remain active.
The DMAcademy discussion that currently ranks for campaign-journal searches contains encounter tables, loot tables, maps, shop inventories, character abilities, and session logs. None of those are bad things to keep. They simply do not all need to live in the same working view.
My rule is blunt: if an entry will not affect a future decision, archive it.
Can you start halfway through a campaign?
Yes, and starting late may be easier. You already know which material survived contact with the players.
Do not rebuild sessions 1 through 22 before documenting session 23. Write the current situation. List every quest the players still discuss. Add the mysteries they can still investigate and the people likely to return. That is your first journal entry.
Backfill on demand. If the party decides to revisit a ruined monastery from session 6, recover what matters about the monastery then. You are running a game, not restoring an archaeological site.
This approach also prevents the journal from competing with your campaign history. Old events can remain in recaps or a wiki. The journal only pulls their consequences forward when they become active again.
Should players see the journal?
Give players a clean version, but keep a GM layer for information their characters do not know.
The shared version can include current goals, known NPCs, discovered clues, party promises, and the last stopping point. The GM version can add hidden clocks, private motives, false assumptions, and consequences that have not arrived yet.
Keep the journal compact and the player copy becomes simple. Removing three secret lines is easy. Sanitizing twelve pages of mixed notes is how the recap gets postponed until ten minutes before the next game.
What if you do not want another document to maintain?
A manual journal works only while someone keeps updating it. That may be part of the fun for you. If it is not, the useful test is whether the journal can be built from work you already do.
Saga20's Campaign Journal is updated from your session recording. It keeps the current situation, quests, mysteries, and important people or places in one GM view. You review what changed after the session instead of reconstructing the night from memory. The linked world builder keeps the deeper character and location history elsewhere, so the journal can stay focused on what matters next.
Five minutes before the game, you should be able to open the journal and see where the story stands. If you cannot, cut it back until you can.
Free Tools
Helpful for This Topic
Session Recap Generator
Turn the player-facing highlights in your journal into a recap card the group can keep.
Session Recap Architect
Build a printable structure for the rough notes that feed your journal after each game.
Session Recap Scribe
Paste the table notes behind your journal and turn them into a readable session recap.
Drop the notebook
Try Saga20 for free
Record your session. We'll write the notes and build your wiki.
Get started freeNo card needed
