How to build a school timetable without double-booking teachers

Confirm who teaches what in each class

A teacher’s subject name is not enough. Mathematics in JSS 1 and Mathematics in JSS 2 may belong to different teachers. Prepare a class-by-class subject assignment list before scheduling periods.

For primary classes, one class teacher may handle most or all subjects. That should be a deliberate assignment, not a reason to ignore the teacher’s other responsibilities. If that teacher also teaches another class, the same conflict rules still apply.

• Check class-teacher and subject-teacher responsibilities separately.
• Resolve missing or outdated subject assignments.
• Confirm any shared teachers before placing lessons.

Set realistic periods and breaks

Define the school day’s start, end, lesson durations and breaks. Review time formatting carefully so that a morning lesson does not accidentally become an afternoon or overnight entry.

Build around actual school constraints, including assembly, shared rooms or staff availability where relevant. Software conflict checks help with supported constraints; they should not be assumed to know every local arrangement unless it has been configured.

• Confirm the correct time for every period.
• Keep breaks distinct from teaching periods.
• Check that the weekly structure is practical for staff and students.

Place lessons using the class assignment

When selecting a subject, use the teacher assigned to that subject for that class. Do not pick a teacher simply because their name appears in a general staff list. If the expected teacher is missing, correct the underlying assignment first.

SkoolDrive’s assisted timetable workflow uses class-subject assignments and checks teacher conflicts. It is not an automatic whole-school scheduling engine: the administrator still arranges the week and reviews whether the sequence makes sense.

Handle parallel Science and Arts lessons explicitly

A class may split into groups during one period—for example, Physics for one group and Government for another. Represent these as separate parallel lessons with distinct labels, rather than hiding two subjects in a single free-text title.

Check that each group has an appropriate teacher and that no teacher is expected to teach both groups at once. A group label describes the timetable arrangement; it does not automatically enrol students into the correct stream.

• Use clear, different group names.
• Verify teacher availability for every parallel lesson.
• Explain the group arrangement to staff and learners.

Treat copied timetables as drafts to review

Copying a schedule can save repetitive work, but the destination class may have different subject teachers. Check the copied lessons against its own assignments, not the source class’s assumptions.

After any change, review the affected teacher’s week as well as the class timetable. A correction that looks right in one class can create a clash elsewhere. Where possible, check the final arrangement with the people who will follow it.

Keep reminders aligned with the live timetable

A reminder is useful only if the underlying lesson is current. Configure the school timezone and supported reminder lead time, then keep recorded holidays and closures up to date. Do not assume every public holiday or emergency closure is known automatically.

When a lesson is rescheduled or a teacher changes, update the timetable promptly. Delivery still depends on notification settings and device or network conditions, so a reminder supplements the published schedule rather than replacing it.

• Review changes before notifying staff.
• Check the school’s configured closures.
• Use the current timetable as the source of truth.