How I Fill In the Google Play Production Access Form After a Closed Test

The closed test is done, the Dashboard finally shows Apply for production, and then you hit a form full of open text boxes. This is the part where a lot of us rush. I did on my first app, and I wrote two-line answers that said almost nothing.

These days I treat the production access application as a short report on my closed test. Here's how I fill it in, section by section, and what I prepare before I even open it.

First, check you're actually eligible

For personal developer accounts created after November 13, 2023, Google asks for a closed test with at least 12 testers opted in continuously for at least 14 days. Before applying I open Test and release > Testing > Closed testing and confirm two things: the opted-in count is 12 or more, and nobody dropped out and rejoined late in the window. If a tester opts out and back in, their 14 days have to be consecutive again.

If either one is shaky, I wait a couple of days. Applying early only sends you back to testing.

Gather three things before you open the form

I keep a plain text file per app with:

1. The test window. Start date, end date and the opted-in count on the last day. A screenshot of the Testers tab helps me stay honest about numbers.
2. A feedback log. Every useful comment, where it came from (Google Play private feedback, email, a chat), the date, and what I did about it. Play Console keeps the private feedback under Monitor and improve > Ratings and reviews > Testing feedback.
3. A change list. Version codes I shipped during the test and one line on what each fixed.

With those three in hand, the form takes twenty minutes instead of an evening of guessing.

Section 1: About your closed test

This part asks how you recruited testers, how easy it was to get them, and how engaged they were. I answer it like I'd explain it to another developer:

• Who the testers were. Friends, a dev community, a tester group, a managed service. Say it plainly.
• What I asked them to do. I list the actual tasks: sign up, finish the main flow, try the new screen, report anything that felt broken.
• What came back. A few real examples from the feedback log, written in my own words. Not "testers loved it". Something like "two testers said the onboarding skipped the permission screen on Android 14, fixed in version 7".

If engagement was low, I say so and say what I'd do differently. Vague answers are what make this section weak.

Section 2: About your app

Here I describe who the app is for and what it does in normal words. One short paragraph on the audience, one on the main features, and a note on anything that needs a login. If the app needs an account, I make sure the test credentials in App content still work, because a reviewer who can't log in can't review anything.

Section 3: Production readiness

This asks what you changed based on the test and how you decided the app is ready. My change list answers the first half directly. For the second half I mention the checks I ran: no crashes on the devices testers used, store listing and content rating filled in, data safety form updated after any new SDK.

Google reviews the application, and the help page says it usually takes 7 days or less. The decision is theirs. All the form can do is show them a real test happened and you acted on it.

A short template I reuse

Testers: [who] recruited via [how]. [N] opted in on the closed track from [date] to [date].
Tasks given: [task 1], [task 2], [task 3].
Feedback: [example 1 + fix + version], [example 2 + fix + version].
Changes: version [x] fixed [y]; version [z] improved [w].
Ready because: [checks you ran].

I fill in the brackets from my notes and then rewrite each line so it reads like me, not a template.

If you don't have enough testers yet

Getting 12 people to stay opted in for 14 straight days is the hard part for a solo developer. I wrote up honest ways to frame these answers, with frameworks for each question, over on 12testers: Google Play production access questions: honest answer frameworks. 12testers also runs a managed closed test for $8 per app if you'd rather not chase testers yourself, though the feedback and the answers still have to come from you.