Free tool · handover tracker
Hand over a closed test the app owner can act on.
Record who is responsible, which checks are done, what testers found and what changed. Tick off each item, add a reference or a next step, and download the handover when you finish.
Updated · 16 checks · saved in your browser, downloadable
Play Console counts testers. This records what they did.
Every closed test leaves two records. Play Console shows whether your account meets the testing requirement. Your own record explains which build testers used, what they tried, what broke and who fixed it. This tracker helps with the second one. It cannot read your Play Console or confirm who took part.
Begin with the exact build and a dry run of what a tester will do. During the test, add dated checks and real observations. At the end, hand the developer a list of references and open decisions. It works for a test you run yourself or one we run for you.
Example: a tester installs the app but cannot log in.
Knowing the install worked does not tell you whether the main feature was tested. Note the blocked login, ask the developer to check access, and reference the new build or setting. Only add a retest result after someone has tried again. If it still fails, keep it open in the handover.
Loading your local tracker…
These ticks are your record of completed work. They do not verify tester eligibility, send an application, or predict Google’s decision. Avoid storing passwords, access tokens, or tester email addresses here.
Done, proven and decided are different things.
- Done means you believe a task is finished. The tracker does not check it for you.
- Proven means there is a reference someone else can open, such as a dated note or an issue number. "All good" is not a reference.
- Decided is the developer's call. List open issues and gaps so they can decide with the full picture.
For personal Play developer accounts created after 13 November 2023, Google asks for at least 12 testers opted in continuously for the 14 days before you apply for production access; organization accounts are exempt. Check Google's help page for the current rule. Finishing this tracker, or any paid plan, does not guarantee approval.
Use it in the next conversation.
Share a version without personal details with whoever makes the release decision. The application notes builder turns these references into notes for your production access answers. The sample closeout report shows one way to lay out findings and next steps. If you want help running the test itself, see the plans.
Using the closed test handover tracker
What counts as a reference?
Anything you or a teammate can open again later: a build number, a dated tester check, an issue number or a retest note. If you have nothing yet, write the next step instead. Never add tester emails, passwords or account tokens.
If I finish the tracker, does my app qualify?
No. The tracker only records your own work. Play Console shows whether your account meets the requirement, and Google reviews the application. A finished tracker can still list open problems.
Can someone else fill it in for the developer?
Yes. Whoever runs the testers can gather the record and spot gaps. The developer should still check the 14-day window, policy declarations, open issues and the final wording in their own account.
Where is my data stored?
Only in this browser, when storage is available. Nothing is uploaded. Download a copy before you switch browsers, use a shared computer or clear your browser data.