The Production Access Questionnaire Answered
Google asks ten questions after your closed test. Here is what each one is looking for, and how to answer it with the testing record you already have.
The production access questionnaire is not a test you can cram for. It is a request for evidence, and the evidence is the testing record you built during the 14 days. The strongest answers are the ones that point to specific facts: tester count, device spread, opt-in dates, findings, and fixes.
Question one: how did you recruit testers? The answer should name the source — a managed pool, a beta community, a professional network — and explain why those testers were representative. “Friends and family” is not a strategy; it is a fallback.
Question two: how many testers opted in? State the number, the date the roster filled, and the date the window ended. A table of opt-in dates is worth more than a sentence, because it shows continuity rather than a single spike.
Question three: what devices did they use? List the Android versions and device types. A spread across current versions shows that the app was tested on the hardware your users actually own, not just on one reference device.
Question four: what feedback did you receive? Summarise the findings, ordered by severity. Crashes and data loss first, broken core flows second, layout and polish third. A reviewer who can see the priority order will spend seconds on the question, not minutes.
Question five: what did you change in response? Name the fixes, the builds they shipped in, and the dates. A report that ends with “we fixed the crash on the payment screen in build 1.2.3” is evidence. A report that ends with “we made improvements” is a claim.
If this matches your situation
12Tests assigns 12 real Android testers within hours, runs the full 14-day window, and delivers a written report you can paste into Google's production access questionnaire. One-time payment per app, no subscription.