After a playtest, it’s tempting to write one sentence and move on to the next game. But the most useful playtest notes preserve a moment: where players hesitated, what they expected to happen, and what the rules actually told them to do. For an edition in development, those details are more actionable than a simple verdict.
Record the table context
Start with the basics you can remember: how many people played, whether they were new to the game, and which version of the materials was on the table. Then describe the situation that prompted your reaction. If a rule took several readings or a decision stalled the game, include the wording or the point in the session where it happened.
Keep observation separate from interpretation. “We paused to reread this paragraph before choosing” tells me what happened; “the game is confusing” tells me how it felt. Both perspectives can matter, but the first gives a clearer place to begin.
Describe more than the verdict
A report can include what felt smooth, what surprised the group, and what you would change on a second play. If a suggestion comes to mind, connect it to the moment that prompted it. That makes it easier to consider the idea without treating every proposed fix as the only solution.
Specific, respectful notes are welcome whether your session was a polished playthrough or a rough first look. When sharing feedback, name the version you played and tell me what happened at the table. That is the kind of detail I can carry into the next development step.