Production access
How to Write Production Access Questionnaire Answers
Write Google Play production access answers that describe your real closed test: testers, feedback, changes and readiness. Section-by-section guide.

On this page · 8 sections
Write your production access answers from a record of what actually happened in your closed test. Google's questionnaire asks about three areas: your closed test, your app, and your production readiness. For each question, give specifics: how you found testers, what they did in the app, what feedback they gave, what you changed because of it, and why you now think the app is ready. Short, generic or copied answers give Google little to go on. Your own plain words about your own app work best. Google's 12-tester, 14-day closed testing rule applies to personal Play developer accounts created after 13 November 2023; organization accounts are exempt (Play Console Help 14151465).
Before you start writing
- Check the dashboard shows the testing requirement as met.
- Gather your notes: tester count over time, tasks you gave testers, feedback you received, and releases you shipped during the test.
- List the changes you made and link each one to the feedback that caused it.
- Check crash and stability data for the closed track.
- Open the questionnaire in Play Console and read every question before answering. Questions can change, so answer what your account shows.
Part 1: About your closed test
These questions cover how you recruited testers, how they engaged, and what feedback you got. Say where testers came from in plain terms, such as friends, a user community, or a paid testing service. Describe what you asked them to do and what they actually did.
For feedback, name the channel you used and summarise the main points. Hypothetical example, not a real case: "Testers said the sign-up code email was slow, two found the settings screen confusing, and one hit a crash when rotating a tablet."

Part 2: About your app
Here Google asks about your intended audience, the value your app provides, and how many installs you expect. Be concrete about who the app is for and what problem it solves. For expected installs, give an honest estimate. A modest, believable number is better than a large guess.
Part 3: Production readiness
This is where you show the test made a difference. List the changes you made based on feedback and how you decided the app was ready. Mention fixed crashes, improved screens, clearer onboarding, or removed features that did not work.
Explain your readiness decision simply: core flows work on the devices testers used, known crashes are fixed, and feedback in the last days of the test was minor.
Tips that make answers stronger
- Use numbers you can back up, like how many testers sent feedback.
- Use your app's real screen and feature names.
- Write in full sentences, but keep each answer focused.
- Do not paste the same text into several answers.
- Do not claim feedback or changes that did not happen.
A weak answer and a stronger one (hypothetical)
Hypothetical example, not a real case (weak answer): "Testers tested the app and gave good feedback, and we fixed bugs." This says nothing a reviewer can picture.
Hypothetical example, not a real case (stronger answer): "We asked testers to sign up and complete the main task. Several said sign-up was confusing, and one reported a crash. We changed the sign-up screen based on tester feedback and fixed the crash, then asked the same testers to try again." Write the stronger kind for your own app, using only things that actually happened in your test.
FAQ
Questions about this topic
Can I use a template for my answers?
Use a structure, not someone else's text. Copied wording does not describe your app and makes the answers weaker.
What if testers gave very little feedback?
Say so honestly and describe what you did to get more, such as specific tasks or a survey. If the notice after a denial mentions feedback, collect more before reapplying.
Do I need to have changed the app during the test?
Google asks what changes you made based on what you learned. Showing at least one real improvement makes this answer much easier.
Sources
Official references used
- App testing requirements for new personal developer accounts (Google Play Console Help)
Continue
Choose the next step
Related
Next pages to read
Rather not recruit testers yourself?
Our managed closed test runs 14 testers for 16 days. Google requires 12 testers for 14 days (for personal Play developer accounts created after 13 November 2023; organization accounts are exempt); the extra 2 testers and 2 days are our buffer.