Closed Testing Tracker Template for Google Play

This closed testing tracker template is a simple spreadsheet for following your Google Play closed test one tester at a time: who joined, which Google account they used, when they opted in, how many days they have been in, and what feedback they sent. It is our own format, not a Google tool. You can download it as a CSV file and open it in Google Sheets, Excel or any spreadsheet app.

It exists because of the rule explained in our guide to 12 testers for 14 days: for new personal developer accounts, Google requires at least 12 testers opted in continuously for the preceding 14 days when you apply for production access.

Download the tracker (CSV)

What the tracker looks like

The file has one row per tester and seven columns. The two rows below are examples with made-up names; replace them with your own testers.

Tester name	Google account email	Opt-in date	Day count	14 days complete on	Still opted in (Y/N)	Feedback notes
Tester 1	tester1@example.com	2026-10-01	=TODAY()-C2	=C2+14	Y	Example note: login screen text cut off on a small phone
Tester 2	tester2@example.com	2026-10-02	=TODAY()-C3	=C3+14	Y	Example note: no issues yet

In the downloaded file, the two formula columns are wrapped in a check, so they stay empty until you enter an opt-in date.

What each column is for

• Tester name: whatever helps you recognise the person.
• Google account email: the account the tester joined with. Users need a Google Account or a Google Workspace account to join a test, so this is the identity that matters, not a different work or personal email.
• Opt-in date: the date the tester confirmed they opted in through your opt-in link. Adding an email to your tester list is not the same as opting in, so fill this in only once they confirm.
• Day count: the number of full days since the opt-in date, calculated with =TODAY()-C2.
• 14 days complete on: the opt-in date plus 14 days, calculated with =C2+14. This is our conservative way of counting; the Google pages we checked do not publish an exact cut-off time.
• Still opted in (Y/N): update this whenever a tester tells you they left, changed account or reinstalled.
• Feedback notes: a short summary of what each tester reported, with a date.

How to use it during your test

1. Before the test: add a row for every person you invite, with their name and Google account email. Leave the opt-in date empty.
2. As testers join: ask each one to confirm once they have opted in, then enter the date. Until a tester opts in, they do not count.
3. Every few days: check the Still opted in column and sort by Day count. Anyone who left and rejoins starts again: if a tester opts out and opts back in later, the 14 days must be consecutive to count.
4. Before you apply: count the rows with Y in Still opted in and a Day count of at least 14. You need at least 12.

When a tester's row changes from Y to N, enter a new opt-in date if they rejoin rather than editing the old one, so the history stays clear. To invite testers in the first place, our tester invitation template has an email and a short chat message you can copy.

Use the notes column for your application

The feedback column is not just housekeeping. When you apply for production access, Google asks you to summarize the feedback you received from testers and describe how you collected it, and to describe changes you made based on what you learned from the closed test. A dated note per tester makes both answers easier to write, because the record already exists.

A practical habit is to add a note whenever a tester reports something, even if it is small, and to mark the note when you fix the issue. By day 14 you then have a list of what was found and what changed.

Pitfalls the tracker helps you catch

Each of these comes from Google's documentation and is covered in our guides:

• Counting invites as testers. A row with an email but no opt-in date is an invite, not an opted-in tester.
• Testers in your internal test. A user who opts in to your internal test is not eligible for your closed test until they opt out of the internal test and opt in to the closed test. Add a note if someone is in both.
• Testers who leave early. Testers who opt in, test for fewer than 14 days and then opt out do not count toward the requirement.
• Exactly 12 testers. If you have exactly 12 opted-in testers and one drops out, you are below the minimum. Tracking more than 12 rows gives you a margin.

Frequently asked questions