Google Play 12 testers and 14 days evidence worksheet Fill in the brackets with your own records. Examples are planning illustrations, not completed test results or approved production-access answers. 1. Account and test record App/package: [app name and actual application ID] Account type and creation date: [personal/organization; actual date] Requirement shown in Play Console: [copy your app's requirement] Closed track: [track name] Build/version code: [actual identifiers] Opt-in link: [copy the actual shareable link from Play Console] Test owner and feedback channel: [owner and private channel] Observation timezone: [use one timezone for the records below] The published gate applies to personal accounts created after November 13, 2023: at least 12 testers must be opted in to the closed test when applying, with a continuous opt-in period covering the preceding 14 days. Adding email addresses or installing the app alone does not establish that enrollment period. Use the eligibility state shown in Play Console before applying. 2. Private enrollment ledger Record one row per participant using a minimal identifier: [tester ID] | [first/current opt-in timestamp] | [opt-out/rejoin timestamp] | [current continuous streak start] | [device/OS] | [build installed] | [mission status] | [evidence reference] | [still enrolled checked at] Do not publish tester email addresses or credentials in the evidence summary. Membership, installation, task completion and feedback are separate fields. A rejoining tester starts a new personal continuous period. A replacement needs their own qualifying period; remaining participants do not automatically reset. 3. Elapsed-time examples, not Console approval predictions - If 12 people join October 1 at 09:00 UTC and remain opted in, 14 elapsed days ends October 15 at 09:00 UTC. Check Console eligibility before applying. - If one of those 12 leaves and a replacement joins October 10 at 09:00 UTC, the replacement reaches 14 elapsed days on October 24 at 09:00 UTC, assuming continuous enrollment. The other 11 keep their own original streaks. - If 13 eligible people joined October 1 and one leaves, 12 uninterrupted original participants can still cover the original period. These examples assume all other conditions hold. Keep your recorded timestamps consistent, and do not treat a spreadsheet estimate as Google's eligibility check. 4. Proposed meaningful test plan - Start: verify opt-in, installation and the exact closed-track build. - Early sessions: fresh-account onboarding and the app's primary task. - Middle sessions: assign relevant device, permission, network or recovery cases. - Throughout: collect feedback, triage and publish fixes to the intended track. - Later sessions: retest affected cases and record remaining coverage gaps. - Before applying: check continuous enrollment, engagement evidence, changes, remaining limitations and the current Play Console eligibility state. There is no fixed daily app-open quota in the published minimum. Plan genuine feature use and feedback rather than manufactured activity or silent waiting. 5. Feedback and change ledger [date/time] | [tester ID] | [version code/device/OS] | [task attempted] | [expected behavior] | [actual observation] | [evidence reference] | [triage decision] | [fix build, if any] | [retest observation] Use real observations. No reported defect is a valid outcome; document completed work rather than inventing bugs, engagement or successful retests. 6. Production-access preparation prompts Recruitment and fit: We recruited through [actual channels] and selected testers because [user fit and device coverage]. Our records show [verified enrollment and participation]. Engagement: Testers attempted [actual features/tasks]. Their use [matched/differed from] expected production use in these ways: [specific evidence and limitations]. Feedback: We collected feedback through [actual channels]. The main observations were [real themes with examples]. Evidence references: [private record identifiers]. App and audience: The intended users are [specific audience]. The app helps them [actual value]. Use a reasoned estimate for any future-install-range question; do not present a projection as an observed result. Changes and readiness: We changed [actual behavior] in build [version code] because [observed issue]. Retesting showed [actual result, or state that retesting remains incomplete]. We judged readiness using [criteria and observed evidence]. Known limitations or unresolved issues: [truthful status and decision]. These are drafting prompts, not text to submit unchanged. Answer the actual questions in your own Console, using your own evidence. Meeting the gate allows an application; Google may request more testing and decides production access. Source guide: https://betaroast.com/blog/google-play-12-testers-14-days Official requirement: https://support.google.com/googleplay/android-developer/answer/14151465?hl=en