School timetable software turns school data (classes, subjects, teachers and the hours of the school day) into a clear weekly timetable for every class and every teacher. Building one by hand is tiring: changing a single period triggers a chain of edits, and a clash discovered late can mean a week of disorder in the classrooms. A timetable needs a system that knows its constraints before they become problems.
This page explains how the timetable module in wakp's school management system builds the timetable step by step and how it connects to the rest of the school's data.
Why is a school timetable hard to build?
A timetable is a problem of overlapping constraints. One teacher serves several classes, one class has dozens of periods, and each subject has a weekly count and an acceptable daily maximum. Add breaks, school days and sometimes different day structures across stages. The failures usually take three forms:
- Teacher clashes: a teacher booked into two classes in the same period.
- Uneven spread: a subject piles into one day and disappears from the rest of the week.
- Lost versions: a timetable edited across Excel copies, and nobody knows which one is approved.
How wakp's school timetable software works, step by step
1. Define the school day (Day Profiles)
Name a day profile, choose the weekdays (for example Sunday to Thursday) and add the periods: lessons and breaks with start and end times. Then link a class to the profile that suits it, or click "save and apply to all classes in the grade". The primary stage can differ from the preparatory stage without manual setup for each class.
2. Set periods per subject (Requirements)
For each subject in a grade you set the group type, the classes, the number of periods per week, the maximum periods of that subject per day, and the status. This is where the academic plan becomes numbers the timetable can work with, and the daily limit stops a subject from stacking on one day.
3. Build the weekly timetable (Board)
Choose the scope: year, term, education type, system, track, stage, grade, class, plan version and timetable version. A grid of periods against days appears. "Start timetable setup" begins the distribution, and "clear distribution" lets you try again. Selecting a scope before loading keeps the screen fast even in large schools.
4. Check for clashes
The conflict check surfaces problems before students see them: a teacher in two classes at once, a subject exceeding its daily limit, and other violations of the constraints you defined. Fix what appears, then check again.
5. Approve a saved version
Once the timetable is clean, click approve timetable. It is saved as a numbered version (tt_version_id), so you always know which version is approved and can work on a new one without losing the old.
Manual timetable or software?
| Area | Excel or paper | wakp timetable |
|---|---|---|
| School day | Redrawn for each class | One day profile applied to a grade |
| Periods per subject | In the coordinator's head | Entered per subject and grade |
| Clashes | Found in week one | Checked before approval |
| Versions | Several similarly named files | Numbered versions with approval |
| Teachers | Typed names | Staff linked as teachers with their assignments |
How to prepare before building the timetable
Timetable quality is decided before any button is pressed. A practical preparation list that works for any software:
- Fix the school day structure. Set the number and times of periods, breaks and school days for each stage, and any exceptions such as one short day a week.
- Review the academic plan. Make sure every subject in every grade has an agreed weekly period count and that the official subjects are in the system.
- Complete teacher assignments. Review who teaches what and in which classes, and resolve assignment conflicts before distribution starts. Importing the teachers' academic distribution from Excel in the school HR management system helps: rows that are ready are separated from rows that need review.
- Check classes and student placement. An incomplete class or a student without a class means an incomplete timetable.
- Write down the non-negotiable constraints, such as the daily maximum for a particular subject, and turn them into system inputs instead of leaving them as the coordinator's verbal knowledge.
- Start with a trial version. Use a new timetable version for experiments, and do not approve until the conflict check is clean.
Common mistakes when building a timetable
- Starting from the grid instead of the constraints. Whoever draws the grid first finds the constraints late. Start by defining the day and the period counts, then distribute.
- Ignoring the daily limit per subject. A heavy subject lands in three consecutive periods and students switch off.
- Editing the approved timetable directly. Every change after approval should go through a new version so everyone knows which timetable is in force.
- Forgetting to tell people. A correct timetable that does not reach teachers, students and parents is useless. Agree one channel for every change.
- Keeping the timetable apart from other data. When it is built in a standalone file, classes and teachers are re-entered, and any change to one breaks the other.
An illustrative example: two stages, two day structures
Suppose a school has a primary and a preparatory stage. Primary finishes earlier with fewer periods; preparatory adds periods after the second break. In wakp you create two day profiles with different names and link each stage's classes to its profile. You then set each subject's weekly periods and daily limit per grade and build each class's timetable. The conflict check reveals that a teacher who serves both stages was placed in two simultaneous periods, so you move one and check again until it is clean, then approve. This example illustrates the workflow; it does not describe a real school.
Substitution cover, printing and publishing
What happens after approval matters as much as what comes before. wakp supports cover for an absent teacher (substitution), so a replacement is assigned to a specific period without touching the approved timetable itself. You can print each teacher's timetable and each class's timetable for display or hand-out, and publish the timetable to the portals so teachers, students and parents see theirs on a phone or computer.
A quick implementation checklist
- Define the day structures and link each stage to its own.
- Enter weekly periods and the daily limit for each subject in each grade.
- Review teacher assignments and student placement.
- Build the timetable and run the clash check until it is clean.
- Approve it as a version, then print and publish it.
- Adopt a change routine: new version, check, notify.
How to handle changes during the year
An approved timetable does not stay fixed forever: a teacher changes, a subject is added, a class is redistributed. The practical rule is to work on a new timetable version instead of editing the approved one, check clashes in it, then approve it and tell those affected. The history of timetables is preserved this way, and everyone knows when each version took effect. It also helps in any dispute about a lesson that was cancelled or moved, because the earlier version is still there to refer to.
Why an organised timetable matters
A school timetable matters beyond tidiness. It underpins a regular school day: teachers know their slot and class, students know their lesson, and administration knows what should be happening in each class at each time. Improvised phone calls decrease when the timetable is clear and current, and the coordinator can review it from anywhere because the system runs in the browser. An approved timetable saved as a version is also a reference when there is a dispute over a lesson time or a teacher's assignment.
Beyond the timetable: how it connects
The timetable draws on the rest of the school's data, so it is not a sheet pinned to a wall:
- Teachers: assignments come from the teacher's file in the school HR management system, where an employee is linked as a teacher with assignment type, subjects and grades.
- Classes and students: classes and student placement come from the student management system, so the timetable is built on real classes.
- Attendance: student attendance is recorded by class and date in the school attendance system.
- Portals: students and teachers see the day's lessons on their own page after signing in, as described on the student and teacher portals page.
- Telling the team: a timetable change has to reach teachers, which is what the school communication system is for.
- Exams: when organising exams and committees, a clear timetable helps; see the school exam control system.
Questions to ask when choosing timetable software
- Does it support different day structures across stages and grades?
- Does it check teacher clashes before approval or only afterwards?
- Can you set a daily limit per subject?
- Does it keep timetable versions and mark the approved one?
- Is the timetable tied to real classes and teachers, or does it use data you must re-enter?
- Does it run from any browser so the coordinator can follow up remotely?
wakp runs as a web app, so you follow the timetable from a computer or phone, and it can be installed on the phone with notifications.
How wakp helps
- A flexible school day: days, periods and breaks with times to suit each stage.
- Explicit constraints: weekly period counts and a daily limit per subject.
- A clash check before students see the timetable.
- Approved versions that keep the timetable's history.
- Linked to core data: classes, subjects and teachers, not copied lists.
- Arabic and English, with right-to-left and left-to-right layouts.
Who is it for?
Private, international and language schools in Egypt and Saudi Arabia, especially those with several stages or education systems, or many teachers who serve more than one class. It is one part of a system that also covers students, attendance, accounts and exam control; browse it in the school management system features.
Frequently asked questions
What is school timetable software?
Software that builds the weekly class timetable from the school day structure, periods per subject and teacher assignments, and checks conflicts before the timetable is approved.
How does wakp prevent teacher timetable clashes?
The timetable screen has a conflict check that flags cases such as a teacher placed in two classes at once or a subject exceeding its daily period limit, before you approve the timetable.
Can different classes have different school-day structures?
Yes. You define more than one day profile (weekdays, periods and breaks with times) and link each class to its profile, or apply a profile to every class in a grade in one step.
Does wakp keep versions of the timetable?
Yes. A timetable is approved as a numbered version, and you work within a scope of year, term and version, so earlier versions are kept.
Does it work for a Sunday to Thursday school week?
Yes. The weekdays are part of the day profile, so you choose the days your school runs, such as Sunday to Thursday.
Is the timetable connected to teacher and subject data?
Yes. It works on the academic plan, official subjects and classes, and teachers are the staff members linked as teachers in the HR module.
Update log
- — English version written alongside the full Arabic rewrite
- — On-page SEO check; internal links to the home page, the features hub and neighbouring features; all links point to English URLs; link to the student and teacher portals page