Overview
This page collects data about how your venues with fixed seating are used throughout the year, including ticketed and non-ticketed activities, and tracks attendance for various event types. The data provides insight into venue utilization patterns and audience engagement.
Fields
Presenter Types
💡 These are classifications used to categorize events, they're not input fields on their own.
Field | Center Presentations |
Description | Programs sponsored and marketed by the PAC, including productions |
Required | - |
Example |
|
Type of data | Classification (not an input) |
Validation | Classification (not an input) |
Source | Event Records |
Field | Resident Company |
Description | Performances by any organization designated by the Center as a resident |
Required | - |
Example |
|
Type of data | Classification (not an input) |
Validation | Classification (not an input) |
Source | Event Records |
Field | Non Profit Rental |
Description | Programs put on by 501(c)3 organizations |
Required | - |
Example |
|
Type of data | Classification (not an input) |
Validation | Classification (not an input) |
Source | Event Records |
Field | Commercial Rental |
Description | Programs put on by for-profit companies, presenters, artists, or other entity. |
Required | - |
Example |
|
Type of data | Classification (not an input) |
Validation | Classification (not an input) |
Source | Event Records |
Venue Configuration
Field | Seat Count |
Description | Typically, the number of usable fixed seats in all active venues where ticketed activity takes place (excludes alternative venues like lobbies and plazas as well as venue seats that are not allocated for sale or comps by Box Office). As seating capacity can fluctuate, we recommend recording the range from minimum to maximum over a season. Total seats is unrelated to the number of events (see Available seats) |
Required | ✓ |
Example |
|
Type of data | Number |
Validation | Must be a positive integer |
Source | Venue Records |
Used in Measures | Available Seats |
Event Counts
Field | # Events |
Description | Total number of events for the fiscal year in a particular genre by a particular presenter type, in that venue. Each performance (curtain) should be considered a separate event. (For example: a one week Broadway run would typically total 8 events.) |
Required | ✓ |
Example |
|
Type of data | Number |
Validation | Must be a positive integer |
Source | Event Records |
Field | Tickets Sold |
Description | The total number of tickets sold for events. Note: this in NOT attendance or drop count, but should measure total sales volume. |
Required | - |
Example |
|
Type of data | Number |
Validation | Must be a positive integer |
Source | Sales Records |
Utilization Days
Field | Performance Days |
Description | Days on which one or more performance open to the public takes place. Generally, revenue-generating activity and may include more than one performance. If a single day includes a load-in and a performance, the day is considered a performance day. |
Required | ✓ |
Example |
|
Type of data | Number |
Validation | Must be a positive integer |
Source | Calendar management |
Used in Measures | Use Days |
Field | Non-Performance Days |
Description | Days on which one non-performance, revenue-generating, activity takes place. Days may attain this utilization label when the venue is dark during a run, or the PAC hosts a wedding or corporate meeting. If the venue is dark during a run, the PAC may not offer the venue to another renter or present themselves, but no performance takes place. |
Required | ✓ |
Example |
|
Type of data | Number |
Validation | Must be a positive integer |
Source | Calendar management |
Used in Measures | Use Days |
Field | Rehearsal Days |
Description | Generally, revenue-generating, rehearsal days suggest facility use absent of ticketed performance. May require stagehands and security. |
Required | ✓ |
Example |
|
Type of data | Number |
Validation | Must be a positive integer |
Source | Calendar management |
Used in Measures | Use Days |
Field | Tech Days |
Description | Generally, revenue-generating, tech days may include load-in or out, or technical activity. |
Required | ✓ |
Example |
|
Type of data | Number |
Validation | Must be a positive integer |
Source | Calendar management |
Used in Measures | Use Days |
Field | Maintenance Days |
Description | Generally, not revenue-generating, maintenance days are a fundamental requirement for any active venue. Most enterprise-scale PACs utilize no less than 2 weeks per year for individual venue maintenance. |
Required | ✓ |
Example |
|
Type of data | Number |
Validation | Must be a positive integer |
Source | Calendar management |
Used in Measures | Use Days |
Field | Dark Days |
Description | Day in which the space generates no revenue. Activity such as usher training or internal meetings that utilize venue space are considered dark. |
Required | ✓ |
Example |
|
Type of data | Number |
Validation | Must be a positive integer |
Source | Calendar management |
Used in Measures | Use Days |
Tips for This Section
Each day of the year should only be counted in one category, using the highest-level activity for that day
Performance days take precedence over other types of use
Ensure your total utilization days add up to 365 (or 366 in leap years)
Keep detailed calendar records to accurately track venue usage or use nested logic to automate reports from your calendar tools
Example: Finding the right Utilization Day Category
A rehearsal took place on Tuesday of this week. Then a performance happened in the evening later that day. That Tuesday is counted as a "Performance Day"
Related Resources
Understanding Venue Utilization Metrics