Live online webinar
Attendees join from their own locations, so the time they can attend matters more than where they are.
- Add: Time zone, with your main regions as the options
An event registration form records who is attending, how to reach them, and anything the host must prepare for, such as a session choice or a meal. For a webinar, most of that fits in four or five fields, while an in-person event adds needs that depend on the venue. Ask only for details that change how the event runs, and leave the rest for a message sent after registration.
Event registration: 1,000 average monthly searches.Google Ads Keyword Planner · 2026-10-09 · United States
| Field | Type | Required | Why you ask it |
|---|---|---|---|
Who is attending | Section header | Groups the identity questions so the attendee sees one short block before the session-specific ones. | |
Full nameFor example: Sam Rivera | Short text | Required | The attendee list, any name badge and the thank-you message all use this name. |
Work email | Required | Join details and follow-up go here. One wrong character means a missing join link, so check the format carefully before the event. | |
Organization | Short text | Optional | Shows which companies attend, which matters for sales-led events. Keep it optional for personal registrations. |
RoleOwner or executiveManagerIndividual contributorStudent or educatorOther | Dropdown | Optional | Lets the presenter pick examples that fit the people in the room. Keep the list short. |
Session details | Section header | Separates the event choice from the personal details, so people know which answer changes their place. | |
Which session will you attend?Morning sessionAfternoon session | Single choice | Required | Needed only when one event runs more than one session. Replace the sample options with your real session times, or delete the field. |
Topics you want coveredSetup and first stepsReportingTeam workflowsPricing and plansSomething else | Multiple choice | Optional | Helps the presenter choose examples. List only what the session will cover, or people will expect content that is not there. |
Questions for the presenterOptional. Keep it to one question if you can. | Long text | Optional | Collects questions before the session, so the presenter can prepare. Say whether questions will also be taken live. |
Accessibility needsDescribe what would help you take part. You do not need to give a reason. | Long text | Optional | Gives you time to arrange captions, seating or large-print materials. Say what you can and cannot provide. |
Follow-up you would likeThe session materialsInformation about future eventsNeither | Multiple choice | Optional | Makes follow-up an explicit choice, so you send only what each person asked for. |
Estimate based on question types; actual completion time varies.
Attendees join from their own locations, so the time they can attend matters more than where they are.
Attendees come to a room, so you need to plan seating, arrival and any food.
Qualifying questions at registration can make attendees feel sold to. Ask about budget in a follow-up, and only if the person has opted in to it.
A large text box turns registration into homework. Ask for the topic in a line or two and let the session answer the rest.
Registration is a decision to attend, not to purchase. Keep purchase timing for a separate conversation after the event.
A scheduled job picks up new registrations, and in production it runs hourly. The form's creator is notified after that job, so check the grid before you send join details.
Use the grid's CSV export to create the list. The form notifies its creator, not the attendee, so plan the confirmation and join details in the email tool your team already uses.
Decide when attendees will receive the join details and draft the message in advance. Processing runs on its own schedule, so do not promise a message within minutes of someone registering.
Decide the limit before you publish, and write down what happens when it is reached. Count submissions in the grid as they arrive, and stop sharing the link once the limit is met.
A name, a work email and one question about what the attendee wants covered are often enough for a webinar. Add a time zone if people join from several regions, and keep organization and role optional. Anything that does not change the session can move to a message sent after registration.
For a webinar, aim for well under a minute on a phone. The stats above estimate time from the field types on this blueprint. Each optional question adds reading time for everyone, so remove any field whose answer you would not use.
A registration form only has to produce a clean attendee list, and most form tools can do that. Check three things: whether you can export the answers, whether people can open the form from a link, and whether your team will read every answer in one place. Attain OS forms are shared by link and export to CSV.
Decide the rule before you publish. You can close the link, open a waitlist with its own short form, or add a second session. Tell people on the page what happens when the limit is reached, so no one registers expecting a place they will not get.
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.