How to Use This Tool
Google's current rule applies to newly created personal developer accounts: before applying for production access, a closed test must have at least 12 testers opted in for the last 14 days continuously. Enter the date on which the twelfth continuously participating tester opted in, not the date you created the track or invited the first tester.
Why the twelfth tester controls the deadline
If eleven testers joined on Monday and the twelfth joined on Thursday, the qualifying group did not exist until Thursday. The earlier eleven days do not make the twelfth tester's clock older. Likewise, replacing a tester who left does not transfer the departed person's history to the replacement.
Inclusive versus elapsed-day planning
The checkbox shows the common “opt-in date is day one” calendar convention. Leaving it off adds 14 full elapsed days, which is the safer planning date when timestamps and Play Console processing are unknown. This page cannot see Google's server timestamps, so the Play Console dashboard remains authoritative.
Keep more than twelve
A buffer of two or three real testers reduces the risk that one person opts out and breaks the minimum. Testers should install, use and give feedback on the app; production access still requires an application and answers about testing quality. Reaching the date is eligibility to apply, not automatic approval.
Sources & assumptions
Tool Spec v2 · verified 2026-08-18. Platform rules and fees can change; the editable inputs remain authoritative for your account.
Official references
- Google Play Console Help — testing requirements for new personal accounts (checked 2026-08-18)
Model assumptions
- The entered start date is when the twelfth continuously opted-in tester joined the closed test.
- The calculated day is a planning date; Play Console status and server timestamps remain authoritative.
