How to answer the production access questionnaire
Google asks four things when you apply for production access. Specific answers get approved and generic answers get sent back. Here is the difference.
Published , 5 min read
After 14 days, Play Console surfaces a short application. It is not a formality. A completed test with a weak application still gets refused.
"How did you recruit your testers?"
Answer honestly and plainly. Paid testing services are an accepted channel: Google's own guidance lists them alongside friends, colleagues and communities. Say what you actually did. Inventing a recruitment story you cannot support is a far bigger risk than naming a service.
A workable answer: "Twelve testers were recruited through a paid Android testing service, plus two colleagues. All installed the app on their own devices and used it through the testing period."
"What feedback did you receive?"
Be concrete. Google is checking that something real happened, so name issues rather than sentiments.
A workable answer: "Testers reported the onboarding screen not scrolling on smaller displays, a crash when opening settings offline, and slow first load on 4G. Two testers said the sign-up flow asked for too much before showing any value."
"What changes did you make?"
Tie each change to a piece of feedback and, ideally, to a release you shipped to the closed track.
A workable answer: "We fixed the settings crash and released it to the closed track on day 6. We made onboarding scrollable in the same release, added a cache to cut first load, and moved two sign-up fields to a later step."
"How did you decide the app is ready?"
Show a threshold you set and met, not a feeling.
A workable answer: "No crashes reported in the final seven days, all reported issues closed, and the last release ran the full period without a new bug report."
The pattern behind all four
Every question is asking the same thing in a different way: did real people use this, and did it change because of them? Answers with named issues, dated releases and specific fixes read as true. Answers made of adjectives do not.
Before you submit
- Confirm 12 or more testers are still opted in right now
- Confirm 14 full days have passed since the twelfth opt-in
- Confirm your data safety form and content rating are complete
- Keep the closed track live until access is granted