What to Do During the 14-Day Window
The window is not dead time. Here is a day-by-day checklist that keeps the testing on track and the record complete.
Days 1-3: confirm the roster is filling. Check the opt-in count in Play Console daily. If it is below the target, investigate. A wrong opt-in link, a stale build, or a store listing that is missing a privacy policy can block testers from joining.
Days 4-7: triage findings as they arrive. Crashes should be fixed immediately. Layout issues and usability problems should be logged and prioritised. Do not batch fixes for the end of the window; the window is the last chance to test them.
Days 8-11: ship fixes into the same track. Do not create a new closed test track for each fix. The continuity of the track is part of the evidence, and a track that changes mid-window looks interrupted.
Days 12-14: compile the testing record. Collect the screenshots, the crash logs, the device list, and the opt-in timeline. Write the report in the order a reviewer will read it: roster, devices, findings, fixes. A report that is ready before the window ends is a report that does not get rushed.
Day 15: apply for production access. Use the report you already have to answer Google’s questionnaire. Do not write new answers from memory; copy the specific details from the report.
If this matches your situation
12Tests assigns 12 real Android testers within hours, runs the full 14-day window, and delivers a written report you can paste into Google's production access questionnaire. One-time payment per app, no subscription.