When do the 14 days of closed testing start? Counting rules and what breaks the count

1. When the 14-day count starts

Google's documentation says you need at least 12 testers who have been opted in for the last 14 days continuously. What matters here is ‘how long testers have stayed opted in.’

1. Add your tester list (emails) to the closed testing track and save it.
2. Click [Send changes for review] in Publishing overview for it to actually take effect. This is the step people miss most often.
3. Each tester opts in through the opt-in link and installs the app.
4. The 14 days start from the moment your 12th tester opts in.

A day fills up in 24-hour increments, not by calendar date. Your app dashboard shows something like “12 testers currently opted in for N days,” and N goes up by 1 every 24 hours after you reached 12 testers. The day you reach 12 doesn't count as day 1, and the number doesn't tick over at midnight.

This isn't in the official documentation; we confirmed it in Play Console for apps we're running. An app that reached 12 testers at 11:40 a.m. on a Monday still showed “1 day” on Tuesday afternoon and Wednesday morning, and only showed “2 days” on Wednesday afternoon, after 48 hours had passed. So the requirement is met not on the 14th day, but a full 14 days after the moment you reached 12.

2. What has to stay in place

It comes down to two things: headcount and continuity.

• The number of opted-in testers must never drop below 12.
• The 14 days must run without interruption. Testing for a few days, pausing, and resuming doesn't add up.
• The app must stay installed. If a tester uninstalls it, they no longer stay opted in and drop out of the count.

Google's documentation says testers who opt out before 14 days have passed since they opted in won't count toward the requirement. If they leave and rejoin, that tester has to complete 14 days from the beginning.

3. What breaks the count

When the count actually breaks, it's usually one of these four.

• You changed the tester list midway. Removing an account drops that person immediately. Adding is fine; removing is risky.
• You paused the track or created a new one. Switching tracks means the opt-ins you've built up don't carry over.
• A tester uninstalled the app or opted out. This is the most common failure when you ask friends to help. That tester drops out of the count, and even if they come back they have to complete 14 days from the start. Tell them up front not to uninstall for 14 days.
• You had no margin. With exactly 12 testers, one dropout breaks the requirement. It's safer to keep extra testers.

4. Why the numbers don't show up

We hear a lot of “the app is installed, but Play Console shows nothing.” It's not in the official documentation, but in our experience it's common for the numbers to show up anywhere from one to three days late. Until they do, the time-series chart may not be drawn at all.

• Seeing 0 right after install can be normal. Give it a day or two.
• The install count on the app's store page is only shown in ranges (10+ and so on), so it's hard to tell the exact number.
• The fastest thing to update is the requirement message on your app dashboard. It changes once you meet the requirement.
• If nothing has changed in days, start by checking that you clicked [Send changes for review] after saving the tester list.

5. How to check every day

There are only two things to watch every day for 14 days.

1. Are at least 12 testers opted in? — check the requirement message and the time-series chart on your app dashboard.
2. Is the app still installed? — if you recruited testers yourself, ask them to check once or twice along the way.

DUIRE checks both of these directly on the devices. Every day at set times it checks that the app is installed and runs it, and keeps one screenshot per device per day. Because there's a record of what happened on which device and on which day, you know where things stand even when Play Console is slow to update.