Network School Support Administrator, Network 13

Chicago Public Schools · Chicago, IL · 1 mo ago

Information Technology$128k–$157k/yrFull-time

We need to output HTML fragment with 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. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like cookie/navigation/legal/EEO etc. The posting includes description about CPS, mission, commitments, values, network description, job summary, responsibilities, qualifications, other requirements, knowledge/skills/abilities, conditions of employment, posting date, location, position type, overtime status, salary range. We need to map to sections. - About the role: could include the job summary and description of role, maybe the mission statements? The "About the role" section should contain prose about the role. We can include the job summary paragraph(s) and maybe the description of CPS? The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". So we can include about the role: the job summary and maybe the description of CPS mission? The posting includes a paragraph about CPS, its mission, commitments, values, network description. That is more about the district, not strictly about the role. But we could include that as part of About the role? Usually "About the role" includes summary of role and maybe context. We'll include the job summary paragraph(s) and maybe the description of CPS mission? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep all substantive info. That includes the description of CPS, mission, commitments, values, network description. Where to put them? Could be in About the role (context) or maybe a separate section like "About CPS"? But we only allowed headings from list. We could put that content under About the role as prose. That seems acceptable. - Responsibilities: list of duties. Use

. - Requirements: maybe education required? Or "Experience Required"? The posting has "Education Required", "Experience Required", "Other Requirements". Could combine into Requirements section. - Qualifications: maybe "Knowledge, Skills, And Abilities"? Actually that is skills. Qualifications could be education and experience. But we have both Requirements and Qualifications headings allowed. We need to decide what goes where. The instruction: "Prefer a few substantive sections over many thin ones." So we might combine education/experience into Requirements, and knowledge/skills/abilities into Skills. Qualifications maybe could be left out if not distinct. But we have to include sections only when posting has real specific content for it. We have content for Education Required, Experience Required, Other Requirements, Knowledge, Skills, And Abilities. Could map: - Requirements: Education Required + Experience Required + Other Requirements (like on-site, transportation). That seems substantive. - Skills: Knowledge, Skills, And Abilities list. - Qualifications: maybe we could include "Valid Professional Educator License (PEL) and an Administrative Endorsement / PK–12 Principal Endorsement required; Master’s degree preferred" as qualifications. But that overlaps with Education Required. Could treat Education Required as part of Qualifications. But we need to avoid duplication. Let's think: The posting has sections: Education Required, Experience Required, Other Requirements, Knowledge, Skills, And Abilities. Also conditions of employment (Chicago residency). Also Pay (salary range). Also Schedule? Not explicitly given; it's full-time exempt position. Could infer schedule: full-time. But we should not create Schedule unless posting actually states them. It says "This is a full-time exempt position". That indicates schedule: full-time. So we could include Schedule section with "Full-time". However, the instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state full-time, so we can include Schedule with "Full-time". Pay: salary range given, so include Pay. Benefits: not mentioned explicitly; no benefits details. So we should not create Benefits section. Thus sections: About the role, Responsibilities, Requirements, Skills, Pay, Schedule. Possibly also Qualifications? But we have Education Required etc under Requirements. Could also have Qualifications for license etc. But we can incorporate license into Requirements or Skills? It's a qualification. Might be better to have Qualifications section for license and preferred master's. But we already have Education Required covering degree. Could move license to Qualifications. Let's decide: - About the role: context + job summary. - Responsibilities: list. - Requirements: Education Required + Experience Required + Other Requirements (on-site, transportation). Could also include conditions of employment? That's more about employment conditions; maybe could be part of Requirements? But conditions of employment is separate: Chicago residency requirement. Could be part of Requirements or maybe a separate section? Not in allowed headings. Could put under Requirements as a bullet. - Skills: Knowledge, Skills, And Abilities list. - Pay: salary range. - Schedule: full-time. We should not include Qualifications separately if we covered license elsewhere. But we have license requirement; we could put under Requirements as "Valid Professional Educator License (PEL) and Administrative Endorsement / PK–12 Principal Endorsement required". That is a requirement. So Requirements will include education, experience, license, other requirements, conditions. Thus we have all content. Now we need to format. We must not include markdown code fences. Just raw HTML. We'll produce:
About the role

