Describe your event, deadline, and refund choices. Makeform creates an event cancellation form that identifies the booking, records released seats, and routes refund requests.
Send cancellations to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a prompt, adapt it to your policy, or send it to the Makeform builder.
Audience
Ticket holders cancelling a conference registration
Format
Cancellation and refund-review form
Prompt size
349 chars
Example form structure
Cancellation and refund-review form
Attendee name and registration email
Confirmation number and ticket type
How many tickets are you cancelling?
Refund review or registration transfer?
Reason for cancelling
Suggested routing tags
Attendance cancelled
Refund review
Transfer requested
Ask for the registration email or confirmation number so staff can match the right booking.
Step 1
Identify
match the attendee and registration
Step 2
Cancel
record seats, sessions, or guests released
Step 3
Review
route refund or transfer requests
Step 4
Confirm
tell the registrant what happens next
Why use a cancellation form
A message saying “I cannot come” may omit the booking reference, affected tickets, and requested outcome. A form collects them together.
Registration email, confirmation number, event date, and ticket type help staff match the request.
Release the spot while routing refund, transfer, or credit requests under your policy.
Use tags such as received, refund review, transfer requested, and completed.
Built for changing plans
Start with the closest scenario, then add your dates, tickets, and policy.
Match tickets and separate cancellation from refund review.
Cancel a whole booking or name only the group members whose seats should be released.
Capture the exact session and offer a transfer request when another date may work.
Make cancellation quick while collecting an optional reason and future-event preference.
Cancellation workflow
Build around your team's decisions, then publish one cancellation link.
Name the event, ticket types, deadline, refund paths, transfer choices, and request owners.
Show refund questions after refund review is selected and group details after partial cancellation.
Notify the event team, route refunds, and record a shared follow-up status.
Distinguish receipt from approval and state when to expect a decision.
Form vs email vs manual edits
Structured data helps when ticket types, group bookings, and refund paths multiply.
Field guide
These six sections help the organizer identify the booking, understand exactly what is changing, and send the request down the correct operational path.
Registrant identity
Collect the booking contact, not only the attendee. For group registrations they may differ, and replies should go to the address used at checkout.
Registration lookup
A confirmation number helps when names repeat. Event, date, session, and ticket type provide useful fallback identifiers.
Cancellation scope
Let the contact choose full or partial cancellation, enter a quantity, and identify affected attendees on a shared order.
Requested outcome
Attendance cancellation and refund approval are separate. Ask for the desired outcome, then show relevant questions.
Reason and context
An optional reason can reveal recurring conflicts or concerns. Use choices for reporting and an Other field for nuance.
Policy and confirmation
Show the organizer's policy beside the request. Explain that submission records it, then give the next step and response channel.
Related tools
Build the intake, RSVP, refund, waitlist, and follow-up forms that sit before and after an attendee cancellation.
Collect attendee and ticket details in a structured registration flow.
Open toolTrack invited guests who accept, decline, or update their RSVP.
Open toolCollect refund details for staff review after a cancellation request.
Open toolCollect interested guests who may fill newly released event places.
Open toolPresent registration and refund-policy acknowledgments in a dedicated form.
Open toolFAQ
Practical answers for event teams managing changed plans, released capacity, and refund requests.
It lets an attendee or booking contact report that they will not attend. It identifies the booking, affected tickets or guests, requested outcome, and follow-up details.
Include booking contact, registration email, confirmation number, event or session, ticket type, cancellation scope, requested outcome, optional reason, and policy acknowledgment. For groups, add affected names or a roster.
Not unless your workflow makes that decision. Record the request, show your policy, and state that review follows. Distinguish successful submission from refund approval.
Yes. Ask whether it is full or partial, then collect the ticket quantity and affected names. Keep the group confirmation number and contact with the request.
Usually it is better as optional. Choices can reveal recurring conflicts, but registrants can release a place without sharing personal context. Add an optional Other field.
Yes. Offer another session, replacement attendee, future credit, or no alternative when available. Conditional questions can collect the new date or name.
Use statuses such as received, registration matched, attendance cancelled, refund review, transfer requested, and completed. Keep booking details and outcomes together.
Yes. Makeform provides unlimited free forms and responses, so you can generate, edit, publish, and collect event cancellation requests without a response cap. The paid tier removes the Makeform badge.
Make changed plans easier to process.
