A great feedback form is short, asks the right questions, and gives you data you can actually use. This page covers what to include, what to skip, and how to build it in Boardssey.

The form builder is part of the playtest setup flow (see Set up a playtest). Open an existing playtest from the hub and click Edit form.

You'll see a list of questions on the form, with controls to add, remove, and reorder.

Pick one per question:

You don't have to use every type. The best forms typically use 2–4 types total.

The single most useful framework: ask about the playtest goal you set when creating the playtest, plus a small number of universal questions.

These four cover most of what matters, every time:

If your playtest hypothesis was "the new scoring rule fixes the runaway leader problem," your form should ask 1–2 specific questions about the scoring and pacing.

If the hypothesis was "the new tutorial mission teaches the rules without a human teacher," the form should ask about the rules being clear, the tutorial flow, and where they got stuck.

Don't ask things you can already see from the components or rules, focus on what only the player can tell you.

Open-ended hard questions ("what would you change?") get better answers when the form starts with easy ones. Order: warm-up → core questions → deep questions.

Five to eight questions is the sweet spot for in-person playtests. Sometimes more for online / async playtests where filling the form is the only direct interaction. Always start shorter than you think; you can expand on follow-ups.

A 30-question form gets fewer completions and worse data per question than a 6-question form. Discipline pays off.

Mark questions Required sparingly, only when missing data would make the response useless. Required name fields, for example, often get junk ("test", "asdf"). Required ratings often get arbitrary 5s.

Make most questions optional. Playtesters will answer the ones that matter to them.

You can edit the form while the playtest is running. New submissions use the updated form; existing submissions are kept as-is (with whatever question text was active at the time).

If you make a major change mid-stream, note it in the playtest description ("Question 3 reworded on Apr 14") so future-you understands why the data looks inconsistent.

If you want a more polished experience for short standalone surveys (not tied to a playtest), the Feedback Survey tool covers it. See Feedback Survey tool.

My responses are sparse, what should I change? Often the form is too long, asks for too much typing, or the link wasn't shared at the right moment. A 15-minute form after a 90-minute playtest gets abandoned. Try cutting it in half.

Can I include images or video in a question? Today the form supports text and rating questions. Image upload from respondents is on the roadmap.

Can a playtester save and finish later? The form doesn't auto-save partial responses. If they close the tab, they'd start over. Keep it short to avoid this being a problem.

Can I see who submitted what? Only if you ask for name or email in the form. Submissions are otherwise anonymous.

Can I have different forms for different playtest groups? One form per playtest. For different audiences, set up separate playtests with different forms.