The best speedrunning notes read like careful engineering logs with a competitive pulse. What makes the scene useful to readers is not just the result but the way runners document route choices, timing splits, reset logic, and what actually changed when a better run was found.
The loud mistake is chasing headline time saves before the runner can execute the baseline route cleanly. The quieter one is letting notes stay vague, which makes it impossible to tell later whether a new idea was actually faster or just more exciting. A healthy speedrunning workflow starts with a category choice, a stable route baseline, and a split file that records improvement honestly. From there the work becomes a cycle of drilling specific segments, reviewing runs, and deciding whether a time save is real enough to deserve a route change.
If you want a cleaner start, build your notes around speedrunning, route-planning, and the real examples behind the most useful speedrunning notes explain why a route changed, not just what the new time save claims to be.. Those records will outlast the summary you write about them later.
Open alongside this question:
- LiveSplit FAQ: livesplit.org/faq/
A useful starting point for timers, layout behavior, and auto-splitter references.
- LiveSplit auto-splitter guide reference: livesplit.org/faq/
The FAQ points readers toward the auto-splitter documentation and surrounding tool ecosystem.
- Games Done Quick video archive: youtube.com/@GamesDoneQuick/videos
Useful for studying commentary, execution pressure, and how strong runs are explained live.
