How to Track a Mystery Clue Across Separate Asynchronous RPG Sessions

Start with a shared record of what happened

Choose one place the group can reliably find and update. It might be a shared campaign document, a channel thread, or a folder of notes. Tell everyone whether the record is a player-facing account, a game-master-only reference, or a mix with clearly marked private sections. For asynchronous play, visibility matters: a clue written in someone’s private notes cannot help the group coordinate unless the player deliberately shares it.

At the end of a scene or session, write a short event entry before analysis. Include the in-fiction date or location if the game uses them, who was present, what the characters did, and what changed. Keep this to the details needed to orient a returning player. An official campaign log in Arkham Horror: The Card Game illustrates the value of recording story developments that later scenarios may reference; it records consequential notes and choices across scenarios. The Campaign Log, The Night of the Zealot Campaign Guide

Give every clue its own entry

Do not bury an important clue inside a long recap. Give it a stable label, such as C-04: Blue wax on the parcel, and use that label whenever it comes up again. A compact record can include:

For example, the evidence might read: “The parcel was sealed with blue wax stamped with three reeds; the note inside says, ‘Ask at the east gate after the second bell.’” An interpretation could be: “Possibly a message from the river wardens.” The characters have not established that yet, so keep it in the theory field. This small separation is the heart of reliable clue tracking: players can revise a theory without rewriting what their characters actually found.

Record source and context, not just the clue

A clue’s meaning can depend on where it appeared and who was there. Note whether the wax was on a parcel in the abandoned observatory or on a letter delivered by a known courier. Record the speaker’s name and exact phrase when dialogue matters; if you are paraphrasing, say so. Add a link from the clue to the scene note, and from the scene note back to the clue list, so the group can move in either direction.

This is useful whether the mystery has six clues or sixty. For example, Free League’s Vaesen handout pack describes maps, letters, and clues as materials for mysteries, illustrating how an investigation can involve several distinct evidence formats. In your own notes, identify the type and origin of each item so a map annotation, a letter, and a witness statement do not blur into one remembered impression. Mythic Britain & Ireland Maps & Handouts, Free League Publishing

Separate confirmed facts, open questions, and theories

Use three headings in the mystery record: Established, Unresolved, and Theories. Put only directly observed or explicitly confirmed information under Established. Put missing information under Unresolved: “Who had access to the east gate?” Put possible explanations under Theories: “The courier may have delivered the parcel.”

When new evidence arrives, update the relationship rather than silently changing the old note. If the courier later says they never visited the observatory, mark the theory contradicted and link the denial to its source. Do not erase the earlier theory if it shaped a character decision; a dated revision makes the sequence understandable. This preserves the difference between what players knew at the time and what they learned later.

Connect clues into leads the group can act on

A list of evidence is not yet a plan. For each unresolved question, add one or more possible follow-ups: ask a named character, inspect a location, compare two documents, or wait for a player to propose an action. Phrase a lead as an invitation, not an instruction. “Could the east gate clerk identify the three-reed seal?” is more useful than “Go to the east gate,” because it states the question and leaves the players free to choose.

Then mark a lead as open, attempted, or answered. If an attempt produces no useful result, record that outcome too; otherwise the next session may repeat the same action. Keep the answer tied to the question, so a player opening the notes can see the current state without inferring it from a scattered conversation.

Make the system easy to navigate

A shared document can use headings and a table of clue IDs. A card-based tool can use one card per clue and a link to the originating scene. If the group already uses a note-taking app, take advantage of features it actually supports rather than building an elaborate database. For example, Obsidian supports text, list, date, and checkbox properties, and its templates can add properties to notes; its Backlinks plugin can show linked mentions and unlinked mentions of a note. Those features can help organize clues and find references, but they do not decide what is true in the fiction. Properties, Obsidian Help and Backlinks, Obsidian Help

Agree on a simple naming scheme before the notes grow: sessions might be S-12, clues C-04, and characters or places can have their own pages. Add links only when they help answer a likely question: “Where did this come from?”, “Who else is connected to it?”, or “What did we try?” A maze of tags and categories can cost more time than it saves if the group must maintain it after every post.

Close each session with a handoff

Before ending a session, add a brief handoff that a player can scan when returning. Include: what changed, which clues remain active, what the group last agreed to do, and any choice awaiting a response. If different players are posting at different times, note whether an action is still proposed or has already been taken. Do not turn a player’s speculation into a shared decision without their agreement.

A practical handoff might say: “We have the parcel and know the seal shows three reeds. The ‘second bell’ could refer to the east gate, but that is still a theory. Mara suggested asking the gate clerk; no one has gone yet. Next question: does the group want to investigate the seal first or follow the timing reference?” That is enough to restart the conversation without requiring a full recap.

Review the trail when a clue changes

When a clue is resolved, mark it resolved and write a one-sentence explanation supported by the events that established it. Link the explanation to the relevant scene. If the answer is only partly known, state what remains uncertain. For example: “The clerk recognizes the seal as belonging to the ferry office; the sender is still unknown.” Avoid converting a partial lead into a complete solution just to make the notes look tidy.

Once in a while, scan the open questions and unresolved clues together. This catches orphaned details: a name that no longer connects to a lead, a question the group already answered, or an old theory that players still mistake for fact. A campaign log is a memory aid, not a substitute for the game’s rules or the group’s shared understanding. If the record conflicts with an actual post or table decision, use the original play record to correct it and note the correction.

A compact template for the next session

Copy this structure into the group’s chosen record and adapt it to the game:

Session / scene: Date, location, and characters present

What happened: A few sentences of observable events

Clues found: ID, exact evidence, source, link

Established: Facts confirmed in play

Theories: Interpretations, clearly labeled

Open questions: What remains unknown

Leads: Possible follow-ups and their status

Handoff: Last agreed action or decision still awaiting a response

The aim is not exhaustive transcription. Keep enough detail to distinguish evidence from interpretation, trace a clue back to its source, and show the next available choice. When players return after a gap, they should be able to find the mystery’s current state quickly and decide what their characters do next.

Sources

Keep exploring this topic