Free resource
Google Play Closed Testing Feedback Template (Free)
Updated 27 September 2026
Quick answer
Collect the same fields from every tester: device and Android version, what they tried, what went wrong (with steps to reproduce), severity, and a suggestion. Log it daily with the date and the build number, then record what you fixed. That log is the evidence Google's production access questions ask for.
Feedback form fields
- Tester name or ID, and date
- Device model and Android version
- App version / build number tested
- What you tried (feature or screen)
- What happened, and what you expected
- Steps to reproduce (for bugs)
- Severity: crash / broken feature / minor issue / suggestion
- Screenshot or screen recording link (optional)
- Overall rating 1-5 and one improvement you would make
Daily testing log
Keep one row per day of the 14-day test: date, testers opted in that day, build number, feedback items received, and fixes shipped. A spreadsheet with these five columns is enough.
Turning feedback into your production answers
- 1Group feedback by theme: crashes, usability, missing features.
- 2For each theme, note what you changed and in which build.
- 3Use the counts and examples when Google asks how you tested and what you changed.
Tips for useful feedback
- Ask specific questions ("Did sign-up work on your phone?") rather than "Any feedback?".
- Request feedback early in the 14 days, so you have time to ship fixes.
- Thank testers and tell them what you fixed; engaged testers give better feedback.
Frequently asked questions
Does Google require a feedback form?
Google does not require a specific form, but it asks how you collected feedback and what you changed, so a consistent log makes your answers concrete.