> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ticketspotapp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Set up multi-day event tickets and day passes

> Choose between a full-event pass, day-only tickets, or both, then review daily prices, capacity, and ticket scope for a multi-day event.

Use **Multi-day Event** for one event that spans several days. Its default **Event Pass** covers the full span. Separate day records are created when you choose day passes; Festival and Conference create day records even with their default full pass.

## Template starting point

| Setting | Initial choice |
| - | - |
| Schedule | Several days |
| Admission | Paid tickets |
| First offer | Event Pass · suggested price 25 in your site’s currency |
| Capacity | 100 |
| Attendees choose a time | Not enabled |

These are editable suggestions, not recommended prices or venue limits. Replace the dates, price, and capacity with your own. See [how onboarding works](./overview#complete-onboarding).

## Choose the onboarding answers

Open **Create Event** in the selected workspace.

1. Choose **Browse more templates → Advanced → Multi-day Event**, enter the title, and set **Several days** to a range of at least two calendar dates.
2. Under **Paid tickets**, choose the access model below and review the selected days.
3. Enter the starting price and capacity. Use **Continue later** to finish each day’s pricing and operating times in draft.

<Note>**Create my event** may publish immediately when the requirements are met. Use **Continue later** to finish setup as a draft. Review any plan or publishing message before sharing the event.</Note>

## Finish the event settings

| Where to go | What to configure |
| - | - |
| **Dates & Times** | A full-pass-only event keeps its actual start/end times. When day records are created, review their calendar-day times and adjust the daily program. |
| **Main Tickets** | Review the shared Event Pass if you offer one. **Day passes only** does not create that full pass. |
| **Each date → custom tickets** | Check its own ticket name, price, quantity, and capacity. Day passes initially copy the entered price and capacity; review each one. |
| **Whole-event pass and shared tickets** | Use [date-specific settings](/event-management/day-specific-tickets) to inspect the resulting ticket source and whole-event offer. |
| **Check-in and communications** | Explain the dates each ticket covers and configure scan limits, entry windows, and confirmation wording accordingly. |

## Choose an access model

| Choice | What is created |
| - | - |
| **Full event pass** | One pass for the whole span. For this generic template, no independent days are created by this choice alone. |
| **Day passes only** | A custom ticket on each selected day, with no full-event pass. A removed day has nothing on sale. Select at least one day. |
| **Full event pass + day passes** | The full pass remains available, and selected dates sell their own tickets. A date without its own ticket uses the shared pass. |

Full event pass is initially selected even though the combined option is labeled Recommended. These day-pass choices are available in onboarding only for paid, multi-day events without assigned seating or attendee-selected session times. Timed sessions show the day-pass choices disabled with a reason. Day-pass pricing is not automatically divided by the number of days.

A full pass and day tickets do not create extra venue capacity: verify the combination your buyers can book. For nonconsecutive dates, use **Specific Dates** in the [full editor](/event-management/datetime#specific-dates).

## Check the attendee experience

* Inspect the main event and every selected date for the expected offers.
* Check that each day price, capacity, and operating time is deliberate.
* Verify admission dates and re-entry behavior for both full-pass and day-pass tickets.

Review the event’s saved status and [publish/share controls](/event-management/manage-events) when it is ready. Return to [all event types](./overview) to compare starting points.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.