5 common mistakes in class list creation (and how to fix them)

When a draft class list does not hold up to review, find the failed check before moving more students. These five mistakes are diagnostic patterns, not reported school case studies. Each includes evidence to inspect, a repair, and a way to check the repair worked.

Use the sequence below during review: verify the roster, separate hard rules from preferences, check room and support capacity, then compare the approved version with the file ready for release. The balanced class-list checklist is the companion signoff record; this page is for diagnosing why a check failed.

1. An average conceals a concentration of needs

The warning sign is a similar class average alongside a very different mix of support needs. Inspect the counts in each current assessment band, the unknown values, and the provision required. Check reading and mathematics separately rather than combining them into one ranking.

Repair the draft against your agreed balance goals, then ask support staff to confirm that provision can be delivered. Recount each affected room after a move. Do not claim that mixed groups guarantee higher attainment or assign advanced students a standing duty to tutor peers.

2. A request bypasses the decision policy

Look for changes with no recorded reason, different answers from different staff, or teacher requests treated as promises. The question is whether the same criteria were applied, not how often a parent contacted the school.

Route requests through one owner. Record the need, decision, and rationale; recheck any resulting move before approval. Use the parent-request triage and sample replies to explain the process without disclosing another student's information.

3. A preference has become an impossible rule

Inspect linked pairs, not just individual rows. Synthetic example: A must stay with B, B must stay with C, and A must stay apart from C. No arrangement can satisfy all three hard rules. Generating another draft without changing the inputs will not resolve that contradiction.

Ask the rule owners which entries are genuine requirements and which are preferences. Correct the inputs, retain documented safety requirements, and rerun the relationship check. In Shibutz, the pre-generation checks flag several kinds of conflict, but passing a check is not staff approval.

4. Equal class sizes override a room limit

Count capacity per room. In the synthetic 72-student example, three groups of 24 exceed the first room's cap of 20. Total seats are sufficient only because the other rooms hold 24 and 28.

Repair the room counts without losing required placements or support. Reconcile the roster against enrollment: every student exactly once, no unknown students, and no room above its approved limit. If total capacity is insufficient, escalate the room plan rather than hiding the gap in a larger class.

5. Approval and the exported list refer to different versions

Check the date and version of the approved draft against the file being shared. A late arrival, withdrawal, or revised request can make yesterday's signoff stale even if the filename still says final.

Keep a change log, name the person authorized to reopen a list, and rerun the checks for affected rooms. Use the release and signoff checklist before updating the school's systems or notifying families.

Choose the smallest repair that addresses the cause

An incorrect roster needs correction; contradictory rules need a decision; insufficient seats need a capacity plan. None is fixed by a more persuasive description of the draft. For review tradeoffs, see ten tips for balanced classes. For a place to record rules and review proposed assignments, start a Shibutz workspace.