REGISTRATION / FORMS
Collect the details you need to welcome participants, not a page of information you will never use. Start with a contest or yoga class registration template, then adapt it for your event, workshop, or program. Explain whether a submission confirms a place or still needs review.
How to choose and use a template2 templates · collections
Preview template
Form · Registration
Collect contest entries in one place with this contest registration form template. Ask for the entrant's details, the entry itself, and the information your team needs to review it fairly.
Make it yours
Preview template
Form · Registration
Collect interest in your classes with this yoga registration form template. Ask about the class, experience level, and contact details needed to share joining information.
Make it yoursNo templates here match those filters. Describe what you need and let Youform AI give you a starting point.
Build with AIShowing of
A LITTLE GUIDANCE
Make the most
of your next ask.
A registration form records someone's details for a specific activity, event, or program. It may register interest or request participation. State clearly when a place becomes confirmed.
Use registration forms for classes, contests, workshops, and programs that need a consistent participant list. Keep consent, preferences, and eligibility checks relevant to the activity.
Start with the closest available template and inspect its actual questions. The collection currently offers contest and yoga class examples; other event or program formats can be created by adapting a copy.
The following are examples of registration workflows, not a claim that each has a separate template here.
Collect entry details and relevant eligibility, with clear contest terms.
Ask for the class, preferred session, and practical participation needs.
Gather the attendee details needed for a named event.
Collect the chosen workshop and any prerequisites that affect participation.
Ask for course selection and required joining information.
Record interest or enrolment details and explain any selection review.
Include the activity, participant name, reply address, chosen session, and practical requirements. Ask for additional details only when organizers need them. Explain deadlines and any review or payment step.
Ask “Which session are you registering for?”, “How can we send joining details?”, and “Do you need any participation arrangements?” Keep sensitive information out of general notes where possible.
Copy a template, replace the activity and dates, and edit participant questions. Set a clear ending message and preview the form on a phone. Publish only after checking how registrations will be reviewed.
Adapt language, session choices, and confirmation rules to the activity. A contest may need entry eligibility; a class may need time and experience level. Do not retain unrelated sample questions.
Name the event, date, location or time zone, and available choices. Decide whether one response represents one attendee or a group. For more starting points, use the event registration collection.
List the class and session choices, then ask about relevant experience and practical needs. Avoid collecting medical histories through a general registration form. Confirm arrangements privately through an appropriate process.
Collect one reliable contact method and explain its use. Do not require both phone and email unless both are necessary. For children, use the organization's approved guardian and consent process.
Review confirmed places against capacity in your registration system or controlled list. Close or update the form when necessary. A template does not automatically reserve seats, synchronize availability, or create a waitlist.
Use the ending screen to acknowledge receipt and explain the next step. If sending confirmation emails, configure that workflow separately and check plan requirements. Do not use “You're booked” while a request is still pending.
Keep a participant list with status, session, and the person responsible for follow-up. Limit access to special requirements. Reconcile cancellations and duplicate registrations before sending final joining instructions.
A signup often records early interest with minimal details. Registration usually collects the information needed for a particular activity. Neither automatically creates a user account unless you separately connect that process.
Applications normally require eligibility or selection review. Registrations usually organize participation, though capacity or payment checks may remain. Use wording that matches the actual decision process.
Share the direct URL in an invitation or embed the form beside activity details. Check date and time-zone wording, phone layout, and the confirmation message before accepting registrations.
Show questions relevant to the selected activity or participant type. For example, ask about a guest only when one is included. Test each branch and keep the main registration details consistent.
State who can register, what happens next, and when registration closes. Keep choices current, provide a contact route, and avoid collecting extra details simply because another event asked for them.
Add or remove questions, move them into order, and choose colors and fonts that fit your website.
Use conditional logic to show a follow-up only when an earlier answer makes it useful.
Connect Google Sheets for a shared response list, or use Slack notifications to bring new submissions to your attention.
Start free with unlimited forms and responses, subject to fair use. See Youform plans and features for the details.
YOUR WORDS. YOUR COLORS. YOUR NEXT GOOD THING.
Pick a template, add your personal touch, and put it out into the world.