When do the 14 days of Google Play closed testing start?

The important milestone is continuous opt-in

For personal developer accounts covered by Google's testing requirement, at least 12 testers must remain opted in continuously for the preceding 14 days when you apply for production access. Sending an invitation does not establish that participation. Neither does paying a provider, uploading a build, or adding email addresses to a list.

Use the eligibility information in Play Console as the source of truth. A spreadsheet can help with coordination, but its start date is not an official counter. Check the actual account, testing track, accessible release, and participation status before promising a launch date.

Separate the four steps

1. Eligibility: the correct Google account is on the allowed list or in the permitted group.
2. Availability: the release and access changes are published, with a supported country and device.
3. Opt-in: the tester accepts participation through the closed-test link.
4. Testing: the person installs the app, uses relevant features, and provides feedback.

If someone only receives the email but cannot join, solve the access issue rather than counting that person as onboarded. Test the journey with an eligible account before inviting the full group.

What happens when somebody leaves?

A tester who opts out and later rejoins does not carry an earlier incomplete period forward as continuous participation. A replacement joining today does not inherit another person's previous days. Keep a modest participation buffer, communicate clearly, and do not ask participants to leave the track during the required window.

Installing an update is not the same as opting out. When shipping a fix, keep the closed track available, preserve eligible accounts, and confirm that testers receive the intended build. Check Console if anything about eligibility changes instead of guessing from install counts.

A practical release plan

Record when onboarding is confirmed, monitor access failures, and leave time to fix reported problems and complete Google's review. Fourteen days is a testing condition, not a promise that an app will be public exactly two weeks after purchase. If a managed test has not started because access is still under review, tell the coordinator immediately.

Check why an invitation does not open or prepare a build update.

Source: Google's continuous participation requirement.