Use one test question, not a vague quality check
A session gives better evidence when its question is observable: whether players find the legal action, whether a four-player game creates downtime, or whether a scoring explanation changes a decision. Record the prototype version and player count beside every finding.
What to observe
Write down the first hesitation, every rule lookup, every disagreement, and any moment where a player waits without a meaningful choice. Separate what players did from your interpretation of why they did it. The Issue Log & Priority Tool turns those observations into a retest order.
Limits and next action
This planner allocates time; it does not prove balance, fun, or rules clarity. If the plan shows too little play time, narrow the test to a teach, setup, round, or endgame slice. Use the Player Count Test Matrix when the question is about the supported range, and use the playtest planning guide before inviting testers.