Global Operations - Event Ticketing Coordinator
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include sections only when posting has real specific content. We have "Who We Are" (company overview) maybe not required but could be considered "About the role"? The role description is under "The Role". Could map to "About the role". Also we have Responsibilities, Requirements (they have a "Requirement" section). Also we have Location, Compensation (Pay). Benefits: they mention eligible for benefits and discretionary bonus but no specifics; we should not create Benefits section unless posting actually states them (they say eligible for benefits and a discretionary bonus, but not specifics). The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. They do state compensation: base hourly rate $23-26, eligible for benefits and discretionary bonus. So we can include Pay section with that info. Benefits: they mention eligible for benefits but not details; maybe we should not create Benefits section because no specific benefits listed. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." For Benefits, they state "eligible for benefits and a discretionary bonus." That's stating benefits exist but not specifics. Might be okay to include Benefits section with that statement? However they said "prefer a few substantive sections over many thin ones." Might be better to combine Pay and Benefits? But they said use headings for Benefits, Pay, Schedule. If we include Benefits, we need to have substantive content. The posting says "eligible for benefits and a discretionary bonus." That's substantive enough? It's not detailed but it's a statement. I'd include Benefits section with that sentence.
Schedule: not mentioned. So no Schedule.
We need to remove boilerplate: EEO, legal, application instructions, etc. Also remove duplicated lines.
We need to preserve all substantive information: Who we are, The Role, Responsibilities, Requirement, Location, Compensation.
We need to format with headings and appropriate
or
- .
We must not repeat job title as heading. Job title is "Event Ticketing Coordinator". Not to be used as heading.
We must not put Job ID/requisition numbers as headings (none present).
We need to output only HTML fragment.
Let's craft:
About the role
Creative Artists Agency (CAA) is the leading entertainment and sports agency, with global expertise in filmed and live entertainment, digital media, publishing, sponsorship sales and endorsements, media finance, consumer investing, fashion, trademark licensing, and philanthropy. Distinguished by its culture of collaboration and exceptional client service, CAA’s diverse workforce identifies, innovates, and amplifies opportunities for the people and organizations that shape culture and inspire the world. The trailblazer of the agency business, CAA was the first to build a sports business, create an investment bank, launch a venture fund, found technology start-up companies, establish a philanthropic arm, build a business in China, and form a brand marketing services division, among other innovations. Named Most Valuable Sports Agency by Forbes for eight consecutive years, CAA represents more than 2,000 of the world’s top athletes in football, baseball, basketball, hockey, soccer, in addition to coaches, on-air broadcasters, and sports personalities and works in the areas of broadcast rights, corporate marketing initiatives, social impact, and sports properties for sales and sponsorship opportunities. Founded in 1975, CAA is headquartered in Los Angeles, and has offices in New York, Nashville, Memphis, Chicago, Miami, London, Munich, Geneva, Stockholm, Shanghai, and Beijing, among other locations globally.
But maybe "About the role" should be about the role itself, not company overview. However the instruction says use headings like About the role, Responsibilities, etc. The "Who We Are" could be considered "About the role"? Might be okay. Alternatively we could omit About the role and just start with Responsibilities. But we need to preserve all substantive information; we could put company overview under awithout heading? The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we must have About the role; it's just examples. We could choose not to include About the role if we think it's not needed. But we need to preserve all substantive information; we could include a
before first heading? The instruction says output ONLY the HTML fragment; we can have
without heading. It didn't forbid that. So we could start with a
containing the "Who We Are" paragraph, then
About the role
with description of the role (the paragraph under "The Role"). Let's do that. Then Responsibilities- ... each responsibility as li.
Then Requirement
- ... each requirement as li.
Then Location
This role will be based out of our Los Angeles office.
Then PayThe base hourly rate for this position is in the range of $23.00 - $26.00. This position is also eligible for benefits and a discretionary bonus.
We could also add Benefits section with that same sentence? But we already included in Pay. Better to keep Pay only. We must not include schedule. Now ensure we removed boilerplate: EEO, legal, application instructions, etc. Check for duplicated lines: none. Now produce HTML. Let's list responsibilities exactly as in posting: - Become a subject matter expert related to each event venue’s online event ticketing platform and portals. - Be responsible for all internal communications to effectively communicate this benefit companywide. - Manage incoming event ticket requests on a daily basis. - Partner with decision makers within various business units to consolidate request lists and submit lists in a timely fashion for review & approvals. - Provide after-hours, evening, and weekend support as needed to ensure all ticketing requests are fulfilled as directed. - Maintain records of all tickets distributed and provide monthly reporting related to ticket usage for both business and personal requests. - Understand and manage contract payments for each venue and be aware of contract terms and renewals. - Fulfill individual ticket purchases for clients and employees to home games for the Rams, Chargers, Lakers, and Clippers. - Manage food and beverage orders for venues as needed. Now requirements: - The successful candidate for this role will have 2-3 years of event management and/or ticketing experience at a global company, preferably in entertainment/production. - Ability to work well under pressure; meet tight deadlines; manage multiple projects and expectations; and maintain a sharp focus while managing competing priorities. - Attention to detail, strong organization, and problem-solving skills are a must. - Strong knowledge of ticketing platforms, distribution tools, Excel, and PowerPoint. - Demonstrates strong communication and client relationship management skills. - Must have the ability to review and provide comprehensive reporting related to ticketing. - Able to function effectively as part of a loosely coupled but highly aligned team. - Flexible, with the ability to pivot and adjust to the needs of the department. - Excels in internal customer service. - Able to anticipate potential problems and knows when to ask for assistance and escalate issues when needed. - Aware that the world of Events is not a 9-5 job and be prepared to do what it takes to complete tasks and get the job done to meet deadlines. - Creative and out-of-the-box thinking is required, as well as a “yes” attitude for our employees and clients. Now location: "This role will be based out of our Los Angeles office." Compensation: "The base hourly rate for this position is in the range of $23.00 - $26.00. This position is also eligible for benefits and a discretionary bonus. Ultimately, wages may vary based on, but not limited to, relevant experience, time in role, business sector, and geographic location, among other criteria. Please speak with a CAA Recruiter to learn more." The last sentence about speaking with recruiter is maybe application instruction? It's not exactly instruction to apply but it's a note. Might be considered boilerplate? It's not EEO/legal but it's a referral to recruiter. Might be considered part of compensation description; we can keep it? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The sentence "Please speak with a CAA Recruiter to learn more." is not exactly an application instruction but could be considered a note. Might be okay to keep. However "Please provide complete and legible information. An incomplete application may affect your consideration for employment." That's application instruction; we must remove that. Also the EEO block we must remove. Thus we keep compensation up to "Ultimately, wages may vary based on, but not limited to, relevant experience, time in role, business sector, and geographic location, among other criteria." That's substantive. Now produce HTML. We'll start with afor Who We Are. Let's craft:
Creative Artists Agency (CAA) is the leading entertainment and sports agency, with global expertise in filmed and live entertainment, digital media, publishing, sponsorship sales and endorsements, media finance, consumer investing, fashion, trademark licensing, and philanthropy. Distinguished by its culture of collaboration and exceptional client service, CAA’s diverse workforce identifies, innovates, and amplifies opportunities for the people and organizations that shape culture and inspire the world. The trailblazer of the agency business, CAA was the first to build a sports business, create an investment bank, launch a venture fund, found technology start-up companies, establish a philanthropic arm, build a business in China, and form a brand marketing services division, among other innovations. Named Most Valuable Sports Agency by Forbes for eight consecutive years, CAA represents more than 2,000 of the world’s top athletes in football, baseball, basketball, hockey, soccer, in addition to coaches, on-air broadcasters, and sports personalities and works in the areas of broadcast rights, corporate marketing initiatives, social impact, and sports properties for sales and sponsorship opportunities. Founded in 1975, CAA is headquartered in Los Angeles, and has offices in New York, Nashville, Memphis, Chicago, Miami, London, Munich, Geneva, Stockholm, Shanghai, and Beijing, among other locations globally.
About the role
Creative Artists Agency (CAA) is seeking an Event Ticketing Coordinator to join the CAA Global Business Services team. This individual will be responsible for supporting CAA’s Event Ticketing Program and support all related ticketing activities. The ticketing coordinator will be required to closely partner with the various stakeholder teams (Music & Sports) to understand their unique needs and be able to manage the request & reporting tools, communications, partners, and resources with a strong customer experience mindset. They actively review and seek opportunities for process improvements and cost savings. The role will report to the head of Global Business Services.
Responsibilities
- Become a subject matter expert related to each event venue’s online event ticketing platform and portals.
- Be responsible for all internal communications to effectively communicate this benefit companywide.
- Manage incoming event ticket requests on a daily basis.
- Partner with decision makers within various business units to consolidate request lists and submit lists in a timely fashion for review & approvals.
- Provide after-hours, evening, and weekend support as needed to ensure all ticketing requests are fulfilled as directed.
- Maintain records of all tickets distributed and provide monthly reporting related to ticket usage for both business and personal requests.
- Understand and manage contract payments for each venue and be aware of contract terms and renewals.
- ... each requirement as li.
Then Location
- ... each responsibility as li.
Then Requirement