Ask the question. Keep the answer.
A custom field is one definition. Event Schedule renders it as a question on the forms it belongs on, and files the answer as a column you can read, print and export.
One field, defined once
{custom_3}- Field name
- Dietary requirements
- Type
- Dropdown
- Choices
- No preference, Vegetarian, Vegan, Gluten free
- Switches
- Required On request form Private
Renders as
This one lives on the schedule, so it is asked on your own event form and on your public event request form. Write a field on an event or a ticket type instead and it is asked at checkout.
Three places
A field belongs to a schedule, an event, or a ticket.
Which one you pick decides who is asked and when. All three are on the Pro plan, and all three take up to ten fields.
Once per event
ProDefined on the schedule: Customize, then Custom Fields
Ten per schedule, answered once for each event. They appear on your own event form, and each one can also be asked of visitors on your public event request form. This is the set that carries the extra switches.
- Answered by
- You, or a visitor submitting an event to you
- Switches
- All four switches
All six field types, in any combination.
Once per order
ProDefined on the event, with tickets or registration
Ten per event, asked once for the whole order. The same set appears on your ticket form and on your registration form, so the question does not change with the way you are taking sign-ups.
- Answered by
- Whoever is buying or registering, once
- Switches
- Required only
All six field types, in any combination.
Once per ticket
ProDefined on each ticket type
Ten per ticket type, shown only while that ticket is in the basket. Turn on per guest fields and everyone in the party answers for themselves instead of one person answering for six.
- Answered by
- The buyer, or each guest in the party
- Switches
- Required only
All six field types, in any combination.
Worth being precise about: the extra switches live on schedule fields, along with an instruction for the AI importer. A checkout field carries a name, a type, its choices and whether it is required.
Six types
Six types. No more, no fewer.
Here is the whole list, what the person filling the form actually gets, and where the choices come from.
| Type | What they get | Choices | Pattern |
|---|---|---|---|
| Text string | A single line to type in | Anything they type | Yes |
| Long text multiline_string | A box that takes paragraphs | Anything they type | On the server |
| Yes / No switch | A switch on a request form, a Yes or No menu at checkout | Fixed | No |
| Date date | A date picker | Any date | No |
| Dropdown dropdown | One choice from your list | A comma separated list you type | No |
| Multi-select multiselect | A checklist, any number of ticks | A comma separated list you type | No |
A long text field is checked against its pattern on the server only, because a multi-line box has nowhere to hang a browser pattern. Everything else that can be pattern checked is checked in both places.
A dropdown
You type Small, Medium, Large, XL once and every buyer picks from exactly those. A required one will not let the form through unanswered.
A multi-select
The same comma separated list, ticked any number of times. This is how a request form becomes a checklist.
Four switches
A question is not just its wording.
Each field on your schedule carries four switches. They are what turn a box on a form into something you can rely on when the answers come back.
The form will not submit without an answer. Checked in the browser and checked again on the server, so an empty answer cannot slip past either one.
Ask the question of visitors submitting an event to you. On by default. Uncheck it to keep the field for your own use inside the admin portal.
Keep the answer off your public schedule. It stays visible to you, and it still fills {custom_N} in graphic templates and URL patterns.
Text fields can require a format. Pick email address, phone number, web address, numbers only or letters and numbers, or write your own, and test a sample value before you save it.
A pattern, and a hint
string- Five ready-made presets: email address, phone number, web address, numbers only, letters and numbers.
- Or write your own, and try a sample value against it before you save.
- Your hint prints under the field, so nobody has to guess what format you meant.
Drag the fields into the order you want them asked in. The order you set is the order on every form.
The honest line
The list is free. The questions are Pro.
We would rather you read that here than find it in the product. Here is exactly where the line falls.
Taking names
FreeTurn on registration and people sign up with their name and email. Set a capacity and each date shows how many places are left. Free forever, on every date of a recurring event.
Asking anything else
ProCustom questions on that same form are Pro, at $5 a month with a 7 day free trial. The form does not change shape, it just starts asking what you need.
Taking money
FreeSelling starts free: 25 paid tickets a month, through your own Stripe account, and scanning those tickets at the door is free too. Pro lifts that ceiling and adds the live check-in dashboard. Event Schedule charges zero platform fees on every plan, so past Stripe's own processing the money is yours.
Nothing here needs a plugin, an integration or a second form tool. See the plans
Question and column
One side asks. The other side files.
A field is only worth defining if the answer turns up somewhere useful. Answers turn up in four places, and one of them is a spreadsheet.
The question you ask
Two extra questions on a form somebody was already filling in. Required ones will not let the order through empty.
The column you get
| Name | Tickets | Dietary requirements | Access needs |
|---|---|---|---|
| Dana Ruiz | Standard x2 | Vegetarian | Step-free access |
| Priya Anand | Standard x1 | Gluten free | |
| Tom Okafor | Concession x1 | No preference | Sign language |
The sales export grows one column per field name. That is the whole trick: the caterer gets a count instead of a conversation.
On the request card
A visitor answers on your event request form and the answer sits on the request in the admin portal, then travels with the event once you accept it.
On the order
Checkout answers appear beside the sale in your sales table, per order and per ticket.
On the ticket
The answers a buyer gave are printed on the ticket itself, so the person on the door reads the same thing you do.
In the export
The sales CSV gains one column per field name, so a spreadsheet of dietary counts is a download rather than an afternoon.
On the request form
Ask before you say yes.
If you take event requests from other people, every schedule field is also a question on that public form, on by default. So the things you always end up emailing about are answered before the request reaches you.
- A multi-select becomes a kit checklist: which of your equipment they need, ticked.
- A pattern forces a reference number into the shape your own records use.
- Answers land on the request card in your admin portal, and stay with the event once you accept it.
- Uncheck one switch to keep a field for your own use and off the public form entirely.
Read the Custom Fields guide for the field-by-field reference.
Request from a visitor
Additional informationThe hint under the last field is yours to write. It is what stops the same correction happening twenty times.
Ten slots
Every field keeps a numbered slot.
A schedule field holds a stable slot from one to ten, and the slot is a variable you can use. The number in the margin of each section on this page is one of them.
Seven of ten slots in use on this schedule. The numbers do not shuffle when you reorder the fields.
In a graphic
Drop {custom_1} into an event graphic template and the value prints on the artwork with the title and the date.
In a URL
The same variable works in your event URL pattern, so a value you already collect can shape the address.
As a filter
A public dropdown or multi-select becomes a filter on your guest calendar. Mark it private and the filter goes away with it.
Everything else
The rest of the paperwork.
Let the import fill it in
ProEvery schedule field can carry an instruction for the importer: what this field means and where to look for it. Paste a flyer or a listing and the value arrives already in the box.
Event import runs on every plan with a daily allowance, 10 a day on Free and 50 on Pro. The custom fields it fills are Pro.
In two languages
ProA field can hold a second name for your schedule's other language. Leave it blank and it is filled in for you, dropdown choices included.
On the door
ProThe answers a buyer gave are printed on their ticket, so whoever is scanning reads the same course choice or access note that you do.
One person, or all six
ProBy default one buyer answers once for the whole order. Turn on individual tickets and then per guest fields, and each person in the party gets their own name, their own QR code and their own answers, which is the difference between a dietary count you can cook to and a note saying "two of us are vegetarian".
Ticket types, sales windows and QR check-in all sit alongside this. How ticketing works
Bring a list with you
ProImporting attendees you already sold elsewhere? The importer accepts their answers to your ticket fields too, so the spreadsheet you have lands complete.
What custom fields are not
They are questions and answers, not a workflow engine. A field cannot branch to another field, cannot price an order differently, and cannot hold a file upload. What it can do is ask a clear question everywhere it belongs and hand you the answer in a column.
If that is what you needed a separate form tool for, this replaces it. If you needed conditional logic, it does not.
Related features
Popular with
Frequently asked questions
Everything worth knowing before you start writing fields.
What types of custom field can I create?
Six. Text, long text, Yes or No, date, dropdown and multi-select. Dropdown and multi-select take a comma separated list of choices that you type, and text fields can also require a format such as an email address or a reference code.
Where do custom fields appear?
It depends on where you define them. Fields defined on the schedule appear on your own event form and, unless you turn it off, on your public event request form. Fields defined on an event are asked once per order on the ticket form and the free registration form. Fields defined on a ticket type are asked only when that ticket is being bought, and can be asked of each guest in the party.
Are custom fields free?
The registration list itself is free forever, including a capacity limit and the count of places left on each date. The custom questions on that form are part of the Pro plan at $5 a month, which comes with a 7 day free trial. Event Schedule charges zero platform fees on ticket sales.
How many fields can I have?
Ten on the schedule, ten on an event and ten on each ticket type. Drag them to change the order they are asked in.
Can I export the answers?
Yes. The sales CSV export adds one column for every custom field name it finds, filled with what each buyer answered. The answers also appear in your sales table and on the ticket itself.
Can I collect an answer without publishing it?
Yes. Mark the field private and the value stays off your public schedule while remaining visible to you in the admin portal. A private field can still be dropped into an event graphic or a URL pattern with {custom_N}.
What if my schedule is not in English?
Each field can carry a second name for your schedule's other language. Leave it blank and it is filled in for you, along with your dropdown choices, so a visitor reads the question in the language they came for.
Stop chasing answers. Ask on the form.
Registration and capacity are free forever. Custom questions come with Pro at $5 a month, with a 7 day free trial and no platform fees on anything you sell.
No credit card required to start