Multiple event dates (Pro)
An event that runs more than once - a workshop repeated over three evenings, a guided tour on four Saturdays - needs more than the single Event Date the free plugin stores. With LocalForm Pro active, the Event Details panel in a form's Settings tab gains a More dates section: add as many dates as you need, each with its own start time, optional end time, and an optional label.
Adding dates
- Edit a form and open the Settings tab.
- In the Event Details card, fill in Event Date and Event Time as usual - that stays the first date of the event.
- Under More dates, click Add date for each further date and fill in:
- Date - required; a row without one is dropped when you save.
- Start time and End time - optional. An end time is only kept when there's a start time and it is later than it.
- Label - optional; a short name for the session ("Evening session", "Dutch-language tour").
- Remove a row with the × button.
- Save the form.
Dates are sorted chronologically and de-duplicated on save, so the order you add them in doesn't matter. A form can hold up to 50 dates.
Asking which date(s) they attend
Tick Ask which date(s) they attend and the form gets a question listing every date - the Event Date first, then the extra dates:
- Question - the wording shown to visitors. Leave it blank for "Which date will you attend?" (or "Which dates …" for a multiple answer).
- Answer - One date only renders a single-choice (radio) question; One or more dates renders a checkbox question.
- Required - whether a visitor must pick a date to submit.
The question is added as a normal question card, placed at the top of the form the first time it appears. You can drag it wherever you like afterwards and it stays put - but its wording, type, options and required flag are owned by the Event Details panel, so those controls on the card are read-only. Add or remove a date, and the question's answer options follow on the next save.
Untick the setting and the question is removed from the form again.
Where the dates show up
- On the form page - the event facts band inside the form shows the first date followed by a +2 dates count (the first extra date leads when no single Event Date is set). The dates themselves are listed by the attendance question, so the band doesn't repeat them.
- In responses - the answer is stored like any other choice question: a column in the submissions table, in the XLSX export, and a per-date count in the Responses summary, so you can see how many people are coming on each date.
- In the webhook payload - the answer travels under the question's field name, and the full schedule is added as an
event_datesarray:
{
"event_date": "2026-09-01",
"event_time": "19:00",
"event_dates": [
{ "date": "2026-09-01", "start_time": "19:00", "end_time": "", "label": "" },
{ "date": "2026-09-08", "start_time": "19:00", "end_time": "21:30", "label": "Evening session" }
],
"fields": { "event_dates": ["1 September 2026, 19:00"] }
}
Notes
- Answer options are written in the site's date format, and that formatted text is what gets stored on a submission. Changing the site's date format (Settings → General) therefore doesn't rewrite answers already collected; the
event_datesarray in the webhook payload always carries the machine-readable dates. - Duplicating a form copies its dates and the question setup along with it.
- Capacity per date isn't tracked separately - Maximum registrations still counts the whole form.