Google Play Production Access Questionnaire: Answer Templates

Google Play's production access questionnaire has three sections: About your closed test, About your app/game and About your production readiness. Below, every question Google lists has a fill-in template with placeholders and a list of what to collect during your 14-day closed test, so you can answer from records instead of memory.

When your closed test has met Google's criteria, you apply for production access from the Dashboard in Play Console by clicking Apply for production. The form asks you to describe your closed test, your app and how you decided it was ready. This page gives a fill-in template for each question, worded as Google lists it in App testing requirements for new personal developer accounts. Replace every [placeholder] with what really happened in your test, and leave out anything that does not apply.

For the steps around the form, including when you can apply and what happens after, see our guide to applying for production access.

What does the production access questionnaire ask?

Google's application form has three sections, and you click Next after the first two and Apply after the last. Part 1 asks how easy tester recruitment was, how testers engaged with your app and what feedback they gave. Part 2 asks for your target audience, your value proposition and an estimated first-year install range. Part 3 asks what you changed after testing and how you decided the app was ready.

How do you answer About your closed test?

Google says the About your closed test section helps verify that apps have been thoroughly tested before publication on Google Play, which protects users from low-quality apps, prevents malware distribution and reduces fraud. It has three questions.

Select an option indicating how easy it was to recruit testers for your app.

This is a selection in the form rather than a written answer. Keep a short note of how you recruited testers, because the rest of Part 1 builds on it.

TEMPLATE

Option selected: [the option in Play Console that matches your experience]
How testers were recruited (your notes): [friends and family / colleagues / online communities / a tester service]
Testers invited: [number] · Testers opted in: [number]

What to collect during the 14 days

  • Where each tester came from: personal network, a community or a tester service
  • The date each tester opted in, for example in our closed testing tracker template
  • How many people you invited compared with how many opted in

Provide details about tester engagement during your closed test.

Google asks you to include whether testers used all available app features, and whether tester usage matched expected production user behavior, with details on any observed differences.

TEMPLATE

[number] testers were opted in to our closed test through [email list / Google Group] from [start date] to [end date].
Features testers used: [feature 1], [feature 2], [feature 3].
Features not used, and why: [feature] – [reason, or none].
Compared with how we expect production users to behave, usage [matched / differed]. Differences observed: [details, or none observed].

What to collect during the 14 days

  • Which features each tester used, from their feedback or your own app analytics
  • Any feature no tester reached, and the reason
  • How testers used the app compared with how you expect real users to use it

Summarize the feedback received from testers and describe how feedback was collected.

Google says you must summarize your testing feedback when applying for production access, and recommends keeping a record of the feedback you receive.

TEMPLATE

We collected feedback through [feedback URL or email on the opt-in page / Google Play private feedback / a messaging group / another channel].
We received [number] pieces of feedback. Main themes: [theme 1], [theme 2], [theme 3].
Examples: [one bug report, in short], [one usability comment, in short].

What to collect during the 14 days

  • Every piece of feedback with its date, tester and channel
  • Private feedback from the Testing feedback page in Play Console (Monitor and improve > Ratings and reviews > Testing feedback)
  • Recurring themes; Google suggests reviewing feedback regularly to identify them

How do you answer About your app or game?

Google says the About your app/game section gives context about your app or game. These answers are not displayed publicly on Google Play and do not affect app visibility, Play Console feature access or eligibility for developer programs. It has three questions.

Specify the target audience for your app or game. Be as specific as possible.

Google asks for as much detail as possible. Describe real groups of people, not everyone with a phone.

TEMPLATE

[App name] is for [specific group of users] who [need or situation].
Main countries or regions: [countries or regions].
Age range: [age range], matching the target age group set in Play Console.

What to collect during the 14 days

  • Who your testers were and how closely they matched your intended audience; Google suggests recruiting testers who represent it
  • The target age group and content rating settings in Play Console, so your answer matches them

