How to answer Google Play’s production access questions

After the closed test, Google asks how you recruited testers, how they engaged and what you changed. How to answer each question with real data.

Updated 20 Nov 2026

What Google asks

When your closed test meets the 12 testers for 14 days requirement, the Play Console dashboard shows the production access application. It has three groups of questions.

About your closed test: how easy it was to recruit testers, how they engaged with the app, and a summary of the feedback you received and how you collected it.

About your app: who it is for, how it provides value to them and how many installs you expect in the first year.

About production readiness: what you changed based on what you learned in testing, and how you decided the app is ready for production.

Be specific and use numbers

Reviewers read many applications that say “testers liked the app”. Yours stands out with facts: how many testers stayed until day 14, how many feedback reports you received, which bugs they found and on which devices.

Write it the way you would explain it to a colleague: short paragraphs, concrete examples, no marketing language.

  1. Recruitment: where testers came from and how long it took to reach 12.
  2. Engagement: how many testers used the app during the 14 days, and what they tried.
  3. Feedback: the most common problems and suggestions, with how you collected them.
  4. Changes: each fix or improvement, and the release that shipped it.

The answer that matters most

The question about what you changed is where many applications are weak. Google wants to see that the test was a real test. List the fixes and improvements you made because of tester feedback, and mention the update you shipped during the test.

If testers found nothing, say what you checked and why you are confident. An honest short answer is better than invented changes.

If your application is rejected

Read Google’s email carefully: it usually says which area was not convincing. Our guide on rejected production access requests lists the common causes and how to run the next test.

How TesterTribe helps

Every TesterTribe tester closes the test with a structured feedback report: device and Android version, bugs, what worked and what they would change. The production access kit turns these reports into draft answers in English, ready to edit and paste into Google’s form. The last answer, about your app and your plans, is yours to write.

Frequently asked questions

How long does Google take to review production access?

Google says it usually takes 7 days or less, and sometimes longer.

Do I have to answer in English?

It is not required, but clear English answers are the easiest for reviewers to check. The TesterTribe kit drafts them in English.

Need 12 testers who stay? Join the tribe: your first campaign is free. Browse apps to test