Production access is the final gate between your completed app and the Google Play Store. Here is exactly what it requires, how to apply, and what to do if your application is rejected.
Production access is the status that allows your app to be publicly listed on the Google Play Store. It is separate from uploading your app — you can have an APK in Play Console for months before gaining production access.
Prerequisites Before Applying
- 14-day closed testing completed with 12+ active testers
- App policy compliant — no policy violations in the account
- Complete store listing: description, screenshots, privacy policy URL
- Target audience and content rating questionnaire completed
- Developer account in good standing (no previous policy strikes)
Where to Find the Production Access Application
In Google Play Console, navigate to your app's dashboard. If you have met the closed testing requirement, you will see a banner or a button under 'Publish your app' labeled 'Apply for production access'. If this button is not visible, your testing period has not yet met the minimum requirements.
What the Questionnaire Asks
The production access questionnaire covers three main areas. First, app purpose and functionality: what the app does, who it is designed for, and how it differs from existing apps on the Play Store.
Second, testing evidence: Google asks how many testers you had, how long they tested, what feedback you received, and what changes you made based on that feedback. This is why tester feedback logs matter — you need real data here, not fabricated numbers.
Third, developer identity: confirmation of your business or personal details, reasons for publishing, and an acknowledgment of Play Store policies.
If you used a testing service, make sure you have the tester participation report they provide. Google's questionnaire directly asks about tester feedback — vague answers increase rejection risk.
Timeline After Submitting
Most developers receive a decision within 3 to 7 business days. If approved, your production track becomes active immediately. If rejected, you will receive an email explaining why. Common rejection reasons include: insufficient testing data, policy violations, incomplete store listing, or a flagged developer account.
What to Do If Rejected
- Read the rejection reason email carefully — it is specific
- Address every point listed before reapplying
- If rejected for insufficient testing, repeat the full 14-day cycle with better data
- Do not appeal without fixing the stated issues first
- If rejected for policy reasons, fix those in the app before resubmitting
Our service includes a tester participation log you can use directly in the production access questionnaire.
Get Your App Tested