How to apply for production access after closed testing

Once you have at least 12 testers who have been opted in to your closed test continuously for 14 days, open the Dashboard in Play Console and click Apply for production. You then fill in a three-part form about your closed test, your app and your production readiness, and submit it for Google's review.

This article covers the process: when to apply, what to prepare, and how to get through the form without losing your work. For example answers to each question, use our apply-for-production guide.

Before you click Apply

Check that you're actually eligible

Google's rule for personal accounts created after November 13, 2023 is that "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."

Two practical consequences:

• The check happens at the moment you apply. If a tester drops out on day 13 and you're left with 11, you're short.
• Applying one day later than the minimum gives you a small cushion. Our guide recommends day 15, the day after testing ends.

If you're not sure your testers count, see what counts as an opted-in tester.

Gather your material first

The form asks for written answers, and Google warns that leaving the page without clicking Next or Apply loses what you entered. Draft your answers in a separate document, then paste them in. Have these ready:

1. Your testing feedback. Google says "you must summarize your testing feedback when applying for production access." Feedback from testers is in Monitor and improve > Ratings and reviews > Testing feedback. Add anything you collected in other ways, such as a chat group or survey. Our article on collecting feedback from closed testers covers this.
2. A list of changes you made during or after the test, with versions if you shipped updates.
3. A clear description of your audience, as specific as you can make it.
4. A realistic estimate of first-year installs.
5. Notes on how you recruited testers and how easy or hard it was.

Check your app against Google's policy list

Before applying, Google tells developers to review app content and features (including monetization), target age group, content rating and store listing accuracy, functional reliability, and test credentials. Google is blunt about this: "review is not a troubleshooting step." Fix known problems first. If your app needs a login, make sure working credentials are in Play Console; see giving testers and reviewers access.

Step by step: submitting the application

1. Open Play Console and select your app.
2. Go to the Dashboard.
3. Click Apply for production. If you don't see it, your app may not yet meet the testing requirement.
4. Fill in Part 1, About your closed test: how easy it was to recruit testers, how engaged they were (whether they used all features and whether their usage matched what you expect in production), and a summary of the feedback and how you collected it.
5. Click Next.
6. Fill in Part 2, About your app or game: the target audience, the value your app provides (for games, what makes the game unique) and your estimated installs in the first year. Google notes these answers "are not displayed publicly" and don't affect your app's visibility.
7. Click Next.
8. Fill in Part 3, About your production readiness: what you changed based on the closed test and how you decided the app was ready.
9. Click Apply.

The account owner receives an email when the review is done. Google says review "usually takes seven days or less, but can occasionally take longer."

Tips for answering well

You'll find a worked example for every question in our apply-production guide, so here are just the principles:

• Be specific and true. Name real features, real feedback themes and real changes. Generic answers are hard to believe.
• Match the evidence. If you say testers used every feature, your test should support that. Ways to keep testers active are in keeping closed testers engaged.
• Describe changes concretely. "Fixed a crash on Android 11 when opening settings" says more than "fixed bugs."
• Keep estimates sensible. A modest, reasoned install estimate is better than an inflated one.
• Don't promise what isn't built. Describe the app testers actually used.

After you submit

Keep your closed test running while you wait. Google's best practice is to "continue running closed tests while resolving user-reported issues and bugs", and if your application isn't approved, Google may ask you to continue testing. Removing your testers the day you apply leaves you with nothing to build on.

When you're approved, the Production page and Open testing are unlocked and you can create your first production release.

If Google asks for more testing, don't panic. Google lists "fewer than 12 opted-in testers or insufficient tester engagement during the testing period" as reasons. Keep testing, address the cause and reapply when you're ready. Google doesn't publish a fixed waiting period.

Checklist

• 12+ testers opted in continuously for 14 days, checked on the day you apply
• Feedback summary drafted from Testing feedback and your own channels
• List of changes made during the test
• Audience, value and install estimate drafted
• Policy items reviewed, test credentials in place
• Answers saved outside Play Console before you start

If you still need the 14-day test itself, GoPlayTester provides 12+ real testers on real devices; see the setup guide or order here. Google makes the final decision on every application.