Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Acceleration Policy topic
No spam. Unsubscribe anytime.
Kutztown staff propose formal acceleration guidelines to identify students for grade/content advancement
Summary
District staff presented draft acceleration guidelines to formalize identification and planning for students ready to move ahead in subject areas; the proposed process uses data teams, teacher input and parent permission and was forwarded to the full board for consideration.
Get email alerts on the Acceleration Policy topic
No spam. Unsubscribe anytime.
District staff presented draft acceleration guidelines intended to create a clear, consistent process for students who demonstrate readiness to accelerate by subject or grade level.
Presenters described the guidelines as a mechanism to identify a small number of students (elementary through middle school) who might accelerate in math or other content areas. The process would rely on teacher input, data‑team review of standardized and local assessments, and evaluation of social‑emotional readiness. Staff emphasized that the decision would be made by a team meeting with parents and relevant educators, similar in structure to existing data‑team or IEP‑style meetings.
Staff said the intent is to limit acceleration to students who demonstrate a clear need and readiness and to avoid ad hoc approaches. Committee members raised scheduling as the key operational constraint: putting a fourth‑ or fifth‑grader into a higher‑grade course can create logistics or extended‑day issues, especially across buildings. Staff said elementary acceleration would generally be implemented in the student’s home building where possible, using in‑building options (e.g., accelerated pacing across a semester) rather than moving students between campuses.
After discussion about team composition, social‑emotional checks, and the need for predictable pathways rather than a fixed menu of options, the committee voted to forward the draft guidelines to the full board with the expectation staff will refine scheduling solutions and provide clearer workflow documentation for building teams.
A staff member summarized the collaborative intent: “we're gonna analyze everything together and then make that decision as a team.” The committee recorded vocal support to move the draft to the full board.

