If you build Android apps for clients, one Google Play rule can drop two or three unplanned weeks into a project: some accounts can't publish until a closed test has had 12 testers opted in for 14 days in a row. Whether it hits you depends mostly on whose account the app ships from. That gets decided early, usually by someone who has never heard of the rule.
I run a closed testing service, so I mostly see the end of this story: the build is done, the client wants it live, and Play Console has no production button. Disclosure at the end. Every claim about Google's rules below links to Google's own help pages.
Which accounts the rule applies to
Google's testing requirements page says personal developer accounts created after 13 November 2023 must run a closed test with at least 12 testers opted in continuously for at least 14 days. Until then, Production and pre-registration stay locked.
The rule names personal accounts. Organization accounts aren't covered, and neither are personal accounts created before that date. For an agency, the account question is really a scheduling question:
| Who publishes the app | 12 testers for 14 days? | What to plan for |
|---|---|---|
| The client's organization account | No | A D-U-N-S number, if they don't have one yet |
| The client's personal account, created after 13 Nov 2023 | Yes | About four weeks before production access |
| The client's personal account, created before that | No | Normal app review |
| Your agency's own account | Depends on its type and age | A transfer later, and test groups don't move with it |
Google's advice on choosing an account type is to pick an organization account if it's for an organization or business. Some apps need one regardless: financial services, health apps, apps approved to use the VpnService class, and government apps.
The catch is the D-U-N-S number. Google won't create an organization account without one, and its account requirements page says getting one can take up to 30 days. That's longer than the closed test. If the client is a company with no D-U-N-S number, get them to apply in the kickoff week. It's free from Dun & Bradstreet, and Google warns about third parties that charge for it.
Publishing from your own account
Some agencies publish under their own account and hand the app over later. Google does allow transferring an app to another account, and users, ratings and reviews go with it. Test groups don't. Google says closed testing groups have to be recreated in the new account, and testers may need to opt in again. Until the transfer, your developer name is the one on the listing.
I'd rather the client owned the account and invited us. Through Users and permissions, the account owner can give your team admin or app-level access, with an expiry date if they like, and invited users don't pay the $25 registration fee. Also agree now who forwards what: when Google finishes reviewing a production access application, the email goes to the account owner, not to you.
Putting the 14 days into the project plan
The sequence, with the waits:
- Finish the app setup in Play Console. Closed testing only opens after that.
- Publish the first closed release. The opt-in link appears once the release is Published, and Google says it can take several hours to start working.
- Get 12 testers opted in and installed. Across 112 closed tests we ran up to 1 October 2026, the median time to the 12th confirmed install was 63.6 hours. One test in ten took 12 days or more (public numbers).
- 14 consecutive days, counted per tester. At least 12 must be opted in when you apply, each for the preceding 14 days.
- Production access review. Google says it usually takes seven days or less, occasionally longer.
About four weeks from a testable build to production access, if nothing goes wrong. The full timeline, backwards from launch day, is in an earlier post in this series.
So start the closed test on a beta, not the final build. You can keep shipping updates during the test: Google's rule is about testers staying opted in, and its own advice is to keep fixing issues and updating the app in closed testing before you release. That way the 14 days run alongside your last sprints and the client's acceptance testing instead of after them. Of everything here, this saves the most time.
Writing it into the contract
I'm not a lawyer, so read this as a list of things to cover.
- Make the closed test its own milestone, with dates that depend on Google. "Production access applied for" is a date you control. "Live on Google Play" isn't.
- If the client's account needs the closed test, don't tie the final payment to the app going live. Tie it to something you deliver, like the accepted build or the submitted application.
- Say who recruits testers, and who pays if they're paid.
- List the client's tasks: identity verification, the D-U-N-S number, inviting your team, forwarding Google's emails, and device verification on new personal accounts, which needs a physical Android phone and the Play Console app.
- Paid app? Google says closed testers have to buy it. Decide who covers that.
- Login? Google asks for working test credentials in Play Console so reviewers can get in. Client apps often sit behind a login, and this gets forgotten.
- What happens after a refusal: who pays for the extra weeks, and whether the launch date moves with them.
Who recruits the testers
Google suggests testers who represent the app's intended audience. For a client app that's usually the client's own people: staff, a few friendly customers, members if it's a club app. They also make the production form easier, because Google asks whether testers used the app the way real users will.
Your QA team on the internal track doesn't count. Google says users who opt in to internal testing aren't eligible for closed testing, even if they're on the closed testers list.
Whoever has Play Console access tends to become the bottleneck, because each tester's Gmail has to go on the testers list before they can join. In 85 closed tests on our platform in August and September, the ones that reached 12 installs within three days had the developer adding each Gmail in a median of 3.7 hours. In the ones that took more than a week, it was 24.7 hours. At an agency, the person with Console access is usually juggling three other projects. Name someone to check the list twice a day, or put a Google Group on the track so testers join on their own.
If you pay a service, ask how you can check real use against your own analytics. In October I read through public reviews of closed testing services, and the complaint that came up most was testers who install and never touch the main feature, with no logins in the developer's backend.
Whoever recruits, get more than 12. A tester who leaves on day 10 takes their days with them, and a replacement starts from zero.
What Google asks on the production access form
The application has three parts:
- About your closed test: how easy recruiting was, whether testers used all the features, whether their usage matched how you expect real users to behave, and a summary of their feedback and how you collected it.
- About your app or game: target audience, how the app gives users value, and an estimated install range for year one. Google says these answers aren't public and don't affect visibility.
- About your production readiness: what you changed because of the closed test, and how you decided the app was ready.
On a client project, parts 1 and 3 are yours. You shipped the fixes and you have the tickets and version numbers. Part 2 is the client's, since it's their market. Draft everything in a shared doc first; Google warns that answers are lost if you leave the page without clicking Next. I went through each question earlier in this series.
What a refusal costs in calendar time
Google says an app may need more closed testing, for two reasons: fewer than 12 opted-in testers, or not enough tester engagement. The refusal email asks for closed testing "for an additional 14 days with real testers" before you apply again.
When the refusal lands, up to a week has already gone on the review. A second round that actually fixes engagement (tasks, a check-in, a shipped fix) takes about two more weeks; here's how I'd run it. Then another review of up to a week. Call it three weeks. If you also fell below 12 testers, add recruiting time and a fresh 14 days for the new people.
Keep the closed test running while Google reviews, because testers who stay opted in keep counting if you need another round. And collect written notes from testers during the first 14 days, so a second application isn't written from memory.
Checklist
- Account type decided at kickoff, D-U-N-S number applied for if needed
- Client owns the account, your team invited through Users and permissions
- Identity and device verification done before the build is ready
- Closed test started on a beta, at least four weeks before any promised date
- Test credentials in Play Console if the app has a login
- 15 or more testers, none of them on the internal track
- One named person adding Gmails twice a day, or a Google Group
- Tasks every few days, written notes on day 7 and day 14, one fix shipped mid-test
- Production form drafted outside Play Console, client writes part 2
- Contract says what happens, and who pays, if Google asks for more testing
Disclosure
The service I run is TestFi, and it's one way to handle the recruiting. A closed test is $39.99 for 16 testers, or $49.99 for 20. We guarantee that 12 are still on your test on day 14, and if fewer are, we run the closed test again at no cost, once. If Google refuses production access and its email names tester engagement, forward it within 7 days after the end date on your campaign page; if fewer than 12 testers' day 7 and day 14 notes show real use of your app, we run it again at no cost, once. That's one free re-run per closed test at most, and it's a re-run, never money back. A re-run is another 14 days, so it doesn't replace the buffer in your plan. Details are on the closed test page.
For client work where you'd rather hand off more of it, there's also TestFi Launch at $499: a 20-tester closed test, five screen recordings in the first days of the test, a fix list, and production access answers drafted for a person to edit. If Google answers "more testing required" for any reason, it gets one free re-run. Google still makes the decision. It's on the launch page.
If your agency has run into a version of this I didn't cover, tell me in the comments.
Top comments (0)