These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Theme Park Management
- Features
- Events and capacity
Events and capacity
Operating days and events with venue, capacity and approval.
OverviewEvents in review×
Theme Park Management · Events and capacity
New
Events in review
Approval waits for the park operations manager
| Record number | Subject | Counterparty | Starts at | Capacity | Revision | |
|---|---|---|---|---|---|---|
| EVN-26574 | Review evn-965 | VNS-8494 | 06 Oct | 410 | 650 | |
| EVN-30700 | Review evn-695 | VNS-6877 | 21 Oct | 540 | 480 | |
| EVN-81386 | Review evn-177 | VNS-8592 | 04 Oct | 190 | 550 | |
| EVN-17680 | Review evn-170 | VNS-3857 | 21 Oct | 560 | 400 | |
| EVN-65201 | Review evn-679 | VNS-2929 | 20 Oct | 510 | 590 |
6 of 6 records
Review evn-965Events · EVN-26574
CounterpartyVNS-8494
Starts at06 Oct
Capacity410
Revision650
What you can do
Open the gates only when the day is ready
Everything in the park hangs off an operating event: a regular day, a night event or a ticketed show. Each has a venue, a start and end, a capacity and an owner. It moves from draft to review, approved, open, completed or cancelled, and its revision number rises with each change so decisions are always made on the current version.
Capacity is the number the gates work to. Reservations count against it, and nothing is sold beyond it. An event is approved and opened only when its capacity is valid and its rides have been released for the day. That ties the commercial decision to sell tickets to the operational fact that the rides are ready.
How the work is organized
The park operations manager plans and approves events; ride and gate teams work inside them.
- Venue and capacity on the event. Every event names its venue and its capacity.
- Opens on readiness. Approval checks the event’s ride readiness before it opens.
- One owner. Each event has an owner who answers for it.
What to agree during setup
Agree how you split the year into operating events, such as one per day, separate night events and special ticketed shows. Agree capacities per venue and event type and who approves events. Prepare examples of a normal day, a night event with lower capacity, a day where one ride is not ready and a cancelled event.
Check the handoff on an actual case
The manager plans a Halloween night event in the main park with a capacity of 4,000. It goes to review while ride operators check the rides. When all the night’s rides have been released, the manager approves the event and it opens for sale and entry. The gates then work to the 4,000 limit, and the event record shows who approved it and when.
If one coaster had failed its inspection, the event could still open with that ride closed. The ride’s readiness record would show it as rejected and the guests would never be sold a ride that was not running.
What your team sees
- Event schedule — Upcoming and open events with start, end and capacity.
- Event lifecycle board — Events by status.
- My events — Events each manager owns.
Follow the work through
- Event to open gates: From a planned event to open gates.
Review the implementation plan before loading events.
What it keeps track of
Data model- Events
- Park operating events with capacity, lifecycle and revision control.
- Venues
- Park venues and operating sites eligible for events.
- Organizations
- Park operating organizations with time zone and currency scope.
Who uses it
Permissions- The manager plans, approves, closes and cancels events.
Set up Theme Park Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.