What it is
One row per playtest session — session date, build version, list of testers, findings, severity (low / medium / high / critical), and recorder. Build it once per session and the trend is visible across the whole project.
When to use it
- Recording every playtest session so findings don't evaporate.
- Tracking which build was tested and what came out of it.
- Reviewing patterns — same finding showing up in three sessions = priority.
- Sharing a session's findings with stakeholders or contractors.
How to use it
- 1Click "+ New Session" — date, build version, testers (free text).
- 2Write up findings — keep them concrete and actionable.
- 3Pick severity for the worst finding in the session.
- 4Cross-link to Issues for individual bugs found.
Tips you should know
- →Severity drives the dashboard alert badge — critical findings are loud on purpose.
- →Build version field references Build Tracker; mismatches show as warnings.
- →A weekly playtest log is one of the best signals when a feature is "done enough".
- →Pair with Risk Register — recurring critical findings should become risks.