Outreach Coordinator

We need to output HTML fragment with sections: use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the posting. First, location line: "St Louis, MO, US, 63101-1114" - minor metadata, we can put in a short

maybe. Then description: "The Archdiocese of St. Louis Catholic Education and Formation features an expansive coalition..." This is about the organization, maybe "About the role"? Actually "About the role" is typical heading for position summary. We have "Position Summary" paragraph: "Catholic Charities of the Archdiocese of St. Louis, through our service line St. Patrick Center, is hiring an Outreach Specialist to provide community outreach to service agencies and homeless veterans. We are looking for a dedicated individual to engage help those on their path to housing and healing. This specialist will explore and investigate areas within Warren, St. Charles, St. Francois, Franklin, Washington, Lincoln, St. Genevieve, and Jefferson counties in Missouri. As an Outreach Specialist, conducting assessments and navigating social service entities will be daily tasks to ensure every individual receives the support they deserve. The core working hours are Monday through Friday 8:00am - 4:30pm." That includes schedule info: core working hours Monday-Friday 8:00am-4:30pm. So we can have a Schedule section with that. Also "Overview And Responsibilities" then list of duties. So we can have Responsibilities section with

• . Then "Knowledge And Experience Requirements" then list of abilities. That could be Requirements or Qualifications? Usually Requirements is knowledge/experience, Qualifications is education etc. We'll map: Knowledge And Experience Requirements -> Requirements (or Qualifications?). Then "Skills And Competencies Required" includes education, driver license etc. That could be Qualifications (or Skills). The instruction says use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide which content fits which. We have: - About the role: could be the Position Summary paragraph (maybe plus brief org description). We'll put that. - Responsibilities: the list under "Overview And Responsibilities". We'll extract each sentence as bullet. - Requirements: maybe the "Knowledge And Experience Requirements" list (abilities). We'll put that. - Qualifications: maybe the "Skills And Competencies Required" list (education, driver license, etc). We'll put that. - Skills: maybe we could combine but we already used Skills heading for something else? Actually we have both Skills and Competencies Required; we could treat that as Skills section. But we already used Qualifications for education etc. The instruction says we can have both Qualifications and Skills sections. We need to decide content for each. We have "Skills And Competencies Required" includes: High school diploma and GED required. BSW or bachelor’s degree preferred. Driver license required (MO residents require a Class E) Valid and current auto insurance required. Reliable vehicle required. Residence within the specified region preferred but not required. Veteran status preferred. Ability to work a minimum of 37.5 hours per week. That seems like qualifications (education, licensure) and also some skills (ability to work hours). Could split: Qualifications: education, driver license, insurance, vehicle, residence, veteran status. Skills: ability to work minimum hours, maybe also other abilities? But we already have abilities in Requirements. Better: Use Requirements for knowledge/experience (the list of abilities). Use Qualifications for education/licensure (HS diploma, BSW preferred, driver license, auto insurance, reliable vehicle, residence preferred, veteran status). Use Skills for maybe "Ability to work a minimum of 37.5 hours per week." plus maybe "Self-motivation due to autonomous nature" etc? Actually those are in Knowledge And Experience Requirements list. Let's re-examine that list: "Knowledge And Experience Requirements Previous experience and knowledge from working with the homeless Experience working in a social service agency. Familiarity with the fields of mental illness and drug/alcohol abuse; symptoms, terminology, and interventions Familiarity with appropriate and available community resources Ability to recognize personal strengths and limitations regarding time, skill, and knowledge. Ability to communicate effectively with both clients, social service agencies, and team members. Ability to build productive relationships within the community and with prospective clients. Ability to set limits and engage with clients. Ability to assess persons and situations. Ability to work in team environment. Excellent verbal and written communication skills Crisis intervention expertise Self-motivation due to the autonomous nature of the position Sensitivity to cultural diversity Ability to work in a team atmosphere Moderate computer skills" That's a long list of abilities/knowledge. So we can put that under Requirements. Then Skills And Competencies Required list: education, driver license, etc. That could be Qualifications. But we still have a Skills heading unused. Could we put something under Skills? Maybe we could treat "Ability to work a minimum of 37.5 hours per week." as a skill? Or we could combine Skills and Qualifications? The instruction says prefer a few substantive sections over many thin ones. So maybe we should not create a Skills section if content is thin. We could merge Skills into Qualifications or Requirements. But we need to follow headings: we can omit Skills section if no real specific content. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can omit Skills if we don't have distinct content. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Schedule. Possibly Pay? No pay info. So omit Pay. Now Benefits: we have a paragraph: "Benefits As a part of the Catholic Charities family, you’ll have the resources to care for those closest to you. Options include generous parental leave policies, flexible working arrangements, group life insurance, permanent health insurance, and dedicated support to help you find the right child care or elder care." That's specific content, so Benefits section. Schedule: we have core working hours Monday through Friday 8:00am - 4:30pm. Also ability to work minimum 37.5 hours per week (but that's more like requirement). We'll put schedule in Schedule section. Now About the role: we can combine the initial description about the Archdiocese and the Position Summary. Let's craft a concise paragraph preserving all substantive information. Must not invent or summarize away detail. We need to preserve all substantive information; we can rephrase but must keep all facts. That's tricky: we must not lose any detail. So we need to include all details from the posting. Let's extract all factual statements. From the top: - Location: St Louis, MO, US, 63101-1114 (maybe minor metadata, we can put in a short p). - The Archdiocese of St. Louis Catholic Education and Formation features an expansive coalition of schools that allow our children to develop a sense of purpose and value, receive a higher quality education, join a welcoming community and feel secure in a a dynamic future. We have a rich history, with its establishment 200 years ago by St. Rose Phillppine Duchesne. A coalition of schools serving over 50,000 students (PreK-12) within an 11-county area. The educational experience provided to our students and their families is rooted in a higher calling from God to honor and celebrate the gifts He has given us. That's about the organization, not the role but we can include as About the role? Might be considered "About the role" but it's about the organization. However we can still include it as part of About the role section (makes sense). We'll keep all that. - Position Summary: Catholic Charities of the Archdiocese of St. Louis, through our service line St. Patrick Center, is hiring an Outreach Specialist to provide community outreach to service agencies and homeless veterans. We are looking for a dedicated individual to engage help those on their path to housing and healing. This specialist will explore and investigate areas within Warren, St. Charles, St. Francois, Franklin, Washington, Lincoln, St. Genevieve, and Jefferson counties in Missouri. As an Outreach Specialist, conducting assessments and navigating social service entities will be daily tasks to ensure every individual receives the support they deserve. The core working hours are Monday through Friday 8:00am - 4:30pm. - Overview And Responsibilities: list of duties (we'll bullet). - Knowledge And Experience Requirements: list of abilities (we'll bullet under Requirements). - Skills And Competencies Required: list of qualifications (education, driver license, etc.) (we'll bullet under Qualifications). - Benefits: paragraph. - Also there is "Resources for Which Accountable None" - minor metadata, can drop. - EEO statement etc - drop. - Pre-Employment Screening etc - drop (boilerplate). - Our Mission etc - maybe could be considered About the role? It's mission statement. Could include but it's boilerplate? It's not EEO but still maybe considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Mission statement might be considered boilerplate but it's substantive about organization. However it's not directly about the role. Might be okay to keep? Safer to drop as it's not directly about the role and could be considered boilerplate. The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. Mission not listed. But to be safe, we could keep it under About the role? It's not duplicated. I'd keep it as part of About the role maybe. But we must preserve ALL substantive information. The mission statement is substantive about the organization's purpose. It might be considered relevant. I'd include it. Now we need to output HTML fragment only, no markdown. We'll structure:

  St Louis, MO, US, 63101-1114

  About the role

  ... (combined org description + position summary + mission)

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Qualifications

  • ...
  ...

  Benefits

  ...

  Schedule

  Core working hours: Monday through Friday 8:00am - 4:30pm.

  We need to ensure we don't repeat job title as heading (we didn't). No Job ID. Now we need to extract each bullet precisely. Let's copy the responsibilities list from "Overview And Responsibilities". The text: "Explore and investigate areas where potential clients may be staying. Engage clients in conversations regarding substance abuse, mental health and other issues that keep them on the street. Respond to calls and requests from the community to assist homeless persons when possible. Be able to complete program assessments where veteran is currently located. Transport clients or veterans needing services as needed. Make persons in need of assistance aware of community resources, especially from St. Patrick Center’s SSVF program. Complete initial assessments on veterans seeking assistance and forward assessments to case managers and the program manager. Research various social service agencies to understand intake procedures and criterion. Conduct regular visits to social service agencies to inform them of the SSVF program and criteria for referrals. Refer clients to appropriate community agencies, assisting clients when needed. Maintain appropriate documentation of all outreaches provided to agencies and clients. Record services provided in CaseWorthy and keep all paperwork updated. Attend local Continuum of Care meetings to inform agencies regarding the SSVF program. Detailed knowledge of SSVF grant and SPC Policy & Procedures to assist case managers with following grant guidelines. Complete all reports including expense reports in a timely and accurate manner