
A better class assignment system may mean clearer ownership and a shared checklist, not necessarily new software. Before changing tools, look for recurring process failures and collect evidence of where the work breaks down. These five signs are prompts for a local review, not claims from school case studies.
If staff cannot explain why one room has a different support load, inspect the placement criteria, provision timetable, and review record. An unequal count may be justified by staffing; it may also be an oversight. Do not infer teacher burnout or student outcomes from the class list alone.
Try a room-by-room support check first. If the evidence exists but is repeatedly lost during sorting, a system that keeps inputs and draft results together may help.
Count requests with no acknowledgment, no named reviewer, or conflicting replies. Complaints do not by themselves prove an unfair placement. They can reveal an unclear process or a genuine unmet need that needs attention.
Assign one request owner and publish the criteria and review route. The parent-request guide includes sample replies and an exception workflow.

Log where staff retype rosters, reconcile different versions, or redo a draft after a missed rule. Separate essential staff review from avoidable rework. The time worksheet uses consistent workload stages and explains person-hours versus elapsed time.
A controlled roster source may be enough. If repeat import is needed, test mapping presets and duplicate review rather than assuming another upload is harmless.
Ask whether reviewers can compare headcounts, current learning needs, provision, and relationship constraints against agreed criteria. Later differences in class attainment do not establish that placement caused them; teaching, attendance, provision, and other factors also need consideration.
Start with the worked before-and-after balance check. Choose a process that makes accepted tradeoffs visible rather than presenting a single score as proof of fairness.
A separation in an email but not in the draft, or a fixed placement lost after a revision, calls for a traceable rule record. Keep the source, owner, current decision, and final check together. Confirm siblings with staff and families; do not rely on surname matching.
Use a second-person check before release. In Shibutz, supported preferences, restrictions, and required placements can be recorded before generation, but staff still need to verify the result.
Document the recurring failure, pilot one change, and compare effort and review quality on the same workload. Include training and cost. The cost worksheet avoids counting meetings and opportunity costs twice.
The placement readiness quiz can help start the discussion; it is not an independent assessment of a school. To evaluate Shibutz, read the product walkthrough and create a free account.
Use a practical procurement checklist for student placement software, including what data to share, GDPR review questions, and Shibutz source-to-claim notes.
Review external-ID matches and choose update, skip, or add as new before saving a repeat roster import. See examples and limits of duplicate detection.
Use a worked SIS mapping example, save a reusable column preset, and review repeat imports in Shibutz. Spreadsheet import is not live SIS sync.
Tools, product walkthroughs, and guides to put balanced class placement into practice.
Answer a few quick questions to see how ready your school is for balanced, low-stress class placement.
DocsDownload four editable Word templates for teacher input, staff review, family communication, and final sign-off.
ProductSee how roster import, placement rules, and generated drafts support staff review.