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

# Mid-size events

> Multi-tier ticketing, promotions and tracking, and an onsite scanning team for events of a few hundred to a few thousand guests.

## Who this is for

You run an event with several ticket tiers, a marketing push through partners and channels, and a team at the gate on the day.

## What to set up

In priority order:

1. **Agree your ticket plan with the PLVR team.** Ticket types, sessions and bundles are arranged with your PLVR representative, not created in the portal. Read [Ticketing concepts](/tickets/concepts) first so you know what to ask for.
2. **Set up tier sales.** Use a release chain so each tier opens automatically after the last. See [General Admission in tiers](/tickets/scenario-ga-tiers) and [Ticket Management](/tickets/ticket-management).
3. **Prepare the event page.** See [Event editor](/events/event-editor) and the [Registration form](/events/registration-form).
4. **Set up promotions.**
   * [Promo codes](/promotions/promo-codes) for partners or limited-time offers. See [Discount campaigns](/tickets/scenario-promo-discounts).
   * [Tracking links](/promotions/tracking-links) per channel.
   * [Affiliates](/promotions/affiliates) if you want partners to earn commission.
5. **Handle guests.** Issue [complimentary tickets](/tickets/scenario-comp-guests) for artists, press and sponsors.
6. **Prepare your scanning team.** Create login codes in [Onsite staff](/onsite/onsite-staff) and practice with the [Command Center](/onsite/command-center).
7. **Watch sales.** Use the [Ticket report](/tickets/ticket-report) and [Audience](/organization/audience).

## What to skip

* PLVR Tap, unless cashless is part of your plan.
* Multiple sessions, unless your event runs over several days.

## Team shape

Split work across the [Core team](/roles/core-team), [Marketing team](/roles/marketing-team), [Scanning team](/roles/scanning-team) and [Data team](/roles/data-team). One person can wear more than one hat.

## Common pitfalls

* Promo codes that overlap with a tier discount, making prices confusing.
* Tracking links without consistent campaign names, which makes channels hard to compare.
* Sending the scanning team to the gate without testing their login codes.


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