> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://learn.nuwebgroup.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://learn.nuwebgroup.com/_mcp/server.

# What is an event schedule in ticketing?

> An event schedule connects one event or production to its dates, performances or timed sessions. It lets an operator manage a run without recreating th

**An event schedule connects one event or production to its dates, performances or timed sessions. It lets an operator manage a run without recreating the underlying event information for every occurrence.**

## Event, occurrence and ticket: what is the difference?

An **event** typically holds the common identity: title, organiser, description and sometimes venue. An **occurrence** or **instance** is the specific date and time at which the event takes place. The **ticket** grants entry to an occurrence, a set of occurrences or a defined entitlement, depending on the product design.

A theatre production might run for six weeks with a separate performance each night. A tour might have the same show name across multiple venues. A visitor attraction might operate half-hour entry sessions. These cases can look alike in a calendar but need different inventory models.

## Which settings belong to each occurrence?

| Shared across a run                 | May vary by occurrence                                |
| ----------------------------------- | ----------------------------------------------------- |
| **Production name and description** | Start time, venue and sales window                    |
| **Brand and general images**        | Capacity, seating layout and price                    |
| **General customer information**    | Availability, restrictions and admission instructions |

Some products deliberately enforce shared settings for all occurrences. Other platforms offer granular overrides. The distinction is important when a matinee requires a lower price, one session is accessible-only or an added date uses a different layout.

## How should changes be handled?

Changing an occurrence after tickets have sold is not merely editing a calendar entry. The platform must identify affected orders, communicate the new timing and preserve the relationship between issued tickets and the correct performance. It should distinguish cancelling one occurrence from cancelling the whole event. If a customer can choose among multiple dates, show the date prominently through purchase, confirmation and entry.

## What should buyers test?

Create a recurring run, change one date's capacity, cancel one performance and export sales by occurrence. Test whether a customer can purchase tickets for two different dates without confusing confirmation details. An event schedule is useful only when the customer journey and operational reports remain tied to the correct occurrence.

## Related explanations

#### [What is a ticket type and how is it different from a price band?](/events-inventory/what-is-a-ticket-type-and-how-is-it-different-from-a-price-band)

Events & Inventory · Event and ticket setup

#### [How do ticketing platforms handle ticket bundles and passes?](/events-inventory/how-do-ticketing-platforms-handle-ticket-bundles-and-passes)

Events & Inventory · Event and ticket setup

[More in Events & Inventory →](/events-inventory)