Sustainable Community Schools Coordinator

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Also must not create sections with filler like "commensurate with experience". We need to parse the posting. Let's extract content: First paragraph: description about CPS, mission, values. That's "About the role" maybe? Actually "About the role" could be overview of position. The posting includes: "Chicago Public Schools (CPS) is a district on the rise..." That's about the organization, not role. Then "The Sustainable Community Schools (SCS) Coordinator is responsible for implementing the Sustainable Community Schools Initiative in a cohort of schools." That's role summary. Then "Job Summary Reporting to the Sustainable Community Schools Manager, the Sustainable Community Schools (SCS) Coordinator will support a shared leadership model with the Chicago Teachers Union." That's also summary. Thus we can put an "About the role" section with that overview. Then responsibilities: list of duties after "The Sustainable Community Schools (SCS) Coordinator will be held accountable for the following responsibilities:" then bullet list (though not bullet but sentences). We need to convert to

• . We'll extract each responsibility sentence. Let's list them: - Support SCS implementation and activities - Implement and guide schools through understanding the SCS pillars and principles, track all activities offered, and monitor funding allocations for a portfolio of participating schools. - Provide operational support for school-based SCS staff and work with key stakeholders, including principals and school leaders, parents, students, vendors, and community-based organizations. - Develop strong, collaborative relationships with program participants and partners - Develop and maintain strong, empathetic relationships with school leaders and staff (including counselors and teachers at CPS schools), partners, and students and their families. - Work closely with CSI team and CPS departments to solve problems on behalf of schools, and broker relationships between schools and community partners; mediate partner issues as needed. - Meet with Lead Partner Agency regularly to provide hands-on coaching to the school Resource Coordinators. - Ensure the development of a school-based leadership team. - Regularly meet with school principals to ensure program delivery meets the needs of the school communities. - Provide training and technical assistance to program participants and partners - Provide program support and guidance to participating schools by planning and implementing professional development activities, trainings, and other resources to address needs that may arise. - Provide ongoing training to school-based and external partner staff in the use required. program tools, such as systems (ex: Cityspan, Foundations tool, etc.) and required documents for compliance and implementation. - Support SCS service delivery and program analysis - Review, approve, and oversee service delivery plans and budgets, monitor service plan compliance and data entry for all CSI activities on a school-by-school basis; collect essential program data and generate reports as needed. - Review and monitor data in Cityspan for accuracy and completion - Respond to all internal and external audit and monitoring requests; support schools in compiling annual implementation binders. - Participate in program quality improvement initiatives - Become trained and certified in the Program Quality Checklist tool and use this tool to observe programs, provide feedback, and make improvements based on outcomes. - Work with other departments in OCCS as well as the Office of Equity to ensure alignment with re-engagement strategies, SEL supports, school-based interventions, and other best practices. - Other duties as assigned. We need to ensure we don't duplicate. Some sentences are similar; we can keep as separate items. Now qualifications: "In order to be successful and achieve the above responsibilities, the Sustainable Community Schools Coordinator must possess the following qualifications:" then subheadings: Education Required, Experience Required, Knowledge, Skills, And Abilities, Conditions of Employment. We need sections: Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Education Required and Experience Required could go under "Requirements" or "Qualifications". The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide mapping. Typically: Requirements could include education and experience. Qualifications could be knowledge, skills, abilities. Skills could be separate but we may combine. We have "Knowledge, Skills, And Abilities" list. That could go under Skills section. We have Conditions of Employment (Chicago residency) maybe under Requirements? Or could be its own but not in list; we could put under Requirements as a note. We have Benefits section described in detail. We have Pay: "Estimated Annual Salary Range 67,000.00" and also "This is a full-time, exempt position that will be paid for time worked on a salary basis." So we have pay info. Schedule: Not explicitly given besides full-time. Could infer full-time but not specific schedule like hours. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. We have Pay stated (salary range). Schedule: not explicitly stated beyond full-time; but "full-time" is a schedule type. Might be acceptable to include Schedule section with "Full-time". However the instruction says avoid filler like "not specified". "Full-time" is specified. So we can include Schedule. But we need to check if they explicitly mention schedule: "This is a full-time, exempt position". So yes. Now we need to remove boilerplate: Posting Date, Primary Location, Job Grade, etc. Those are minor metadata; we can fold into a short

  or drop. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. So we can include a short paragraph at top maybe with Posting Date and Location? But they said fold minor metadata into a short

  or drop it. Probably better to drop them entirely, as they are not substantive. However we need to preserve ALL substantive information; posting date and location may be considered metadata but not substantive? Might be considered minor. I'd drop them. Now we need to output only HTML fragment, no /, no markdown. We'll produce sections as needed. Let's craft:

  About the role

  Chicago Public Schools (CPS) serves over 325,000 students in 500+ schools and employs over 45,000 people, most of them teachers. The district is focused on providing equitable resources and a world‑class learning experience aligned with its six core values: student‑centered, whole child, equity, academic excellence, community partnership, and continuous learning. The Sustainable Community Schools (SCS) Coordinator implements the SCS Initiative in a cohort of schools, reporting to the Sustainable Community Schools Manager in the Office of College and Career Success and supporting a shared leadership model with the Chicago Teachers Union.

  Then Responsibilities.

  Responsibilities

  • Support SCS implementation and activities
  • Implement and guide schools through understanding the SCS pillars and principles, track all activities offered, and monitor funding allocations for a portfolio of participating schools.
  • Provide operational support for school‑based SCS staff and work with key stakeholders, including principals and school leaders, parents, students, vendors, and community‑based organizations.
  • Develop strong, collaborative relationships with program participants and partners
  • Develop and maintain strong, empathetic relationships with school leaders and staff (including counselors and teachers at CPS schools), partners, and students and their families.
  • Work closely with the CSI team and CPS departments to solve problems on behalf of schools, and broker relationships between schools and community partners; mediate partner issues as needed.
  • Meet with the Lead Partner Agency regularly to provide hands‑on coaching to the school Resource Coordinators.
  • Ensure the development of a school‑based leadership team.
  • Regularly meet with school principals to ensure program delivery meets the needs of the school communities.
  • Provide training and technical assistance to program participants and partners
  • Provide program support and guidance to participating schools by planning and implementing professional development activities, trainings, and other resources to address needs that may arise.
  • Provide ongoing training to school‑based and external partner staff in the use of required program tools, such as systems (e.g., Cityspan, Foundations tool, etc.) and required documents for compliance and implementation.
  • Support SCS service delivery and program analysis
  • Review, approve, and oversee service delivery plans and budgets, monitor service plan compliance and data entry for all CSI activities on a school‑by‑school basis; collect essential program data and generate reports as needed.
  • Review and monitor data in Cityspan for accuracy and completion
  • Respond to all internal and external audit and monitoring requests; support schools in compiling annual implementation binders.
  • Participate in program quality improvement initiatives
  • Become trained and certified in the Program Quality Checklist tool and use this tool to observe programs, provide feedback, and make improvements based on outcomes.
  • Work with other departments in OCCS as well as the Office of Equity to ensure alignment with re‑engagement strategies, SEL supports, school‑based interventions, and other best practices.
  • Other duties as assigned.
  Now Requirements: Education and Experience.

  Requirements

  • Education: Bachelor’s degree from an accredited college or university required; Master’s degree preferred.
  • Experience: Minimum of five (5) years of relevant work experience coordinating programs and analyzing program data; experience in urban education or related fields preferred.
  • Conditions of Employment: Must establish and maintain Chicago residency within six months of hire and maintain residency throughout employment (Illinois residency required for all CPS employees).
  Now Qualifications: maybe we can put Knowledge, Skills, Abilities under Skills. But we have a separate Qualifications heading. Let's put Qualifications for knowledge, skills, abilities.

  Qualifications

  • Ability to conduct multiple projects concurrently, both independently and in a team environment.
  • Strong service and support orientation towards schools and school communities.
  • Strong analytical and project management skills.
  • Exceptional verbal and written communication and negotiation skills necessary to effectively communicate with a variety of audiences.
  • Ability to work with minimal supervision outside of a formalized, central office setting.
  • Ability to manage multiple projects simultaneously and maintain paperwork and documentation.
  • Familiarity with non‑profit organizations and school‑community partnerships.
  • Strong ability to organize and prioritize information quickly and strategically.
  • . We'll keep as list. Now Skills: maybe we can combine but we already used Qualifications for KSAs. Could also have Skills separate but might be redundant. The instruction: prefer a few substantive sections over many thin ones. So we could merge Qualifications and Skills into one section called "Qualifications & Skills". But headings list includes both Qualifications and Skills; we could still include both if they have content. However we have content for both: Qualifications (knowledge, skills, abilities) and Skills maybe we could list specific skills like "Project management", "Data analysis", "Communication". But we already covered those. To avoid thin sections, we could combine them into one heading "Qualifications". But the instruction says use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't require us to use all; we can omit sections lacking real specific content. So we can omit Skills if we feel it's covered. However we have a list of abilities that could be considered skills. But we already put them under Qualifications. That may be okay. Now Benefits: we have detailed benefits