Notes
(notes by Justin L. Karr)
Considerations
Trigger
- Have engagement
Actions
- Start Scheduling
Questions:
- How many performances?
- How expensive?
- Price?
- Schedule?
- Date?
- Times?
- # of Perfs?
- Title?
- Description?
- Who will run the Box Office? [Need to Assume it is Producer for Core Case]
- What is the Deal? [Rental? BO Split? Something Else?]
- Type of Payments Accepted?
- What is the Method of Delivery?
- Will there be Designated Seating?
- What are the Patron Conditions?
- Types
- Relative to Patron Needs
- Exclusionary Conditions
- Age?
- Language?
- Content?
- Strobe Lights?
- How Many Tickets are we selling?
- How Many Ticket each way [if multiple Methods of Delivery]?
- Sales Schedule
- Patrons
- Always have to Build House
- Identify Allocations and Reservations
- How Many in each Allocation?
- Even for General Admission? [Yes]
- Allocation is Number of Tix but not Geographical Location [per Run, per Perf aka Press, Opening, ADA Perf, etc. OR per segment ala Each Sat Night]
- Additional Information Ticket for Bundled Event [Opening Night Party, etc.]
Base Case
- House manager needs list of purchases and/or patrons to validate tickets at the performance.
- Question: Do we need a ticket? ["BIG Q!"]
- After building show, then create on-sale schedule.
- Sale Schedule
- Who [has access to tickets]?
- Out of which allocation?
- When [are tickets available]?
- How many [tickets are available]?
- MUST have security to enforce this.
- Approval Workflow
- Venue set parameters
- For Producer
- Schedule
- Sale Schedule: Producer in Marketing Role
- Work Schedule
- Plan Criteria
- Approval of Criteria
- Load Systems
- Load Test & Approval
- Announcement
- On-Sale: Pre-Sale
- On-Sale: Regular Sales
- Fill Seats as Needed AND Change Criteria as Needed
Concerns
- Base case should have multiple prices per performance. [Multiple Model]
- Workflow Idea: Declaration from all parties at beginning
- Workflow Idea: Workflow Roles
- Testing Tools Very Important ---> All Work Must Be Validated
- Contractual Question [Union/Performer Contracts] - System should inform user if configuration creates a contractual violation.
