A school timetable maker for the Kenyan curriculum must support different school levels and teaching structures. Primary, junior, senior and secondary settings do not use identical subject lists or staffing patterns. The timetable process should let each school define its own classes, learning areas, subjects, teachers, rooms and weekly requirements.
Start with the school level
List every class or stream exactly as the school uses it. Primary schools may organise classes by grade and stream. Junior schools add specialist learning areas and practical rooms. Secondary schools often manage several subject teachers, laboratories and multiple streams. Senior school planning may require pathway and subject-combination decisions.
Represent learning requirements accurately
Enter the weekly lesson requirement for each class-subject allocation. Identify double lessons, practical sessions, assemblies, clubs and games. Avoid copying a generic timetable when the school’s approved programme has different lesson totals or daily routines.
Manage teachers and shared resources
One teacher may serve several streams or school levels. Laboratories, workshops, computer rooms and fields may also be shared. The generator must check availability across every connected schedule. A practical lesson is only possible when the class, teacher and room are free together.
Curriculum timetable workflow
- Confirm the classes, learning areas or subjects offered.
- Record teachers and their allocations.
- Enter weekly lesson totals and double lessons.
- Add specialist rooms and availability restrictions.
- Validate the complete dataset.
- Generate alternatives and review every school-level output.
Review for educational balance
A clash-free timetable still needs human review. Check that demanding learning areas are not concentrated badly, practical sessions have suitable periods and teacher workloads are reasonable. Heads of department or learning-area leaders should review subject schedules before approval.
Example Kenyan school scenario
A combined school may have upper-primary classes, Grades 7–9 and shared ICT facilities. The ICT teacher and computer room must be available for each scheduled class. By entering the classes, teacher and room as connected resources, the school can generate schedules that protect both staffing and facility limits.
Transition between curriculum structures
Schools operating more than one structure during transition should keep class names and subject allocations clear. Do not combine different lesson requirements under one generic label. Separate records help teachers understand which programme they serve and allow administrators to review each school level without losing the whole-school view.
Preparing for a new term
Before copying an earlier timetable, confirm staffing, streams, subjects, facilities and daily periods. Update changed records first, then generate a fresh set of alternatives.
Use consistent names across class, teacher and room records. Consistent labels improve exports, reduce duplicate entries and help users compare the same allocation across different timetable views throughout the school year.
Frequently asked questions
Can the same system support different school levels?
Yes. Schools define their own classes, subjects or learning areas and allocations.
Can practical lessons use specialist rooms?
Yes. Add the room requirement so it is checked during scheduling.
Does the system decide curriculum lesson totals?
No. The school enters the approved requirements it follows. The software schedules them.
Can subject leaders review their own timetable?
Yes. Subject views support departmental checks alongside class and teacher schedules.
Explore all timetable features, see the CBC timetable guide, or open the timetable workspace.