... prose ...
Then
Responsibilities
Then
Requirements
Then
Skills
Then
Pay
...
Then
Schedule
...
We need to preserve all substantive information. Let's extract. About the role prose: Should include the description of CPS, mission, commitments, values, network description, job summary. Let's craft a paragraph that includes all that info without omitting. Original text: "Chicago Public Schools (CPS) is one of the largest school districts in the United States, serving over 325,000 students in 500+ schools and employing approximately 45,000 people, most of them teachers. CPS has set ambitious goals to ensure that every student, in every school and every neighborhood, has access to a world-class learning experience that prepares each for success in college, career, and civic life. In order to fulfill this mission, we make three commitments to our students, their families, and all Chicagoans: academic progress, financial stability, and integrity. Six core values are embedded within these commitments – student-centered, whole child, equity, academic excellence, community partnership, and continuous learning. District-run CPS schools are organized into 18 networks, which provide administrative support, strategic direction, and leadership development to the schools within each network. This network support model is designed to support the unique needs of CPS elementary and high schools and their school leaders that focus exclusively on those needs. Network 13 focuses on the elementary schools in the south geographic areas of Chicago. Job Summary Reporting to the Network Chief of Schools, the Network School Support Administrator (NSSA) will coordinate and facilitate the implementation of multiple initiatives designed to support parents, community stakeholders, principals, and network leaders. This role partners with Central Office (CO) function owners to build and maintain efficient systems of operation that serve student learning and district accountability, ensuring alignment with CPS policy and procedures. This is a full-time exempt position that will be paid for time worked on a salary basis." We need to keep all that. We'll put in
maybe multiple paragraphs but okay. Now Responsibilities: list bullet points from "The Network School Support Administrator will be held accountable for the following responsibilities:" then list. Let's extract each bullet: - Ensure focused, differentiated support is provided to Principals utilizing district data to monitor and support district initiatives and identify areas requiring additional Network or CO support - Support Network Chiefs and Deputies in the supervision, development, and performance management of Network Office staff and dotted line resources, including performance evaluations - Support Network Chiefs and Deputies, in partnership with appropriate CO function owners, in the day-to-day management, monitoring, and support of non-instructional school operations, including but not limited to: * School budgets, contracts, and policy alignment; * Manage day-to-day concerns related to CPS policies and procedures * Support and escalation for school auxiliary services (e.g., facilities, transportation, nutrition, information technology, etc.) * Misconduct, incident, and accident reports * Suspension appeals, expulsions, and emergency referrals * Grade changes * Student enrollment and transfers * Support schools in coordinating evacuation and other school drills and emergency plans; Partner with CO departments and external agencies, as directed, to support the response to and resolution of school operational emergencies * Field trip/travel approvals - Collaborate with CO departments on issues related to student achievement and school support needs - Build and manage cohesive partnerships and professional relationships both internally and externally to support schools in realizing the District’s vision - Create and share clear, transparent communications regarding CPS policies and procedures - Identify and implement solutions to improve student attendance in partnership with Network staff - Manage Summer Bridge programs in collaboration with Network staff - In collaboration with Network Chiefs and school principals, resolve concerns regarding schools, parents, and stakeholders - Facilitate parent conferences in partnership with schools and Network leadership as needed - Attend Board Meetings to support families and schools as applicable - Other duties and workstreams as assigned We need to preserve all. Some bullets have sub-bullets. We'll flatten maybe but keep content. Could keep sub-bullets as separate
items. We'll produce
- ...

Network School Support Administrator, Network 13

About the role

Responsibilities

Requirements

Skills

Pay

Schedule

Similar jobs

Network School Support Administrator, Network 6

Network School Support Administrator, Network 3

Network School Support Administrator, Network 7

Network School Support Administrator, Network 8

Network School Support Administrator, Network 9

Network School Support Administrator, Network 10