Skip to content

Production Access

How to Apply for Google Play Production Access After Closed Testing

Follow the production-access application process after 12 testers complete 14 days, including readiness checks, evidence, and submission steps.

TestMyApps EditorialPublished July 16, 2026Updated July 16, 2026Reviewed by TestMyApps EditorialApplication guide
Illustration of an Android QA workflow with a checklist, a bug under a magnifying glass, and launch steps

You can apply for Google Play production access after an affected personal developer 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. Google also asks about the app, the test, what you learned, and why the release is ready.

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

Check production readinessScore the evidence and policy checks you should complete before opening the application.

Confirm that the closed test qualifies

Use the Play Console dashboard 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 time spent only on internal testing, invitations that were never accepted, or sideloaded builds. If the count dropped below twelve, resolve the gap and use a conservative date before applying.

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

Prepare evidence before opening the questionnaire

Create a short testing summary with the number of testers, device or Android-version coverage, scenarios completed, feedback themes, bugs found, and fixes released. Use real details from your run rather than generic claims.

Keep private tester information out of the application. Aggregate counts and concrete examples are more useful than names or email addresses.

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 says it reviews the submission and emails the account owner when the decision is ready.

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

FAQ

Questions about this topic

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 the request?

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

What should I include as testing evidence?

Use tester counts, scenarios, device coverage, feedback themes, bugs found, fixes released, and retest outcomes without exposing personal tester data.

Sources

Official references used

Continue

Choose the next step

Related

Next pages to read

Apply the guide to your closed-testing run.

Use the free tools to check your setup, or review managed tester support when recruitment and coordination are the blocker.