Completing your 14-day closed test is the hard part. The production access questionnaire should be straightforward, but a surprising number of developers get rejected at this final stage because they treat the form as a formality and submit vague, template-sounding answers.
This guide explains what Google's reviewers are actually looking for, what each question is really asking, and how to write answers that read as genuine rather than copied from a forum post.
Critical Reminder
The production access application is reviewed by a real human, not an automated system. Google employs policy reviewers who read these forms carefully. Answers that sound templated, evasive, or inconsistent with your app's actual functionality are the leading cause of unnecessary rejections.
What the Form Actually Asks
The exact questions on the production access form change periodically, but the current version (as of 2026) consistently covers these areas:
- What is your app's primary purpose and core functionality?
- Who is your target audience?
- How did you recruit your closed testers?
- What devices did your testers use?
- What feedback did you receive from testers?
- Have you previously applied for production access? If so, what was the outcome?
- Are there any sensitive permissions, features, or audience considerations in your app?
Question: What is Your App's Purpose?
This is the question that trips up the most developers. The reviewer wants to understand exactly what your app does, who uses it, and why it provides value. They are also checking for category misrepresentation: apps that describe themselves as "productivity tools" when they are gambling apps, adult content platforms, or financial instruments requiring specific licensing.
What to Write
Be specific and literal. Describe the core feature, the problem it solves, and who benefits. Do not use marketing language. Do not overstate features that do not exist in the version you submitted for review.
Example: Specific Answer
"[App Name] is a personal finance tracker that allows users to manually log daily income and expenses across multiple categories, set monthly budgets, and view spending trends as charts. It stores all data locally on the device. There is no account creation, no cloud sync, and no advertising. Target users are adults who prefer tracking finances without sharing data with a third-party service."What Not to Write
"My app is a useful productivity tool that helps users manage their daily life and improve their workflow through an intuitive and easy-to-use interface." This tells the reviewer nothing and reads as a copied template. It often triggers a request for clarification or a rejection.
Question: How Did You Recruit Your Testers?
This is one of the most important questions on the form. The reviewer is checking whether you used real people you actually engaged with, or whether you used an automated service that could be providing synthetic engagement.
Be honest about your actual recruitment method. If you used a combination of personal contacts, Reddit communities, and a professional testing service, say that. Reviewers understand that not everyone has 12 developer friends willing to test an app for free.
Example: Honest, Specific Answer
"I recruited testers through three channels: five personal contacts (colleagues and friends who own Android devices), four members of the r/androiddev developer community on Reddit who volunteered through a testing exchange post, and three verified testers from a professional testing service (Hire App Testers) who provided documented evidence of device model and engagement. All testers used physical Android devices and real Google accounts. I have opt-in records showing all 12 testers joined the closed track and remained active for the full 14-day period."Question: What Devices Did Your Testers Use?
Google is checking for device diversity and specifically hunting for emulator red flags. If you used a cheap Fiverr testing gig, you will not be able to answer this question accurately, and the reviewer will instantly recognize the generic, fabricated answers standard to bot farms.
If you used a premium service like Hire App Testers, you will have a comprehensive dossier of photographic evidence (screenshots of the real device model settings) to reference. Name actual device models and Android versions exactly as they appear in your documentation.
Example: Device Answer with Evidence
"Testers used a range of physical Android devices including Samsung Galaxy S23 (Android 14), Google Pixel 7 (Android 14), OnePlus Nord (Android 13), Xiaomi Redmi Note 11 (Android 12), and Motorola Moto G (Android 12). I have screenshots of each tester's device settings page available as documentation."Question: What Feedback Did You Receive?
This question confirms that your testing was real and substantive. Reviewers are looking for specific, plausible feedback, not generic statements like "everyone loved it" or "no issues were found."
Even if your app worked perfectly, there are always things testers notice: a button that was confusing, an onboarding step that was unclear, a feature request, or a performance observation on a specific device. Write what actually happened.
Example: Specific Feedback Answer
"Testers flagged that the onboarding tutorial was skippable without clearly explaining the core features first, which left a few testers initially unsure how to create their first budget. One tester on Android 12 reported a slow load time on the settings screen, which I traced to an inefficient database query and fixed in v1.0.2. Three testers requested the ability to export data as a CSV file, which I have added to the roadmap. Overall, core functionality worked across all tested devices without crashes."Question: Sensitive Permissions or Features
If your app requests any of the following permissions, you must address them explicitly and accurately: Camera, Microphone, Location, Contacts, SMS, Phone, Storage with broad access, Accessibility Service, Device Admin, or any special Play permissions.
For each sensitive permission, explain: exactly why the feature requires it, when the permission is requested relative to user action, and what happens if the user denies it. If your app uses a permission but it is not obvious from the description why, a reviewer will flag it.
The Specific Mistakes That Get Applications Rejected
- Mismatching descriptions: Your store listing says one thing, your questionnaire says another. Reviewers check both.
- Claiming testers gave all-positive feedback: It reads as fabricated. Real testing always surfaces something.
- Vague device answers: "My testers used Android phones" without naming models or versions.
- Inconsistent permission justifications: Claiming location access is needed for "personalised content" when the app has no local content features.
- Category mismatch: Submitting as an app category that does not match the functionality described in the questionnaire.
Frequently Asked Questions
How long does Google take to review a production access application?
Most applications receive a decision within 7–14 business days. Apps in sensitive categories (finance, health, gambling-adjacent) typically take longer. If you have not received a response after 3 weeks, contact Google Play Developer Support to request a status update.
Can I submit before the 14 days are complete?
No. The "Apply for production access" button only becomes available after your closed track has met the 14-day qualifying criteria. Google's system controls the timing; you cannot submit early.
What happens if my application is rejected?
Google will provide a rejection reason. Most rejections can be resubmitted after addressing the specific issue. If rejected for insufficient tester engagement, you need another qualifying testing period. If rejected for a policy issue, resolve the policy concern before resubmitting.
Do I need to keep my closed test running while under review?
No. Once you have submitted your production access application, you do not need to maintain the closed test. Do not delete your closed track or make major changes to the listing while under review, as this could complicate the process.