DnD Note-Taking App: Two Tools for Better Campaign Notes

Pick Notelyn for turning your written notes into a recap and Obsidian for building a manually linked campaign reference. These recommendations depend on the work you want to do between sessions.

The recap route suits a player who finishes a session with scattered paragraphs and wants a readable starting point for the next gathering. You provide the material, generate a summary, and check it against your notes. The useful output is a short account of decisions, discoveries, and unresolved business.

The linked-reference route suits someone who repeatedly asks, “Where have we met this person before?” You maintain separate entries for recurring people and places, then connect them to session records. That asks for more deliberate naming and maintenance, but gives you a path through the material you have connected.

Try both with the same small example: the party meets Mara at the North Gate, finds a blue seal, and agrees to visit the mill. Ask each workflow to help you recover those three details. Judge the effort required to create and revisit the record, rather than choosing from a long feature list.

It should help you retrieve the information that affects the next decision. For one group, that means reading last session's recap. For another, it means following a person's appearances across several sessions.

The difference is where you spend your attention. A generated outline can reduce the effort of arranging a long note. A network of links can make your own cross-references easier to follow. Neither workflow relieves you of deciding whether a statement was witnessed, reported, or merely suspected.

For Dungeons and Dragons note-taking, use three retrieval questions as your standard: What happened? What do we still need to investigate? Where did this information come from? If your notes answer those questions without a lengthy reread, the structure is doing useful work.

Use Notelyn to turn your written session record into a structured recap while keeping the source available. Start with Text Input, choose Text, and paste your notes. Basic formatting is preserved; headings such as Events, Reported Claims, and Open Questions give the material a clear shape.

In Notelyn, add a title such as “Session 07: The Blue Seal,” choose a campaign notebook, and tap Save while online. Creating and saving a Text note requires an internet connection. Generate the Summary to arrange the material into headings, key points, and takeaways.

Compare the result with the original input in the Transcript tab. Check names, promises, and the difference between “Mara reported a light” and “we saw a light.” Edit the summary where needed, then use it for your next opening recap. The game-specific headings are your own template. Start your next Notelyn recap with AI Summary Notes, using one session's written material.

Create a session record and separate entries for people or places you expect to revisit. This is a suggested filing method, built with Obsidian's documented links and templates.

The official internal-links guide explains wikilinks such as [[Mara]] and links that include a folder path. In a session record, you could write “We met [[NPCs/Mara]] at [[Places/North Gate]].” Give each destination a short description and a reference back to the session where the information appeared.

The official Templates guide describes inserting predefined text snippets into an active note. Use that to insert the same blank session fields each time. For more examples of connecting your entries, see How to Link Notes in Obsidian.

Use a DnD notes template that separates events, reported claims, interpretations, and next actions. Those categories prevent an attractive theory from quietly becoming part of the group's accepted history.

Copy this structure into your chosen editor. These fields are suggestions for your own notes, rather than a built-in game template.

Campaign: [name]
Session: [number and title]
Played on: [date]
Starting point: [place and immediate situation]

Events we witnessed:
- [event; people involved]

Claims we heard:
- [speaker; claim; session reference]

Party theories:
- [idea; supporting clue; unanswered question]

People and places:
- [name; identifying detail; related entry]

Decisions and promises:
- [decision; who agreed; intended follow-up]

Open threads:
- [question or task; next lead; status]

Next session starts with:
- [one immediate choice]

Example: The party saw a blue seal on a dropped letter. Mara said the mill was empty. Someone guessed that the seal belonged to the mill's owner. Record those as an observation, a reported claim, and a theory, respectively. The next action might be “Visit the mill and ask who uses the blue seal.”

A useful DnD note template also records changes of plan. If the group decides to visit the harbor first, keep the mill thread open and update the immediate next step. Otherwise, last week's intention can look like an action already completed.

Use short entries with a person, action, and object: “Mara offered to introduce us to the courier” is more useful than “Mara, courier, introduction.” Complete sentences are most valuable where a relationship or commitment might be ambiguous.

Keep a compact reference for each recurring person and one current entry for each unresolved thread. The session record preserves the sequence of events; the reference entry helps you find the latest position.

For an NPC, record a distinguishing description, first appearance, relevant claims, and the party's current relationship. “Mara, North Gate keeper, Session 07” is easier to recognize than a name on its own. If another Mara appears, add a different identifying label immediately.

For a clue, preserve both the object and its context. “Blue seal on a letter found beside the gate” offers more to work with than “blue seal = mill.” Put the proposed connection in a theory field until later events settle it.

For an unfinished quest or personal promise, use simple statuses you define yourself: open, waiting, resolved, or abandoned. These are writing conventions, not automated campaign tracking.

Keep player knowledge separate from the Dungeon Master's preparation whenever revealing the preparation would spoil an unresolved situation. A player's useful record describes discoveries, decisions, and questions. A DM may also need possible developments, unrevealed motives, and ideas that never reach the table.

Separate those materials in your writing, and prepare a player-facing recap by selecting only the information the group should receive. Do not assume that putting a heading above a secret controls who can access it.

Example: A preparation note says the courier intends to leave through the east gate. During play, the party hears only that the courier is packing. The shared recap should preserve what the characters learned; it should not import the planned destination.

When several people take notes, agree on one recap editor. Other players can supply missing details or flag disagreements, and the editor can produce a settled version without erasing the underlying questions. A disputed recollection can remain “Check with the group” until resolved.

Keep the shared record short enough to read before play. For the broader filing habits behind this approach, How to Organize Notes explains ways to keep reference material and current work easy to locate.

Write different kinds of notes at each stage. Before play, make the next decision visible. During play, capture changes. After play, turn those changes into a record you can reuse.

You do not need a transcript of every conversation to remember that a promise was made. Capture the promise, the person involved, and any condition attached to it. Direct wording is useful when the exact phrase becomes a clue; ordinary travel and repeated discussion can usually be condensed.

Test one representative session before transferring an archive. Choose notes with a recurring NPC, an uncertain clue, and an unfinished task. A perfectly tidy sample will not show you where the workflow becomes awkward.

Use the same material in both tools. In Notelyn, create a Text note and review its Summary; in Obsidian, connect the session to a person and a place. Then stop arranging the notes and try using them as you would at the next session.

Choose a DnD note-taking app by the record you need next time: a readable recap or a set of connected references. Start with Notelyn when you want a structured summary of your written material. Start with Obsidian when you want to build and maintain links between campaign entries.

For the next session, copy the template, give the note a clear session number, and write down one unresolved decision. After play, update that decision and the people or places it affected. Keep the system small enough that you will maintain it between games. One usable session record is a better starting point than an empty campaign archive with dozens of categories.