> ## 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.

# Scenario: Multi-day Festival

> Set up a festival that runs over several days using one session per day, with consistent tiers and clear sales per day.

**Goal:** Your festival runs Friday, Saturday, and Sunday. Attendees should be able to buy tickets for the days they want, and you want to track each day separately.

## How multi-day events work

Each day is its own **session**, and every ticket belongs to one session. A Friday ticket is a Friday ticket. This means:

* Each day has its own capacity, prices, and sale windows.
* Ticket Management groups the table by session, and you can filter by **Session**.
* The [Ticket Report](/tickets/ticket-report) and [Complimentary Tickets](/tickets/comp-tickets) can also be filtered by session.

> [!NOTE]
>
> Sessions and their tickets are set up with your event. If you need another day or a new ticket type, contact your PLVR representative. This portal then lets you manage them.

## The example

| Session | Ticket | Quantity | Price |
| - | - | - | - |
| Friday | Day Pass | 400 | \$40 |
| Saturday | Day Pass | 600 | \$55 |
| Sunday | Day Pass | 400 | \$40 |

Each day is sold and counted on its own, so Saturday selling out does not affect Friday.

## Review each day

**1. Open Ticket Management**

Go to [Ticket Management](/tickets/ticket-management). With several sessions, a table appears for each, and a **Session** filter lets you focus on one.

**2. Check each session's tickets**

For each day, confirm **Price**, **Total**, and sale dates. Remember that **Name** and **Price** lock after the first sale.

**3. Set purchase limits**

Use **Limit Qty per Order** and **Limit Qty per User** to stop a single buyer from taking too many tickets for a popular day.

**4. Turn days on or off**

Use the **Status** dropdown to keep a day **Inactive** until you are ready to announce it.

## Add tiers to each day

Want Early Bird pricing for every day? Build a [release chain](/tickets/scenario-ga-tiers) for one session, then copy it:

**1. Build the chain on one session**

Create and fill the chain for Friday's tiers, such as Early Bird then Day Pass.

**2. Copy it**

Select **Copy to...** on the chain card, then tick the other sessions.

**3. Review the matches**

The portal matches tiers by name. If your tickets are named the same on each day (for example "Early Bird" in every session), they match automatically. Otherwise, choose the right ticket for each tier, or **Don't copy this tier**.

**4. Turn Auto-release on for each copy**

Copied chains start paused. Review the copies (and fix any sales end times the portal flags), then switch **Auto-release** on in each session.

> [!TIP]
>
> Use consistent ticket names across days, such as "Early Bird" and "Day Pass", so copying and reporting stay simple.

## What about a full-festival pass?

The portal manages tickets inside each session. A ticket that is valid across all days is not something you build in this portal today. If you need a pass for the whole festival, talk to your PLVR representative about how to set it up for your event. For groups that want several tickets at once, see [Group packages](/tickets/scenario-bundles).

## Track and operate

* In the [Ticket Report](/tickets/ticket-report), choose a **Session** to see only that day's sales, or export it to CSV.
* When comping artists or press, choose the **Session** in the comp form so each guest gets a ticket for the right day. See [Comping guests](/tickets/scenario-comp-guests).
* Promo codes can apply to **All ticket types** or to one ticket in one session, so you can discount only a slow day. See [Discount campaigns](/tickets/scenario-promo-discounts).

## Related

* [Ticketing Concepts](/tickets/concepts)
* [Ticket Management reference](/tickets/ticket-management)


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