Event Operations Coordinator

We need to output HTML fragment with sections: About the role? Actually we have "About The PWHL" then "Position Summary". We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We need to include sections only when posting has real specific content. So we need to parse content. Content includes: - About The PWHL (description of league). That could be "About the role"? Actually "About The PWHL" is about the organization, not role. But we can treat as "About the role"? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map sections accordingly. We have "About The PWHL" which is about the organization; maybe we can treat as "About the role"? But it's not exactly about role. However we need to include a section only when posting has real specific content for it. The posting includes an "About The PWHL" paragraph. That is substantive. So we could create a section heading

About the PWHL

but the instruction says use headings like About the role etc. It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exclusive? Likely they expect those exact headings. But we can adapt: we have content that matches "About the role"? Not exactly. Could we treat "About The PWHL" as "About the role"? Might be okay. However they said "Do NOT repeat the job title as a heading (the page already shows it)". So we can use "About the role" heading and put the PWHL description there. That seems plausible. Then we have "Position Summary" which could be considered part of About the role? Or we could combine with About the role. But we can also treat "Position Summary" as a separate section? Not in list. Might be better to merge into About the role. Then we have "Key Duties & Responsibilities" -> Responsibilities section. Then "Required Qualifications" -> Requirements or Qualifications? We have both Required Qualifications and Preferred Qualifications. Could map Required Qualifications to Requirements (or Qualifications). Preferred Qualifications could be Skills? Or we could have Qualifications section containing both required and preferred? The instruction says use headings like Requirements, Qualifications, Skills. We could have Requirements for required qualifications, Qualifications for preferred? Or Skills for preferred? Let's think. We have "Required Qualifications" list: Bachelor's degree, 1 year experience, strong organizational skills, flexibility to work evenings weekends travel. We have "Preferred Qualifications": Experience in professional sports, live events, or hockey; Flexibility to work evenings, weekends, and travel as required (duplicate); Flexibility & Travel: Candidate must be able to work remotely, with regular travel required. Also we have Pay range: $46,000 to $50,000 USD/CAD annually. We have Schedule? Not explicitly, but flexibility to work evenings, weekends, travel as required indicates schedule expectations. Could create Schedule section? The instruction says only create Pay/Schedule/Benefits sections if posting actually states them. We have pay range, so we can create Pay section. For Schedule, we have mention of flexibility to work evenings, weekends, travel as required. That's schedule info. So we can create Schedule section. Benefits: Not mentioned. So we omit Benefits. Skills: Could be derived from required qualifications: strong organizational, project management, and communication skills. Also maybe flexibility. Could create Skills section. But we must not create sections with filler text like "commensurate with experience". We have actual content. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details. We need to output only HTML fragment, no /, no markdown fences. We'll structure:

About the role

... (About The PWHL + Position Summary combined)

Responsibilities

• ... each duty

Requirements

• ... required qualifications

Skills

• ... maybe from required qualifications: Strong organizational, project management, and communication skills

Pay

The pay range for this position is $46,000 to $50,000 USD/CAD annually.

Schedule

• Flexibility to work evenings, weekends, and travel as required
• Candidate must be able to work remotely, with regular travel required to support Takeover Tour and other league events.

We need to ensure we don't duplicate content. The Preferred Qualifications includes "Experience in professional sports, live events, or hockey" and duplicate flexibility line. We could add that to Skills or Requirements? It's preferred, not required. Could add to Skills or maybe a separate "Preferred Qualifications" but not in allowed headings. Could add to Skills as preferred skills. Or we could add to Requirements but note it's preferred? Better to add to Skills as preferred skills. We also have "This position may be based in either the United States or Canada. Applicants must be legally authorized to work in their country of residence on a full-time basis." That's location/eligibility. Could be part of Requirements? Might be a separate section like "Location" but not in list. Could incorporate into Requirements as a bullet. Also "This posting is for a newly created position." Could be a note in About the role. Also "A background check will be conducted once a successful candidate is identified." That's boilerplate? Might be considered legal/EEO? It's not EEO but it's a standard hiring process. Might be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Background check might be considered legal boilerplate; but it's substantive? It's a condition of employment. Might be okay to keep? Not sure. Safer to omit as it's generic. However it's not exactly EEO. But it's a standard statement. I'd lean to omit to avoid boilerplate. Also "The Professional Women’s Hockey League is an equal opportunity employer..." that's EEO boilerplate, remove. Thus we will omit those. Now we need to ensure we preserve all substantive information: About PWHL, Position Summary, duties, required qualifications, preferred qualifications (experience in professional sports, live events, or hockey), flexibility to work evenings weekends travel, remote work, regular travel, pay range, location (US/Canada, work authorization), newly created position. We need to include location and work authorization somewhere. Could add to Requirements bullet: "Applicants must be legally authorized to work in their country of residence on a full-time basis." and "Position may be based in either the United States or Canada." We also need to include "This posting is for a newly created position." Could add to About the role paragraph. Now let's craft the HTML. We'll need to escape any special characters? Not needed. Let's write:

