Template
Beta feedback board template
A beta feedback board template: a private Looph board for your testers, with the statuses, tags and setup steps for triage before general release.
Teams running a private or invite-only beta that need structured, votable feedback before a general release.
- Statuses
- 4
- Tags
- 4
- Things to ask for
- 4
- Setup steps
- 6
Use this template
Copy the setup, import the starter posts
Two ways to start from this template today: copy the checklist below into your setup notes, and import the starter CSV into a new board from the Posts page of your team area. The file holds this page's example posts, with each status mapped to Looph's built-in name so the importer accepts it; delete them before you share the board.
Columns: title, details, status. 3 example posts.
Setup checklist
Beta feedback board template (looph.ing/templates/beta-feedback-board) Statuses (the Statuses page in the team area): - Keep "Open" - Keep "Under review" - Keep "Planned" - Keep "Complete" Statuses are shared by every board in a workspace, so a rename or a hidden status shows on all of them. If the beta runs beside your public boards, keep the built-in names; if it has a workspace of its own, rename freely, for example Complete to Addressed. Tags: - Onboarding - Core flow - Performance - Missing feature Board description: What were you trying to do, what happened instead, and which build are you on? Ask for in the details: - What happened, as a title - What they were trying to do - Which build - A link to a recording Setup steps: 1. Create the board and set it to Private. Add each tester's email, or a design partner's whole @domain; people you add individually get an email with access. 2. Leave posting, voting and commenting open to anyone who can view, and paste the prompt above into the board description. 3. Create the four tags, and hide any statuses the beta will not use. 4. Workspace members are subscribed to new boards automatically, so your team hears about each new post. Check notification settings so nobody has switched that off for the beta. 5. After launch, move posts that still matter to your public board. Votes, comments and followers go with them; internal notes stay staff-only. 6. Remove testers from the board's access list when the beta ends.
Templates aren't applied automatically yet: you set the board up yourself by following the steps on this page. One-click templates are coming soon.
Fit
When to use this template
A good fit when
You are running an invite-only beta and want testers' feedback in one place you can triage before general availability. A private board is visible only to your team and the testers you add, and testers can still vote on each other's posts, so you see which problems are widespread rather than which tester writes the most.
It suits a programme with a known cohort and an end date: a new product, a redesign, a major version.
Pick something else when
For an open beta that anyone can join, a Beta tag on your existing public board is simpler to run.
Do not let it become a permanent second feedback board. When the beta ends, move the posts that still matter to your public board and stop taking new ones here.
What's inside
Statuses, tags and what to ask for, and why each one is there
Looph has a fixed set of statuses that you can rename, recolour, reorder and hide, but not add to; each status below says which built-in one to use. Posts are a title plus details, so the last list is what to ask for in the details.
Statuses
- OpenBuilt-in status
- Where new posts start. Triage this queue daily during a beta; testers who hear nothing back tend to stop testing.
- Under reviewBuilt-in status
- Someone is on it: reproducing a bug, or discussing whether the feedback should change the design before launch.
- PlannedBuilt-in status
- Valid, but not going into this release. It keeps the item on record without pretending it will land before launch, and it is the first place to look when planning the next cycle.
- CompleteBuilt-in status
- Fixed or changed in a beta build. Say which build in a comment so testers know when to check again.
Statuses are shared by every board in a workspace, so a rename or a hidden status shows on all of them. If the beta runs beside your public boards, keep the built-in names; if it has a workspace of its own, rename freely, for example Complete to Addressed.
What to ask for in the details
- What happened, as a title
- A short statement of what happened or what is missing, written so other testers recognise it and vote instead of duplicating.
- What they were trying to do
- And what happened instead. Context matters more here than on a public board, because the product is still changing under them.
- Which build
- It matters when cohorts are on different builds. A dedicated field is coming soon with custom fields; until then, ask for it in the details.
- A link to a recording
- Screenshots or recordings from the beta build help. File attachments are coming soon; until then, ask for a link and keep it optional.
Custom fields and file attachments are coming soon. Until then, a post is a title plus up to 5,000 characters of details.
Suggested board description
Put a line like this in the board description, so people know what to include: “What were you trying to do, what happened instead, and which build are you on?”
Tags
- Onboarding
- Core flow
- Performance
- Missing feature
These four cover where beta problems tend to cluster. Tags are workspace-wide and testers can filter by them. Missing feature collects the requests that belong on your main feature board once the beta ends.
Setup
Set it up in Looph
Each step in order, with the guide that covers it.
- 01
Create the board and set it to Private. Add each tester's email, or a design partner's whole @domain; people you add individually get an email with access.
- 02
Leave posting, voting and commenting open to anyone who can view, and paste the prompt above into the board description.
- 03
Create the four tags, and hide any statuses the beta will not use.
- 04
Workspace members are subscribed to new boards automatically, so your team hears about each new post. Check notification settings so nobody has switched that off for the beta.
- 05
After launch, move posts that still matter to your public board. Votes, comments and followers go with them; internal notes stay staff-only.
- 06
Remove testers from the board's access list when the beta ends.
Illustrative examples
Example posts
Made-up posts that show what a useful entry on this board looks like. They are not from real customers.
Example · Onboarding
Import fails silently on large files
Uploaded a 40 MB file during setup. The progress bar finished but nothing was imported and no error appeared. Beta build 3.
Under review
Example · Core flow
Could not find notification settings
Looked under Profile and Settings before finding them inside each project. Comment from the team: moved to Settings in beta build 4.
Complete
Example · Missing feature
API access to the new reports
We would pull these reports into our own dashboards. Comment from the team: not in the first release; this moves to the public board at launch.
Planned
Plan
Which plan it needs
Needs Starter. An invite-only beta needs a private board, and private boards start on Starter, which includes 1 private board. Free has no private boards. Testers who vote count as tracked voters: 1,000 on Starter. Your own team joins as free members on every plan. Compare plans.
How the pieces work: Feedback boards. Teams running this workflow: Feature voting and roadmaps for mobile app teams and Customer feedback management for SaaS product teams.
More templates
Other starting points
Internal IT request board template
Internal IT and operations teams that need a searchable, votable alternative to a ticketing spreadsheet.Design feedback board template
Design and product teams collecting structured critique on in-progress work from stakeholders or users.Feature request board template
Product teams that need a single public place to collect and prioritize customer-driven feature ideas.Public bug tracker board template
Teams that want bug reports separated from feature requests, with triage by impact that reporters can follow.
Related
The features and reading behind this template
Start collecting feedback in five minutes
Free forever on one board, with unlimited members and a 14-day Business trial. No credit card, no sales call.
Unlimited members · Published prices · Cancel anytime