How do you choose a form for a waitlist or survey?
Start with what you’ll do with one answer. For a workshop waitlist, ask for an email address and a session preference, save the answers where your organizer can find them, and tell the person whether they joined a list or got a seat. Choose a form that lets the right people send and read those answers.
What should you ask for on a workshop waitlist?
Ask for the information you need to take the next step. An email address lets you contact the person when a seat opens. A session preference helps you choose what to schedule. Collect names only if your organizer will use them.
Tell people what the form does before they start. “Join the waitlist for a Saturday workshop” sets a different expectation from “Reserve a seat.” Repeat the actual outcome on the confirmation screen and say when you expect to contact them, if you know.
A waitlist form works even if you follow up by hand. A seat reservation has another job. It needs one reliable record of how many places are left and a way to handle two requests for the last place.
Can anyone fill it in without seeing other answers?
Yes, when the respondent link and the saved answers have separate access rules. Keep the response table private. Give the organizer access to the saved answers and send respondents only the link for filling in the form.
| Person | What they should be able to see |
|---|---|
| Someone on the public waitlist | The form and its confirmation screen. No response summary, spreadsheet or editing controls. |
| Someone outside a restricted workshop | The required sign-in or access message. A shared password can be forwarded, so use named access when individual identity matters. |
| The organizer | The saved response and any approved working copy. Check access on a connected spreadsheet independently. |
Compare tools
Scroll the table sideways to read every column.
| Tool | Who can fill it in?The link someone opens and any sign-in or access setting. | Where do answers go?The first saved copy and ways to take answers with you. | What does the person see?The screen after they send their answers. | What changes the cost?The allowance or paid features that can change your choice. |
|---|---|---|---|---|
| Google Forms | Publish for anyone with the link or give named people responder access. The one-response setting requires Google sign-in. | Forms saves answers under Responses. You can link a Google Sheet or download a CSV. | Set a confirmation message. Keep the results summary off if responses should stay private. | Google offers Forms free for personal use. It has storage and response ceilings per form. |
| Tally | Share the form link or add a shared password. A published form can also sit inside a web page. | Find answers under Submissions, download a CSV or connect a Google Sheet. Inviting a team into workspaces is a Pro feature. | Customize the thank-you page or send the person to another page after they submit. | Free submissions are unlimited within fair use. Sustained high volume and paid team features can change the plan you need. |
| Typeform | Share or embed the published form. A code question is suitable only for low-stakes screening. | Find answers under Results, then Responses. Export CSV or XLSX, or connect a Google Sheet. | Show an ending screen. Plus and higher can send the person automatically to another page. | Free includes 10 responses per month across the account. Basic starts at 100 monthly responses. At the limit, forms can stop accepting answers. |
| Fillout | Publish a respondent link or embed the form. Paid login pages can verify an email address or ask for a shared password. | Read responses in Fillout or download a CSV. Connect Airtable or Zite Database if the organizer needs a separate table. | Edit the default thank-you page. Use page logic for different paths. Paid plans can redirect after submission. | Free lists 1,000 completed responses a month across the organization. Fillout says collection can continue above the allowance. |
| Jotform | Anyone with the public link can open the form. Private forms use invited sign-in, and company access can check an email domain. | Find answers in Jotform Tables. Export answer rows as CSV or Excel and download uploaded files separately. | Customize the thank-you page or use conditions to change what people see after submitting. | Starter lists 100 new submissions a month and 500 stored answers. Views and upload space have separate limits. |
| Formbricks | Share a Link Survey or connect your app to show one after a specific action. A link can use a PIN. | See individual answers under Responses. Download all, filtered or selected rows as CSV or Excel. | Use block rules to change which question comes next. Link surveys can send someone to another page when they finish. | Cloud Hobby lists 250 completed or partial responses per month. Self-hosting uses your own server and supporting services. |
How can you check the waitlist before sharing it?
Walk through two made-up requests before you publish or connect anything. Write the expected result beside each one. Use a private, separate draft or paper copy with no email, payment, customer records or active integrations.
- Write the form and the outcomeUse one email field and a choice between morning and afternoon. Add an on-screen message such as “You’re on the waitlist. This does not reserve a seat.” Write down where the organizer should find the answer.
- Check what a visitor can doPreview on a narrow screen. Move through the fields with the keyboard. Try a blank or badly formatted email in the draft or on paper. The person should see what to correct without having to start over.
- Trace two made-up requestsUse casey@example.com for morning and robin@example.com for afternoon. On paper, match each to its expected row. Then repeat Casey’s address. Decide whether the organizer will keep the first choice, update it or ask Casey.
- Check the two destinationsWrite down what the respondent sees after pressing Submit and what the organizer sees in the response table. A preview can show the first without saving the second. For a real response test later, use an isolated copy with a private test destination and no live connections.
What changes when answers go to another app?
Connecting a spreadsheet or customer list creates another place to find and protect answers. Decide where the organizer corrects a response and what should happen if the same submission is delivered again.
A form can save each submission as its own row. A customer list may need one contact per email address. Set a rule for repeat requests before connecting them. Joining a workshop waitlist and agreeing to receive a newsletter are different choices.
A CSV is a file of rows you can open in a spreadsheet. Check who can open that copy and any file links it contains. Handle each copy separately when you delete a response. Leave file uploads out unless someone needs the file to do the job.
When do you need more than a hosted form?
A standalone link can be enough for an occasional waitlist. An embedded form appears inside a page you already have. Consider an in-app form if you need to use the signed-in person’s account, save directly into their records or assign access after a payment.
A survey may ask different follow-up questions depending on an earlier answer. Test each route so respondents see the right questions and ending. A team that needs a running total, a scheduled follow-up or approval can add that workflow after it verifies where each answer goes.