ClosedTestYou are on day 9 of your closed test and the number of opted-in testers just went from 14 to 13. Or from 12 to 11. This happens to almost everyone, and it is fixable if you act early. This guide explains what Google actually counts, what to do today, and how to make the next test safer.
It is based on Google's own help page. Google can change its rules, so check that page before you decide anything.
What Google counts
Google requires a closed test with at least 12 testers who have been opted in continuously for at least 14 days. Two details matter for dropouts:
- Opting out early removes the tester from the count. Google says testers who opt in, test for fewer than 14 days, and then opt out do not count toward the requirement.
- Opting out and back in does not restart nicely. If a tester opts out and later opts back in, the 14 days must be consecutive to count.
Google also says at least 12 testers must be opted in when you apply, and must have been opted in continuously for the preceding 14 days. As we read that wording, a replacement tester who joins on day 9 has not been opted in for 14 days by day 14. That is why a late dropout can delay your application, not just reduce a number.
What to do today
1. Find out exactly who left and when. Note the date. This decides everything below.
2. Recruit a replacement now. Every day you wait is a day the replacement is not counting. Google suggests recruiting through personal and professional networks and communities where your users already are.
3. Do the arithmetic for your planned application date. Count how many testers will have been opted in continuously for the 14 days before that date. Use a simple table:
| Tester | Opted in on | Still opted in? | Reaches 14 days on |
|---|---|---|---|
| Tester A | Day 1 | Yes | Day 14 |
| Tester B | Day 1 | No (left day 9) | Does not count |
| Replacement for B | Day 10 | Yes | Day 23 |
In this example you have one fewer tester reaching day 14 on time. If you were at exactly 12, you are now at 11 until the replacement reaches 14 days. That means waiting, not applying early and hoping.
4. Decide: wait or apply. If you still have 12 testers who meet the 14 days by your application date, you can apply. If not, wait until you do. Applying with too few testers is one of the reasons Google names for asking you to keep testing.
You can check the numbers with our free 12 tester calculator.
How common is it? In ClosedTest's own records, about one in nine testers contributed on four days or fewer. See what 1,495 tester assignments show.
How to avoid it next time
- Recruit more than 12. A buffer is the cheapest protection. If you need 12 and recruit 16, up to four people can leave without delaying you.
- Tell testers the rule in plain words. Google itself advises you to inform testers that they must remain opted in continuously for at least 14 days. Say it when you invite them, and again on day 3, day 7 and day 12.
- Give a clear feedback channel. Google advises clear instructions and a feedback channel such as email or a messaging group. Testers who feel involved stay longer.
- Check the count regularly. Look at your closed test every few days, not only at the end.
- Replace early. A replacement recruited on day 3 costs you nothing. One recruited on day 12 costs you nine days.
Where ClosedTest fits
If you use ClosedTest, tester replacement is part of the service: when a tester becomes inactive or drops out, we replace them. The Safe Buffer and Maximum plans also include testers above Google's minimum of 12, which is the buffer this guide recommends. You can see the plans on the pricing section and the conditions on the refund policy.
Google makes the final decision on every application. What a service can give you is a bigger safety margin and a record of what happened each day.
ClosedTest is an independent service and is not affiliated with Google.