Closed Testing 14-Day Tracker
Track Google Play’s 14-day closed testing requirement: tester count, continuous opt-in days, the exact date you become eligible for production access, and the checklist most developers fail on.
Free · No signup · Runs entirely in your browser
Your test
Saved in this browser only. Nothing is sent to a server.
Production access checklist
The items reviewers actually look at. Ticks are saved in this browser.
0 of 9 complete
How the requirement actually works
Personal developer accounts created after 13 November 2023 must run a closed test before applying for production access. The condition is 12 testers opted in, continuously, for 14 days. All three parts matter, and the one that trips people up is “continuously”.
Counting from the wrong day
The clock starts when your twelfth tester has accepted the invitation and opted in— not when you created the track, sent invites, or uploaded the build. Developers who count from the upload date routinely find the eligibility check still failing two weeks later.
Why you should recruit more than the minimum
If your opted-in count falls below the threshold at any point, the window is compromised. Testers uninstall, lose interest, or switch accounts. Running a buffer above the minimum means one or two drop-offs do not cost you the whole fortnight. Never remove people from the tester list mid-test — adding is safe, removing is not.
The application itself
Production access is a questionnaire: how you recruited testers, what feedback you got, and what you changed because of it. Specific answers pass; generic ones get sent back. This is why the checklist below asks you to keep a change log from day one.
Google periodically adjusts the tester count and duration. Confirm the current numbers on the Play Console Help page for production access before planning a launch date.
Frequently asked questions
- When does the 14-day clock actually start?
- On the day your twelfth tester has opted in — not when you created the track or sent invitations. Invited-but-not-opted-in testers do not count towards the requirement.
- What happens if a tester opts out on day 10?
- If your opted-in count drops below the threshold, the requirement is no longer continuously satisfied and your progress is compromised. This is why recruiting more than the minimum matters.
- Does this requirement apply to everyone?
- It applies to personal developer accounts created after 13 November 2023. Organisation accounts follow a different path. Google adjusts these rules periodically, so confirm the current numbers in Play Console Help before planning a launch.
- Is my tracker data stored on your server?
- No. It is saved in your browser’s local storage on this device only. Clearing site data will clear it.
- What gets production access applications rejected?
- Vague answers about how you recruited testers and what feedback you got, plus tests that look synthetic — a dozen new accounts with no session time and simultaneous opt-ins. Keep a real change log.