Describe your app or game value proposition.

For apps, Google asks how your app provides value to users. For games, it asks what makes your game unique.

TEMPLATE

App: [App name] helps [audience] [do the main task] by [how it works]. Compared with [how they do it today], users get [specific benefit].
Game: [Game name] is a [genre] game where players [core activity]. What makes it unique is [unique element].

What to collect during the 14 days

  • Tester comments on what they found useful, in their own words
  • The features testers used most often

Select an estimated install range for your app or game during its first year.

This is another selection. Note how you reached your estimate so you can explain it if you need to.

TEMPLATE

Option selected: [install range shown in Play Console]
Basis for the estimate (your notes): [launch plans, marketing channels, size of your audience]

What to collect during the 14 days

  • Your launch and marketing plans for the first year
  • The size of the audience you described in the target audience answer

How do you answer About your production readiness?

Google says the About your production readiness section helps evaluate whether your app or game is prepared for production release. It has two questions, and you finish with Apply.

Describe any changes made to your app or game based on what you learned from your closed test.

Google asks specifically for changes that came from the closed test, so link each change to the feedback behind it.

TEMPLATE

Based on closed test feedback, we:
– fixed [bug], reported by [number] testers on [device / Android version];
– changed [screen or feature] because [feedback];
– added [item] after testers asked for [request].
These changes are in version [version name or code], released to the closed testing track on [date].

What to collect during the 14 days

  • Each fix and change, with the feedback it came from
  • The version code and release date of every closed testing release
  • Issues from the pre-launch report that you resolved; see our pre-launch report guide

Describe how you determined that your app or game was ready for production.

Explain the checks you used to decide. Google's own guidance points to stability, the overall user experience and policy compliance.

TEMPLATE

We decided [app name] was ready for production because:
– [criterion, for example: no open crash reports from testers since version [version]];
– [criterion, for example: testers used all main features without blocking issues];
– we checked [policy areas: app content and features, targeting and content rating, functional reliability, test credentials].

What to collect during the 14 days

  • Crash and bug reports from the 14 days, and when each one was closed
  • Results of the pre-launch report
  • Your check of the policy areas Google lists

Which common mistakes does Google warn about?

Each of these comes from Google's testing requirements article:

  • Fewer than 12 opted-in testers. Google names this as a reason for required continued testing.
  • Insufficient tester engagement. Google names insufficient tester engagement during the testing period as the second reason.
  • Counting testers who left early. Testers who opt in, test for fewer than 14 days and then opt out do not count. A tester who opts out and back in needs 14 consecutive days.
  • Losing your answers. If you click Discard or leave the page without clicking Next or Apply, your changes are not saved.
  • Using review as a troubleshooting step. Google says submitting non-compliant apps, expecting reviewers to identify issues, leads to rejections, review delays and lengthier appeal processes.
  • No working test credentials. If your app requires user authentication, Google asks you to provide valid, working login credentials in Play Console so reviewers can test your app fully.

How should you use these templates?

Start a document on day 1 of your closed test with the eight questions above, and add to it as feedback arrives. By day 14 most answers are already written. Keep every statement true and specific: Google reviews the application, and only your real numbers, dates and changes belong in the placeholders. Before you submit, run through our production access checklist.

Frequently asked questions

Are my answers in the About your app or game section public?

No. Google states that these answers are not displayed publicly on Google Play and do not affect app visibility, Play Console feature access or eligibility for developer programs.

What happens if I leave the form without clicking Next?

Google says your changes are not saved if you click Discard or leave the page without clicking Next, or Apply on the last section. Drafting your answers somewhere else first avoids losing them.

How long does Google take to review the application?

Google says review usually takes seven days or less, but can occasionally take longer. The account owner receives an email notification when the review is complete.

Do these templates make Google approve my app?

No. Google makes the production access decision. The templates only help you describe what actually happened in your closed test, using your own records.