For inclusion planning
Balanced placement for inclusion and special education
Inclusion works when support is spread on purpose. Pile the students with the highest needs into one room and even a strong teacher is set up to struggle. Shibutz helps you distribute support needs across classes, lock in the placements that are non-negotiable, and check the load in each room before the lists are final.
Why inclusion placement is easy to get wrong
The hardest part is not identifying needs. It is distributing them fairly across classrooms and staff without breaking a required placement.
Support needs cluster without anyone deciding they should
When lists come together by hand, the students with the most support often end up together, usually because one teacher "is good with them." The result is a room that carries far more than its share.
Required placements are hard to hold across a reshuffle
A student who must be with a specific aide or in a specific room can drift when the rest of the roster gets rearranged. Losing one required placement can undo an entire plan.
Paraprofessional coverage is left out of the math
A class list that looks balanced on paper can be impossible to staff if three students needing an aide land in the same room and the same block.
How Shibutz handles support distribution
You define what "too much" looks like, lock the placements that cannot move, and let the balance run inside those limits.
- 1
Rate support needs on a scale you control
Record support levels on each student so the balance engine treats them as a load to distribute, not a checkbox to ignore.
Set support levels - 2
Lock the placements that cannot move
Pin a student to a specific classroom before generation, so a required placement holds no matter how the rest of the roster shifts.
Set required placements - 3
Check the support load in every room
Review per-class statistics to confirm no single class is carrying an outsized share of high-support students before you finalize.
Review placement balance
Spreading a heavy support load across four classes
A fourth grade has eight students on IEPs, two of whom must stay in specific rooms for aide coverage, and a wide range of reading support needs. Left to a manual draft, most of them would land with the one teacher known for patience.
The inclusion coordinator rates each student’s support level, locks the two required placements to their rooms, and sets the generator to spread support load across all four classes. The result gives each teacher a manageable share instead of concentrating the need.
Reviewing the per-class numbers, the coordinator sees one room still runs slightly heavy and moves a student the aide schedule can absorb. The final lists are ones the teachers and paraprofessionals can actually run in September.
Questions from special education and inclusion teams
- Can we make sure support needs are spread evenly?
- Yes. You rate each student’s support level, and the balance engine distributes that load across classes so no single room carries an outsized share.
- How do we guarantee a required placement holds?
- Lock the student to a specific classroom before you generate. That placement stays fixed while the rest of the roster is balanced around it.
- Can we reflect aide and paraprofessional needs in placement?
- Yes, for placement-level decisions. Use required placements to keep students in the right room and review support load per class before finalizing. Staffing schedules are still planned by your school team.
- Does this replace the judgment of our inclusion team?
- No. It handles the distribution math so your team can focus on the decisions that need human judgment. You review every result and adjust before anything is final.
Build inclusion classes teachers can actually run
Spread support needs on purpose, hold the placements that matter, and check the load in every room.