Free tool · No signup
Draft your Google Play production access answers
After the 14-day closed test, Play Console asks nine questions before a new personal account can publish: how you found testers, how they used the app, what they told you and what you changed. Describe your test below and get a first draft of every answer. Where a fact only you have is missing, the draft leaves a bracket instead of guessing.
The nine questions, and what a strong answer has
This is the production access form as developers see it in Play Console in 2026. Google does not publish it, and the wording shifts a little between accounts.
About your closed test
1. How did you recruit users for your closed test? For example, did you ask friends and family, or use a paid testing provider?
Name the method plainly, including the service or community if you used one. If it was a mix, say which part came from where.
2. How easy was it to recruit testers for your app?
Multiple choice. Pick what was true.
3. Describe the engagement you received from testers.
Numbers and behaviour together: how many testers used the app, how often, and what they did in it. "Testers used the app" on its own says nothing.
4. Provide a summary of the feedback that you received from testers. Include how you collected the feedback.
Two or three specific things testers told you, good and bad, and where you collected them. A named screen or a quoted sentence beats an adjective.
About your app
5. Who is the intended audience for your app?
One concrete group of people, like "students who split rent with flatmates", not "everyone".
6. Describe how your app provides value to the users.
What a user gets done with the app, in plain words.
7. How many installs do you expect in your first year?
Multiple choice. Pick a realistic range.
Your production readiness
8. What changes did you make based on your closed test?
Each change next to the feedback that caused it. If you changed nothing, say why.
9. How did you decide that your app is ready for production?
The test, the fixes and how you checked them. Leave out claims you cannot back up, like zero crashes.
If Google asks for more testing
The refusal email is titled "More testing required to access Google Play production". It asks for another 14 days of testing and lists tester engagement among the possible reasons. Your answers to questions 3, 4 and 8 are the only place engagement can show up, so keep notes for them from day one of the next test. What to do after a refusal.
If you run the test on TestFi, these answers come from your testers' own notes. Each of the 16 testers writes on day 7 and day 14, your dashboard drafts the form from what they wrote, and if 12 are not still opted in on day 14 we run it again at no cost.
Start a closed test · $39.99Rather hand over the whole launch? TestFi Launch, $499: a 20-tester closed test, recordings, a fix list and these answers edited by a person.
Questions
Is the tool free?
Yes, and there is no signup. Each visitor gets a few drafts an hour, which is plenty for one app.
Is what I type saved?
No. The text goes to our AI provider, Anthropic, to write the draft and comes straight back to your browser. TestFi does not store it.
Will these answers get my app approved?
No tool can promise that. Google decides from your whole test and your account. The draft makes what happened in your test easy to read, and it says only what you told it.
Can I say I used a paid testing service or a swap group?
Yes. The draft names the method you pick, and the service or community if you give its name. Google asks the question directly, so the honest answer is the safe one.
Who has to answer these questions?
Personal developer accounts created after November 13, 2023, once the closed test has had 12 testers opted in for 14 continuous days. Organization accounts are not required to run the closed test.
How long does Google take to reply?
Google says the review usually takes 7 days or less. If the answer is more testing, you test for another 14 days and apply again.
Still inside the 14 days? See which day you are on, or read the requirement, explained.