Day15 › Guides

Google Play production access questionnaire: what it asks and how to prepare

Checked against Google’s Play Console Help on Oct 29, 2026 · By Anchor Point Apps

Once your closed test meets the requirement, the Dashboard offers “Apply for production”. The form has three parts. Here is what each asks, per Google, and what to have ready.

Before you start: Google warns that if you click Discard or leave a page without clicking Next (or Apply on the last page), your changes aren’t saved. Draft your answers in a document first.

Part 1: About your closed test

Google says this section “helps verify that apps have been thoroughly tested before publication.” You’ll:

1. Select how easy it was to recruit testers.
2. Describe tester engagement: whether testers used all available features, and whether their usage matched what you expect from production users (with details on any differences).
3. Summarize the feedback you received and describe how you collected it.

Prep worksheet:

• How you found testers (communities, friends, a mailing list) and how long it took.
• Which features you asked them to test, and which ones you know went untested.
• Where feedback came from (Play testing feedback, email, a chat group) and 3–5 concrete themes.
• Where real usage might differ from the test (e.g. “testers used it for a few minutes a day; real users will use it during commutes”).

Part 2: About your app/game

Per Google, answers here “are not displayed publicly on Google Play and do not affect app visibility, Play Console feature access, or eligibility for developer programs.” You’ll:

1. Specify the target audience, “as specific as possible.”
2. Describe your app’s value proposition (for games, what makes it unique).
3. Select an estimated install range for the first year.

Prep: a one-sentence audience (“freelance photographers who invoice from their phone” beats “everyone”), a two-to-three sentence value proposition, and an honest install estimate.

Part 3: About your production readiness

1. Describe the changes you made based on what you learned in your closed test.
2. Describe how you determined the app was ready for production.

Prep: a dated list of fixes you shipped in response to feedback (this is why a feedback log matters), plus your readiness criteria: crash-free sessions, the pre-launch report Google offers in Play Console, device coverage, remaining known issues.

A skeleton for each answer

Fill the brackets with your facts. Don’t submit template text with the brackets still in it, and don’t describe testing that didn’t happen.

Also check before you hit Apply

Google says it’s your responsibility to ensure policy compliance before applying, and that “review is not a troubleshooting step.” It highlights app content and monetization, target age group and content rating, functional reliability (no crashes or missing screens), and test credentials: if your app needs sign-in, provide working login details in Play Console. Also make sure your Data safety form and privacy policy are done.

After you apply

Google emails the account owner when the review completes. It says review usually takes seven days or less. If the result is that more testing is required, keep your closed test running.