Production access application form: questions and what to watch for

In short: once 12 testers have been opted in for 14 days in a row, Apply for production on your Dashboard opens the form. It has three parts: your closed test, your app, and your production readiness. This page gives the closed test questions in Play Console's own English wording. It gives no sample answers, because your answers should come from your own test.

Last checked: Source: Play Console and Play Console Help

Leave the test to us

12 testers plus 3 backups, 14 days in a row. Follow every day on a live table.

See packs

When does the form open?

Google's requirement: “At least 12 testers must be opted in to your closed test when you apply for production access, and they must have been opted in continuously for the preceding 14 days.” Once that's met, open your app's Dashboard in Play Console and click Apply for production. In Play Console's English interface, the form's window is titled “Apply for access to production”.

12 people must still be opted in when you apply.

Part 1: About your closed test

Google describes the purpose of this part: “This process protects users from low-quality apps, prevents malware distribution, and reduces fraud.” The four questions, as Play Console's English interface words them:

  1. “How did you recruit users for your closed test? For example, did you ask friends and family, or use a paid testing provider?” Free text, up to 300 characters.
  2. “How easy was it to recruit testers for your app?” Options: Very difficult, Difficult, Neither difficult or easy, Easy, Very easy.
  3. “Describe the engagement you received from testers during your closed test” The question's description: “Include whether or not testers utilized all of the features in your app, and whether tester usage was consistent with how you would expect a real user to use your app. If not, describe the differences you would expect to see.” Up to 300 characters.
  4. “Provide a summary of the feedback that you received from testers. Include how you collected the feedback.” Up to 300 characters.

Google's help page covers questions 2, 3 and 4; it doesn't mention question 1 or the 300-character limit. We saw those in our own app's application window in November 2026.

Part 2: About your app/game

According to the help page, in this part you:

  • Specify your app's target audience: “Be as specific as possible.”
  • Describe its value proposition: for an app, how it provides value to users; for a game, what makes it unique.
  • Select an estimated install range for the first year.

According to Google, these answers “are not displayed publicly on Google Play and do not affect app visibility, Play Console feature access, or eligibility for developer programs.”

Part 3: About your production readiness

  • The changes you made to the app based on what you learned in the closed test.
  • How you decided the app was ready for production.

Then click Apply. We haven't yet seen the full wording of the part 2 and part 3 questions in Play Console, or their character limits; listed here are the topics the help page names.

What to watch for

  • Write your answers somewhere else first. Google's warning: “If you click Discard or leave the page without clicking Next, your changes are not saved.” That way your text won't be lost if you have to leave the form halfway.
  • Write the truth. Say where you actually found your testers; Google itself mentions paid testing providers as an option in the question. Don't write about engagement or feedback that didn't happen in your test.
  • Explain differences, don't hide them. If usage didn't match your expectations, the engagement question asks you to explain the differences.
  • Record feedback throughout the test. Google's tips: “Maintain a record of received feedback.” and “You must summarize your testing feedback when applying for production access.” Testing feedback is in Play Console under Monitor and improve > Ratings and reviews > Testing feedback.
  • 300 characters is short. In the free-text questions of part 1, be specific: what, how many days, how it was collected.
  • Check policy compliance before you apply. Google: “review is not a troubleshooting step.” Look especially at four areas: app content and features, target audience and content rating, functional reliability (no crashes, broken functionality or missing screens), and, if your app has a login, working test credentials in Play Console.

After you submit

Google reviews the application and the result goes to the account owner by email: “Review usually takes seven days or less, but can occasionally take longer.” If it's approved, the Production page and Open testing become available. Google may ask for more testing; what that means and what to do is covered in this guide.

Not in the official sourcesWhat happens if the number of opted-in testers drops below 12 after you apply, while the review is running: Google lists “having fewer than 12 opted-in testers” among the reasons for continued testing, but doesn't say whether that's measured when you apply or during the review. The full wording and character limits of the part 2 and part 3 questions in Play Console.

Sources

Play Console Help page. The part 1 questions, options and 300-character limit are quoted word for word from our own app's application window in Play Console's English interface (November 2026); Google can change the form over time.

Leave the test to us

12 testers plus 3 backups, 14 days in a row. Follow every day on a live table.

See packs