14-Day Closed Testing Compliance Checklist
Last updated: June 2026 · 7 min read
Google's 14-day Closed Testing requirement is strict. Failing any one condition — tester engagement, device verification, or the 14-day minimum — means a rejection and another two-week wait. This checklist covers everything you need to do before, during, and after your Closed Testing period to pass on the first attempt. For a broader overview of the policy, read our guide to the Closed Testing requirement.
Important: Google's review process is automated in part but includes manual review. Meeting the minimum requirements does not guarantee approval. Your app must be functional, stable, and provide genuine value to testers.
Before you start
Recruiting testers (Day 0)
During testing (Days 1-14)
After 14 days
Top reasons Google rejects production access
Insufficient tester engagement
Testers joined but did not open the app regularly. Google tracks session data and flags accounts where testers show minimal activity.
Duplicate or fake accounts detected
Multiple testers from the same device fingerprint or IP range. Google has sophisticated detection for shared devices and emulator usage.
14-day period not continuous
One or more testers dropped out, causing the active count to fall below 12. The clock does not pause — the entire period must be unbroken.
App is non-functional or crashes
If testers report crashes or the app is unusable, Google may determine it does not meet minimum quality standards.
Pro tips for passing on the first attempt
- 1Over-recruit. Get 14-15 testers. Dropouts are the #1 cause of failure, and a buffer costs nothing.
- 2Send daily reminders. A simple "thanks for testing today" message keeps testers engaged. The more they open the app, the stronger your case.
- 3Use device diversity. Testers on different Android versions, screen sizes, and manufacturers look more genuine to Google's review system.
- 4Fix bugs during testing. Upload updates throughout the 14 days. It shows Google you are actively improving the app based on tester feedback.
- 5Document everything. Keep a log of tester activity, feedback received, and bugs fixed. If Google asks questions, you will have answers.
How Google verifies your 14-day compliance
When you apply for production access, Google reviews your testing period data to verify compliance with the 14-day requirement. Here is what they check and how to ensure each check passes:
Duration verification
Google confirms that at least 14 consecutive calendar days elapsed between the first tester opt-in and your production access application. The 14 days are counted as calendar days, not business days. Weekends and holidays count. If you apply on day 13 (even if testers were active for 13 full days), your application will be rejected for not meeting the minimum duration.
Tester count continuity
Google checks that your tester count stayed at or above 12 throughout the 14-day period. A single day with 11 testers can be grounds for rejection. This is why buffer testers are so important — one person uninstalling on day 9 should not threaten your entire testing period.
Engagement consistency
Google looks at whether tester engagement was consistent across the 14 days or concentrated in the first few days. A pattern where all testers were highly active on days 1-3 and then silent from day 4 onward suggests that testing was not meaningful. Engagement should be reasonably distributed across the full period.
Tester authenticity signals
Google runs automated checks for signs of fake testers throughout the testing period: IP diversity, device fingerprint diversity, account age and activity history. These checks run continuously, not just at the end. If suspicious patterns are detected mid-testing, your application may be flagged before you even apply.
Compliance checklist: Day-by-day verification
Use this day-by-day checklist during your testing period to stay compliant. Check each item daily:
| Check | Frequency | What to verify |
|---|---|---|
| Tester count | Daily | 12+ testers still opted in; no uninstalls |
| Tester activity | Every 2-3 days | Each tester has opened the app recently |
| Crash reports | Daily | No new crashes; crash rate below 1% |
| Store listing | Weekly | All fields remain complete and accurate |
| Policy status | Weekly | No new policy warnings in Play Console |
| Feedback log | As received | All tester feedback is documented |
| Update deployed | At least once | At least one update pushed during testing |
Frequently asked questions
What if I accidentally apply before 14 full days have passed?
Can I take a break during the 14 days and resume later?
Why did Google reduce the requirement from 20 to 12 testers?
TesterBee handles compliance for you
We recruit, monitor, and manage your 12 testers for the full 14 days. If Google rejects your app due to tester engagement, we refund your payment — no questions asked.
Start your 14-day testCommon questions about the 14-day testing period
Does the 14-day clock start when I upload my AAB or when testers opt in?
When the 12th tester opts in. Uploading your AAB and adding emails to the tester list does nothing to start the clock. Each tester must open the opt-in link on their Android device and tap "Become a tester." The 14-day countdown begins only after 12 people complete this step. Play Console may take 24-48 hours to reflect the timer start in your dashboard.
What counts as "active" — does installing the app once count?
No. Google tracks daily app opens, session duration, and feature usage. A tester who installs your app, opens it once, and never touches it again will likely be flagged as inactive. Aim for at least one meaningful session per day per tester. Send reminder notifications and keep testers engaged with updates and feedback requests.
Can I push app updates during the 14 days?
Yes — and you should. Google reviewers look for evidence that you responded to tester feedback. Pushing at least one update during the 14-day period that addresses bugs or adds features based on tester input is a strong signal that real testing happened. Just ensure new builds don't introduce crashes.
What if one of my testers drops out on day 10?
If your count drops below 12, the clock pauses. If it stays below 12 for more than 48 hours, the clock may reset entirely — forcing you to restart a new 14-day cycle. This is why you should always recruit 14-15 testers, not exactly 12. A 2-3 person buffer protects against individual dropouts.
My 14 days are done — why is the "Apply for production" button still greyed out?
The Play Console dashboard has a 24-72 hour delay. If it has been more than 3 days since your 14th day and the button is still grey, check: do you have at least 12 testers still opted in? Did any testers drop out near the end? Contact Google Play support via the Help menu in Play Console if the issue persists.
Is testing on emulators or virtual devices acceptable during the 14 days?
No. Google can detect emulators, and emulator installs do not count toward your 12 testers — even if they are opted in. Every tester must use a real physical Android device. Attempting to use emulators to meet the requirement can result in your production access being denied and may flag your account.