Player-Facing Campaign Notes: Share Lore Without GM Spoilers

Player-facing campaign notes solve a problem that grows with every long-running TTRPG campaign: players need an easy way to remember the world, but the GM’s notes contain information they should not see yet.

The cleanest solution is not to sanitize one giant document over and over. Keep two layers of information: the campaign truth the GM uses to run the world, and the version of that truth the characters have actually learned.

Separate observed facts from hidden truth

For every important NPC, faction, location, or mystery, ask two questions: what is true, and what has the party confirmed?

The GM might know that a merchant secretly funds a rival faction. The player-facing note should only say what the characters can support: “Merchant Edrin met privately with two members of the Ash Guild after the council vote.”

That distinction keeps shared notes useful without turning them into accidental spoilers.

Label rumors as rumors

Players often remember a rumor as a fact several sessions later. A simple label prevents that.

• Confirmed: the party has direct evidence.
• Reported: a named NPC claimed it.
• Rumor: the source is unclear or unreliable.
• Question: the party suspects a connection but has not proved it.

This also makes mysteries more satisfying because the notes preserve uncertainty instead of flattening everything into a wiki entry.

Write what characters would remember

Player-facing notes do not need every historical detail in your setting. They need the details that help players make decisions next session.

Prioritize names, promises, debts, recent events, visible goals, known relationships, and places the party can act on. If a paragraph of lore does not affect a likely choice, it can stay in the GM notes until it becomes relevant.

Use short entries for NPCs

A useful NPC entry can fit in four lines:

• who they are;
• what the party knows they want;
• what the party owes them or vice versa;
• the last important thing they did.

This pairs naturally with a TTRPG relationship map, where links between people can carry the same confirmed or rumored labels.

Keep a separate campaign timeline

World notes answer “what is this?” A timeline answers “what happened when?” Keeping those jobs separate makes both easier to scan.

Record only events that could matter later: arrivals, deadlines, public announcements, promises, faction moves, discoveries, and unresolved consequences.

If tracking in-world time is getting complicated, see our guide to a TTRPG campaign calendar.

Let players own part of the record

The GM does not need to write every shared note. Players can maintain the recap, relationship map, or rumor list while the GM confirms only whether an entry should be labeled as known, reported, or uncertain.

This distributes the work and gives players a reason to revisit information between sessions.

Do not correct every wrong theory

If the players write a theory as a theory, let it remain. The shared document should represent their understanding, not an omniscient encyclopedia.

Correct factual recording errors—wrong names, dates, or who was present—but do not use the document to quietly steer them toward the intended answer.

Update after the session, not during every scene

A five-minute pass after play is usually enough. Add new names, update changed relationships, mark one or two facts as confirmed, and record the biggest unresolved question.

Trying to maintain perfect documentation during play can pull attention away from the table. The same selective approach appears in how to take TTRPG notes without missing the game.

Use a reveal workflow for secrets

When the party discovers something important, move it from the hidden note into the player-facing version. Do not rewrite the whole page. Add the new fact, note when it was learned, and update any relationships it changes.

This turns the shared notes into a record of discovery. Players can see how their understanding evolved instead of receiving a finished lore document all at once.

A simple player-facing template

• People: name, role, visible goal, latest interaction.
• Factions: public purpose, known allies, known conflicts.
• Places: why the party cares and what changed there.
• Timeline: important dates and deadlines.
• Rumors: unconfirmed claims with sources.
• Questions: mysteries the party still wants to investigate.

Shared notes should preserve discovery

The purpose of player-facing campaign notes is not to give players everything the GM knows. It is to make the information they earned easy to use.

Separate truth from knowledge, label uncertainty, keep entries short, and update only what changed. The result is a shared reference that supports memory without spoiling the next reveal.