FormsFort
EN ES

HTML Event Registration

HTML event registration form template.

Use this event registration form to collect one attendee's contact and attendance details. The structured options make it easier to confirm capacity, prepare the venue, and follow up after the event.

Get the code Browse examples

Put this template to work

Connect the form to the workflow around it.

The html event registration workflow is only one part of a production form. Use these resources to refine markup, compare backends, and route accepted submissions.

Field guide

HTML form elements

Choose accessible inputs, textareas, radio groups, selects, and validation patterns for this form.

 Free tool

HTML form template generator

Generate a complete starting form, then adapt its fields to the workflow on this page.

 Comparison

Compare form backends

Review delivery, uploads, webhooks, notifications, and migration trade-offs before launch.

 Solution

Lead capture forms

Turn structured contact and qualification fields into a sales-ready intake workflow.

 Solution

Form notifications

Route accepted submissions to verified email recipients, team chat, or a webhook.

 Solution

File upload delivery

Add upload rules and delivery handling when this workflow needs supporting documents.

Fields

What this form captures

  • Attendee name, email, and organization
  • Attendance mode and ticket type
  • Dietary or accessibility requirements
  • Questions for the event team

Workflow

How to use it with FormsFort

  1. Send a registration confirmation with the selected attendance mode.
  2. Track ticket type and attendee details in a spreadsheet or CRM.
  3. Notify event staff about dietary and accessibility requests.
  4. Use capacity checks or a waitlist webhook when registrations approach the limit.

Copy-paste HTML

Backend-ready form code.

Replace YOUR_ACCESS_KEY with your FormsFort public access key, then deploy the form on your site. 

<form action="https://api.formsfort.com/submit" method="POST">
  <input type="hidden" name="access_key" value="YOUR_ACCESS_KEY" />
  <input type="hidden" name="subject" value="New event registration" />
  <input type="hidden" name="event" value="spring-workshop" />

  <label for="attendee_name">Full name</label>
  <input type="text" id="attendee_name" name="name" autocomplete="name" required />

  <label for="attendee_email">Email address</label>
  <input type="email" id="attendee_email" name="email" autocomplete="email" required />

  <label for="organization_name">Organization</label>
  <input type="text" id="organization_name" name="organization" autocomplete="organization" />

  <fieldset>
    <legend>How will you attend?</legend>
    <label for="attendance_in_person">In person</label>
    <input type="radio" id="attendance_in_person" name="attendance_mode" value="in-person" required />
    <label for="attendance_remote">Online</label>
    <input type="radio" id="attendance_remote" name="attendance_mode" value="online" />
  </fieldset>

  <label for="ticket_type">Ticket type</label>
  <select id="ticket_type" name="ticket_type" required>
    <option value="">Choose a ticket</option>
    <option value="general">General admission</option>
    <option value="student">Student</option>
    <option value="sponsor">Sponsor</option>
  </select>

  <label for="requirements">Dietary or accessibility requirements</label>
  <textarea id="requirements" name="accessibility_requirements" rows="4"></textarea>

  <label for="event_question">Question for the organizers</label>
  <textarea id="event_question" name="organizer_question" rows="4" maxlength="2000"></textarea>

  <input type="checkbox" name="botcheck" style="display:none" tabindex="-1" autocomplete="off" />
  <button type="submit">Register for the event</button>
</form>

Production notes

Make it reliable before launch

  • Submit from the real production domain and confirm delivery logs show the expected origin.
  • Keep hidden fields for routing and context, not secrets. Public access keys are identifiers.
  • Use allowed domains, honeypots, rate limits, and optional CAPTCHA for public forms.
  • Test uploads, webhook payloads, spreadsheet rows, and autoresponder copy before publishing.

FAQ

Common questions

Can this registration form handle online and in-person attendees?

Yes. The attendance mode is a required choice, so confirmation and event-staff workflows can use different instructions for each attendee.

How should I manage a full event?

Send registrations to a spreadsheet or webhook that checks capacity, then redirect or notify people through a waitlist workflow when the event reaches its limit.

Does this process ticket payments?

No. It collects registration details. Use a payment provider for paid tickets and pass a confirmed order reference into a separate FormsFort workflow if needed.

Related templates

Build the next form in the workflow.

Registration Forms

Registration form templates

Registration forms should capture only the fields needed to approve, confirm, or route a signup.

 HTML Waitlists

HTML waitlist signup form template

Use this short waitlist workflow to collect a reachable email address and enough preference data to send a relevant launch update without building a signup backend.

 HTML Signup

HTML signup form templates

Signup forms should be short, fast, and easy to route into email, spreadsheets, or product waitlists.