Anti-Trafficking Specialist for VOCA

We need to output HTML fragment with sections: headings

for sections like 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 preserve all substantive info, no invented. Remove boilerplate like cookie/navigation/legal/EEO etc. The posting includes sections: Who We Are, CITY MISSION’S MISSION, Job Summary, Essential Duties And Responsibilities (with many subpoints), Minimum Knowledge, Skills, And Abilities (Education, Experience, Skills/Abilities), JOB LIMITATIONS, PHYSICAL DEMANDS/WORK ENVIRONMENT, COMPETENCIES, PERFORMANCE MEASUREMENTS. Also includes PAY GRADE: 205 PAY RANGE: ($22.57 to $27.09). Also STATUS TYPE: RFT (full-time). FLSA CATEGORY: Non-Exempt. Also location/dept: City Mission. People manager: No. Reports to: STOP-IT Program Manager. We need to decide sections: About the role (maybe Job Summary). Responsibilities (Essential Duties). Requirements/Qualifications (Education, Experience). Skills (Skills/Abilities). Benefits? Not mentioned. Pay? Yes pay range given. Schedule? Not given explicitly but STATUS TYPE: RFT implies full-time; maybe we can include Schedule as full-time? But rule: never create Pay/Schedule/Benefits sections unless posting actually states them. Pay is stated: PAY RANGE: ($22.57 to $27.09). So we can include Pay section. Schedule: Not explicitly stated; only STATUS TYPE: RFT (regular full-time). Could infer schedule but not explicit; better not to include Schedule unless explicit. Benefits: not stated. So we omit Benefits and Schedule. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format them. We need to avoid boilerplate like "This job description is not designed to cover..." maybe that's substantive? It's a statement about job description; we should keep it? It's part of Other Duties. It's substantive but maybe we can keep as prose. We need to remove duplicated lines, cookie/navigation/legal/EEO etc. There's none evident. We need to output only HTML fragment, no /, no markdown fences. Let's structure:

  About the role

  Job Summary ...

  Maybe also include location etc in About the role? Could include location/dept, reports to, FLSA, status type, pay grade? But pay grade we will put in Pay section. Could include location in About the role as prose. Better: About the role includes location, department, reports to, FLSA, status, etc. Responsibilities: list essential duties. Requirements/Qualifications: Education, Experience. Skills: Skills/Abilities. Pay: Pay range. Also maybe include Physical Demands/Work Environment as a section? Not in allowed headings list but we could treat as Responsibilities? But rule: use headings only from list; we could not create other headings. So we need to fit that info into existing sections. Could put Physical Demands under Responsibilities as a

  or maybe under About the role? But we need to preserve all substantive info. We could add a

  under Responsibilities for physical demands. Similarly Competencies and Performance Measurements could be under Requirements or Skills? Might be better to put them under Requirements/Qualifications as additional bullet points? But they are not exactly qualifications; they are competencies and performance measurements. Could treat them as part of Skills? Or maybe we can create a section "Competencies" but not allowed heading. The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we should use those headings only? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings only. So we must map content to those headings. Thus we need to fit all info into those sections. Let's plan: About the role: includes Who We Are, City Mission’s Mission, Job Summary, location/dept, reports to, FLSA, status type, maybe pay grade? But pay grade we will put in Pay. Responsibilities: Essential Duties And Responsibilities (all bullet points), plus Physical Demands/Work Environment, Intra-Agency Responsibilities, Community Relations, Continuing Education, Other Duties, Job Limitations? Actually Job Limitations maybe under Requirements? But we can put under Responsibilities as a note. Requirements: Education, Experience, maybe also Minimum Knowledge, Skills, And Abilities? Actually that's split: Minimum Knowledge, Skills, And Abilities includes Education, Experience, Skills/Abilities. But we have Skills separate. So Requirements could be Education and Experience. Skills could be Skills/Abilities. Qualifications: maybe we can combine with Requirements? But we have both headings; we could use Requirements for Education/Experience, Qualifications for Minimum Knowledge, Skills, And Abilities? But Skills heading also exists. Hmm. We have headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide mapping: - About the role: overview, mission, job summary, location, reporting, FLSA, status. - Responsibilities: essential duties, intra-agency, community relations, continuing education, other duties, job limitations, physical demands. - Requirements: Education, Experience. - Qualifications: Minimum Knowledge, Skills, And Abilities? But Skills heading also there; maybe Qualifications for Minimum Knowledge, Skills, And Abilities (excluding the Skills/Abilities part?), and Skills for the Skills/Abilities list. But the Minimum Knowledge, Skills, And Abilities section includes Education, Experience, Skills/Abilities. Since we already have Education/Experience under Requirements, and Skills under Skills heading, Qualifications could be left empty? But we must not create empty headings. So maybe we combine Requirements and Qualifications: Requirements for Education and Experience, Qualifications for Minimum Knowledge, Skills, And Abilities (including Skills/Abilities). Then Skills heading maybe not needed. But we have Skills heading available; we could still use it for something else like "Core Competencies" but that's not in posting. Better to follow the instruction: use headings only when posting has real specific content for it. So if we don't have distinct content for Skills beyond what's in Minimum Knowledge, we could omit Skills heading. But we have Skills/Abilities content; we could put that under Skills heading. Then Qualifications could be for Minimum Knowledge (maybe knowledge of principles, data management etc). But the Minimum Knowledge, Skills, And Abilities includes knowledge, skills, abilities. Hard to split. Simplify: Use Requirements for Education and Experience. Use Skills for Skills/Abilities. Omit Qualifications heading (since no distinct content). That respects rule: only include heading when posting has real specific content for it. Qualifications may be considered covered by Requirements and Skills; we can omit. Thus sections: About the role, Responsibilities, Requirements, Skills, Pay. Check if any other content like "Competencies" and "Performance Measurements" could go under Skills or Responsibilities? Could be under Skills as additional bullet points. We'll include them under Skills as bullet points. Now we need to format lists. Let's extract details. About the role: - Who We Are: At The Salvation Army, we are dedicated to Doing the Most Good. We are made up of thousands of officers, soldiers, staff, volunteers, donors, and partners working together to holistically meet the physical, emotional, and spiritual needs of our most vulnerable neighbors. - CITY MISSION’S MISSION: To assist in accomplishing the mission of The Salvation Army through the coordination of all mission activities, corps and social service, within the City of Chicago. - Job Summary: The Anti-Trafficking Specialist for VOCA provides short-term, emergency case management services to survivors of Human Trafficking who are awaiting placement or transition into longer-term programs. Case management activities will result in 1) establishing a trusting and supportive relationship during a time of crisis, 2) addressing immediate safety concerns and stabilizing urgent needs such as housing, food, medical care, and legal protections, and 3) ensuring a coordinated and smooth transition into appropriate long-term services through active advocacy and resource connection. Carry out functions that result in achieving expected outcomes as identified in the STOP-IT Program Plan. Special functions may be assigned. - LOCATION/DEPT: City Mission - PEOPLE MANAGER: No - REPORTS TO: STOP-IT Program Manager - FLSA CATEGORY: Non-Exempt - STATUS TYPE: RFT - PAY GRADE: 205 (but we will put in Pay) We'll combine into prose. Responsibilities: list essential duties and responsibilities (the long list). Also Intra-Agency Responsibilities, Community Relations, Continuing Education, Other Duties, Job Limitations, Physical Demands/Work Environment. We need to preserve all substantive info; we can break into bullet points for each major duty. Let's extract bullet points from Essential Duties And Responsibilities: - Provide case management services as directed by the agency’s program policies and procedures, focused on assisting victims in leaving human trafficking. - May be required to conduct a majority of direct service or outreach-related activities off-site. - Implements trauma-informed, survivor-centered, and strengths-based service delivery consistent with STOP-IT program philosophy. - Provides short-term stabilization services focused on immediate safety, housing access, emergency financial assistance, and crisis intervention. - Maintains an active caseload consistent with grant expectations. - Coordinates warm handoffs to long-term service providers and ensures continuity of care. - Develops transition plans to prevent service gaps. - With close supervision, conducts an assessment of the victim’s immediate threat of harm. - Utilizes and implements the Motivational Interviewing model for assessing the trafficking victim’s readiness for recovery or for leaving their trafficking situation, for designing interventions for planning the victims' escape strategies. The strategies utilized in this model include: 1) build trust, 2) strengthen victim-identity, 3) teach informed decision-making skills, 4) create hope of escape, 5) problem-solve barriers to leaving, 6) assist the victim to plan effective escape strategies when he or she are safe and fully prepared to do so, 7) assist in the escape. - Consults with supervisor in reviewing and assessing the current stages of outreach cases. - Develops and implements appropriate intervention strategies that recognize the current stage, and supports the victim’s movement to the next stage toward exiting trafficking. - Regularly reviews client’s progress with the supervisor. - Identifies community resources and assists in developing linkages with providers and law enforcement that support the implementation of the STOP-IT program and the client outcomes. - Maintains frequent case-related contacts with local resources, collateral sources, public and private agencies and organizations, and law enforcement, to advocate on behalf of clients. - Refers clients for services, as needed. - Obtains appropriate Release of Information before a referral is made. - Under the supervisor’s direction, processes requests for financial assistance to clients within agency policy. - In consultation with the Supervisor, initiates contact with the Illinois Department of Children and Family Services as a mandated reporter when child abuse or neglect is suspected. - In Consultation with the Supervisor, initiates contact with the Elder Abuse Hotline as a mandated reporter when elder abuse is suspected. - Keeps supervisor informed regarding case related subpoenas and attends court