About the role

The Professional Women’s Hockey League delivers world-class competition and fosters meaningful connections with fans and communities through operational excellence, purposeful partnerships, and a focus on long-term sustainability. The league is dedicated to cultivating a workplace and league culture rooted in integrity, innovation, and inclusion, on and off the ice. The Event Operations Coordinator plays a key role in bringing the PWHL's Takeover Tour and other league events to life. Reporting to the Manager, Event Operations, this position supports event logistics, stakeholder communications, venue coordination, credentialing, and onsite operations to ensure every event is delivered successfully. The ideal candidate is highly organized, detail-oriented, and energized by fast-paced, multi-project environments. This posting is for a newly created position. The role may be based in either the United States or Canada, and applicants must be legally authorized to work in their country of residence on a full-time basis.

Responsibilities

• Support planning and execution of Takeover Tour events and other league events, from early planning through onsite delivery
• Coordinate venue logistics, vendor relationships, and operational documentation
• Prepare event schedules and information packages to keep teams and stakeholders informed
• Serve as a communications point of contact for teams, league staff, officials, and event partners, including credential management
• Travel to support onsite event operations, including setup, execution, breakdown, and troubleshooting

Requirements

• Bachelor's degree in Sport Management, Event Management, Business, or a related field
• Minimum of 1 year of experience in hockey operations, event management, or a related field
• Strong organizational, project management, and communication skills
• Flexibility to work evenings, weekends, and travel as required
• Applicants must be legally authorized to work in their country of residence on a full-time basis
• Position may be based in either the United States or Canada

Skills

• Experience in professional sports, live events, or hockey (preferred)
• Ability to work remotely
• Regular travel required to support Takeover Tour and other league events

Pay

The pay range for this position is $46,000 to $50,000 USD/CAD annually.

Schedule

• Flexibility to work evenings, weekends, and travel as required

Check for duplication: Flexibility appears in Requirements and Schedule. That's okay; it's substantive. Could we avoid duplication? Might be okay. We have "Flexibility to work evenings, weekends, and travel as required" appears in Requirements and Schedule. Could keep both but maybe we should only have in Schedule and not duplicate in Requirements. However Requirements already includes flexibility as a requirement; it's not duplicate if we keep both. But we could remove from Requirements to avoid duplication. However the requirement list includes flexibility as a qualification; it's a requirement. So we could keep it there and not have Schedule separate? But we need Schedule section because we have schedule info. Could keep Schedule with just the remote work and regular travel? Actually schedule info includes flexibility to work evenings, weekends, travel as required. Also remote work and regular travel. So we could put all schedule items in Schedule section and not duplicate in Requirements. But then we lose flexibility as a requirement. However flexibility is a requirement; we could still list it under Requirements but also under Schedule; duplication is allowed? The instruction didn't forbid duplication, but we should avoid unnecessary duplication. However it's not harmful. Might be okay. But we also have "Ability to work remotely" and "Regular travel required" under Skills; maybe those belong under Schedule instead. Let's think: Skills section should contain skills like experience in professional sports, live events, or hockey (preferred). Ability to work remotely is more of a work arrangement, not a skill. Regular travel required is schedule. So maybe we should move those to Schedule. Let's restructure: Requirements: Bachelor's degree, 1 year experience, strong organizational/project management/communication skills, flexibility to work evenings weekends travel, work authorization, location US/Canada. Skills: Experience in professional sports, live events, or hockey (preferred). (Maybe also "Strong organizational, project management, and communication skills" but that's already in Requirements.) Schedule: Flexibility to work evenings, weekends, and travel as required; Ability to work remotely; Regular travel required to support Takeover Tour