Day14

A free tracker for 12 testers over 14 days

One sheet for the Google Play closed test: who opted in, which phone, which of the 14 days you know they opened the app, the swaps and the reports. It works out the day to look for Apply for production. It holds no data of anyone and it does not find testers for you.

Download the Excel tracker Download the CSV

When can you apply?

Enter the day Console first showed 12 testers opted in. The calculator adds the 14 days. It runs in your browser and keeps nothing.

Before that day the Dashboard says N testers currently opted-in.

Enter the day Console first showed 12 testers opted in. The date to look for the button appears here.

Our runs On our first two apps the 12th opt-in came on 12 October 2026 and Console showed 14 days on 26 October: the date plus 14. Google Testers must have been opted in continuously for the 14 days before you apply. The date here is the earliest we would look, not a promise of the button.

What is in the workbook

Five sheets, all blank, nothing pre-filled
SheetWhat it holdsWhy it matters
Register30 rows for testers: alias, source, phone model, opt-in date, still opted in, and 14 day columns. At the top: testers opted in now, day 0, the day of the test today and the earliest day to apply.It is the 12 by 14 grid. The top numbers tell you each morning whether the count still holds.
Daily logOne line a day with the sentence Console shows on the Dashboard, word for word, and who joined or left.It is your evidence for questions 2 and 3 of the application.
Swap ledgerEach test-for-test swap: their app, whether they added your group, when each side installed and opened, and whether a screenshot was sent and received.A swap that no one can show was not a test. This keeps you from counting it twice.
FeedbackEvery report, what you did, the version it shipped in and the phone you checked it on.Questions 4 and 8 of the application are built from this sheet.
Read meHow to use it and what it does not do.The rule about marking days is there too.

What a register looks like when it goes wrong

Below is a sample, with made-up testers. Marigold means the tester opened the app that day. An empty cell means opted in with no sign of use. A hatched cell means not opted in.

Sample register: 12 made-up testers by 14 days
Tester1234567891011121314
Tester 1opened the appopened the appopened the appopened the appopened the appopened the appopened the appopened the appopened the appopened the appopened the appopened the appopened the appopened the app
Tester 2opened the appopened the appopened the appopted in, no sign of useopened the appopened the appopened the appopened the appopened the appopened the appopened the appopted in, no sign of useopened the appopened the app
Tester 3opened the appopened the appopened the appopened the appopened the appopened the appopened the appopened the appopened the appopened the appopened the appopened the appopened the appopened the app
Tester 4opened the appopted in, no sign of useopened the appopened the appopted in, no sign of useopened the appopened the appopened the appopted in, no sign of useopened the appopened the appopened the appopted in, no sign of useopened the app
Tester 5opened the appopened the appopened the appopened the appopened the appopened the appopted in, no sign of useopened the appopened the appopened the appopened the appopened the appopened the appopted in, no sign of use
Tester 6opened the appopened the appopened the appopened the appopted in, no sign of useopened the appopened the appopened the appopened the appopened the appopened the appopened the appopened the appopened the app
Tester 7opened the appopened the appopened the appopened the appopened the appnot opted innot opted innot opted inopened the appopened the appopened the appopened the appopened the appopened the app
Tester 8opened the appopened the appopened the appopted in, no sign of useopened the appopened the appopened the appopted in, no sign of useopened the appopened the appopened the appopted in, no sign of useopened the appopened the app
Tester 9opened the appopened the appopened the appopened the appopened the appopened the appopened the appopened the appopened the appopened the appopened the appopened the appopened the appopened the app
Tester 10opened the appopted in, no sign of useopened the appopened the appopened the appopened the appopened the appopted in, no sign of useopened the appopened the appopened the appopened the appopened the appopened the app
Tester 11opened the appopened the appopened the appopened the appopened the appopened the appopened the appopened the appnot opted innot opted innot opted innot opted innot opted innot opted in
Tester 12opened the appopened the appopened the appopened the appopted in, no sign of useopened the appopened the appopened the appopened the appopened the appopted in, no sign of useopened the appopened the appopened the app
opened the app opted in, no sign of use not opted in

Twelve names, but this sheet would not pass. Tester 11 left after day 8. Tester 7 was out on days 6 to 8 and rejoined on day 9, so their 14 days start again. That leaves 10 testers who held all 14 days, two short of the 12 you need. The fix is not on the sheet, it is before it: start with 15 to 20 testers and replace the ones who leave the same week.

How to fill it honestly

  • Our ruleWrite 1 only for a day you know. A tester’s screenshot, a message that says what they did, or your own analytics. If you do not know, leave the cell empty. Never fill a day you did not see.
  • Our runsConsole shows opt-ins, not use. We found no per-person usage in Console. Firebase Analytics, or the usage view of your build service, is where you see sessions.
  • GoogleTell testers to stay. Google says to tell them to stay opted in for at least 14 days. Write the day you told them in the daily log.
  • Our ruleUse aliases. The sheet has no column for e-mail addresses on purpose. Keep contacts somewhere else.
  • Our ruleCount a swap when both sides can show it. Your screenshot of their app open on your phone, theirs of yours.

Using it in Google Sheets

  1. Open Google Sheets and choose File, then Import, then Upload.
  2. Pick the Excel file. Choose Create new spreadsheet. The formulas and the yes/no lists come with it.
  3. If you use the CSV instead, you get the Register columns only, without the formulas. Use the calculator above for the date.

The formulas are plain COUNTIF, IF, MIN, MAX and TODAY. We checked them against the sample register below with a formula engine, and spreadsheet programs read them the same way. We have not opened the file in every program.

Questions

When can I apply for production access?

The Dashboard should show 14 days 14 calendar days after it first counted 12 testers opted in. On our first two apps the 12th opt-in came on 12 October 2026 and Console showed 14 days on 26 October. Console decides, so look for the Apply for production button on that date and again the next morning.

What if a tester leaves and comes back?

Google says a tester who leaves and rejoins must be opted in for 14 consecutive days to count, and a tester who opts in, tests for less than 14 days and leaves does not count. Keep 15 to 20 testers opted in so that 12 still hold.

Does Play Console show which testers opened the app?

We found only the opted-in counter in Console, no per-person use. Mark a day in the tracker only when you know it from a tester’s message or screenshot, or from your own analytics.

Next

Rule: App testing requirements for personal developer accounts, Play Console Help, read 27 October 2026. The tracker does not find, buy or simulate testers or their use. Day14 is an independent kit by Peak Apps Studio and is not affiliated with Google.