Skip to content

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.

Your testing handover record

0 of 16 checks marked complete · 0 evidence references recorded

Loading your local tracker…

Testing handover checks and evidence
01

Before invitations

Agree on the testing handover

Make the developer and the testing coordinator work from the same release record. A paid package or a tester list is not a substitute for working access.

Record the package name, version code, closed-track name, and person who can publish a replacement build. Keep a reference to the release record rather than guessing from a screenshot.

Use an eligible tester account to open the opt-in page, install the closed release, sign in, and finish the main task. Note any country, device, or account restriction that prevented access.

Give testers a goal, a short path through the app, expected results, and a place to report failures. Keep passwords and private tester details out of this public-browser tracker.

Name the role responsible for missing access, a blocked login, an unavailable tester, and a release-blocking defect. Agree how that role will be contacted and how a resolution is recorded.

02

Participation record

Record the qualifying window

Use Play Console to establish eligibility. Use your own run record to explain what happened during testing; the two records answer different questions.

For personal accounts created after 13 November 2023, Google's current guidance requires at least 12 testers opted in continuously for the preceding 14 days before applying. Check the account's current Play Console guidance.

Record when the qualifying group was established and where the count was checked. An upload date alone does not establish a continuous opt-in window.

If someone leaves or cannot use the release, record the date and action taken. Do not assume a replacement tester inherits the previous tester's qualifying time.

Reconcile your participation notes with the status shown in Play Console. Leave the application date unconfirmed when the underlying count or continuity is uncertain.

03

Evidence trail

Connect observations to released fixes

A useful closeout explains an actual app journey, what testers observed, and how the developer responded. More checkmarks do not make missing evidence real.

Name a task such as creating a project or completing a booking, the build used, and the outcome. Include failed attempts and relevant device context, not just app-open counts.

Link an observation to reproduction steps, an expected result, an actual result, and an owner. Remove personal data before sharing reports outside the team.

Reference the issue, the changed build, and the repeated task. A developer saying 'fixed' and a tester confirming the result are separate pieces of information.

List unavailable devices, unexercised features, or scenarios that remain uncertain. Give each gap a next action instead of describing all features as fully tested.

04

Closeout review

Hand the decision back to the developer

The service can help coordinate a run. The account owner remains responsible for the application, policy declarations, and decision to release.

Collect the participation summary, task coverage, issue references, changed builds, retests, and open risks. Make sure someone receiving the packet can find each source.

Record whether a remaining problem blocks release, who owns it, and when it will be reviewed. Do not mark an issue resolved merely because the testing package has ended.

Use the evidence brief builder to prepare notes in your own words. Verify claims about engagement and fixes against the actual run before using them in Play Console.

Confirm the current Play Console status, app setup, and policy declarations. Completing this tracker neither submits an application nor guarantees Google's production-access decision.

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.