Community Supports Coordinator, Charles County

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule? We need to include only sections with real content. The posting includes description (about role) and responsibilities (list of duties). Also requirements (list). Qualifications (list). Benefits (list). Salary (Pay). Schedule? There's mention of flexibility: ability to work flexible schedule including evenings and weekends. That's schedule info. Also maybe "General Conditions" includes flexibility, physical capacity, transportation, home office. Those could be considered schedule? But schedule section is for schedule details; we have flexibility info. We'll include Schedule section with that content. We must not repeat job title as heading. No Job ID. Remove boilerplate: EEO, application instructions, etc. Also remove "How To Apply" and EEO statement. Also remove "General Conditions" maybe we split into Schedule and maybe other? But we can incorporate physical capacity etc into maybe a "Working Conditions" but not required. Since we only have headings for specific list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We don't have a separate Skills section; skills are within qualifications. Could combine but we can omit Skills if no explicit list. We'll include About the role (prose), Responsibilities (ul), Requirements (ul), Qualifications (ul), Benefits (ul), Pay (p), Schedule (p or ul?). Schedule: flexibility info. Could be a p. We must preserve all substantive information. Let's extract. About the role: first paragraph: "The Community Supports Coordinator is responsible for facilitating outreach, education, training, information and referral services, and prevention activities associated with Charles County’s Coordinated Community Supports program. This role supports the coordination and implementation of a comprehensive prevention and mental health promotion initiative within Charles County. The Coordinator will help deliver essential programs, including Teen Mental Health First Aid and Youth Mental Health First Aid, and will work with schools, families, community organizations, providers, and other partners to promote mental well-being among students, families, and communities. This role will also raise awareness of available behavioral health resources and services and help families access the support they need. This role contributes to the management practices necessary for grant compliance and effective program operations, including documentation, evaluation, and reporting." That's about role. Responsibilities: list from Requirements? Actually the "Requirements" section includes bullet points that are responsibilities. Let's extract those bullet points: - Obtain certification as both a Teen Mental Health First Aid Instructor and Youth Mental Health First Aid Instructor within the first 90 days, as scheduling allows, and coordinate instructor certification for other Teen and Youth Mental Health First Aid instructors in Charles County. - Partner with Charles County Schools and community organizations to develop and deliver Teen and Youth Mental Health First Aid training, including a program for all 10th-grade students, and promote prevention and awareness efforts that support mental well-being among students, families, and communities. - Engage Charles County schools and community organizations in prevention and awareness efforts that promote mental well-being among students, families, and communities. - Connect families and community members with mental health and well-being resources, including publications, materials, service information, expert contacts, and training opportunities related to mental health, child development, trauma-informed care, and substance use treatment. - Establish and maintain strong partnerships with experts, agencies, and service providers in behavioral health, physical health, social services, and other child-serving systems. - Maintain accurate and timely documentation, perform data entry and reporting, and manage records using organizational systems (including CRM, financial, survey, and other program platforms) to support program operations, program evaluation, financial tracking, and grant compliance. - Complete required administrative tasks and reporting activities within established timelines. These are responsibilities/duties. We'll put under Responsibilities. Requirements: The posting has a "Requirements" heading but actually those bullet points are responsibilities? The text shows "Requirements" then bullet points. Actually they are labeled Requirements but they look like duties. However we already used them as responsibilities. The posting also has a "Qualifications" section with bullet points. So we need to separate: Requirements (maybe the bullet points under Requirements) and Qualifications (the bullet points under Qualifications). The instructions: Use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to keep both. Thus Requirements = the bullet list under "Requirements". Qualifications = the bullet list under "Qualifications". We'll keep them. Now Benefits: list: "Full-time, non-exempt. Benefits include PTO, sick, and holidays; a 403(b) retirement plan; a Health Savings Account; and life, short-term, and long-term disability insurance, as well as medical, dental, and vision insurance." We'll put as ul. Pay: Salary $55,000-$61,000 annually. Compensation will be based on the candidate's experience and qualification. We'll put as p. Schedule: Flexibility: Ability to work a flexible schedule, including evenings and weekends, to meet the needs of communities and families. Also maybe mention physical capacity etc but those are not schedule. We'll include flexibility statement. We should not include physical capacity, transportation, home office as they are not schedule; but they are substantive. Could we include them under a separate section? Not allowed headings besides those listed. Could we incorporate them into About the role or Responsibilities? Probably not appropriate. But instructions: "Prefer a few substantive sections over many thin ones." We could omit those details? But we must preserve ALL substantive information. So we need to include them somewhere. Since we don't have a heading for "Working Conditions", we could add them to About the role or Responsibilities as extra sentences. But they are not about role; they are general conditions. Could we add them to Schedule? Schedule section could include flexibility, physical capacity, transportation, home office. That would be okay as schedule/working conditions. We'll include all general conditions under Schedule heading as a list maybe. Thus Schedule section: ul with items: Ability to work a flexible schedule, including evenings and weekends, to meet the needs of communities and families.; Ability to sit or stand for extended periods and lift up to 25 pounds as needed; Access to reliable transportation to ensure timely travel to various work locations throughout Charles County and the State of Maryland, and to attend out-of-state conferences and meetings as required.; Access to a designated home office or workspace suitable for conducting confidential business, with secure, high-speed internet service to support remote work. Now we must not include boilerplate: EEO, How To Apply, etc. Now produce HTML fragment. Structure:

