Private drafting tool
Prepare your Google Play production-access questionnaire.
Draft answers for the same 10 production-access questions shown in Play Console, then copy them in.
0 of 10 answers have at least 40 characters
Your draft stays in this browser tab and is not submitted to TestMyApps. Copy it before leaving the page.
How to turn your closed-test record into honest answers
Start with evidence from the run, not an answer copied from another developer. Open your tester tracker, feedback notes, release history, crash dashboard and Play Console status before drafting. Record how you recruited testers, when the qualifying count was reached, which devices or Android versions were covered, what testers actually tried and how you kept the group active. Exact dates and examples are more useful than claims such as “everything was tested.”
Compare your notes with an example run with drafted answers.
For the recruitment section, explain the real channel you used—your audience, a community, colleagues or a testing service—and how testers joined the official closed track. State how many people opted in and what process you used to check continuity. Do not describe internal testing, APK installs or invitations that were never accepted as part of the qualifying closed test.
Connect feedback to releases and retests
Strong answers show a cause-and-effect chain: a tester reported a problem, the team investigated it, a build changed and the affected flow was checked again. Group findings into concrete themes such as onboarding, sign-in, permissions, navigation, crashes or unclear copy. Mention build numbers or dates when you have them. If no severe issue was found, describe the scenarios that were exercised and the signals you reviewed rather than inventing a bug.
The readiness section should reconcile tester feedback with current production behavior. Confirm that policy links load, Data safety answers match the app, restricted features have review instructions and important crashes or blockers are resolved. A closed test can satisfy the time requirement without proving that every store-policy or quality issue is fixed, so keep those claims separate.
Review the draft before submitting in Play Console
Read every answer against the underlying record. Remove promises you cannot verify, generic marketing copy and numbers that do not match the live tester count. Ask whether a reviewer can understand who tested, what they did, what you learned and why the current build is safer to release. Keep screenshots, feedback excerpts and release notes available in case Google asks for more testing or clarification.
This worksheet stores the draft in your browser and does not submit anything to Google. Copy the final text into Play Console only after checking it against the current application questions, because Google can change wording or request additional details. Completing the worksheet does not guarantee production access; Google reviews the app, testing history and answers independently.
If production access is denied, use the decision to identify what to change before resubmitting.
Use facts from your run, not a copied script.
Google reviews the app and its testing process. Reconcile this draft with your tester count, feedback log, released fixes, and current store declarations. Credible evidence starts with understanding why real testers beat bots.