Review playtest results
Read feedback form responses per form or across a whole game, filter and export them, and turn what you learn into tasks.
Last reviewed October 11, 2026
The point of a playtest is the next version of your game. This page shows where feedback form responses land, how to read them one by one or as a table, and how to carry what you learn into your project board.
What this page helps you do
- Read the responses to one feedback form.
- See every response for a game in one table, filtered by version or player count.
- Export responses to a spreadsheet.
- Write up what you learned and turn it into tasks.
You'll start from the sidebar: Playtests, then click the game.
Before you start
- Responses only arrive through a feedback form link (see Build feedback forms). Feedback you collected on paper goes in the playtest's Feedback tab instead (see Record feedback from paper, email or conversations).
- Numbers about the session itself (times, scores, engagement) are on the game's Dashboard tab, not with the form responses. See Read your game's playtest dashboard.
Read one form's responses
Open the playtest, click the Feedback Form tab, then View Responses on the form card. A "Form Responses" panel opens under the card, newest response first.
Helpful details
- Key areas: each response is a card with the playtester's name, the time it was submitted and, when they gave one, a button with their email that opens your mail app. Below, every question with its answer.
- What you can do: Reload fetches new responses, Export to CSV downloads this form's responses, Close folds the panel. "No responses yet" means nobody has submitted.
- Good to know: answers are labelled with the question's current title. If you reworded a question after people answered, the old answers sit under the new wording.
See every response for a game
Back on the game's playtests page (Back to <game> playtests), click the Feedback tab. Its badge shows the total number of responses across all playtests of this game.
Helpful details
- Key areas: one table with Playtest Date, Version, Player Count, Name, Email, then one column per question asked in any of the game's forms. Long answers are cut short in the cell; hover to read the whole answer.
- What you can do: filter with Filter by Version, Players ≥ and Players ≤ (the playtest's player count) and Search Respondent ("Name or email..."). A badge shows how many rows match out of the total. Export CSV downloads the filtered rows.
- Good to know: the table is empty until a form has at least one response: "No feedback responses yet. Share a feedback form link with your playtesters to collect responses."
Look for patterns, not outliers
Read all the long-text answers in one sitting and give each one a short label in your head ("scoring unclear", "endgame drags", "loved the cards"). Labels that repeat are your themes.
Helpful details
- Key areas: the Feedback table is the fastest way to scan one question across every session: find its column and read down.
- What you can do: filter by Version to see whether a complaint went away after a change, or by player count to see whether the problem only shows up at four players.
- Good to know: one person saying something nobody else mentioned may be a real issue or may be that one person. Gather more data before you redesign around it.
Export to a spreadsheet
Both views export CSV files you can open in Excel, Numbers or Google Sheets.
Helpful details
- Key areas: Export to CSV in a form's responses panel, Export CSV on the game's Feedback tab, and Export CSV on the Playtesters tab.
- What you can do: the per-form file is named
feedback-form-<id>-<date>.csvand holds name, email, submitted time and one column per question. The game-wide file (feedback-responses.csv) adds playtest date, version and player count, and respects your filters. - Good to know: Boardssey does not chart form answers. For averages or counts of a rating question, export and use a pivot table.
Write up what you learned
Open the playtest and use its Feedback tab (a rich-text editor) for a short summary: what worked, what did not, what you will change in the next version, what is still uncertain.
Helpful details
- Key areas: the Feedback and Notes tabs on the playtest page.
- What you can do: paste striking quotes from the responses into the summary so the context stays with the session.
- Good to know: this summary is for your team only. Playtesters never see it.
Turn results into tasks
Each "what we will change" item should become a task on a project board. There is no button on the playtest for this; create the tasks on the board.
Helpful details
- Key areas: sidebar Projects, open the game's project, then New Task.
- What you can do: title the task with the change ("Rebalance the scoring track to slow the leader") and mention the playtest number in the description ("From Playtest 5, three of five players").
- Good to know: see Tasks and subtasks for assignees, due dates and priorities.
Tips & common questions
Can I delete one bad or duplicate response? Not today. Responses cannot be edited or deleted one by one. Deleting the whole form removes all of its responses. Duplicates are rare because a browser can only submit each form once.
Can I share results with someone outside Boardssey? Export the CSV and send it, or invite them to the team. There is no public results page.
How long are responses kept? As long as the form and its playtest exist. Deleting the form, the playtest or the game deletes the responses with it.
Where are the charts? On the game's Dashboard tab, built from the playtest records (Score Board, times, engagement rating), not from form answers. See Read your game's playtest dashboard.
Can I filter the Feedback tab by playtest? Not directly. Filter by Version and by player count, or open that playtest's Feedback Form tab and click View Responses to see one form at a time.