If Google asked for more testing, the second round of your closed test needs a plan, not just another two weeks of the same thing. You decide whether to keep your current track or rebuild it, change whatever caused the first result, track every tester's opt-in date, and reapply only when at least 12 testers have been opted in continuously for the preceding 14 days. Google doesn't publish a waiting period between applications or a fixed length for the extra testing, so the timing is yours to plan.
If you've only just received the decision, start with what to do if production access is rejected. In short: don't tear down your track or remove testers, reread the email and your answers, and work out the cause. This article picks up from there.
Keep the same track or rebuild it?
Google's wording is "you may need to continue running your closed test," so keeping the existing closed track is the default. Testers who stay opted in keep building continuous days, nobody has to opt in again, and you can ship fixes to the same track.
Rebuilding has a cost: anyone cut off by a change starts their 14 days again. Does updating your app reset the 14 days? explains which changes are safe. Use this to decide:
| Your situation | Keep or rebuild |
|---|---|
| Testers are real and still opted in, just too few | Keep, and add testers |
| Testers are opted in but rarely used the app | Keep, and change how the test runs |
| Wrong countries selected on the track | Keep the track, fix the countries, re-check who can reach it |
| Tester list is mostly people who never took part | Rebuild the list, keeping anyone who did take part |
| Testers joined with the wrong Google accounts | Fix the accounts; affected testers start again |
Shipping a new build to the track is not a reason to rebuild. Version updates are normal during a closed test; see updating during a closed test.
Diagnosis: what to change in round 2
Round 2 only helps if it differs from round 1. Match each cause you found to a concrete change:
| Cause | What to change in round 2 |
|---|---|
| Exactly 12 testers, one left | Recruit a buffer above 12 and confirm each opt-in |
| Testers joined on different days | Record every opt-in date and plan around the latest one |
| Testers installed once and went quiet | Weekly tasks and a feedback channel |
| Little or no feedback to summarize | Ask specific questions and log answers as they arrive |
| Testers stuck at login or onboarding | Fix the flow, share working credentials, ship a new build |
| Crashes on some devices | Fix them, check the pre-launch report, ship a new build |
| Generic answers in the application | Keep notes during the test so answers have specifics |
Google names two official reasons for more testing: "fewer than 12 opted-in testers" and "insufficient tester engagement during the testing period." The other rows are practical causes we see, not Google rules. Common reasons production access is denied separates the official from the community-reported.
Rebuilding tester engagement
If engagement was the problem, the same testers doing the same thing for another two weeks won't change much. Treat round 2 as a restart of the relationship:
- Tell testers what happened. A short, honest message that you need another round and why.
- Give them tasks. A short list each week: sign in, complete the main flow, try one specific feature.
- Open a channel. Google suggests a messaging group for testers. It also gives you a record of feedback.
- Ship a visible fix early. Fix something testers reported and tell them it's done. People engage more when they see their reports matter.
- Collect feedback as you go. Testing feedback appears under Monitor and improve > Ratings and reviews > Testing feedback. Copy it into a log weekly.
Google doesn't say daily use is required, but keeping the app installed and using it regularly is strongly advised. More ideas are in keeping testers engaged for 14 days and showing real engagement.
Track opt-in dates so you know when you're ready
The requirement is checked on the day you apply: at least 12 testers opted in, each "opted in continuously for the preceding 14 days." Someone who opts out and back in starts a new streak. So in round 2, keep a simple sheet:
| Tester | Google account | Opted in on | Still opted in? | Day 14 reached on |
|---|---|---|---|---|
| 1 | [email protected] | Oct 3 | Yes | Oct 17 |
| 2 | ... | Oct 9 | Yes | Oct 23 |
Sort by "Day 14 reached on". Find the 12th tester in that order who is still opted in; their date is your earliest possible reapply date. Add a day of margin, and recalculate whenever anyone leaves or joins. Play Console shows how many testers have opted in (how to check), but the dates are easiest to keep yourself.
If you shipped fixes during round 2, many developers also prefer a full 14-day stretch after the main fix lands, so the evidence reflects the improved app. That's a judgment call, not a Google rule.
What to write differently in the new application
The form is the same three sections as before. What changes is what you can say. In round 1, many answers describe the app. In round 2, your strongest material is what you changed in the test itself:
- how you added testers and kept them opted in
- what you did to raise engagement, and what testers then used
- specific feedback themes from round 2, with the fixes and versions that addressed them
- why you now consider the app ready
Keep every answer true and consistent with what the test shows. Our production access guide has example answers for each section, so we won't repeat them here. Draft outside Play Console first, because leaving the page without clicking Next or Apply loses your answers.
Keep the test running while Google reviews. Review "usually takes seven days or less, but can occasionally take longer."
Key takeaways
- Keep the existing track unless the setup itself was the problem.
- Map each cause from round 1 to a specific change in round 2.
- Rebuild engagement with tasks, a channel and visible fixes.
- Track opt-in dates and reapply once 12 testers have 14 continuous days on the day you apply.
- Use the new application to describe what changed, honestly.
If tester numbers or engagement held you back, GoPlayTester can provide 12+ real testers on real devices for 14 continuous days in your second round. Google makes the final decision; you can order here.
