How to apply for production access on Google Play after closed testing

When you can apply

Production access requires 12 testers opted in for the preceding 14 days at the moment you apply. The Play Console dashboard tracks this for you and shows the application option when the bar is met. Until then, the Production and Pre-registration tracks remain disabled.

Do not rush to apply the minute the counter turns green if the test itself was thin. A few more days of visible usage and one more update can be the difference between approval and a request to keep testing.

Where the form is and how it saves

Open the app's Dashboard in the Play Console and click Apply for production. The form is split into three sections. Each section is saved only when you click Next (or Apply on the last one); if you discard changes or leave the page early, what you typed in that section is lost.

Draft your answers in a document first. It avoids losing work, and you will want the same material if you ever need to apply again.

Section 1: About your closed test

This is the section reviewers care about most, because it describes the evidence. Google asks how easy it was to recruit testers, whether testers used all the app's features, whether their usage matched what you expect from production users (and how it differed), and for a summary of the feedback you collected and how you collected it.

• State the facts: how many testers joined (e.g. "14 testers, 12 completed the full 14 days"), which countries and device types they used, and how you recruited them.
• List the features testers exercised and name the ones they did not, with a reason.
• Describe how usage compared with real-world expectations — session length, frequency, flows that got more attention than you expected.
• Summarise the feedback concretely: the top three issues reported, how you collected them (in-app form, chat, email, a testing report), and what you changed.

Section 2: About your app or game

Here Google asks who the app is for (target audience), what value it provides (value proposition), and an estimate of first-year installs. Google says these answers are not shown publicly and do not affect how your app is surfaced; they help the reviewer understand what the app is and whether the closed test made sense for it.

• Be specific about the audience: a city, a profession, a use case — not "everyone".
• Explain the problem the app solves in two or three sentences, in plain language.
• Give an honest install estimate; nothing is gained by inflating it.

Section 3: About your production readiness

The final section asks what you changed based on the closed test and how you decided the app is ready for production. Reviewers want to see cause and effect: tester feedback led to specific fixes, fixes were shipped as new builds during the test, and you checked the result.

• Name the builds you shipped during the window and what each one fixed or improved.
• Mention crash and ANR fixes, including anything the pre-launch report flagged.
• Describe your readiness check: crash-free sessions, device coverage, completed store listing and policy declarations.

After you apply

Google reviews the application, usually within about seven days, though it can take longer. The account owner receives an email when the review is complete, and the dashboard updates as well.

If the app is approved, the Production page becomes available and open testing unlocks. If Google decides more testing is needed, your closed test continues; the help pages name two usual causes — fewer than the required opted-in testers, or insufficient tester engagement.

If you are asked to keep testing

A "continue testing" decision is common and recoverable. Treat it as feedback about the test rather than the app.

1. 1Check the tester count: confirm at least 12 testers are still opted in, and add replacements if anyone left.
2. 2Raise engagement: ship an update with visible changes, ask testers to try specific flows, and remind them to keep the app installed.
3. 3Collect more feedback and act on it, so Section 1 and Section 3 have new, specific material.
4. 4Let the window run until 12 testers have another 14 consecutive days if your count was the issue.
5. 5Apply again with precise numbers and a short account of what changed since the first application.

How TesterMandi helps with the application

The application is easiest to write when the test produced evidence. TesterMandi's Genuine Feedback & Testing plan is built around that: 12 genuine testers, daily proof of participation, structured feedback collection and a detailed testing report you can summarise directly in Section 1 and Section 3. Play Console Approval gives you the same testers and daily proof, without the feedback and report.

TesterMandi helps developers organize and participate in testing. Google Play production approval is determined solely by Google and cannot be guaranteed by TesterMandi.