Playtesting & rulebook validation

Playtest Issue Log & Priority Tool

Rank what you saw with an explicit rule: blocked progress and repeatable critical failures come before ordinary tuning work.

Observed findings

Issue 1
Issue 2

Do not hide a decision inside a score

Scores are only a tie-breaker here. A blocker is a progression stop or a repeatable critical failure: the group cannot set up, cannot find a legal move, cannot resolve an essential state, or cannot finish. Fix it before asking whether a smaller issue feels better.

Keep the evidence with the issue

For each finding, retain the game version, player count, timing, observation or quote, and the specific situation that triggered it. After a fix, recreate that situation first. A broad new playtest may create more noise before you know whether the repair worked.

Related workflow

Use the Session Planner to decide what evidence to collect. The Rulebook Completeness Checker is for pre-test review; this log is for findings from the table. See the playtest plan guide for a simple observe–classify–retest loop.