Curse of Strahd DM notes: a campaign tracker for everything the book cannot know
This is not a walkthrough or a summary of the adventure, and it names nothing beyond what is on the book’s own contents page. It is the sheet for the half of a Curse of Strahd campaign that exists only at your table: what the reading said, where the party has been, who they have turned into an enemy, and what was promised to whom.
· 6 min read
What Curse of Strahd DM notes are for
There are two kinds of notes for a published adventure, and they do opposite jobs. Prep notes shrink the book: a page per chapter in your own words, so you are not reading at the table. Running notes record what the book cannot contain: what your players did to it. If you came for the first kind, a chapter-by-chapter summary or advice on running each location, this is not that page, and the adventure has a large community that has written years of them.
This page is the second kind, and Curse of Strahd needs it more than most adventures. It is a long book, 256 pages for levels one to ten, in fifteen chapters, thirteen of them named for a place. And its opening card reading randomises where key things are, so your Barovia is your own from the day the cards are drawn. Thirty sessions in, the book is still accurate about the map and wrong about nearly everything else: who is alive, who is hostile, what has already happened in Vallaki.
The Curse of Strahd campaign tracker (copy this)
One page for the whole campaign, rewritten after each session, not added to. The place names are the book’s chapter titles; everything after the colon is yours. Paste it into whatever your campaign already lives in.
Curse of Strahd campaign tracker (copy this)
CURSE OF STRAHD - CAMPAIGN TRACKER
Session #: __ In-world day: __ Party level: __
THE READING (Fortunes of Ravenloft)
card 1, artifact:
where: found? held by:
card 2, artifact:
where: found? held by:
card 3, artifact:
where: found? held by:
card 4, Strahd's enemy:
where: met? on our side?
card 5, Strahd:
where:
what the party THINKS it meant:
STRAHD
times they have met him: last (session, where):
what he has learned about each character:
what he wants from the party right now:
what the party wrongly believes about him:
PLACES (visited s__ / what changed / left unfinished)
Village of Barovia:
Castle Ravenloft:
Town of Vallaki:
Old Bonegrinder:
Argynvostholt:
Village of Krezk:
Tsolenka Pass:
Ruins of Berez:
Van Richten's Tower:
Wizard of Wines:
Amber Temple:
Yester Hill:
Werewolf Den:
SPECIAL EVENTS (the book lists them chapter by chapter)
happened: session: outcome:
primed, party is close:
PEOPLE
allies (who / why they help / what they were promised):
enemies made (who / over what / session):
dead (who / session / who knows):
invitations, letters and bargains still in play:
THE PARTY
promises and debts:
items that matter, and who carries them:
the question the players keep asking:Write the Tarokka reading down before anything else
The reading is the one part of the campaign that exists nowhere but in your notes. As D&D Beyond’s own write-up describes it, the cards set the locations of three artifacts that can defeat Strahd, of Strahd’s enemy, and of Strahd himself, and because they are drawn at random the answer belongs to your table alone. Lose that page and no amount of rereading the book gets it back.
So record it in full the day you do it: each card, where it points, and later whether the thing has been found and who holds it. The same article suggests doing the reading privately ahead of time if it is your first run, so you can prepare for the locations instead of taking notes on the fly. Whether you do it in advance or at the table, the result goes at the top of the tracker.
Then add the line most trackers leave out: what the party thinks the reading meant. Players interpret a fortune, argue about it and act on their interpretation for months. Their wrong reading of it is as much a fact of your campaign as the right one, and it is the first thing you forget.
A villain who comes back needs a log
A villain the party meets once needs a stat block. One they meet again and again needs a memory, and you are it. After every appearance, write three things: what he saw the party do, what he said he wanted, and what he now knows about each character that he did not before. Next time he appears, he acts on that list, and the table feels watched in a way no description achieves.
Keep the players’ beliefs about him on the same block. What they think he wants, what they think he cannot do, what they believe they got away with. A campaign this long turns on the gap between those beliefs and the truth, and you can only use the gap if you remember what it is.
One line per place: visited, changed, unfinished
The book’s chapters are places, and the party will leave most of them with business unfinished and come back weeks later. Give each place one line and keep it current: the session they were last there, what is different because of them, and what they walked away from. That line is what you read before they return, and it is usually enough.
Most of those chapters also list special events. Note which have happened, in which session and how they came out, and which are primed because the party is nearby. An event you forgot you already ran is the most visible continuity mistake a DM can make in this adventure, because the players will remember it.
People: allies, enemies and the dead
An adventure with this many named places produces a long cast quickly. The tracker keeps only their status, in three lists: who is helping and what they were promised, who the party has made an enemy of and over what, and who is dead and who knows it. For anyone the party talks to more than twice, keep a card as well: the NPC tracker template has one built for continuity, with the voice, what they know and what was promised both ways.
Groups get the same treatment at a larger size. Where a town, an order or a family acts as one, track its stance toward the party as a consequence of what the party did, session by session, on a faction tracker.
The tracker is now; keep a session log for then
A tracker you overwrite cannot tell you when something happened or how. That is the job of a session log: ten minutes after each game, a dated entry with what happened, what you improvised and are now committed to, and what the party decided to do next. The session notes templates include a log sheet and the one-line-per-beat sheet to take notes on during play. Update the tracker from the log, never the other way round.
Curse of Strahd notes in Obsidian, OneNote, Notion or Kanka
The tracker is plain text on purpose, so it pastes into any of them. In Obsidian or OneNote, make it the campaign’s front page and give each place its own note underneath, linked from its line. In Notion, the places and people lists become two small databases with a status column. In Kanka, the places are locations and the people are characters, and the tracker is a pinned note that points at them.
The tool matters less than whether you can answer a player’s question in ten seconds at the table. If you are choosing one, Obsidian and Notion and Kanka each have a comparison here that says what they are best at.
Why the notes matter more the longer it runs
A book that takes characters from first level to tenth is a long campaign: six months to a year of weekly play by the arithmetic in the session-length guide, and longer at a fortnightly table. Over that span the book stays the same and your table’s version of it drifts further every week. By the final chapters, your tracker is the only accurate description of the place that exists.
If you record your sessions, the reading and every promise are on the recording, which takes the pressure off writing during the scenes that matter most. The tracker is still worth keeping. A recording tells you what was said; the tracker tells you where things stand.
What this page says about the book, with sources
Every third-party figure quoted above, with where it came from and when it was checked. Prices move — if a date here is old, verify before relying on it.
| What | Value | Source |
|---|---|---|
| Curse of Strahd: length and levels | "A fantasy-horror adventure for characters levels 1-10"; a "256-page horror adventure" | sourceas of 2026-11-13 |
| Curse of Strahd: the chapters | Fifteen chapters on the public contents page: Into the Mists; The Lands of Barovia; The Village of Barovia; Castle Ravenloft; The Town of Vallaki; Old Bonegrinder; Argynvostholt; The Village of Krezk; Tsolenka Pass; The Ruins of Berez; Van Richten’s Tower; The Wizard of Wines; The Amber Temple; Yester Hill; Werewolf Den | sourceas of 2026-11-13 |
| Curse of Strahd: sections the tracker follows | Chapter 1 contains "Fortunes of Ravenloft"; "Special Events" is listed under 11 of the 15 chapters; Appendix E is "The Tarokka Deck" | sourceas of 2026-11-13 |
| What the Tarokka reading sets | D&D Beyond, 30 October 2019: "The first three cards are drawn from the low deck, and determine the location of the three artifacts capable of defeating Strahd"; "the fourth card determines the location of Strahd’s enemy, and the fifth card determines the location of Strahd himself" | sourceas of 2026-11-13 |
| Why the reading is random, and when to do it | Same article: the locations "are determined by a random tarokka reading, which prevents players from memorizing the exact location of the artifacts"; "you may wish to perform the card reading in private ahead of time so that you can prepare for these locations instead of taking notes on the fly" | sourceas of 2026-11-13 |
| The Tarokka deck in Curse of Strahd | D&D Beyond, 2 June 2026: "In Curse of Strahd, it allowed you to randomize key elements of the gothic adventure" | sourceas of 2026-11-13 |
How we sourced this: Curse of Strahd is a Wizards of the Coast adventure. This page is not affiliated with or endorsed by Wizards of the Coast, quotes none of the book’s text, and names only what its public contents page and D&D Beyond’s own articles name. We have not read the adventure itself, which is why there is no advice here on running any part of it. The two Tarokka rows come from a D&D Beyond article about a one-shot variant that describes the reading’s five cards; we did not read the reading’s tables, and nothing on this page is a rule. The tracker’s fields are our own.
Related guides
- A D&D session zero checklist, and the questions to ask your players
A session zero checklist to copy: questions for players, safety tools, table rules and the names to settle before session one. What does yours miss?
- How to become a paid DM: what it takes, what it pays, what it costs
Becoming a paid DM: building a listing, setting a price, platform fees and payouts, refunds, and the prep load of several tables. Is it worth it for you?
- How to make a D&D campaign website your players will open
What to put on a D&D campaign website, five ways to host one (Google Sites, Notion, GitHub Pages, Obsidian Publish, Kanka) and who sees it. Which fits?