Supervisor, Ticket Operations

We need to output HTML fragment with sections: About the role? The posting includes description of responsibilities, qualifications, benefits, salary range, work environment, physical abilities maybe. We need to follow rules: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to decide which sections to include. The posting includes: description of responsibilities (under direction of Entertainment Manager...), qualifications (High School Diploma...), benefits (Benefits Include...), salary range (Salary Range $52,000-$62,000). Also work environment and physical abilities. Could include "Work Environment" and "Physical Abilities" but those are not in the list of allowed headings? The list includes: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map content accordingly. "Responsibilities" can hold duties. "Qualifications" can hold education, experience, skills. "Benefits" holds benefits. "Pay" holds salary range. "Work Environment" and "Physical Abilities" are not in allowed headings; we could either omit them or incorporate them into other sections? The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying these are examples, not exclusive? But later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text ... and never create Pay/Schedule/Benefits sections unless the posting actually states them." It doesn't forbid other headings, but the examples suggest typical sections. However, to be safe, we could include only those sections that have content: Responsibilities, Qualifications, Benefits, Pay. Possibly also "About the role" could be a brief summary from first paragraph about team members health etc. That is generic company statement; could be considered About the role? It's more about company benefits. Might be better to put that in About the role? The first paragraph: "Our team members are the key to our company’s success, and their health and well-being, as well as that of their families, is very important to us. We offer a comprehensive benefits package that allows our team members stay healthy, plan for their future and maintain a healthy work-life balance. Benefits may vary with employment status. To see our fill list of Team Member Benefits please visit our career site: www.gotoworkhappy.com/benefits". That's generic benefits statement, but we already have Benefits section with specifics. Could treat that as About the role? Not exactly. Might be better to omit About the role because it's generic fluff. The instruction says prefer a few substantive sections over many thin ones. So we could include Responsibilities, Qualifications, Benefits, Pay. That seems sufficient. We need to extract responsibilities list: many sentences. We'll turn into

  • items. Must preserve all substantive information; do not invent or summarize away detail. So we need to list each duty as separate bullet. Let's parse responsibilities paragraph: "Under the direction of the Entertainment Manager, incumbent assists in effectively managing the daily operations and staff of the Box Office. Assist in overseeing events, upholds exemplary guest service standards and maintains internal Box Office controls. Generates & distributes the daily ticket count report for all shows. Assist in building concerts and other events in the Ticketmaster system. Manages cash/credit reconciliation of daily sales and deposits and prepares corresponding reconciliation reports. Process internal, external and season ticket orders. Coordinates ticket printing for Casino Marketing Player Development, advertising and promotional tickets. Communicate ticketing information regularly and assist other departments with same. Resolve customer service issues as necessary. Maintain accurate box office accounting records and archives. Develop department members’ knowledge and skills through education, training, coaching, corrective counseling, etc. Ensure appropriate staffing levels to best manage labor costs while maintaining outstanding guest service. Monitors the performance of department direct reports and team members. Ensures only the most qualified candidates are selected for open positions. Monitor and order office and ticketing supplies for department. Inputs & uploads upcoming events in Ticketmaster Access Manager System for accurate event drop counts. Prepare Accounts Receivables Box Office invoices. Uploads all database entries into Ticketmaster Mail Manager System. Supervises daily ticket sales and will call operations. Responsible for submitting staff time and attendance reports to payroll. Efficiently and courteously answer questions concerning pricing, seating and events. Demonstrates excellent customer service skills, responds to customer needs, responds to requests for service and assistance, Performs other duties and responsibilities as assigned." We need to split each sentence into bullet. Some sentences have multiple actions but we can keep as one bullet. Now qualifications: "High School Diploma or equivalent required and 2-3 years Box Office/Supervisory experience, preferably in the entertainment field. Must have Classic Ticketmaster, Ticketmaster Access Manager & Mail Manager computer experience. Working knowledge of Microsoft Office applications (Outlook, Word, Excel, etc.). Must be able to create, manipulate and update Excel spreadsheets. Experience in box office training and guest relations is essential. To perform this job successfully, an individual must be able to perform each essential duty satisfactorily. The requirements listed below are representative of the knowledge, skill, and/or ability required. Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions." Then there is a Physical Abilities table but we might ignore because not in allowed headings and it's detailed but could be considered part of Qualifications? Might be considered "Requirements". The list includes Requirements as a possible heading. Could put physical abilities under Requirements. But the instruction says we can use Requirements heading. However we have Qualifications already; maybe we should use Requirements for physical abilities and other non-education requirements. But we already have qualifications covering education, experience, skills. The physical abilities could be part of Requirements. However we need to decide whether to include Requirements section. The posting includes a table of physical abilities with percentages. That's substantive. So we could include a Requirements section for physical abilities. But we also have Qualifications section for education/experience/skills. The instruction says prefer a few substantive sections over many thin ones. Having both Qualifications and Requirements may be okay if both have substantive content. But we could merge them into Qualifications (including physical abilities). However the heading list includes Qualifications and Requirements as separate examples; we can choose to use only Qualifications and include everything there. That would reduce number of sections. The instruction: "Prefer a few substantive sections over many thin ones." So maybe better to have just Qualifications (including education, experience, skills, physical abilities) and Responsibilities, Benefits, Pay. That's four sections. But we need to ensure we don't miss any substantive info: The physical abilities table is quite detailed; if we put it in Qualifications as a list, we need to preserve all info. Could we represent as
    • items? The table has categories: Lift, carry or restrain up to 10 pounds etc with percentages. We could convert each row to a bullet like "Lift, carry or restrain up to 10 pounds: None (0%)" etc. But we need to preserve the percentages exactly. Let's extract the table: Physical Abilities Percent of Time None Under 1/3 Seldom to Occasionally To 2/3 Occasionally to Frequently Over 2/3 Constantly Lift, carry or restrain up to 10 pounds X Lift, carry or restrain up to 25 pounds X Lift, carry or restrain up to 50 pounds X Lift, carry or restrain up to 100 pounds X Lift, carry or restrain more than 100 pounds X Push/Pull up to 10 pounds X Push/Pull up to 25 pounds X Push/Pull up to 50 pounds X Push/Pull up to 100 pounds X Push/Pull up more than 100 pounds X Overhead Reach X Interpretation: The columns indicate percent of time: None, Under 1/3 (Seldom to Occasionally), To 2/3 (Occasionally to Frequently), Over 2/3 (Constantly). The X marks which column applies. So each row has an X under one column. For example, first row: Lift, carry or restrain up to 10 pounds X under "None"? Actually the X is under the first column after the description? Let's map: The header row: "Physical Abilities Percent of Time None Under 1/3 Seldom to Occasionally To 2/3 Occasionally to Frequently Over 2/3 Constantly". Then rows: each has description then an X under one of the columns. So we need to interpret which column the X is under. The formatting is ambiguous but likely each X corresponds to the column after the description. Let's assume each row's X is under the first column (None) for all? That seems unlikely. Probably the X moves across columns as the weight increases. But we cannot guess. Safer to preserve the table as is? But we cannot use tables? Not prohibited but we should use
      • for lists. Could we keep the table as or something? Not ideal. Perhaps we can omit physical abilities because it's not in allowed headings and might be considered too detailed but still substantive. However the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we must include it somehow. We could include a Requirements section with a
        • list describing each physical ability with its frequency. We need to deduce the mapping. Let's attempt to infer: Usually such tables list increasing weight and the frequency decreases. For lifting up to 10 pounds: likely "None" (i.e., not required). For 25 pounds: maybe "Under 1/3". For 50 pounds: "To 2/3". For 100 pounds: "Over 2/3". For more than 100 pounds: "Constantly". Similarly for push/pull. Overhead reach maybe "Constantly". Let's test: The pattern of X's: each row has an X under a different column moving right. The rows are: 1 Lift, carry or restrain up to 10 pounds X 2 Lift, carry or restrain up to 25 pounds X 3 Lift, carry or restrain up to 50 pounds X 4 Lift, carry or restrain up to 100 pounds X 5 Lift, carry or restrain more than 100 pounds X 6 Push/Pull up to 10 pounds X 7 Push/Pull up to 25 pounds X 8 Push/Pull up to 50 pounds X 9 Push/Pull up to 100 pounds X 10 Push/Pull up more than 100 pounds X 11 Overhead Reach X If the X moves one column to the right each row, then mapping would be: Row1: None Row2: Under 1/3 Row3: To 2