What Happens After 14 Days? The Production Questionnaire
A complete walkthrough of the final questionnaire Google asks before granting your app production access - the exact questions, real example answers, and the pro tip most developers miss.
Congratulations - you survived the 14 days of closed testing. Your tester count never dropped below 12, and the Play Console finally unlocked the "Apply for Production" button.
But you aren't done yet. Before Google flips the switch, you must convince a human reviewer that your testing was actually meaningful by filling out the Production Access Questionnaire.
The questionnaire asks three things: how you found your testers, what specific feedback they gave you, and what you changed because of it. Specific, concrete answers pass. Generic ones don't.
Before You Start
The 3 Core Questions
Here are the core questions you must prepare for, in the order Google asks them:
- 1
How did you gather your testers?
Google wants to know your recruitment methodology. If you used a professional service, explain that you hired an agency to source a diverse group of real users to stress-test the application across various hardware profiles and network conditions. If you used friends, explain how you reached out to them.
- 2
What specific feedback did you receive from testers?
This is the most critical question. "They liked it" is an unacceptable answer. You need concrete examples of UX issues, bugs, or feature requests testers encountered, for example:
- "Testers noted that the checkout button on smaller screens was obscured by the keyboard."
- "Several users reported a 2-second delay when loading the image gallery."
- "A tester requested a dark mode option because the white background was glaring at night."
- 3
What changes did you make based on that feedback?
You must prove you actually listened. Explain exactly how you altered your app's codebase during or after the 14-day testing period, for example:
- "We implemented a ScrollView wrapping the checkout screen to ensure the button is always accessible."
- "We implemented image caching and compressed the thumbnails, reducing gallery load times to 0.5s."
Weak vs. Strong Answers
The feedback question is the one Google's reviewers flag most often. Here's the exact difference between an answer that gets rejected and one that passes:
"They liked it."
"Testers noted that the checkout button on smaller screens was obscured by the keyboard."
The Secret to Passing
The human reviewers reading these questionnaires want to see a story of iteration. They want to see that you didn't just view the 14-day rule as an annoying hurdle, but as a genuine QA phase.
How GetAppTesters Helps
When you use GetAppTesters, we don't just provide the testers:
We actively generate detailed, actionable bug reports and UX feedback during the 14-day run, not just a pass/fail signal.
We hand you the exact data you need to copy and paste into the questionnaire - no guessing what to write.
Backed by our retest-or-refund guarantee if Google still rejects your app due to testing metrics.
Frequently Asked Questions
What happens if I give vague answers on the questionnaire?+
Vague or one-word answers, like "it works great," are one of the most common and entirely avoidable reasons an otherwise-successful 14-day test still gets rejected at the final step. Google's reviewers are specifically looking for concrete, specific detail.
Do I really need to push an app update during the 14 days?+
It's not mandatory, but it strengthens your answers significantly. A code change during the active testing window leaves a visible, timestamped record in Play Console proving you were genuinely iterating, not just waiting out the clock.
What's the single most important question to get right?+
The feedback question. "They liked it" is an unacceptable answer - reviewers want specific examples of real issues testers found, which is also the question most developers get wrong by being too generic.
Does GetAppTesters write my questionnaire answers for me?+
We generate the underlying data - detailed, actionable bug reports and UX feedback collected during your 14-day run - and hand it to you to use directly in your answers, backed by our retest-or-refund guarantee if Google still rejects your app due to testing metrics.
Need Real Testers?
Skip the hassle of recruiting and managing testers. Get real humans on real devices for 14 straight days. Guaranteed approval or your money back.
See Pricing & Plans