Production access date calculator
Enter the date each tester opted in to your closed test. You get the first date Google's rule is met: at least 12 testers opted in, each for the preceding 14 days. Free, no account, and nothing you type leaves your browser.
Enter your testers' opt-in dates
Google requires at least 12 testers who are still opted in.
How is the date worked out?
Google's wording for new personal developer accounts is:
“At least 12 testers must be opted in to your closed test when you apply for production access, and they must have been opted in continuously for the preceding 14 days.”
So every tester has their own 14 days, starting when they opt in. You are eligible once 12 of them have finished theirs, which is 14 days after the twelfth tester to join opted in. Testers who joined earlier do not bring the date forward, and a thirteenth tester only helps if someone else leaves.
A tester who opts out and comes back starts again: Google says the 14 days “must be consecutive to count.” Enter their rejoin date. Review of the application then “usually takes seven days or less, but can occasionally take longer,” which is where the calculator's 7-day estimate comes from.
The calculator works in calendar days. Play Console's own dashboard is the authority: the Apply for production button appears when its count agrees.
How do I keep the date from slipping?
- Recruit more than twelve. With exactly twelve, one tester leaving leaves you short until you replace them. A few extra testers are a buffer.
- Check the opted-in count every few days, not only on day fourteen. Play Console shows the current count, not its history. How to verify a tester opted in.
- Keep shipping fixes. A new build does not reset anyone's days. Does a new build reset the 14-day clock?
- Short of testers? Get testers through the free test-for-test exchange: you test other developers' apps, they test yours, and every opt-in is verified.
Common questions
- When can I apply for production access on Google Play?
- When at least 12 testers are opted in to your closed test and each has been opted in continuously for the preceding 14 days. If nobody leaves, that is 14 days after the twelfth tester opted in.
- Does the 14-day count start when I create the closed test?
- No. The rule counts testers, not the track, so each tester's 14 days start when they opt in. A test whose twelfth tester opted in on the 9th of the month is eligible on the 23rd.
- What if a tester opts out and then opts back in?
- Google says the 14 days must be consecutive to count, so that tester's days start again from when they rejoined. Enter their rejoin date in the calculator.
- How long does Google take to review the production access application?
- Google says review usually takes seven days or less, but can occasionally take longer. The calculator shows the date seven days after you become eligible as a guide, not a promise.
- Does uploading a new build reset the 14 days?
- No. The count is about who is opted in, not which build they are running, so you can keep shipping fixes during the test.
Read next
The 12 testers for 14 days requirement, explained
Google requires 12 testers opted in for 14 continuous days before production access. What that means exactly, who it applies to, and how to satisfy it.
How to verify a tester actually opted in, in Play Console
Asking a tester if they opted in is not verification. Here is where Play Console shows the real number, and how to reconcile it against your list.
How to answer Google Play's production access questions
The nine questions Google asks when you apply for production access after closed testing, what each one checks, and example answers to adapt.