Healthcare Coordinator
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info. Remove boilerplate etc. Include a section only when posting has real specific content. Avoid filler like "commensurate with experience". Pay and Schedule sections only if posting actually states them. Benefits section only if posting actually states them.
Let's parse the posting.
Content:
- Intro: "Ready to Be a Voice for Independence? If you want a career where your work directly impacts people's freedom, dignity, and quality of life, we'd love to hear from you. Apply today and help people live life on their own terms."
- Location: "Location: Tomahawk, Rhinelander and surrounding areas."
- Pay: "Pay $19.23/hour + Mileage Reimbursement"
- Work arrangement: "Semi-Remote (Home Office + Community Travel Required)"
- Then a paragraph: "This Isn't Just a Job... Advocacy..." etc.
- About Community Horizons: description.
- Your Role: Support Broker description.
- What You'll Do: list of duties.
- You're a Great Fit If You Have: list of requirements.
- Why Join Community Horizons? Benefits list.
- Then "Please note: This position does not include health insurance."
- Then "Benefits: 401(k) matching Flexible schedule Mileage reimbursement Paid time off Paid training Benefits: 401(k) matching Flexible schedule Paid time off" (duplicate)
- Application instructions: email resume.
We need to remove application instructions, boilerplate, duplicated lines, cookie/navigation/legal/EEO etc. Not present.
We need to keep substantive info: location, pay, semi-remote, description, role, duties, requirements, benefits.
We need to structure sections: maybe About the role (or About Community Horizons?), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have Pay explicitly. Schedule? Not explicitly given; we have "Semi-Remote (Home Office + Community Travel Required)" and "Flexible schedule" mentioned under benefits. So schedule info: "Flexible schedule" is a benefit, not a schedule requirement. The posting does not give specific schedule like full-time, part-time, hours. So we should not create a Schedule section unless posting actually states them. It mentions "Flexible schedule" as a benefit, but that's under Benefits. So we could include schedule info under Benefits or maybe not create a separate Schedule heading. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine.
We need to decide sections: About the role (maybe "About Community Horizons" or "About the role") - we have description of organization and role. Could use "About the role" heading.
Responsibilities: list of duties under "What You'll Do".
Requirements: list under "You're a Great Fit If You Have". Could include healthcare recruiting experience required, 5+ years supporting individuals..., strong organization and communication skills, passion..., experience with self-directed..., valid driver's license.
Qualifications: maybe same as requirements? But we can separate: Qualifications could be education? Not present. Could omit Qualifications if no specific content.
Skills: maybe "Strong organization and communication skills" etc. Could be under Skills.
But we need to avoid thin sections. Perhaps combine Requirements and Skills into one section "Requirements". Or we could have "Requirements" and "Skills" as separate if we have content.
Let's extract:
- Healthcare recruiting experience (required)
- 5+ years supporting individuals with disabilities or the frail elderly
- Strong organization and communication skills
- A passion for person-centered support and advocacy
- Experience with self-directed or long-term care programs (a plus)
- A valid driver's license and reliable transportation
These are requirements/qualifications/skills.
We could have a section "Requirements" with bullet list.
Benefits: list includes:
- Semi-remote work environment
- Mileage reimbursement
- Paid time off
- Weekends and holidays off
- Supportive, mission-driven team
- The opportunity to make a real difference every single day
- 401(k) matching
- Flexible schedule
- Paid training
Note: "Weekends and holidays off" is a benefit. Also "Supportive, mission-driven team". Also "The opportunity to make a real difference every single day". Also "Please note: This position does not include health insurance." That's a note about missing benefit; we could include as a note in Benefits section maybe as a
.
We should not duplicate. The posting had duplicated benefits lines; we need to preserve all substantive info but not duplicate. So we need to deduplicate.
Let's compile unique benefits:
- Semi-remote work environment
- Mileage reimbursement
- Paid time off
- Weekends and holidays off
- Supportive, mission-driven team
- Opportunity to make a real difference every single day
- 401(k) matching
- Flexible schedule
- Paid training
- (Note) No health insurance
Also "Semi-remote work environment" already mentioned earlier as work arrangement; but it's also a benefit. Could keep.
Pay: "$19.23/hour + Mileage Reimbursement". Note mileage reimbursement also appears in benefits; but we can keep both.
Schedule: Not explicitly given; we have flexible schedule as benefit. So we could not create a Schedule section.
Now sections:
- About the role (or About Community Horizons). We'll use
About the role
with prose summarizing organization and role.
- Responsibilities: Responsibilities
with - list of duties.
- Requirements:
Requirements
with - list.
- Benefits:
Benefits
with - list plus maybe a
about no health insurance.
- Pay:
Pay
with "$19.23/hour + Mileage Reimbursement".
We should not repeat mileage reimbursement in Pay and Benefits? It's okay to mention both; but we could keep in Pay and also list under Benefits as mileage reimbursement. It's not duplicate if appears in both sections; but we might want to avoid duplication. However instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep mileage reimbursement info; it's okay to appear in both Pay and Benefits if it's substantive. But we could also just put it under Pay and not duplicate in Benefits. However Benefits list originally includes mileage reimbursement as a benefit. If we omit it from Benefits, we lose that substantive info (that it's a benefit). But we could still mention it under Benefits as "Mileage reimbursement". It's not duplicate if we also have Pay section; it's just same info appears in two places. The instruction says preserve all substantive info; duplication is not prohibited, but they said remove duplicated lines. That refers to duplicated lines in the source. So we can keep it in both sections if we want; but better to avoid unnecessary duplication. However we need to decide.
I think we can include mileage reimbursement under Pay, and also list it under Benefits as it's a benefit. It's not harmful.
Now we need to ensure we don't create sections with filler like "commensurate with experience". Not present.
Now produce HTML fragment.
We must not include or . Just the fragment.
Let's craft:
About the role
Community Horizons supports individuals with disabilities and older adults to live independently through self-direction, helping people navigate the onboarding process of their own care teams so they can remain in their homes and communities. Serving 47 counties across Wisconsin, the organization champions independence, choice, dignity, and a voice in one's own care. As a Support Broker, you will partner with members and families to recruit, screen, and hire caregivers, mentor members on employer responsibilities, guide them through scheduling, timecards, EVV systems, assist with Medicaid renewals and benefit applications, and advocate for the individual's voice and independence.
But we need to preserve all substantive info; we should not summarize away detail. The above is a summary; we might lose some specifics. Better to keep the original prose but we can combine paragraphs.
We have two paragraphs: intro about mission, and "About Community Horizons". Also "Your Role: Support Broker". We could keep them as separate elements under About the role.
Let's extract exact sentences:
Intro: "Ready to Be a Voice for Independence? If you want a career where your work directly impacts people's freedom, dignity, and quality of life, we'd love to hear from you. Apply today and help people live life on their own terms."
But we should remove application instructions? The "Apply today" is part of intro but it's basically a call to apply; maybe considered application instruction? The instruction says remove application instructions. The phrase "Apply today" could be considered application instruction. Safer to remove that sentence? However it's part of the motivational intro. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove explicit application instructions like "Apply today". The intro also includes "Ready to Be a Voice for Independence? If you want a career where your work directly impacts people's freedom, dignity, and quality of life, we'd love to hear from you." That's fine. We'll keep that but drop "Apply today and help people live life on their own terms." That's an application instruction. So we keep first sentence.
Next: "Location: Tomahawk, Rhinelander and surrounding areas." This is location; we could include as a
maybe under About the role or separate. Not a heading. We'll include as a
.
Then Pay line: "Pay $19.23/hour + Mileage Reimbursement". We'll put under Pay section.
Then "Semi-Remote (Home Office + Community Travel Required)". Could be under Benefits or maybe a separate line under About the role. We'll include as a
under About the role maybe.
Then paragraph: "This Isn't Just a JobIt's Advocacy. At Community Horizons, we believe people with disabilities and older adults deserve the power to choose how they live, who supports them, and what independence looks like in their own lives. Self-Direction is about freedom, dignity, and controland we're looking for someone who shares a passion for advocating for the individuals we serve. If you are passionate about empowering others, skilled in healthcare recruiting, and ready to stand beside people as they build the life they want, we want to meet you."
Note there's missing spaces due to formatting; we need to fix spacing: "This Isn't Just a JobIt's Advocacy." Should be "This Isn't Just a Job. It's Advocacy." We'll add space.
We'll keep as is but fix spacing.
Then "About Community Horizons Community Horizons supports individuals with disabilities and older adults to live independently through self-direction. We help people navigate the onboarding process of their own care teams so they can remain in their homes and communitieson their terms. Serving 47 counties across Wisconsin, we believe everyone deserves: Independence Choice Dignity A voice in their own care"
We need to preserve line breaks? We'll make a paragraph.
Then "Your Role: Support Broker As a Support Broker, you are more than a recruiteryou are a partner, mentor, and advocate helping individuals build the team that makes independent living possible. You'll work alongside members and families to ensure they have the tools, support, and confidence to lead their own care and navigate complex systems that impact their independence
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info. Remove boilerplate etc. Include a section only when posting has real specific content. Avoid filler like "commensurate with experience". Pay and Schedule sections only if posting actually states them. Benefits section only if posting actually states them. Let's parse the posting. Content: - Intro: "Ready to Be a Voice for Independence? If you want a career where your work directly impacts people's freedom, dignity, and quality of life, we'd love to hear from you. Apply today and help people live life on their own terms." - Location: "Location: Tomahawk, Rhinelander and surrounding areas." - Pay: "Pay $19.23/hour + Mileage Reimbursement" - Work arrangement: "Semi-Remote (Home Office + Community Travel Required)" - Then a paragraph: "This Isn't Just a Job... Advocacy..." etc. - About Community Horizons: description. - Your Role: Support Broker description. - What You'll Do: list of duties. - You're a Great Fit If You Have: list of requirements. - Why Join Community Horizons? Benefits list. - Then "Please note: This position does not include health insurance." - Then "Benefits: 401(k) matching Flexible schedule Mileage reimbursement Paid time off Paid training Benefits: 401(k) matching Flexible schedule Paid time off" (duplicate) - Application instructions: email resume. We need to remove application instructions, boilerplate, duplicated lines, cookie/navigation/legal/EEO etc. Not present. We need to keep substantive info: location, pay, semi-remote, description, role, duties, requirements, benefits. We need to structure sections: maybe About the role (or About Community Horizons?), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Pay explicitly. Schedule? Not explicitly given; we have "Semi-Remote (Home Office + Community Travel Required)" and "Flexible schedule" mentioned under benefits. So schedule info: "Flexible schedule" is a benefit, not a schedule requirement. The posting does not give specific schedule like full-time, part-time, hours. So we should not create a Schedule section unless posting actually states them. It mentions "Flexible schedule" as a benefit, but that's under Benefits. So we could include schedule info under Benefits or maybe not create a separate Schedule heading. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine. We need to decide sections: About the role (maybe "About Community Horizons" or "About the role") - we have description of organization and role. Could use "About the role" heading. Responsibilities: list of duties under "What You'll Do". Requirements: list under "You're a Great Fit If You Have". Could include healthcare recruiting experience required, 5+ years supporting individuals..., strong organization and communication skills, passion..., experience with self-directed..., valid driver's license. Qualifications: maybe same as requirements? But we can separate: Qualifications could be education? Not present. Could omit Qualifications if no specific content. Skills: maybe "Strong organization and communication skills" etc. Could be under Skills. But we need to avoid thin sections. Perhaps combine Requirements and Skills into one section "Requirements". Or we could have "Requirements" and "Skills" as separate if we have content. Let's extract: - Healthcare recruiting experience (required) - 5+ years supporting individuals with disabilities or the frail elderly - Strong organization and communication skills - A passion for person-centered support and advocacy - Experience with self-directed or long-term care programs (a plus) - A valid driver's license and reliable transportation These are requirements/qualifications/skills. We could have a section "Requirements" with bullet list. Benefits: list includes: - Semi-remote work environment - Mileage reimbursement - Paid time off - Weekends and holidays off - Supportive, mission-driven team - The opportunity to make a real difference every single day - 401(k) matching - Flexible schedule - Paid training Note: "Weekends and holidays off" is a benefit. Also "Supportive, mission-driven team". Also "The opportunity to make a real difference every single day". Also "Please note: This position does not include health insurance." That's a note about missing benefit; we could include as a note in Benefits section maybe as a
. We should not duplicate. The posting had duplicated benefits lines; we need to preserve all substantive info but not duplicate. So we need to deduplicate. Let's compile unique benefits: - Semi-remote work environment - Mileage reimbursement - Paid time off - Weekends and holidays off - Supportive, mission-driven team - Opportunity to make a real difference every single day - 401(k) matching - Flexible schedule - Paid training - (Note) No health insurance Also "Semi-remote work environment" already mentioned earlier as work arrangement; but it's also a benefit. Could keep. Pay: "$19.23/hour + Mileage Reimbursement". Note mileage reimbursement also appears in benefits; but we can keep both. Schedule: Not explicitly given; we have flexible schedule as benefit. So we could not create a Schedule section. Now sections: - About the role (or About Community Horizons). We'll use
About the role
with prose summarizing organization and role. - Responsibilities:Responsibilities
with- list of duties.
- Requirements:
Requirements
with- list.
- Benefits:
Benefits
with- list plus maybe a
about no health insurance. - Pay:
Pay
with"$19.23/hour + Mileage Reimbursement". We should not repeat mileage reimbursement in Pay and Benefits? It's okay to mention both; but we could keep in Pay and also list under Benefits as mileage reimbursement. It's not duplicate if appears in both sections; but we might want to avoid duplication. However instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep mileage reimbursement info; it's okay to appear in both Pay and Benefits if it's substantive. But we could also just put it under Pay and not duplicate in Benefits. However Benefits list originally includes mileage reimbursement as a benefit. If we omit it from Benefits, we lose that substantive info (that it's a benefit). But we could still mention it under Benefits as "Mileage reimbursement". It's not duplicate if we also have Pay section; it's just same info appears in two places. The instruction says preserve all substantive info; duplication is not prohibited, but they said remove duplicated lines. That refers to duplicated lines in the source. So we can keep it in both sections if we want; but better to avoid unnecessary duplication. However we need to decide. I think we can include mileage reimbursement under Pay, and also list it under Benefits as it's a benefit. It's not harmful. Now we need to ensure we don't create sections with filler like "commensurate with experience". Not present. Now produce HTML fragment. We must not include or . Just the fragment. Let's craft:
About the role
Community Horizons supports individuals with disabilities and older adults to live independently through self-direction, helping people navigate the onboarding process of their own care teams so they can remain in their homes and communities. Serving 47 counties across Wisconsin, the organization champions independence, choice, dignity, and a voice in one's own care. As a Support Broker, you will partner with members and families to recruit, screen, and hire caregivers, mentor members on employer responsibilities, guide them through scheduling, timecards, EVV systems, assist with Medicaid renewals and benefit applications, and advocate for the individual's voice and independence.
But we need to preserve all substantive info; we should not summarize away detail. The above is a summary; we might lose some specifics. Better to keep the original prose but we can combine paragraphs. We have two paragraphs: intro about mission, and "About Community Horizons". Also "Your Role: Support Broker". We could keep them as separateelements under About the role. Let's extract exact sentences: Intro: "Ready to Be a Voice for Independence? If you want a career where your work directly impacts people's freedom, dignity, and quality of life, we'd love to hear from you. Apply today and help people live life on their own terms." But we should remove application instructions? The "Apply today" is part of intro but it's basically a call to apply; maybe considered application instruction? The instruction says remove application instructions. The phrase "Apply today" could be considered application instruction. Safer to remove that sentence? However it's part of the motivational intro. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove explicit application instructions like "Apply today". The intro also includes "Ready to Be a Voice for Independence? If you want a career where your work directly impacts people's freedom, dignity, and quality of life, we'd love to hear from you." That's fine. We'll keep that but drop "Apply today and help people live life on their own terms." That's an application instruction. So we keep first sentence. Next: "Location: Tomahawk, Rhinelander and surrounding areas." This is location; we could include as a
maybe under About the role or separate. Not a heading. We'll include as a
. Then Pay line: "Pay $19.23/hour + Mileage Reimbursement". We'll put under Pay section. Then "Semi-Remote (Home Office + Community Travel Required)". Could be under Benefits or maybe a separate line under About the role. We'll include as a
under About the role maybe. Then paragraph: "This Isn't Just a JobIt's Advocacy. At Community Horizons, we believe people with disabilities and older adults deserve the power to choose how they live, who supports them, and what independence looks like in their own lives. Self-Direction is about freedom, dignity, and controland we're looking for someone who shares a passion for advocating for the individuals we serve. If you are passionate about empowering others, skilled in healthcare recruiting, and ready to stand beside people as they build the life they want, we want to meet you." Note there's missing spaces due to formatting; we need to fix spacing: "This Isn't Just a JobIt's Advocacy." Should be "This Isn't Just a Job. It's Advocacy." We'll add space. We'll keep as is but fix spacing. Then "About Community Horizons Community Horizons supports individuals with disabilities and older adults to live independently through self-direction. We help people navigate the onboarding process of their own care teams so they can remain in their homes and communitieson their terms. Serving 47 counties across Wisconsin, we believe everyone deserves: Independence Choice Dignity A voice in their own care" We need to preserve line breaks? We'll make a paragraph. Then "Your Role: Support Broker As a Support Broker, you are more than a recruiteryou are a partner, mentor, and advocate helping individuals build the team that makes independent living possible. You'll work alongside members and families to ensure they have the tools, support, and confidence to lead their own care and navigate complex systems that impact their independence
- list plus maybe a
- list.
- Benefits: