Google refused your production access, and the email says your testers weren't engaged with the app, or that you didn't follow testing best practices. Your account is fine and nothing gets removed. Google wants a better closed test, and it doesn't publish a waiting period, so the real question is what to do with the next two weeks.
This is the plan I'd follow. I run TestFi, a closed testing service, so I read a lot of these emails. Google doesn't say how it scores engagement, so treat this as a plan built around what the production form asks, not a formula.
Day 0: work out which reason it is
There are two. Fewer than 12 opted-in testers is a count, and Play Console shows it to you. Insufficient engagement is a judgment about what your testers did. They need different fixes:
- Below 12: recruit back up. Each tester needs 14 days in a row, so in practice the clock starts again from the day you're back at 12.
- Engagement or "best practices": keep the testers you have if they'll actually use the app, and change what you ask of them.
Either way, don't delete or pause the closed track. That throws away everyone who's still opted in.
Day 1: give testers tasks, not "try the app"
Write down three to five things a real user would do in their first week. For a made-up recipe app: save three recipes, build a shopping list from two of them, switch units to metric, cook one thing in step-by-step mode. Send the list with one place to reply, an email address or a form.
"Try the app and let me know" gets you nothing you can put on the form.
Days 2 to 6: keep a log
One row per tester per thing they did: date, who, what, what broke. A spreadsheet is plenty. You'll copy from it on day 14, because the form asks for exactly this: whether testers used all the features, whether their usage looked like real users, and a summary of the feedback and how you collected it.
Day 7: ask for a note, then ship a fix
Ask each tester what they did and what annoyed them. Pick one thing they reported and fix it. Push the build to the closed track and tell testers what changed, so they open the new version. An update doesn't reset anyone's days, since Google counts opt-ins, not versions.
That one update is the most direct answer to "testing best practices". The production readiness part of the form asks what you changed because of the closed test, and "version 1.0.3 fixed the crash two testers hit on Android 13" is an answer.
Days 8 to 13: a second round
Give the testers who went quiet one more task, ideally one that touches the fix. If someone has gone for good, don't worry about it unless you'd drop below 12.
Day 14: write the answers from the log
A weak answer to the engagement question: "Testers used the app and gave positive feedback." It's probably true, and it tells the reviewer nothing.
A stronger one, for the made-up recipe app: "11 of 14 testers saved at least three recipes in the first week. Most used the shopping list; only two tried unit conversion, which is what we expect from new users. Four testers said the screen turned off in the middle of step-by-step mode. Version 1.0.3 on day 8 keeps the screen awake in that mode, and three of those four cooked with it again after the update."
That one has counts, a problem, a version number and a date, and you can only write it if you logged things as they happened. Then apply. Google says the review usually takes 7 days or less.
If you need new testers
If your testers were swap partners who stopped opening the app, recruit people who will use it, and get more than 12 so a single dropout doesn't restart the clock. Across 112 closed tests we ran up to October 2026, reaching 12 confirmed installs took a median of 63.6 hours, so add about three days to the plan.
That part is what TestFi sells: 16 testers on your track for $39.99, a note from each one on day 7 and day 14, and draft answers for the production form written from those notes. If fewer than 12 are still opted in on day 14, the test runs again free, and the same goes if Google refuses you over engagement and fewer than 12 testers wrote notes that show real use. Nobody controls Google's decision, us included.
Still choosing a track? The previous post in this series covers internal vs closed vs open testing. The longer version of this one, with an FAQ, is on our blog.
Top comments (0)