Booking and Participant Forms

Booking fields describe the reservation as a whole; participant fields collect information for individual registrants where the booking flow requires it. Put a question in the appropriate group so customers are not asked to repeat reservation-level information for every participant.

Global forms and offering overrides

Open DayTidy → Settings → Booking → Form for the shared Booking Fields and Participant Fields builders. In an offering’s Booking → Forms section, Inherit from global options determines whether it uses that shared configuration. Turn inheritance off only when the offering needs its own form, then save the offering after editing.

For example, an accessibility request for a workshop attendee belongs with participant information. A purchase-order reference for the entire group belongs with the booking. Avoid collecting sensitive information that the business does not need.

Add and configure a field

1. Open the appropriate builder and choose a field type from its dropdown.
2. Select Add and expand the field’s options.
3. Enter its Name, choose its Page where available, and set Required if the answer is essential.
4. Add a short Hint explaining the expected answer.
5. For choice fields, enter the options the customer may select.
6. Save the containing settings form or offering, then open the public booking flow to check it.

The built-in builder offers Text, Number, URL, Email, Date, Time, Dropdown, Radio, Text Area, Checkbox, Separator, and Agreement. Options differ by type: a separator organizes the form; a choice field needs choices; an Agreement can have a checked-by-default control. Existing system fields have protected behavior and should not be treated as arbitrary custom fields.

Conditional display example

To ask for details only when needed:

1. Add a Dropdown such as “Do you need an accessibility arrangement?” with “Yes” and “No” choices.
2. Add a Text Area for the details.
3. In the details field’s Conditional Display, select the dropdown and its “Yes” answer.
4. Save and test both answers in the public flow.

Use Always display to remove a condition. Conditions depend on another compatible choice field in the same form. The interface supports conditions based on Dropdown, Checkbox, Radio, or Agreement answers. Avoid circular dependencies; invalid conditions must be corrected before relying on the form.

Verify the result

On a test site, try submitting with a visible required field empty, then complete it and submit. Test both the shown and hidden branches of a conditional field. Open the resulting booking and inspect submitted booking and participant data. Hidden conditional answers are pruned, so do not expect an answer from a field the customer was not asked to complete.

If changes are missing, first check whether the offering still inherits global options and whether you saved the correct containing form. For a group booking, verify the participant count and each participant’s information rather than checking only the primary booker.