Timetable Management for K-12 Schools

PowerSchool Scheduler and Infinite Campus Scheduling are the two dominant K-12 SIS-integrated scheduling tools in the US market, together serving a majority of US public school districts. Both include native support for rotating schedules, block schedules, homeroom, and advisory. OpenEduCat offers the same core scheduling capabilities on an open-source LGPLv3 license, typical district cost lands at 40-70% below PowerSchool or Infinite Campus, savings redirect to staffing or instructional programs. Districts requiring per-district scheduling customization avoid the PowerSchool customization queue (typically 3-9 months for custom development) because OpenEduCat modifications are standard Python module work.

Students with IEP or 504 Plans have documented service minutes (special education pull-out, speech-language pathology, occupational therapy, physical therapy, ELL push-in, counselor consult) required per week. The scheduling engine reads the IEP / 504 document, extracts required service minutes per service area, and constrains the student's schedule to meet or exceed those minutes. Related-service providers (speech pathologists, OTs, PTs, counselors) schedule across multiple students without conflict, the system optimizes provider schedules against student availability. Automatic alerts trigger when a student's scheduled minutes fall short of IEP requirements, the special education coordinator sees the shortfall list weekly, not at annual IEP review when the shortfall has compounded.

US public school teacher contracts commonly specify daily prep-period minimums (typically 45-50 minutes per day, often collectively bargained), weekly prep minimums, daily duty maximums (cafeteria, hallway, arrival, dismissal), and instructional-time maximums (some contracts cap instructional periods at 5 or 6 per day). Independent school teacher contracts specify similar constraints per school policy. The scheduling engine treats prep and duty constraints as hard constraints, no teacher receives a schedule violating the contract. When constraints conflict (small school with high duty coverage need vs teacher prep requirements), the engine flags the conflict for administrative resolution rather than silently violating the contract.

Yes. Elementary self-contained classrooms (one teacher teaches most subjects to one classroom cohort, with specialist rotation for art, music, PE, library, and computer science) schedule with the specialist rotation configured centrally. Middle school interdisciplinary teams (Team Alpha with 4 core teachers sharing about 100 students, Team Beta with a different faculty and cohort) schedule with common planning periods for team teachers, team-based scheduling for students, and team-level parent communication. Departmentalized middle school (traditional subject-specialist model where students rotate to different teachers) configures separately. Schools blending the two structures (self-contained core with departmentalized specials) handle in one master schedule.

Rotating schedules (Day A / Day B rotation common at K-8 schools with 30-year traditions; 1-8 rotation common at independent day schools where an 8-day cycle allows every subject to meet in every period across the cycle; 4x4 block common at US high schools where 4 courses meet per day rotating semester by semester; A/B block alternating daily block schedule) each configure with their own rotation pattern. The engine reads the rotation type, applies the correct interpretation to attendance, gradebook, and parent-facing calendar, and publishes the correct day designation. Rotation-specific edge cases (school closure days shifting the rotation, professional development days maintaining rotation, snow day insertion) handle per school policy.

Yes. K-12 schools with separated lower school, middle school, and upper school campuses (common at independent schools with 800+ students, typical at some parochial diocesan schools with separated K-8 and 9-12 campuses) schedule from one platform. Shared faculty (a Latin teacher covering middle school in mornings and upper school in afternoons, or a math coach coaching across campuses) schedules with travel-time constraints between campuses. Cross-campus students (a 5th grader at the lower school with orchestra at the upper school; a 9th grader taking a Latin course at the middle school as prerequisite completion) schedule individually with cross-campus timetables and communicated pickup / travel logistics.

Activity periods (independent schools: clubs, athletics, community service; public schools: intervention block, enrichment, RTI / MTSS tier-based grouping) schedule with student choice within capacity constraints, RTI / MTSS tier-based grouping per progress-monitoring data, and enrichment grouping by student interest. Lunch waves (a 900-student middle school typically runs 3 lunch waves of about 300 students each with 25-30 minute lunch periods) assign per grade level, per team, or per per-teacher structure per school policy. Bus route arrival and dismissal windows constrain morning and afternoon scheduling, a school where the first bus arrives 25 minutes before the second wave cannot schedule an all-school activity in that 25-minute window.

Once the master schedule publishes, attendance rosters, gradebook rosters, and parent-portal schedule views populate automatically. Period attendance pulls from the published schedule, when third period starts, third-period attendance rosters appear in each teacher's attendance app. Gradebook rosters inherit from the schedule so course teachers see their students without CSV imports. Parent portal displays each child's daily / rotational schedule with room numbers and teacher names, updated automatically on schedule changes. Mid-year schedule changes (a student moves from Math 6 to Math 6 Advanced in October) update attendance and gradebook records for the student without registrar-teacher manual reconciliation.