Quick Answer
Write production access questionnaire answers like a mini test report: what testers did, what feedback you collected, and what you fixed. For new personal developer accounts, Google requires at least 12 testers opted in for at least the last 14 days continuously before you can apply. PrimeTestLab provides 12 pre-qualified testers for $19.99, typically starting within 4 hours (guaranteed within 6), with testing running the full 14 days.
After your closed test meets Google's requirements, you'll see "Apply for production" in your Play Console Dashboard. But between clicking that button and getting approved sits a questionnaire that trips up thousands of developers every month. This guide shows you exactly how to answer each question with evidence Google actually wants to see.
What Is the Production Access Questionnaire (and Why Google Cares)
When your closed test meets the criteria, Google surfaces an "Apply for production access" option on your Play Console Dashboard. Google then asks questions in three sections:
Google says the purpose of the closed test section is to confirm apps are satisfactorily tested before publication, helping protect users and reduce low-quality apps, malware, and fraud.
What Google says
The review "usually takes 7 days or less", sometimes longer. Your app may be asked to continue testing if you don't have 12 eligible testers or if testers weren't engaged. See Google Play Console Help for the full closed testing requirements.
Note on answer length: Some developers report the production access form may enforce a short character limit (around 300 characters per answer). If you see a limit, remove filler words and keep only specifics: tester count + duration + core flows + feedback themes + changes.
What Evidence Do You Need Before Writing Answers?
Do this once, and the form becomes easy. Gather four things before you open the questionnaire.
- At least 12 opted-in testers
- Opted in for the last 14 days continuously (no opt-out breaks — note: uninstalling the app does NOT opt a tester out, only visiting the test link and clicking "Leave" does)
Google suggests you describe engagement such as whether testers used all features and whether usage matches expected real users. Write down:
- Which core flows they used (onboarding, search, checkout, upload, etc.)
- Where they got stuck
- What you improved
Google points developers to Play Console's Testing feedback page and recommends keeping a record. Also consider grabbing:
- Pre-launch report issues you fixed (if you used it)
- A short changelog of the fixes you released during testing
Google warns that if you discard or quit without clicking Next and finishing, your changes won't be saved. Draft your answers in a document first, then paste them in.
How Do You Answer the Closed Test Questions? (Part 1)
This is the section where most developers lose marks. Google wants evidence, not adjectives. Below are the questions you'll see, with strong and weak answer templates for each.
Note: Google occasionally updates the questionnaire. You may see slightly different questions or formats (some are dropdowns, not free text). These templates cover the most commonly reported questions as of early 2026.
Ready-to-copy
Each question below includes a ready-to-copy answer you can use directly. For best results, customize the audience and app value questions to match your specific app.
How to Answer: "How did you recruit users for your closed test?"
Google asks how you found your testers. This is a free-text answer where you describe your recruitment approach. The key is to show diversity in your tester sources -Google wants to see that real people from different backgrounds tested your app, not just one group of friends. Mention specific channels: personal network, social media groups, developer forums, or a testing service.
I recruited testers through friends, family, colleagues, and online communities. I also reached out via social media and forums related to my app category. This diverse approach helped gather feedback from different types of users who might use my app.
"I found testers online."
Too short. No channels mentioned, no diversity shown.
How to Answer: "How easy was it to recruit testers?"
Google gives you multiple-choice options. Pick the one that fits your experience. We recommend selecting "Easy" for most cases.
How to Answer: "Describe the engagement you received from testers"
Google's examples include feature usage and whether usage matched expected production users. Your answer needs to show real interaction, not just "they used it." Think of this as a mini engagement report: which core flows did testers complete? Did they use the app daily or weekly? Did their usage pattern match what a real production user would do? The more concrete you are, the stronger your application looks. Always include tester count, duration, and at least 2-3 named features.
| Element | What to Include |
|---|---|
| Tester count + duration | e.g., "12 testers, 14 consecutive days" |
| Core flows used | Name 2-4 specific features (sign-in, onboarding, core feature, settings) |
| Usage pattern | Daily usage, repeating key actions, matched expected real users |
| One concrete learning | Something specific you discovered from engagement data |
Testers were highly engaged throughout testing, actively exploring all features and providing valuable feedback on functionality and UX. Many used the app daily and shared thoughts on improvements. Their input helped me identify areas needing attention and make meaningful updates.
"Testers were active and used the app."
No features mentioned, no duration, no specifics.
How to Answer: "Provide a summary of the feedback you received"
Google asks you to summarize feedback and explain how you collected it. This is where many developers fail because they say "feedback was positive" without explaining how they gathered it or what specific themes emerged. Cover three things: your collection channels (Play Console feedback page, in-app forms, direct messaging), the top 2-3 feedback themes that came up, and the concrete actions you took in response. Even if feedback was mostly positive, mention at least one minor improvement you made.
| What to Cover | Details |
|---|---|
| Collection channels | Play Console Testing feedback, in-app form, direct chats, email |
| Top feedback themes | Positive UX feedback, minor improvement suggestions, bug reports |
| Actions taken | Specific fixes and improvements you made in response |
Testers gave positive feedback on functionality and UX, appreciating the clean interface and smooth performance. Some suggested minor improvements which I implemented in updates. Feedback came through direct chats, in-app options, and observing usage. Testers recommended the app for production.
"Feedback was good."
No method, no themes, no actions taken.
Stuck on recruiting testers who stay opted in for 14 days?
PrimeTestLab provides 12 pre-qualified testers starting at $19.99. Testing begins within 4 hours (guaranteed within 6).
How Do You Answer the App and Game Questions? (Part 2)
Google says this section helps them understand your app. Your answers are not shown on Google Play and won't affect access to Play Console features.
How to Answer: "Who is the intended audience for your app?"
Google asks you to be as specific as possible. Don't say "everyone" or "all ages." Instead, cover three things: who they are (age range, role, interest), what problem they face, and when they use the app. If your app caters to different user types, mention both -for example, "casual users who check in daily and power users who rely on it for work." The sample below uses a task management app as an example; replace the details with your actual app's audience.
My app is designed for individuals aged 18 to 45 who are looking for an easy and efficient way to manage their daily tasks and stay organized. The app caters to both casual users and those who need it for regular use in their daily activities.
Customize tip: Replace the audience description with your actual target users. For example, "fitness enthusiasts who want to track their workouts" or "small business owners managing invoices."
"Everyone."
Too vague. Google wants specifics about who your users actually are.
How to Answer: "Describe how your app provides value to users"
Google asks you to describe the value the app provides. Don't just list features -explain the outcome users get. Start with the core benefit ("saves time," "keeps users organized," "makes workouts trackable"), then support it with 2-3 key features that deliver that benefit. For games, focus on what makes your game stand out: unique mechanics, art style, or player experience. Google says this answer is not shown on Google Play and won't affect access to features, so be honest and specific rather than marketing-speak.
My app helps users save time with an intuitive, streamlined experience. Key features include a clean dashboard, smart notifications, and seamless navigation that keeps users productive. The interface is designed so anyone can get started quickly without a learning curve.
Customize tip: Describe your app's unique value and 2-3 main features. For games, focus on what makes your game stand out (unique mechanics, art style, player experience).
"My app is useful and has good features."
No specific features named, no user benefit explained.
How to Answer: "How many installs do you expect in the first year?"
Google says it's okay if this is a rough estimate and the ranges are wide. We recommend "10k - 100k" for most apps.
How Do You Answer the Production Readiness Questions? (Part 3)
This is where Google checks whether you actually learned something from the closed test and acted on it.
How to Answer: "What changes did you make based on your closed test?"
Google asks what changes you made based on closed test learnings. This is the question that separates approvals from rejections. Be specific: don't say "improved the app." Instead, list concrete categories of changes -UI improvements (simplified navigation, fixed layout issues), bug fixes (resolved crashes, fixed login errors), performance enhancements (reduced load times, optimized memory usage), and usability improvements (clearer onboarding, better error messages). Even small changes count. If you genuinely made no changes, explain why the app was already stable -but this is a red flag, since Google expects the test to reveal something worth improving.
| Category | Include In Your Answer |
|---|---|
| Stability fixes | Bugs you fixed, crashes resolved |
| UX fixes | Navigation improvements, better layout, clearer labels |
| Performance | Responsiveness, load times, overall performance |
| Usability | Addressed usability issues raised by testers |
Based on tester feedback, I improved the UI for more intuitive navigation, fixed reported bugs, and enhanced overall performance. I also addressed usability issues and made the app more responsive. Testers confirmed these changes significantly improved their experience.
"We improved the app."
No specifics. Google will flag this as vague.
How to Answer: "How did you decide your app is ready for production?"
Google wants to know your decision criteria -not "I felt it was ready," but what specific evidence led you to that conclusion. Show that you made a deliberate, evidence-based decision by referencing: completed 14-day testing period, all major bugs resolved, positive tester feedback confirming stability, and updates released during testing. This question is your closing argument -tie together everything from the previous answers into a confident, evidence-backed summary.
After completing 14-day testing with multiple testers, I gathered their feedback. Testers found the app stable, easy to use, and valuable. I addressed major issues and released updates during testing. The positive response confirmed my app is ready for a wider audience.
"I felt the app was ready."
No evidence, no criteria. Google wants data-backed reasoning, not feelings.
How to Answer: "What did you do differently this time?" (Re-applicants)
Note: This question only appears if you have applied for production before and were asked to continue testing.
This time I focused on gathering and implementing feedback throughout testing. I actively engaged with testers to understand their needs and made continuous improvements. I also ensured the app met all Google's requirements before applying for production.
The 7 Mistakes That Trigger "More Testing Required"
Google says you may be required to continue testing if you don't have 12 eligible testers or if testers weren't engaged. But your questionnaire answers also play a role. Avoid these:
"Good engagement" tells Google nothing. Name specific flows and actions.
Google reviews thousands of these. Generic templates are obvious and may trigger deeper review.
If you say you got feedback, explain how (in-app form, Play Console, email).
Be consistent. If testing found nothing, don't claim you fixed things (and vice versa).
Even small changes count. Always list concrete improvements you made.
Google specifically requires continuous opt-in. Mention it to show you understand the requirement.
Don't just say testers "engaged." Describe sessions, flows, and repeat usage with specifics.
What Should You Do If Google Rejects Your Production Access?
If Google responds with "We need more time to review your app" or asks you to "continue testing," don't panic and don't resubmit the exact same answers. Here's the step-by-step recovery process:
Google usually tells you why in the rejection email or Play Console notification. Common reasons: not enough testers (need 12 minimum), testers weren't opted in for the full 14 days continuously, or testers weren't sufficiently engaged with the app.
If you had fewer than 12 testers or they dropped out mid-test, adding more testers and running the full 14 days again is required. Simply rewriting answers without fixing the underlying issue won't work -Google can see your tester data in Play Console.
Don't resubmit the same answers. Use the second testing round to gather new evidence: additional feedback themes, more specific engagement data, and new changes you made. Reference Q10 above for how to explain what you did differently this time.
Google requires the most recent 14 consecutive days to have eligible testers. Rushing a reapplication before the new testing cycle completes will just result in another rejection. Be patient and let the full 14 days pass with active testers.
Pro tip
Most rejected developers get approved on their second attempt when they fix the tester count issue and provide specific answers. If you keep getting rejected after multiple attempts, the problem is almost always with your testers (not enough, not engaged, or not opted in continuously) rather than your answers alone. See our rejection troubleshooting guide for detailed help.
How Can PrimeTestLab Help You Pass the Questionnaire?
If your biggest blocker is getting reliable testers who stay opted in for 14 consecutive days, PrimeTestLab is designed for exactly this requirement. We start testing within 4 hours (guaranteed within 6), use real human testers on real devices, and have helped 7,400+ apps through closed testing and production approval.
Our Starter plan provides 12 testers for $19.99, the Professional plan provides 20 testers for $29.99, and the Enterprise plan provides 25 testers for $27.99 — all with the full 14-day guarantee.
Only need the minimum requirement
Most coverage for the same 14-day period
Extra engagement for stronger questionnaire answers
Why this helps with the questionnaire
PrimeTestLab includes support and guidance throughout the process, including a production questionnaire guide and progress reporting, so you're not guessing what to write. You'll have real engagement data and tester feedback to reference in your answers.
See all plans at /pricing-plan
Frequently Asked Questions
What is the production access questionnaire in Google Play Console?
It's the application form you submit after closed testing, where Google asks about your test, your app or game, and your production readiness. You'll see it when you click "Apply for production access" in your Play Console Dashboard after meeting the closed testing criteria.
How to answer production access questions Google Play?
Use specific, truthful evidence: how testers used core features, what feedback you collected (and how), and what changes you made based on that feedback. Never copy-paste generic templates. Google wants to see real testing evidence specific to your app.
Production access denied Google Play: why?
Google says you may be required to continue testing if you didn't have at least 12 opted-in testers for the last 14 days continuously (for new personal accounts) or if testers weren't engaged. Weak or vague questionnaire answers can also trigger "more testing required." See our detailed rejection troubleshooting guide for help.
How long does production access review take?
Google says it usually takes 7 days or less, but it may take longer. Providing strong, specific answers with real testing evidence can help avoid delays from additional review.
What should I do if Google rejects my production access application?
Do not resubmit the same answers. Read Google's rejection reason carefully, fix the specific issue (usually vague answers or insufficient testers), rewrite your questionnaire answers with more specific evidence, and wait at least 7 days of additional testing before reapplying. See our detailed recovery steps above.
Can I use a template for production access questionnaire answers?
You can use a template as a starting framework, but you must customize every answer with your actual app name, real tester feedback, and specific changes you made. Google flags identical copy-pasted answers across developer accounts, so always personalize with your real testing data.
Bottom Line
Summary
Google approves production access fastest when your questionnaire answers match reality: who tested, what they did, what they reported, and what you changed. If you're stuck finding users who will stay opted in for 14 consecutive days, PrimeTestLab provides 12 pre-qualified testers starting at just $19.99. With testing guaranteed to start within 4 hours and a 99.9% success rate across 7,400+ apps, we provide the real engagement data you need to apply with confidence. See pricing plans →