Survivor's Notes Ending and 51-Achievement Route Tracking Template

The key to reducing save reloads is to identify irreversible states and the latest shared branch point, rather than guess the “correct option” in advance. Survivor's Notes features two protagonists, QTEs, branches, and 51 Steam achievements, so a guide must track perspective, choices, action outcomes, relationships, and achievement triggers together.

Play the first run blind and establish only the main path: record key nodes, perspectives, QTEs, and the final ending. On the second run, work backward from the choice closest to the ending, testing just one variable at a time. On the third run, clean up missable, mutually exclusive, collection, and failure achievements.

Repeat the test for every conclusion at least once. Keep in-game timestamps and evidence of Steam unlocks for achievements; do not revise entries based solely on third-party videos.

• Change only a choice or a QTE at a time, never both together;
• First verify whether chapter jumping carries over relationships, items, and action outcomes;
• Label saves with the character, chapter, and key states;
• Distinguish dialogue changes, short scene changes, and actual route changes;
• Use the official in-game names for endings and achievements.

The final version must list the trigger conditions for all 51 achievements, missable and mutually exclusive flags, the minimum number of playthroughs, chapter carryover rules, and every reproducible ending. Until verification is complete, this is a template for collecting guide information, not a “100% achievement solution.”

Achievements can be divided into six categories: guaranteed progression, key choices, QTE success or failure, collection, endings, and combined states. Progression achievements unlock through normal completion; local QTEs and collection are suitable for chapter jumping; endings and combined states may require carryover from earlier nodes.

If an achievement description is hidden, do not guess the answer from its icon. Only an actual in-game trigger or an official explanation can confirm the official name, conditions, and missable flag, and the version should be noted. Community speculation can go into personal notes, but must be marked “Unconfirmed.”

Work backward from an ending you have already reached, first changing the most recent key choice. If the ending changes, that choice is a candidate branch point; if only the dialogue changes, move further back. Keep all other variables unchanged each time, and record the save or chapter loaded.

After finding a branch point, perform two more checks: whether repeating the same choice from the same state produces the same ending, and whether entering through chapter jumping matches a full playthrough. Many guides fail precisely because they overlook the default states used when jumping between chapters.

Use the naming format “Chapter—Current Perspective—Key Relationship—QTE State—Target Ending.” If the game does not allow custom names, record the save time and chapter identifier in an external spreadsheet. Do not write only “Route Two” or “Before the Good Ending”; a few days later, it will be difficult to tell what the save carried over.

Truly minimizing reloads should also reduce repeated playback, state risks, and ambiguity in verification. A theoretically shorter route that requires changing five variables at once is unsuitable for a reliable guide. It is better to replay one extra local node so that the cause of every achievement and ending can be reproduced.

Publish it in two layers: a low-spoiler route at the top that tells players only when to create saves and which nodes are mutually exclusive, followed by expandable sections with specific choices and endings. Use consistent fields in the 51-achievement table: name, category, chapter, prerequisite state, triggering action, whether it is missable, nearest reload point, and verified version.

This lets players preserve their first-playthrough experience while locating what they need directly when aiming for 100% completion, without searching lengthy prose for scattered answers.

• Survivor's Notes — Steam (51 achievements; checked: 2026-09-22)

After each playthrough, first compare unlocked achievements against the platform's achievement page, then update your own node table. Divide missing achievements into five categories: guaranteed story achievements, mutually exclusive choices, action challenges, collection, and endings. Complete items in the same category together to avoid replaying an entire chapter for one small omission. Before syncing cloud saves, check the local timestamps and slots to prevent new progress from overwriting a key branch point.

If an achievement does not pop up, check in order whether you are offline, whether you used skip or assist mode, whether the conditions require full playback, and whether the current version changed the trigger logic. Do not guess conditions from names alone, and do not download all-unlocked saves from unknown sources. Hidden conditions that cannot be confirmed should be marked “Unconfirmed,” with the steps attempted retained rather than presented as established facts.

When publishing your own route table, specify the date of the achievement tally and the platform, and place potentially spoilery achievements in collapsible sections. Readers should be able to learn the planning method first, then decide for themselves whether to view specific trigger conditions; efficiency should not come at the cost of the first-playthrough experience.