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

# Festivals

> Multi-day events with sessions, bundles and add-ons, PLVR Tap cashless, and a larger onsite team.

## Who this is for

You run a multi-day event with several ticket types, packages, vendors and a large team onsite.

## What to set up

In priority order:

1. **Plan with the PLVR team early.** Event creation, sessions (one per day), ticket types and bundles are arranged with your PLVR representative, not created in the portal. If you want PLVR Tap, ask for it to be enabled for your event.
2. **Understand your ticket structure.** Read [Ticketing concepts](/tickets/concepts), then [Multi-day festival](/tickets/scenario-multi-day-festival), [Group packages with bundles](/tickets/scenario-bundles) and [VIP tickets and add-ons](/tickets/scenario-vip-addons).
3. **Manage tiers and add-ons in the portal.** See [Ticket Management](/tickets/ticket-management), where you can turn tickets on or off, edit them and create add-ons.
4. **Set up PLVR Tap.** Start with the [PLVR Tap overview](/tap/introduction), then [Top-up setup](/tap/top-up-setup), [Vendors](/tap/vendors), [Approvals](/tap/approvals) and the [Personalization form](/tap/personalization-form).
5. **Promote.** [Promo codes](/promotions/promo-codes), [tracking links](/promotions/tracking-links), [affiliates](/promotions/affiliates) and [email campaigns](/promotions/campaigns).
6. **Handle guests.** See [Comping guests, artists and press](/tickets/scenario-comp-guests).
7. **Prepare onsite operations.** Create login codes in [Onsite staff](/onsite/onsite-staff), then learn the [Command Center](/onsite/command-center), [Wristbands](/onsite/wristbands), [Cashless](/onsite/cashless) and [Cases](/onsite/cases).
8. **After the festival,** review the [Spending report](/tap/spending-report), [Cashless activity](/tap/cashless-activity) and the [Ticket report](/tickets/ticket-report).

## What to skip

* Anything that duplicates a ticket you already have. Keep tiers consistent across days.
* Table booking, unless you take venue reservations.

## Team shape

Use every role: [Core team](/roles/core-team), [Scanning team](/roles/scanning-team), [Data team](/roles/data-team) and [Marketing team](/roles/marketing-team). Give each gate, binding and top-up team its own login codes.

## Common pitfalls

* Asking the PLVR team for a new day or ticket type late, since you cannot add them yourself.
* Forgetting that bundles draw on the same ticket inventory as the underlying tickets.
* Vendor menus not approved before doors open.


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