WORKER'S COMPENSATION & CLAIM COORDINATOR

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must remove boilerplate like EEO, legal, application instructions, etc. Must preserve all substantive info. We need to parse the posting. Key sections: - About Apis Services (maybe "About the role"? Actually "About Apis Services" is about organization. Could be "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have: - Intro: "Help Employees Navigate Recovery. Support a Safer Workplace. Worker’s Compensation & Claims Coordinator 📍 Remote 🕒 Full-Time Looking for More Than Just a Job? At Apis Services, we know that supporting employees through workplace injuries and claims is critical to maintaining a healthy, productive workforce. We're seeking a detail-oriented and compassionate Worker’s Compensation & Claims Coordinator who thrives in a fast-paced environment and enjoys problem-solving, relationship-building, and managing complex processes. If you're someone who can effectively balance employee support, compliance, communication, and claims management, we'd love to hear from you. Whether you're experienced in worker's compensation, claims administration, risk management, or employee relations, this role offers the opportunity to make a meaningful impact while supporting a mission-driven organization." That could be "About the role" (description). We'll put that in

About the role

with

. - "About Apis Services" paragraph: could also be part of About the role or separate? But we only have limited headings. Could incorporate into About the role. - "Why Join Our Team?" includes subsections: Competitive Pay & Benefits, Career Growth & Development, Meaningful Work That Matters. We need to extract Benefits, Pay, etc. Benefits list: Competitive Compensation, DailyPay – Access Your Earned Wages Before Payday, Medical, Dental & Vision Insurance, 401(k) Retirement Plan, Paid Time Off, Employee Assistance Program, Wellness Programs, Employee Referral Bonuses, Company-Paid Training. Career Growth & Development: Professional Development Opportunities, Leadership Development Programs, Career Advancement Opportunities, Exposure to Multi-State Claims Administration Opportunities Across Multiple Service Lines. Meaningful Work That Matters: Support Employees Through Challenging Situations, Help Improve Workplace Safety Outcomes, Collaborate with Leaders Across Multiple Affiliates, Make a Positive Impact on Employee Well-Being, Join a Mission-Driven Organization. We need Benefits section: list of benefits. Pay: maybe "Competitive Compensation" is pay. But they didn't give specific salary numbers. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. They do state "Competitive Pay & Benefits" and list benefits. They also say "Competitive Compensation". That's vague but still states competitive compensation. Should we include Pay section? It says "Competitive Pay & Benefits" heading, but they didn't give actual numbers. The rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "Competitive Compensation" is somewhat vague but not exactly placeholder like "commensurate with experience". It's still a statement. I'd include Pay section with that statement? Might be considered filler. Safer to not include Pay unless specific numbers. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." They do state benefits (list). So Benefits section is okay. Pay: they state "Competitive Compensation" but no numbers. Might be considered vague but still states something. I'd include Pay with that statement? However they also have "Competitive Pay & Benefits" as a heading; they list benefits under that. Could treat Pay as part of Benefits? But we need separate sections if content exists. I'd include Pay with "Competitive Compensation" as a

. Might be acceptable. Schedule: they state "Full-Time Monday through Friday Standard business hours with flexibility based on operational needs Remote position". That's specific enough. So Schedule section. Responsibilities: bullet list under "What You'll Do". We'll create

• . Requirements: maybe "Who We're Looking For" list of traits (detail-oriented etc.) plus Qualifications section. Could separate Requirements (maybe the traits) and Qualifications (education/experience). But we have both Requirements and Qualifications headings allowed. We'll put traits under Requirements? Or maybe Requirements = mandatory qualifications (education, experience). Qualifications = preferred qualifications? Let's see. The posting: "Who We're Looking For You may be a great fit if you are: ✔ Detail-Oriented ✔ Organized ✔ Empathetic ✔ Collaborative ✔ Analytical ✔ Professional ✔ Dependable ✔ Committed to Supporting Employees". That's more like desired attributes/skills. Then "Qualifications Bachelor's degree ... Minimum of two (2) years of experience ... Strong understanding ... Excellent communication ... Ability to manage multiple priorities ... Experience working with confidential information ... Proficiency with Microsoft Outlook..." That's qualifications. Then "Preferred Qualifications Certification ... Experience with claims management systems ... Experience analyzing claims data ... Previous experience working with insurance carriers..." Thus we can map: - Requirements: the mandatory qualifications (education, experience, etc.) maybe under Requirements heading. - Skills: the traits list (detail-oriented, organized, etc.) maybe under Skills heading. But we also have a Skills heading allowed. Could put the traits under Skills. Let's decide: - About the role: intro paragraph. - Responsibilities: What You'll Do bullet list. - Requirements: mandatory qualifications (education, experience, etc.) bullet list. - Skills: personal attributes list (detail-oriented, organized, etc.) bullet list. - Benefits: list of benefits. - Pay: maybe "Competitive Compensation" as a paragraph. - Schedule: description. We must not include sections with filler. Ensure each section has substantive content. Now we need to strip boilerplate: remove "Equal Opportunity Employer" etc. Also remove "About Our Organization" (Apis Services is part of the Inperium family...). Also remove "Apply Today" and any application instructions. Also remove "Some jobs process paperwork..." etc. Also remove "Help Employees Navigate Recovery..."? That's part of intro, keep. Also remove "❤️ WORKER’S COMPENSATION & CLAIMS COORDINATOR Help Employees Navigate Recovery. Support a Safer Workplace. Worker’s Compensation & Claims Coordinator 📍 Remote 🕒 Full-Time". The job title repeated; we should not repeat as heading. We can keep the intro text but not the title as heading. We need to preserve all substantive information: location Remote, Full-Time. That's schedule info. Let's craft HTML. We'll start with

  About the role

  ... intro paragraph ...

  Then

  Responsibilities

  • ... each bullet from What You'll Do ...
  Then

  Requirements

  • ... mandatory qualifications ...
  Then

  Skills

  • ... personal attributes ...
  Then

  Benefits

  • ... benefits list ...
  Then

  Pay

  Competitive Compensation

  Then

  Schedule

  Full-Time Monday through Friday Standard business hours with flexibility based on operational needs Remote position

  Check for any duplicate content: Ensure we didn't miss any substantive info like "Coordinate with medical providers..." etc included in responsibilities. Let's extract responsibilities bullets exactly: - Manage and facilitate the entire worker’s compensation claims process from initiation through resolution. - Coordinate with medical providers, insurance adjusters, employees, and affiliate partners to gather required documentation and information. - Monitor and track active claims, ensuring timely follow-up and communication with all parties involved. - Maintain accurate records, claim documentation, and compliance-related reporting. - Analyze claims data to identify trends and recommend opportunities for workplace safety improvements and injury prevention initiatives. - Educate employees regarding worker’s compensation processes, rights, responsibilities, and available resources. - Work collaboratively with internal stakeholders and affiliate leadership to ensure claims are adjusted timely and appropriately. - Communicate regularly with insurance carriers, third-party administrators, and legal partners as needed. - Assist with return-to-work coordination and ongoing case management activities. - Support organizational risk management and compliance initiatives related to worker’s compensation programs. Now Requirements (mandatory qualifications): - Bachelor's degree in Human Services, Human Resources, Business Administration, Healthcare Management, or a related field preferred. (Note: "preferred" but still part of qualifications; we can keep.) - Minimum of two (2) years of experience in worker's compensation claims management, claims administration, risk management, or a related field. - Strong understanding of worker’s compensation processes and applicable regulations. - Excellent communication, problem-solving, and interpersonal skills. - Ability to manage multiple priorities while maintaining attention to detail. - Experience working with confidential information and maintaining accurate records. - Proficiency with Microsoft Outlook, Word, Excel, PowerPoint, Teams, OneDrive, and SharePoint. We could also include "Preferred Qualifications" but we have separate Skills for traits; maybe we could add another section for Preferred Qualifications but not allowed headings. We could incorporate preferred qualifications into Requirements or Skills? But we have only these headings. Could add another section like "Qualifications" but we already used Requirements for mandatory; we could rename Requirements to Qualifications and Skills to Attributes. However the instruction says use those headings; we can still use them as we like. We'll keep Requirements as mandatory qualifications, Skills as personal attributes, and we could put preferred qualifications under Requirements as well? Might be mixing. Better to put preferred qualifications under Requirements as well, but we could also add a separate section "Qualifications" but we already used Requirements. The instruction list includes Qualifications as a possible heading. So we could use Requirements for mandatory, Qualifications for preferred? But we also have Skills for traits. Let's map: - Requirements: mandatory qualifications (education, experience, etc.) - Qualifications: preferred qualifications (certification, experience with systems, analyzing data, experience with carriers) - Skills: personal attributes (detail-oriented, organized, etc.) That seems logical and uses three headings. Thus:

  Requirements

  mandatory

  Qualifications

  preferred

  Skills

  attributes
  Now Benefits list: - Competitive Compensation (but we already have Pay section; maybe we shouldn't duplicate). Actually Benefits list includes Competitive Compensation as first item. We'll keep Benefits list as other benefits excluding compensation? But we need to preserve all substantive info. If we put Competitive Compensation in Pay section, we should not duplicate it in Benefits. However the Benefits list includes it; we could keep it there and not have separate Pay. But we have schedule and pay sections; we need to decide. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." They state Competitive Pay & Benefits heading and list benefits including Competitive Compensation. So we could have Benefits section that includes all items, and we could omit Pay section because compensation is included in Benefits. However they also have "Competitive Pay & Benefits" as a heading; but we could treat that as Benefits. The instruction says prefer a few substantive sections over many thin ones. So maybe combine Pay into Benefits. But we also have Schedule separate. Thus we could have Benefits section that includes all items: Competitive Compensation, DailyPay, Medical..., etc. Then we don't need a separate Pay section. That reduces sections. Let's do that: Benefits section includes all bullet points from "Why Join Our