Timetable guide
How should a school build a timetable and review conflicts before publishing?
A journey from setup and draft to teacher, class and room conflict checks, then review and publication.
- Written by
- Raqeem content team
- Product review
- Raqeem product team
Direct answer
Timetable work starts with periods, days and resources, then a draft schedule. Before publication, the school checks that a teacher, class or room is not assigned to two lessons at the same time. An authorised leader corrects, approves and publishes the version intended for users.
Guide method and boundaries
This guide reflects capabilities reviewed in Raqeem at the stated revision date. It separates available functionality from planned work and does not claim external certification, integration or synchronisation without published evidence.
Prepare resources and constraints
Periods, teachers, classes, rooms and subjects are defined before lessons are arranged.
Accurate foundation data makes conflict review clearer.
Build a reviewable draft
A draft allows lessons to move without presenting the schedule as final.
Time conflicts are checked for teacher, class and room together with school-specific constraints.
Approve and publish
After conflicts are handled, the authorised leader approves and publishes the user-facing version.
Later changes should remain identifiable so different groups do not unknowingly use conflicting versions.
Pre-publication checklist
- Periods and days configured.
- Every lesson linked to class, subject and teacher.
- No teacher, class or room conflict.
- Draft distinct from published version.
- Approval and publication restricted to authorised roles.
Related questions
Does conflict detection mean automatic timetable generation?
No. Conflict checks may support a manually built timetable without claiming full automatic generation.
Do students see the draft?
The normal approach is to show the approved published version, not the internal draft.
More guides on governance and security
Guides on institutional data isolation, permissions, information protection and timetable conflicts.
How does Raqeem isolate each school’s data?
A clear explanation of institution separation, permissions and the rule against transferring one school’s methods to another.
Who can do what? Roles, permissions and sensitive actions
Understand role, capability and data scope, then control viewing, creation, editing, deletion, review and approval.
How should a school protect student, family and staff data?
Practical principles for limiting access, isolating institutions, protecting accounts and separating production from testing.