A beta tester signup should collect enough to choose testers for the build you are about to release, and no more. Ask about the devices and operating systems you need to cover, how often people use a product like yours, and whether they accept your beta terms. Submitting the form should not give anyone a place in the beta, so the invitation stays a separate decision your team makes.
| Field | Type | Required | Why you ask it |
|---|---|---|---|
Name | Short text | Required | Lets the team address an invitation. It is not an identity check, so a first name and last name are enough. |
| Required | The route for any invitation or question. The form does not email applicants, so this field is how your own process reaches them. | ||
Main device for testingDesktop or laptopPhoneTabletMore than one | Single choice | Required | Lets the team cover each platform in the release, rather than filling the beta with one kind of device. |
Operating system and versionFor example: macOS 15, Windows 11 or iOS 18 | Short text | Required | Versions matter more than device names when a build behaves differently on an older system. |
How often do you use a product like this?DailyWeeklyMonthlyRarely or never | Single choice | Required | Separates regular users, who are more likely to notice friction, from people who will try the product once. |
Do you need an accommodation to take part?NoYes, I will describe it below | Single choice | Optional | Lets the team plan testing around a need before the sessions start. Answering is optional. |
Accept the beta termsI have read the beta terms and agree to themI do not agree | Single choice | Required | Records the acknowledgement that testing depends on. Your own counsel should review the wording of the terms before you use them. |
Anything else we should know | Long text | Optional | Catches context the other questions missed, such as a constraint on when they can test. |
You have a set number of places this cycle and need to match testers to an area of focus and an availability window.
The testers work at customer companies, and each invitation has to go to the right account.
A software beta rarely needs it. If you must confirm an age, decide the rule with your counsel and ask only for the answer that rule requires.
Choosing a tester does not require an identity document. Storing one creates a risk you do not need to take on.
Health details are not needed to pick testers. Ask only whether an accommodation is needed, as in the field above, and let the person describe it in their own words if they choose to.
The form has no e-signature field. Send any agreement through the signing process your legal team already uses, and tell applicants about that step in the introduction.
Only the form's creator is notified, and only after the hourly processing run in production. Build your selection timeline around that run, not around the day someone applies.
Write down the platforms, workflows and availability you need before you open the grid. Then choose a group that covers those needs, and record why each person was or was not selected.
The form does not send invitations or rejections. Write to selected testers with the start date and terms, and send a short, polite decision to everyone else through your own process.
If your testing tool needs a list, export the responses as CSV and import only the selected rows. Keep the export in an access-controlled location and delete it when the beta ends.
Customer Care cases are optional for each submission. A beta application is not a support request, so leave that option off unless you want every applicant tracked in the support queue.
The fields here are a starting point, not a downloadable Word or PDF file. Attain OS publishes the form to a link, and it does not email applicants, so your invitation and terms still go through your own process.
Choose by the criteria you wrote before reading the responses: the platforms and workflows you need, regular use, and availability. Note who you selected and why, and keep the responses of people you did not select only as long as your data policy allows.
The form has no e-signature field, so do not expect a signed agreement to come back through it. If you need one, send it through the signing tool your legal team uses and mention that step on the form. Have your counsel review the terms before anyone is asked to accept them.
Usually not. A software beta rarely needs a home address or a date of birth. If you need an age check, decide the rule with your counsel and collect only the answer that rule requires, such as a yes or no.
Choose a category and a form type in the wizard. Answer three Atty Suggestions questions, then give the form a title. Atty builds the fields in the background. Edit the fields and ask Atty to refine them, then publish and share the /f/ link.
