# How to Apply for Google Play Production Access After Closed Testing

> Apply for production access after 12 testers complete 14 days: readiness checks, questionnaire answers, evidence, and what to do while you wait.

Canonical: https://testmyapps.app/blog/apply-for-google-play-production-access
Last updated: 2026-10-26

Author: Arun

Published: 2026-07-16
Updated: 2026-10-26
Reviewed by: Arun

## At a glance

- Finish 12 testers × 14 continuous days on the closed track first — that only unlocks the form.
- Approval is separate: Google still reviews your answers and the app.
- Write specific answers (recruitment, tasks, feedback, fixes) and keep the closed test healthy while you wait.

You can apply for Google Play production access after an affected personal account has at least twelve testers opted in to its closed test for the last fourteen days continuously. Meeting that threshold unlocks the application; it does not guarantee approval.

Before submitting, verify the tester count in Play Console, review feedback and fixes, and check that store listing, privacy policy, Data safety, and reviewer access match the current build.

If any policy surface is unclear, review the [common Google Play policy rejection reasons and fixes](https://testmyapps.app/blog/google-play-policy-rejection-reasons-fix) before submitting.

### Eligibility ≠ approval

The 12×14 rule lets you open the form. Google still decides based on the app, the test, and your answers.

## Confirm that the closed test qualifies

Use Play Console as the source of truth. At least twelve testers should still be opted in when you apply, and the qualifying group should have remained opted in for the last fourteen days continuously.

Do not count internal testing time, invitations never accepted, or sideloaded builds.

Before you apply, check [recent Play policy changes](https://testmyapps.app/blog/google-play-policy-updates-closed-testing) that affect closed testing. If the test is not finished yet, start with [how to pass closed testing](https://testmyapps.app/blog/how-to-pass-play-store-closed-testing).

- Closed release is available to the intended tester group
- At least twelve testers are currently opted in
- Those testers cover the last fourteen continuous days
- Feedback and fixes from the test are documented

*Play Console is the source of truth.*

## How to answer the questionnaire (without fluff)

Write like a human who ran a real test. Google wants to know how you found testers, what they did, what you fixed, and why the app is ready.

Draft answers while the test is running so details do not disappear. Prefer short evidence-backed paragraphs over filler.

### Avoid this

Generic lines like "we tested thoroughly with many users" without numbers or examples look empty.

- Recruitment: where testers came from (community, friends, paid service) — be specific
- Engagement: tasks completed (login, core feature, purchase flow if any)
- Feedback: 2–3 real themes you heard (bugs, confusion, requests)
- Changes: what you shipped after feedback, with build numbers or dates if you have them
- Readiness: store listing, Data safety, and privacy policy match the build

*Draft answers while the test is running so details don't disappear.*

## Submit and keep the test healthy

Open the production-access task from the Play Console dashboard, answer each question directly, and check that your answers agree with the current app. Google reviews the submission and emails the account owner when a decision is ready.

Keep the closed test and support channel available while the request is under review. If Google asks for more testing, use the feedback in the decision rather than resubmitting the same answers.

*Open the production-access task from your Play Console dashboard after a qualifying closed test.*

## Frequently asked questions

### Does completing 14 days guarantee production access?

No. It makes an affected account eligible to apply. Google still reviews the app, test, answers, and production readiness.

### Should testers remain opted in while Google reviews?

Keeping the test healthy is the conservative approach in case Google asks for more testing or clarification.

### Can I copy answers from another app?

No. Answers should describe your app and its actual test. Generic copied answers can conflict with the evidence Google sees.

### Should I mention a paid testing service?

Describe recruitment honestly and focus on real opt-ins, scenarios, feedback, fixes, and the work your team performed.

## Sources

- [App testing requirements for new personal developer accounts](https://support.google.com/googleplay/android-developer/answer/14151465?hl=en) - Google Play Console Help
- [Set up an open, closed, or internal test](https://support.google.com/googleplay/android-developer/answer/9845334?hl=en) - Google Play Console Help

## Related

- [Production access approval timeline](https://testmyapps.app/blog/google-play-production-access-approval-timeline) - What to expect while you wait for a decision.
- [Production access denied: fixes](https://testmyapps.app/blog/production-access-denied-google-play) - What to change if Google says no or asks for more testing.
- [Get 12 testers for 14 days](https://testmyapps.app/get-12-testers-for-14-days) - Paid help if the closed test is not solid yet.
- [Blog](https://testmyapps.app/blog) - All published TestMyApps guides.
