Quick answer
Once your closed test meets the requirement, open the Dashboard in Play Console and choose to apply for production access. Google asks about your app, how you ran the closed test, what feedback you got and whether the app is ready for release. Give specific, honest answers based on your real testing notes.
When you can apply
For personal accounts covered by the testing requirement, the application unlocks after you have run a closed test with at least 12 testers opted in continuously for at least 14 days, as described in Google's Play Console Help page on app testing requirements. Play Console shows your progress on the Dashboard. If the option isn't available yet, check your tester count and dates — our tracker helps with the maths.
What Google asks about
The exact questions can change, but they generally cover three areas:
| Area | What they want to understand |
|---|---|
| About your closed test | How you recruited testers, how easy it was, and how testers used the app |
| About your app | Who it is for, what value it gives, and how many installs you expect |
| Production readiness | What you changed based on feedback and how you decided the app is ready |
How to write strong answers
- Be specific. "Testers found the signup OTP failed on Android 12; we fixed it in version 1.0.3" is far better than "We fixed bugs."
- Show engagement. Mention daily tasks, which features were tested, and the kind of feedback received.
- List real changes. Name two to five improvements you made because of testing.
- Be honest about the audience. Describe who the app is for and why they would use it.
- Don't copy templates. Generic, copied answers read as generic, copied testing.
Keep notes during the test
The easiest way to answer well is to keep a simple log while you test:
- Date, build version and what testers were asked to do.
- Bugs reported, with device and Android version.
- Usability comments and feature requests.
- What you changed and in which build.
TestLancer campaigns deliver daily check-ins, bug reports and a campaign summary, which makes this log easy to build. See Google Play Closed Testing.
After you apply
Google reviews the application and replies, usually by email and in Play Console. If you are approved, you can release to production. If not, Google normally explains what to improve — see production access rejected? what to fix.
Frequently asked questions
How long does the review take?
It varies. Google publishes general review guidance in Play Console; plan for some days rather than hours, and don't schedule a launch event for the day you apply.
Can I keep testing while I wait?
Yes. Keeping your closed test running and continuing to fix issues is a sensible use of the time.
Will a testing service guarantee approval?
No legitimate service can. Google alone decides. A good service helps you run a genuine test and collect evidence of it.