About the role

...

Responsibilities

• ...
...

Requirements

... same as responsibilities? Wait we used those as responsibilities. Actually we need to separate: The bullet list under "Requirements" heading are responsibilities/duties. The bullet list under "Qualifications" heading are qualifications. So we need to keep both. Thus Responsibilities = the bullet list under Requirements? But the heading "Requirements" in the posting is actually duties. However we must follow instruction: Use headings for Requirements, Qualifications, etc. So we will treat the bullet list under "Requirements" as Requirements section. And the bullet list under "Qualifications" as Qualifications section. Then we need a Responsibilities section? The posting didn't have a separate Responsibilities heading; but we can still create Responsibilities section from the duties? However the instruction says include a section ONLY when the posting has real, specific content for it. The posting does have specific content for duties/responsibilities (the bullet list). So we can create Responsibilities section with that content. Then we need to decide what to put under Requirements and Qualifications. The posting already has headings Requirements and Qualifications. So we should map accordingly: Requirements = the bullet list under Requirements heading (which are duties). Qualifications = bullet list under Qualifications heading (which are qualifications). Then Responsibilities? That would duplicate. Actually we would have duplicate content if we also make Responsibilities. Better to treat the bullet list under Requirements as Responsibilities, and treat Qualifications as Qualifications. Then we need a Requirements section? The posting didn't have separate requirements beyond those duties; but we could treat the "Requirements" heading as Requirements (which are actually duties). However the instruction says use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid using Responsibilities heading; it's allowed as per list. So we can have Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. We need to decide what goes where. We have three blocks of bullet points: under "Requirements" heading (duties), under "Qualifications" heading (qualifications). There's no separate "Skills" list. So we can assign: - Responsibilities: maybe we can combine the duties from Requirements? But then Requirements would be empty. Better to follow the posting: Use Requirements heading for the bullet list under Requirements (which are duties/competencies). Use Qualifications heading for bullet list under Qualifications (which are qualifications). Then we still need Responsibilities? Could we treat the initial paragraph as About the role, and the bullet list under Requirements as Responsibilities? But then we would have no Requirements section. However the instruction says include a section ONLY when the posting has real, specific content for it. If we omit Requirements, we would be missing the content under that heading (the bullet list). So we must include Requirements section with that content. So we need both Requirements and Responsibilities? But we only have one bullet list of duties. Could we split duties into Responsibilities and Requirements? Not logical. Maybe the posting's "Requirements" heading actually contains both requirements and responsibilities (they are phrased as duties). The "Qualifications" heading contains qualifications. So we can map: - Responsibilities: maybe we can extract from the initial paragraph (the role description) as responsibilities? But that's more about role. Given the ambiguity, I think safest is to follow the posting's headings: Use

About the role

for the introductory paragraph. Use

Requirements

for the bullet list under "Requirements". Use

Qualifications

for the bullet list under "Qualifications". Use

Benefits

for benefits. Use

Pay

for salary. Use

Schedule

for flexibility and general conditions. Omit Responsibilities section because we don't have a separate responsibilities list beyond what's in Requirements (but we could treat Requirements as responsibilities). However the instruction says we can use Responsibilities heading if there is content. If we omit it, we might be missing the nuance that responsibilities are captured under Requirements. But the instruction says "Prefer a few substantive sections over many thin ones." Having both Requirements and Responsibilities might be thin if they overlap. I'd choose to use Requirements for the duty list, and not include Responsibilities. But we must ensure we didn't lose any substantive info: the duty list is captured under Requirements. That's okay. Thus final sections: About the role, Requirements, Qualifications, Benefits, Pay, Schedule. Check if any other content: "General Conditions" includes flexibility, physical capacity, transportation, home office. We'll put those under Schedule. Now produce HTML. Make sure to not include any extra text outside HTML. Let's craft. About the role paragraph: combine the two sentences? We'll keep as one paragraph. Now Requirements ul: each bullet as li. Qualifications ul: each bullet. Benefits ul: maybe split into items: PTO, sick, and holidays; a 403(b) retirement plan; a Health Savings Account; life, short-term, and long-term disability insurance; medical, dental, and vision insurance. Could keep as one li with semicolons but better to split? The instruction: use
• for any list of duties/requirements/benefits. So we can split each benefit as separate li. We'll parse. Benefits list: PTO, sick, and holidays;