Google's production access form has three sections: about your closed test, about your app, and about your production readiness (Play Console Help, retrieved 2026-10-23). It asks you to describe how easy recruiting was, how engaged testers were, the feedback you got, and the changes you made. If you keep notes during the test, filling this in takes minutes instead of hours.
This one-page report is organised the same way. It is your own record; you copy the answers into the form. The form's wording can change, so check it in the Play Console.
Template
Copy this block and fill it in.
CLOSED TEST RESULTS REPORT
App: [name, package]
Report date: [date]
1. ABOUT THE CLOSED TEST
Test start: [date] Test end: [date]
Testers opted in: [number] Still active at the end: [number]
How testers were recruited: [e.g. friends, community, test group]
Recruiting effort: [easy / medium / hard, and why]
Engagement: [how many testers used the app more than once; how you know]
Feedback channels: [form, email, chat]
Feedback received: [number of reports]
Top themes:
- [theme 1]
- [theme 2]
- [theme 3]
2. ABOUT THE APP
Target audience: [who it is for]
Value: [what problem it solves, in two sentences]
3. PRODUCTION READINESS
Issues found and what you did:
| Issue | Severity | Fix | Build/version | Verified by |
|-------|----------|-----|---------------|-------------|
| [..] | [..] | [..]| [..] | [..] |
Issues not fixed and why: [..]
Why the app is ready: [your reasoning, 3-5 sentences]
Next steps after launch: [monitoring, update plan]
Example (invented, for illustration only)
Example. A notes app. Testers: recruited from a developer community and a test group. Recruiting: medium; the first week was slow. Engagement: most testers opened the app on several days (visible in the in-app feedback log). Theme 1: sync failed after airplane mode. Fix: retry logic in build 14, re-tested by three testers. Not fixed: dark mode flicker on one old device, low severity, planned for the next update. Ready because: crash-free sessions in the last week of the test, all high-severity issues closed.
How to adapt it
- Use only facts you can show: dates from your Play Console, numbers from your feedback log.
- Do not invent testers or activity. Do not inflate numbers. Be honest about weak points; a clear list of what you fixed is stronger than a perfect-sounding story.
- Keep tester names and addresses out of the report. Refer to them by "Tester 1", "Tester 2".
- Update it once a week during the test, not at the end.
AppReviewX gives you private, structured feedback from testers, which is easy to turn into the table above. Start with a test group.
Related: Google Play closed testing: the complete guide, Day 1 of a closed test, Closed test requirements.