Record or import
Record in the browser or bring in session files and supported local recorder uploads, linked to the right game and night.
Record and review
Adventure Scribe Notes Keeper
Record the game and review what happened.
Adventure Scribe turns session audio into a campaign record you can check and use. Keep the full transcript and review material, prepare a readable account, and use the recap to help players catch up before the next night.
What it helps you do
Review the evidence
Work through the transcript, speaker map, proof, and continuity review, with human review copies in Google Docs.
A readable account
Prepare Reader Mode chapters, images, and recap material from the recording.
Keep processing visible
Track recording, transcription, artwork, and handoff stages separately, and retry failed work where supported.
Choose what to share
Review archive access, recap material, and wiki drafts before publishing them to the intended audience.
Getting ready
Establish the campaign, game, numbered night, schedule, and participant or character context before recording or importing. For several audio parts or coordinated devices, keep them associated with the same intended session. Check the resolved destination after a recorder handoff so a well-recorded evening does not become an unrelated generic upload.
Choose browser recording, an existing audio file or folder, or a supported local-recorder bundle. Keep source recordings while the work is processed and reviewed. Expected names and the roster help interpretation, but they do not establish who spoke or prove that a planned event happened.
How to use Adventure Scribe Notes Keeper
Record or import and follow processing
Capture the evening, stop deliberately at the end, and open the saved session when processing is ready. For an import, inspect the file parts, manifest, and destination. Follow upload and backend status separately. A received file can still be waiting for transcription, finalisation, summary generation, or presentation rebuilding.
Fix identity and speaker decisions first
Check the night, campaign names, and participant context before polishing prose. In Speaker Map, inspect suggestions and the source evidence, then confirm a participant or retain Unknown. A phone’s owner may not be the person most audible on it. Separate speaker identity, character context, and in-character versus out-of-character speech.
Review the account against the recording
Read the Full Log, proof, continuity material, and generated account. Correct names, promises, decisions, and uncertain events using the source evidence. Keep private GM notes separate from player-facing material. A clearer chapter is useful only if it still represents what the group actually played.
Use Human Scribe Review for longer edits
Create or export the supported Google Docs review package and give the intended collaborators access. Edit the marked sections, then import supported edited sections or pasted review text into the correct night. Inspect and accept the changes explicitly. Rejected edits remain outside the accepted account; a document is a review surface, not an unrestricted replacement for the transcript.
Prepare Reader Mode and artwork
Read the accepted chapters in order, review illustrations and their relationship to the story, and retain the artwork choices with the night. Make the account useful as a recap for someone returning after a week. Check narration or video readiness in the configured workflow instead of assuming a completed transcript includes every presentation asset.
Chapter playback example: use the recording and chapter boundaries to revisit the relevant part of the game during review. Publish only after checking content and destination
For Campaign Wiki Draft, choose the target page, check it, approve the destination, publish the intended night, and inspect the published page. Recheck if the page or draft changes. Preserve continuous chapter numbering; a skipped game night need not consume a chapter number. Approve later renumbering separately rather than silently moving existing references.
Return reviewed evidence to the campaign tools
Use the accepted record for Mentor Night Review and approved recap material, or as evidence for NPC history. Check archive access and expiry before sharing. If a later image or presentation job fails, retry the relevant stage while retaining the reviewed transcript, rather than rebuilding the entire night unnecessarily.
A game example
Turn a negotiation into a useful next-night recap
For example, several players discuss possible bargains, but the party finally agrees to escort an NPC. Review the recording to identify the actual promise and its speaker before writing the chapter. Accept the corrected Reader Mode account, choose an image that fits the event, and prepare a short player recap. Send the reviewed agreement to Mentor as carry-forward evidence. Keep discarded hypothetical plans in the transcript without presenting them as commitments the party made.
What you keep
A retained session record
The source-linked transcript, speaker decisions, proof and continuity material, plus visible processing or review state.
An accepted readable account
Human-reviewed chapters and associated artwork or recap material for the intended audience.
Explicit publications and handoffs
The approved wiki or archive result and the reviewed evidence or recap supplied to Mentor and NPC Forge.
How it fits with the other apps
Common questions
Why is the recording uploaded but the summary still missing?
Upload, transcription, finalisation, summary, artwork, and presentation are separate stages. Inspect the particular job’s waiting, running, failed, or retry status. Completion of one stage does not establish completion or publication approval for the others.
Can I publish the generated story immediately?
Check identity, speakers, played events, private content, chapter order, and the destination first. Content acceptance and wiki target approval are separate decisions. Review access for archives too; recording a game does not make all of its private evidence public.
Usage guide based on the 7 October 2026 project summary, reviewed 8 October 2026. Examples illustrate possible games. Some connected features require sign-in, GM permissions, or a configured local table.