TestAppsGoogle Play Production Form: How to Fill It Out and Get Approved
You've completed the 14-day closed testing. The testers used the app. Now there's one last step: the production access request form. This form is what separates your app from the general public on the Play Store — and filling it out incorrectly is one of the most common reasons for rejection.
What is the production form?
After the closed testing cycle, the Google Play Console enables the “Request production access” button. When you click it, you have to answer a questionnaire that evaluates whether the app is ready to be published to all users.
Google uses these answers to decide whether the app:
- Was properly tested by real people
- Is stable and functional (no critical crashes)
- Complies with Google Play policies
- Offers real value to users
The form questions (and how to answer each one)
The form may vary depending on the app's category, but the main questions are consistent. Below is each question with examples of approved answers.
1. “Describe what your app does”
Google wants to understand the app's value proposition. It's not enough to say “it's a finance app”. Be specific about the features.
GOOD EXAMPLE
“FinanceApp is a personal finance management app that lets users record income and expenses, categorize transactions, view monthly spending charts, and set savings goals. It works 100% offline and syncs to a cloud backup when connected.”
BAD EXAMPLE
“Finance app.”
2. “How many testers took part and how did the testing go?”
Cite specific numbers: how many testers, how many days, which devices, and which flows were tested.
GOOD EXAMPLE
“The app was tested by 14 testers over 14 consecutive days on physical Android devices (Samsung Galaxy A54, Motorola G84, Xiaomi Redmi Note 12, among others). Testers performed sign-up, login, transaction entry, report viewing, and data export. Every session was documented with the device model, Android version, and timestamp.”
BAD EXAMPLE
“Some people tested the app and liked it.”
3. “What bugs or issues were found and how were they resolved?”
Don't say you found no bugs. Google knows that all software has issues. Showing that you found and fixed bugs demonstrates maturity in your development process.
GOOD EXAMPLE
“During testing, we identified 3 issues: (1) a crash when rotating the screen on the reports page — fixed in version 1.0.2; (2) text cut off on small screens (below 5”) — we adjusted the responsive layout; (3) slowness when loading more than 500 transactions — we implemented lazy-loading pagination. All fixes were released as updates within the closed testing track.”
4. “Does the app collect personal data? How is it protected?”
If the app collects any type of data (email, phone, location, photos), describe how it is stored and protected. Google requires a privacy policy published at an accessible URL.
GOOD EXAMPLE
“The app collects name, email, and financial data entered by the user. All data is stored locally on the device using SQLite with AES-256 encryption. The cloud backup uses Firebase with OAuth2 authentication. The privacy policy is available at example.com/privacy and details which data is collected, how it is used, and how the user can request deletion.”
5. “Why is the app ready for production?”
Summarize the testing results and show well-founded confidence (not arrogance).
GOOD EXAMPLE
“After 14 days of closed testing with 14 testers across 8 different Android device models, the app had 0 crashes in the last 7 versions. Every bug reported during the cycle was fixed. Android Vitals shows a crash rate of 0.1% and 0 ANRs. The app is stable, performant, and ready to be distributed to the general public.”
Need help with the form?
Every TestApps US plan includes assistance with the production form. We help you put together the ideal answers based on the testing performed on your app.
Talk to TestApps US →Mistakes that cause the form to be rejected
Generic or short answers
Google wants details. 'I tested it and it worked' isn't enough. Cite numbers, devices, flows, and fixes.
Saying you found no bugs
All software has bugs. Showing that you found and fixed them demonstrates professionalism. Saying 'zero bugs' raises suspicion.
Not mentioning devices and testers
Google cross-checks your answers against the Console data. If you say '20 testers' but the Console shows 8, it's inconsistent.
Missing or generic privacy policy
If the app collects data, the policy needs to be published and accessible. Generic templates may be rejected.
Incorrect app category
If the app is a finance app but is categorized as 'Tools', Google may question the classification.
Timeline: from the form to publishing
Frequently asked questions
What is the Google Play production form?
It's a mandatory questionnaire that Google requires after your closed testing is complete. In it, you describe what was tested, how many testers took part, which bugs were found and how they were resolved.
When can I fill out the production form?
After completing at least 14 consecutive days of closed testing with 12+ active testers. The 'Request production access' button will appear automatically in the Console once the requirements are met.
How long does Google take to review the form?
Between 3 and 7 business days. During periods of high demand it can take up to 10 days. Google notifies you by email when the result is ready.
What happens if the form is rejected?
You can resubmit the form with corrections. You don't need to redo the closed testing unless Google identifies issues with the testers or devices.
Can I get help filling out the form?
Yes. TestApps US includes assistance with the production form in every plan. We help craft the ideal answers based on your app and the testing performed.
From testing to the form: TestApps US handles it all
Complete testing cycle + production form assistance. Real executions documented in every cycle. Starting at $9.00.
Get started now →