Beta tester recruitment worksheet Replace bracketed fields before sharing. These are reusable templates and illustrative planning examples, not results from a completed study. 1. Recruitment brief App and purpose: [app name and the problem it solves] Release question: [one decision this test should inform] Target user: [relevant experience or use case] Device requirements: [platform, supported OS, required hardware] Mission: [one core journey and one recovery case] Time required: [minutes per session and number of sessions] Deadline: [date, time and timezone] Distribution: [TestFlight / Google Play testing track] Reward: [none or exact reward and completion conditions] Feedback destination: [private form or testing round URL] Support: [contact channel] Test data: [synthetic account or instructions] 2. Short screening form - Which device model and exact OS version will you use? - How do you currently handle [problem the app solves]? - Have you used [app/product category] before? What for? - Can you complete [mission length] by [deadline and timezone]? - Can you install through [distribution channel]? - Can you describe steps, expected behavior and actual behavior, and provide a redacted screenshot if it helps? - [Ask one locale, network, hardware or accessibility question only if it changes selection. Explain why you need it.] 3. Recruitment post or invitation Subject: Help test [app] on [platform] in a [minutes]-minute session We are the team behind [app], which helps [audience] with [problem]. We are looking for [target users] using [device/OS requirements]. The task is to [core mission] and tell us where the flow fails or feels unclear. The session takes about [minutes]. Please finish by [deadline, timezone]. Install through [TestFlight / Google Play test link after selection]. Reward: [amount/type or volunteer; completion and payment conditions]. Use [test account/synthetic data]. Submit findings privately at [feedback URL]. Interested? Complete [screening URL]. Questions: [support channel]. For a community post, check that recruitment is permitted and adapt this brief to the community rules. Do not publish participant-specific access credentials. 4. First mission - Confirm your installed build number and device/OS. - Start from [fresh install or signed-out state]. - Complete [core action] using [synthetic record]. - Repeat the relevant step with [one safe recovery case, such as denied permission or temporary disconnection]. - Report completion or the first point where you could not continue. - For a defect, include steps, expected result, actual result, build, device, OS, frequency and safe evidence. A completed task with no defect is valid. 5. Follow-up message Hi [name], the [app] test closes on [deadline, timezone]. If you have not started, the task and build link are at [round URL]. If installation is blocking you, reply with the error and device/OS so we can help. If you cannot participate, let us know. Thank you for your time. Retest message: Build [new build] addresses [issue]. Please repeat [original steps] and report whether [expected behavior] now occurs on [original device]. 6. Coverage and recruitment funnel worksheet Coverage rows: [device/OS], [user context], [tester], [mission], [status]. Stages: qualified applicants -> invited -> installed -> completed -> feedback. Count each stage separately and retain the denominator for every rate. Illustrative calculation only: To plan for 12 completed missions when you assume half of delivered invitations lead to installs and three quarters of installs lead to completed missions, start with 12 / 0.50 / 0.75 = 32 delivered invitations to screened candidates. These are assumptions, not promised response rates or platform requirements. Replace them with your measured rates after the first round. Invite more only where your coverage gaps justify it. A mission that ends in a documented blocker can count as completed participation; do not count only successful journeys. Completion rate = completed missions / invited testers. Installation rate = confirmed installs / invited testers. Do not count duplicate bug reports as additional completed missions. Source guide: https://betaroast.com/blog/how-to-find-beta-testers