School timetable guides
Check weekly lesson loads in a school timetable
Counting timetable cards is not enough when lessons have different durations or alternate between weeks. Start from the class requirements and use the same units when comparing the plan with the timetable.
Open manual modeWrite down the weekly requirement
For each class and subject, choose the teacher and record lessons per week. Set the lesson duration separately. A requirement for three lessons is not necessarily three periods: each lesson may occupy more than one slot.
Include the lesson duration
The manual workspace workload accounts for the number of slots each lesson occupies. Three weekly lessons lasting two slots each contribute six academic lesson units. Treat this as teaching load, not automatically as six clock hours; the grid defines the actual start and end times.
Review the complete cycle
If the timetable alternates between weeks, inspect the entire cycle. A requirement of half a lesson per week can be represented by one lesson in a two-week cycle. Compare weekly averages with weekly averages, and cycle totals with cycle totals.
Reconcile placed and remaining load
Use class and teacher views to compare planned, placed, and unplaced amounts. Unplacing a card preserves the planned workload; deleting a lesson changes it. If the totals look wrong after editing requirements, check the teacher assignment, duration, and cycle before placing more cards.
Common questions
Is an academic lesson unit the same as a 60-minute hour?
No. Keep the workload units separate from elapsed time. Use the grid’s actual lesson times when calculating clock minutes or checking overlaps.
Why does removing a placement leave the planned total unchanged?
Unplace changes the timetable position, not the requirement. Delete is the action that changes how many lessons are required.