Closed testing task plan: 14 days of tester tasks (template)
By Sabahattin Sudan, founder of SwapTesters · Updated October 14, 2026 · 3 min read
The most common reason apps are refused production access is that testers weren't engaged. The fix isn't more testers — it's giving testers something specific to do across the whole 14 days. This page is a template you can copy, adapt to your app and send.
Four rules for good tester tasks
- One task, one feature. “Add your first expense” beats “try the app”.
- Short. Two to five minutes. People who are busy still do short tasks.
- One question at the end. “What confused you?” gets far better answers than “any feedback?”.
- Spread over 14 days. A task every one or two days keeps the app in use for the whole test, which is what Google asks about.
The 14-day plan
| Day | Task for testers | Question to ask |
|---|---|---|
| 1 | Install, finish onboarding / sign-up | Where did you hesitate or get stuck? |
| 2 | Use the main feature once, for real | Did it do what you expected? |
| 3 | Use the main feature again with different data | Anything slow or broken? |
| 4 | Try settings: language, theme, notifications | Which setting was hard to find? |
| 5 | Use a second feature (search, filters, sharing…) | Would you use this feature? Why or why not? |
| 6 | Make a mistake on purpose: wrong input, back button, no internet | What happened? Did you lose anything? |
| 7 | Free use — use the app as you normally would | One thing you'd change? |
| 8 | Install the update and check the fixes from week one | Is the problem you reported fixed? |
| 9 | Try a feature nobody has used yet | Was it clear what it does? |
| 10 | Use the app at a different time of day or on another network | Anything different? |
| 11 | Explore every screen you haven't opened | Anything that looked unfinished? |
| 12 | Free use | Anything new you noticed? |
| 13 | Repeat day 2's task | Is it easier now than on day 2? |
| 14 | Fill in the final form | Would you keep using the app? |
Ship your update around day 7 or 8 with fixes for what testers reported. Day 8's task then shows Google — and you — that you acted on feedback.
Messages you can paste
Invitation
“Hi! I'm testing my app [name] on Google Play before launch. Google requires testers to stay in the test for 14 days. It takes 2–5 minutes every day or two — I'll send a small task each time. To join: 1) open this link with the Google account you use on Play Store: [opt-in link] 2) tap ‘Become a tester’ 3) install from Google Play. Please don't leave the test before [end date]. Thank you!”
Daily task
“Day [n] of 14 🙌 Today's task (2–5 min): [task]. Then answer one question here: [form link] — [question]. Thanks for staying in the test!”
Update notice
“Version [x] is out with fixes from your feedback: [two or three fixes]. Please update from Google Play and check if your issue is gone.”
Feedback form questions
Use one Google Form for the whole test, with these fields. At the end you'll have dated, countable feedback — exactly what the production application asks you to summarise.
- Your name or nickname (so you can follow up)
- Which day / task is this about?
- Answer to today's question
- Did anything crash or not work? What were you doing?
- Device and Android version (optional)
- Screenshot (optional)
Turning it into your application answers
- Engagement: count how many testers answered on how many days.
- Feedback: group the answers into bugs, usability notes and ideas, with numbers.
- Changes: list what your day-7/8 update fixed and which feedback it came from.
See how to write those answers in the 9 production access questions, and send your testers our guide to joining a closed test.
Google's own advice — clear instructions, use many features, collect and act on feedback — is in Play Console Help. Checked on 14 October 2026.