Education
A timetable built by hand takes weeks and pleases nobody. A model builds it without clashes. When something changes late, it adjusts only the sessions affected.
- Free 30-minute call
- No commitment
- You own the code
Typical problems in education.
You spend weeks fitting courses, rooms and lecturers into one grid. Then you lose a room in August, and you have to plan half the timetable again.
Timetables take weeks
Your team spends much of the summer on next year’s timetable. It still goes out with clashes.
One change, a new timetable
One lecture hall closes for repairs. Instead of moving only the affected courses, you rebuild half the timetable.
Rooms booked twice
Two seminars land in the same room on Tuesday at ten. Nobody saw it, because nobody sees the whole picture.
Exams collide
A student has two exams on the same morning. The complaint arrives after the exam plan is published.
In short: A university timetable assigns every course, exam, room and lecturer to a time slot so that nothing clashes. Timetabling software does this with a model. The model always keeps the hard rules and meets wishes as often as possible.
Why university timetables take weeks by hand
In late June, you have the course list, the rooms and the lecturer requests. Week by week, you fit sessions into the grid. Then a room clash appears, and half the timetable gets rebuilt. Lecturers get slots they didn’t ask for, and students get exams back to back.
Course timetabling, exam scheduling, room allocation and the assignment of lecturers and equipment are one connected puzzle. You solve the parts one after another, in separate spreadsheets. So every fix in one part breaks something in another. The weeks go into repairs, and the result still pleases nobody.
What changes with a timetabling model
Today, a room clash in August means days of rework. Our model moves only the sessions affected by the clash. The rest of the timetable stays as it is. You enter the rules once: rooms, lecturer availability, course combinations, exam spacing. The model returns a timetable free of clashes, and you review it instead of building it.
Lecturers see their requests met where the rules allow. When one can’t be met, you can show them why. Students get their exams spread out, with time to prepare in between. You get the summer back for other work.
How a project runs.
Each of the three phases ends with something you can check before we go any further.
-
Understand
We start with your operation. What do you plan, where does it go wrong, and what would a better week look like? Then we tell you straight whether optimisation can help, and sometimes the answer is no.
- A written assessment
- A clear go or no-go
-
Model
We write your decisions, goals and rules into a mathematical model, which is just a precise description of how your operation works. Then we run it on your own data. You see side by side what each plan costs and what it delivers, and pick the one that fits your priorities.
- A documented model
- Results on your own data
-
Implement
We test with your data and go through the results with your team. Once they trust it, we connect the model to your systems, so it runs every day without anyone stepping in by hand.
- Source code and documentation
- Training for your team
Common questions.
Something else? Ask us directly.
Hard constraints are always kept: no student in two rooms at once, no room booked twice. Soft constraints are wishes the model meets as often as it can, such as a lecturer’s preferred day. You decide how much each wish weighs. That weight tells the model which wishes you can most easily give up.
Usually, yes, because exams come later and follow different rules. The exam plan spreads each student’s exams over several days. It also puts large groups in large rooms. To do that, it has to know which student takes which course. So both plans use the same data. We calculate them one after the other.
Yes, there are open-source tools for course and exam timetables, and some universities run them. Free software still needs a person who enters your rules and data. That person also has to step in when the plan for a term doesn’t work. Compare the total effort over a few terms, not only the licence fee.
It depends on the problem, so we agree the timeline with you up front. Every project starts with a diagnostic, a short look at how you plan today. It shows which data, how much time and what budget a model for daily use needs. Only then do you decide.
No. We connect to your ERP, your warehouse management system or your planning spreadsheet. We build the model only for the planning that gives you trouble today. Your systems keep running as before.
Almost nobody’s data is clean. The diagnostic shows what the model needs and what’s missing. Then we build the model to cope with messy data.
Off-the-shelf tools are built for many companies at once, so they don’t know your special rules. We build a model that follows exactly your rules. Then we hand it over, and your team owns it.
Similar pages.
Tell us what you’re planning.
In a free 30-minute call with a specialist, you find out whether optimisation can help.
- Free, no commitment
- You talk to a specialist directly
- A clear go or no-go