Coach Enhancement - Practice Player LOVB Madison

The user wants me to reformat a job posting into clean, well-structured semantic HTML. Let me analyze the content and apply the rules. First, I need to identify the sections that have real, specific content. The posting has: - About LOVB (company description) - Job Description with metadata (title, department, FLSA, employment status, reports to, location, season, schedule) - Job Summary - Essential Duties and Responsibilities (with subsections) - Required Skills/Abilities - Behavioral Competencies - Education and Experience - Work Environment & Physical Requirements - Pay Range Rules: - Use

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

• for lists,

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

  or drop - Preserve ALL substantive information; do NOT invent or summarize away detail - Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning), duplicated lines, application instructions - Include section ONLY when posting has real, specific content — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") - Never create Pay/Schedule/Benefits sections unless posting actually states them - Prefer few substantive sections over many thin ones - Output ONLY HTML fragment — no /, no markdown code fences Now, I need to map the content to appropriate headings. The user suggested headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But I should only include sections that have real content. Let's see: - "About LOVB" is company description, could be "About the role" or "About the company". The rule says "About the role" as heading. But the posting has "About LOVB" and "Job Description". I think "About the role" could encompass the job summary and company context. However, the rule says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I should use those exact headings if they have content. I'll structure: - About the role: includes company description and job summary - Responsibilities: essential duties and responsibilities (with subsections as lists) - Requirements: required skills/abilities - Qualifications: education and experience - Skills: maybe behavioral competencies? But "Skills" heading might be for required skills. The posting has "Required Skills/Abilities" and "Behavioral Competencies". Could combine into "Requirements" and "Qualifications". But the example headings include "Skills". I'll use "Requirements" for required skills/abilities, "Qualifications" for education and experience, and maybe "Competencies" for behavioral competencies? But the example doesn't have "Competencies". The rule says use those headings e.g. So I can choose appropriate ones. Better to follow the example headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But only if content exists. The posting has: - Pay Range: "The Pay Range For This Role Is 7.25 - 7.25 USD per hour (LOVB Pro Madison)" -> Pay section - Schedule: "Schedule: Hours vary based on the team's practice and training schedule..." -> Schedule section - Benefits: not mentioned, so no Benefits section. - Work Environment & Physical Requirements: could be part of Requirements or Qualifications? Might be separate but not in example headings. Could fold into Requirements or Qualifications. I'll create sections: 1. About the role (company description + job summary) 2. Responsibilities (essential duties) 3. Requirements (required skills/abilities) 4. Qualifications (education and experience) 5. Competencies (behavioral competencies) - but not in example. Could include under Requirements or Qualifications. Since example includes "Skills", maybe "Skills" for required skills/abilities, and "Qualifications" for education/experience. But "Required Skills/Abilities" is a list of skills. "Behavioral Competencies" is another list. I'll combine into "Requirements" and "Competencies"? But the rule says prefer few substantive sections. I'll make "Requirements" include both required skills/abilities and behavioral competencies? Or separate "Skills" for required skills/abilities and "Competencies" for behavioral? The example includes "Skills". I'll use "Skills" for required skills/abilities, and "Qualifications" for education/experience. Behavioral competencies could be part of "Requirements" or "Skills". I'll include them under "Requirements" as a subsection. But the rule: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So I can use those headings. I'll use: - About the role - Responsibilities - Requirements (for required skills/abilities) - Qualifications (for education and experience) - Skills (for behavioral competencies? But that's not typical. Maybe "Skills" is for required skills/abilities. Actually "Required Skills/Abilities" is a section. So "Skills" heading could be that. Then "Requirements" could be for other requirements like physical, compliance? Hmm. Let's read the posting: "Required Skills/Abilities" is a list. "Behavioral Competencies" is another list. "Education And Experience" is another. "Work Environment & Physical Requirements" is another. I think best to map: - About the role: company description + job summary - Responsibilities: essential duties - Skills: required skills/abilities (since it's a list of skills) - Qualifications: education and experience - Requirements: could include behavioral competencies and physical requirements? But "Requirements" heading is in example. I'll use "Requirements" for behavioral competencies and physical requirements? Or maybe "Requirements" for required skills/abilities, and "Qualifications" for education/experience. The example includes both "Requirements" and "Qualifications". Often they are separate: requirements = skills, qualifications = education/experience. I'll do: - Requirements: required skills/abilities - Qualifications: education and experience - Competencies: behavioral competencies (but not in example). Could fold into Requirements. But the rule says "Prefer a few substantive sections over many thin ones." So I'll combine behavioral competencies into Requirements or Qualifications. Since they are behavioral, maybe under Requirements. Also, Work Environment & Physical Requirements: could be under Requirements or a separate section. Not in example headings. I'll include under Requirements as a subsection. Pay and Schedule are explicit, so include Pay and Schedule sections. Now, metadata: Title, Department Code, FLSA Status, Employment Status, Reports To, Location, Season. These are minor metadata. Fold into a short

  in About the role or at top. The rule: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So I'll create a paragraph with key metadata. Now, let's write HTML. Structure:

  About the role

  About LOVB... (company description)

  Job Summary: ...

  Title: Coach Enhancement Program - Seasonal | Department: 904020 – Athlete Experience | FLSA: Non-Exempt, Hourly | Employment: Part-Time, Seasonal | Reports To: Head Coach or Designee | Location: On-site at an LOVBPro team training location | Season: November 1, 2026 – April 30, 2027

  Responsibilities

  • On-Court & Practice Support
    • Support LOVBPro coaching staff during practices and training sessions.
    • Serve, toss, simulate positional play, and assist with small-sided or controlled drills as directed by coaching staff.
    • Assist with practice setup and teardown, including equipment preparation and organization.
    • Support timing, scoring, and other practice-management activities as assigned.
    • Conduct basic equipment and practice-area safety checks and help maintain equipment appropriately.
  • Observation & Professional Development
    • Observe professional-level practice structures, coaching methodologies, and athlete-development strategies.
    • Capture relevant drill structures, coaching cues, and practice-flow observations.
    • Complete assigned learning summaries, reflections, or applied takeaways as part of the program.
  • Film & Analytics Support
    • Assist with tagging actions, identifying or pulling video clips, and basic charting within established team workflows.
    • Support other basic film or analytics activities as directed by coaching staff.
  • Professional Conduct & Compliance
    • Maintain athlete focus, confidentiality, and appropriate professional boundaries at all times.
    • Protect confidential team, athlete, medical, competitive, and organizational information.
    • Follow LOVB policies, team protocols, SafeSport requirements, and applicable training-facility rules.
    • Maintain professional conduct consistent with LOVB standards when interacting with athletes, coaches, staff, and other stakeholders.
  • Timekeeping & Scheduling
    • Accurately record all hours worked using LOVB's designated timekeeping system.
    • Attend required practices, meetings, training sessions, and other scheduled activities as assigned.
    • Obtain advance approval before working outside the established schedule or working overtime.
    • Report all time worked, including required meetings, preparation, film/analytics work, setup, teardown, and other assigned responsibilities.
  But the rule: use
  • for any list of duties/requirements/benefits. The responsibilities have subsections. I could make each subsection a separate
    under a heading? But we only have

    for main sections. Could use

    ? Not allowed? The rule says use

    for section headings. It doesn't forbid

    but says use

    for section headings. Probably only

    for top-level sections. For subsections, we can use or just list items with bold? But the rule says use

    • for any list. I think we can nest lists. That's fine. Alternatively, we can make each responsibility area a separate
      with a bold label. But the rule says use

      for section headings. So we keep only top-level sections as

      . For subsections, we can use

      On-Court & Practice Support

      then

      . That's acceptable. I'll do:

      Responsibilities

      On-Court & Practice Support

      • Support LOVBPro coaching staff during practices and training sessions.
      ...

      Observation & Professional Development

      ...
      ... That's clean. Now Requirements (required skills/abilities):

      Requirements

      • Prior volleyball coaching or playing experience and ability to support professional-level training activities.
      • Strong on-court presence, communication, and ability to follow coaching direction.
      • Physical ability to participate in controlled practice activities.
      • Strong organizational, collaboration, and time-management skills.
      • Sound judgment and commitment to confidentiality and athlete-centered environments.
      • Completion of required SafeSport and LO