Custom timetabling software for education
The timetable is where the curriculum meets reality: which group gets which subject, from which teacher, in which room, at what time. Four kinds of scarcity at once, with thousands of people planning their day around it and a deadline that doesn't move. Appfront builds custom timetabling software for secondary schools, vocational colleges (mbo), universities of applied sciences and universities: from constraints and clustering to day-to-day scheduling and publishing every change to everyone who needs to know.
What makes timetabling in education different
A calendar appointment reserves one thing. A timetable allocates four at once: a teacher can only be in one place, a group can only attend one lesson at a time, a room hosts only one activity and a timeslot occurs only once a week. All four must be free at the same moment, otherwise that lesson doesn't exist. That makes a timetable not a collection of separate appointments but one interlocking structure. Move one lesson and the puzzle shifts in places you didn't think of: the same group's next lesson, the lab that is now double-booked, the part-time teacher who doesn't work on Thursdays. That is why timetabling can rarely be solved by simply working harder and usually calls for a model.
Are you in the right place? This page is solely about timetabling: scheduling educational activities across teachers, groups, rooms and time. If your question is about student administration, meaning enrolment, curriculum, results and graduation, you belong with a student information system for higher education. If it concerns running the whole organisation, with timetabling logistics as just one part alongside staff, procurement and the data behind your funding, then education ERP is the broader starting point. There, timetabling is a module in a larger landscape; here, it is the subject. A simple rule of thumb helps with that separation: if the question is about the status of a person, such as an enrolment, an earned credit or a diploma, the answer belongs in the administration. If the question is about who is in which room at what time, it is about the timetable. The two systems exchange data, which is exactly why the boundary has to be sharp: enrolment is the source, the timetable is derived from it, and that direction should never be reversed.
Workforce planning also looks related, and the comparison holds up to a point: availability, qualifications and contract size play a role in both. Yet it is a different puzzle. In a business you schedule people against demand that you forecast, and if necessary you can run a shift with one person fewer. In education the demand is fixed by the programme, and there is a second party on the other side that cannot be duplicated either: the group itself. A lesson without a class or without a classroom does not exist, and nobody judges a business rota by the free periods of its customers.
Four scarcities at once
Teacher, group, room and time slot must all be free. If a single element is taken, the lesson cannot go ahead.
One change affects hundreds of calendars
A lesson that moves changes the day for students, teachers, parents, reception and the screens in the hall.
Quality is a management trade-off
Fewer free periods for students often comes at the expense of teacher preferences. The timetable makes that choice visible.
Hard and soft constraints
Everything in a timetable falls into two kinds of rules, and that distinction determines what your software should look like. Hard constraints are the rules whose violation makes the timetable unworkable. A teacher cannot be in two places at once. A group does not follow two lessons in the same hour. A classroom does not host two activities. There are no more students in a room than there are seats. A teacher who does not work on Thursdays does not teach on Thursdays. A practical takes place in a room with the right facilities, and a group does not walk to a building on the other side of town during the break between two lessons. If such a rule is broken, you do not have a mediocre timetable but one that falls apart on Monday.
Soft constraints are the preferences that determine whether the timetable is experienced as a good one. As few free periods as possible for students. A subject spread across the week rather than three hours in a row. No days that start at eight o'clock and only end after the last period. Fixed rooms per department, so materials do not have to travel with every lesson. Consecutive working days for part-time teachers. Practical subjects in the block after the related theory has been covered. These preferences are not optional, because they shape how your organisation is judged, but they are interchangeable: you can drop a few of them and still end up with a working timetable.
In practice, the distinction works like this: hard constraints determine whether a timetable can exist at all, while soft constraints determine whether it will be accepted. Both must be stated explicitly in the system. Where that doesn't happen, they end up in the timetabler's head, which is exactly why schools get stuck as soon as that person leaves or falls ill. Being honest about which rule belongs in which category matters just as much. Every wish entered as hard shrinks the solution space, and many timetables described as "impossible" are in fact over-specified: a preference written down as a requirement. Conversely, a hard rule can sometimes be relaxed by giving something on the other side, for example by splitting a group or freeing up an extra room.
Weighting is a management decision, not a technical one
As soon as wishes contradict each other, and they always do, someone has to decide which weighs more. Software can't make that call for you, but it can make the choice visible and repeatable. It does this by giving each soft constraint a weight and adding those weights up into a single score, so that two timetable variants can be compared with each other rather than on gut feeling. The value lies in the conversation this makes possible: if the school leadership wants to know what it would cost to halve the number of free periods in the upper school, the answer should be expressed in the wishes that would have to give way.
The same weights have a side effect that is often underestimated: they make the timetable explainable. A teacher whose request has not been granted accepts that far more easily if the system shows which wishes were counted and how heavily. Without that accountability, the discussion shifts to the person who made the timetable, and that is an unfair place to have it.
What a solver does and doesn't do for you
In computer science, timetabling is known as a computationally hard problem: the number of possible combinations grows so fast that calculating every variant is not a viable route. Timetabling software therefore searches cleverly rather than exhaustively. It first places whatever is most constrained, then systematically swaps lessons for as long as the score improves, and delivers a good solution without proving that no better one exists. That is not a shortcoming; it is the nature of the problem. It does, however, have consequences for what you can expect from your software.
Most importantly, the timetabler stays in charge. They must be able to lock parts of the timetable and have the rest recalculated without yesterday's manual work disappearing. They must be able to compare variants side by side and go back to an earlier version. And when no solution comes up, a message saying "no timetable found" is worthless. What they need is a diagnosis: which lessons together require more practical-lab space than is available on Tuesday afternoon, which teacher is needed in too many places at once, which cluster of elective subjects can't be placed with this staffing. Only then does the conversation with the programme become a conversation about a solvable problem. The last few percent remain human work, and that's fine; the aim is for those hours to go to the exceptions rather than to filling in the obvious.
What timetabling software for education needs to do
These components are interdependent. Constraints without good source data produce a neatly calculated timetable that isn't about your school, and a perfect timetable that students can't reach on time is still a problem on Monday morning. The integration with your administration system belongs in the picture from the start: enrolments, groups and staff appointments are maintained elsewhere and should flow in here rather than being retyped.
Weighted constraints
Record rules as hard or soft, with a weight and a scope: institution-wide, per programme, per location or per teacher.
Clustering elective subjects
Derive groups and clusters from students' subject packages, with a clash analysis before choices are finalised.
Rooms by capacity and facilities
Allocation that takes account of seats, room type, facilities, accessibility and the distance between buildings.
Daily timetabling with cover
Enter absences, trips and room unavailability and choose an outcome per lesson: cancel, merge, reschedule or cover.
Publish to every channel
One change that lands at the same time in the app, the portal, the screens in the building and the calendar subscription.
Versions, scenarios and traceability
Compare variants side by side, roll back to an earlier version and see for every change who altered what and when.
The sources that must be right before you can start timetabling
A timetable is derived data. It only exists if four registers are in order: people, groups, rooms and the curriculum. Timetabling projects that run into difficulty rarely get stuck on the algorithm and almost always on these four. That is good news, because this part is not hard, just unforgiving if skipped.
For people, it takes more than names. For each teacher you need the subjects they are qualified to teach, the size of their contract expressed in teaching and non-teaching hours, the days they are available, and the duties outside the classroom that take up just as much time: mentoring, coordination, supervising work placements. If that last part is missing, someone appears to have capacity they do not have. This is also the least stable of the four registers, because appointments continue right up to the start of the year and the timetable has to be able to keep moving with them.
The curriculum is the register that most often stays implicit. You need the subjects or teaching units, the number of contact hours per week or per period, and the teaching formats in which they are delivered. That last point matters more than it seems: a lecture, a seminar and a practical for the same subject each have a different group size, a different room type and sometimes a different teacher. On top of that come the constraints you must not break, such as lessons that have to run back to back or a practical that can only take place after the theory block.
Groups are the third register and the most confusing, because several kinds exist side by side. There is the form group or class a student belongs to administratively, there are teaching groups that differ from it as soon as a subject is taught in smaller units, and there are groups that only come into being from choices made. In higher education, the split between lecture groups and seminar groups is added to that. All these groups should be derivable from the enrolments in the administration, with an indication of which kind each one is. Where that does not happen and groups are maintained by hand, the timetable drifts out of step with actual numbers without anyone noticing.
Rooms are more than a number of seats
A room list that only holds a room number and a number of seats forces the timetabler to fill in the rest from memory. You also need the room type, the facilities present, accessibility and the location within the building. A lab with fume extraction, a workshop with machinery, a computer room, a sports hall and a studio are not interchangeable square metres. Capacity is also not a single number: a hall where forty students attend a lecture holds considerably fewer people during an exam, and exam seating is a problem in its own right, closely related to exam software. A room with a fixed layout also does not suit every teaching format. Distance matters too, because consecutive lessons in two buildings produce a timetable that is correct on paper and starts late in practice.
This list needs a single owner and a simple change procedure, otherwise it quietly goes out of date. In almost every institution there are rooms that have been renovated, let out or refitted, and the timetabler knows this but the system does not. What helps is closing the feedback loop: if you measure afterwards which rooms were how full, you will soon find out which entries in the list are no longer correct.
Elective subjects and the groups that follow from them
As soon as pupils or students make their own choices, the hardest part of the puzzle appears. In secondary education this means profiles and subject packages, in vocational education (mbo) elective modules, and in higher education elective subjects and minors. These choices are recorded in the administration and determine two things at once: how many groups each subject needs, and which subjects may be scheduled at the same time.
The number of groups follows from the number of enrolments and the maximum group size, and the numbers rarely divide neatly: 53 pupils with a maximum of 28 gives two unequal groups, and choosing to make it three costs an extra teacher and an extra room. Clustering comes next. Subjects chosen by different pupils in the same year are deliberately scheduled at the same time, so that everyone goes to their own elective in that period. Such a cluster only works if no pupil has two subjects from the same cluster in their package. One unfortunate combination, chosen by a handful of pupils, can make an entire cluster impossible.
That is why the clash analysis should happen before the choices are confirmed, not after. Software that shows, based on the provisional choices, which combinations make the timetable expensive gives the programme a chance to steer: open a second group, stop offering a particular combination, or put an alternative to a few individual pupils. If this only happens once all packages are fixed, the only remaining solution is the most expensive one.
- Qualifications, appointment and teaching hours per teacher, up to date for each period
- Groups that follow from enrolments, not from a separate list
- Rooms with type, capacity and facilities, with a single owner
- Course offering with teaching formats and contact hours per period
- Subject packages with clash analysis before the choices are fixed
- One source per data item, with visible origin and date
Test your idea first: a working prototype in 1 day
With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.
View OneDayBuild →The day itself: absence, room changes and publishing
The annual timetable is a snapshot that comes under pressure from the first day of school. A teacher calls in sick at ten past seven. A classroom closes after a leak. There is a field trip, a test week, an open day, a guest lecture that gets moved, a group that has to relocate to another room for a project. Every event calls for a decision per lesson, and the options are limited: the lesson is cancelled, the group is merged with a parallel group, a colleague takes over, the pupils work independently under supervision, or the lesson moves to another time. Which of these five is appropriate is partly a matter of policy and partly a matter of calculation. Policy, because many schools accept no cancellations in the lower years but do in the upper years. Calculation, because the system has to know who is free, qualified and present in that period.
Daily timetabling is therefore a different mode from annual timetabling, and software that ignores that difference does not get used. With the annual timetable you are looking for the best possible solution, and you have time. With the daily timetable you are looking for the smallest possible disruption, and you have minutes. Recalculating everything is exactly the wrong answer: it moves lessons that nobody needed to move. What the daily timetabler needs is an overview of the consequences before choosing. Which groups are left without a lesson, which students get an extra free period, which room becomes available, and which colleagues are available without their own day becoming unworkable. And once the choice has been made, it should be recorded who made it, because daily timetabling is where agreements on workload are tested in practice.
Publishing to everyone is the real work
The change itself takes a minute. Making sure everyone it affects sees it in time is the real work. A single moved lesson means the students need to know, their parents too in the case of structural changes, plus the teachers involved, the colleague covering, reception, the caretaker and the screens in the hall. As soon as each of those channels keeps its own copy of the timetable, the classic error appears: two versions of the truth. The app says room 2.14, the screen says 1.09, and the student who opened the portal before the change was entered ends up somewhere else. The only lasting solution is a single publishing source that all channels draw from, with a version and a timestamp, so that you can trace afterwards what went out and when.
The timing of publication matters at least as much as the content. A change for the first period that appears at five past eight reaches no one in time; the same message helps if it goes out before people leave home. Equally decisive is targeting. If you send everything to everyone, you teach your users to ignore notifications, and then the student the message was actually meant for misses it too. Timetable changes should therefore go to the people concerned, with a short reason attached, because "changed" raises questions that would otherwise end up with the administration. For teachers' and students' calendars, a calendar subscription is the most convenient format: the open standard for this is iCalendar, defined in RFC 5545. There is one caveat, though: the calendar app decides when it fetches updates, not you. A subscription is excellent for next week's timetable and unsuitable as the only channel for a change made this morning.
The realised timetable is your measurement data
If you only keep the planned timetable, you end up measuring a school year that never took place. Only when cancellations, cover and room swaps are recorded do you get the realised timetable, and that is the dataset you can actually steer by. The first question it answers is about your building. Room occupancy is not a single figure but a product of two: how often a room is in use within the hours the building is open, and how full it is then relative to its capacity. A lecture hall that is booked all week but half empty, and a practical lab that is full on two mornings and otherwise stands empty, can score the same on average and call for opposite measures.
That is why the breakdown matters more than the total: per building, per room type and per part of the day. Almost every institution finds the same pattern, namely Tuesday and Thursday mornings full and Friday afternoons empty, and that distribution can be influenced with scheduling rules before anything is built or rented. The second thing the realised timetable substantiates is teaching time. In secondary education, the Secondary Education Act 2020 (Wet voortgezet onderwijs 2020) sets out in Article 2.38 that pre-university education (vwo) comprises at least 5,700 clock hours, senior general secondary (havo) at schools for havo at least 4,700, and mavo and vbo at least 3,700 each, with at least 1,425 clock hours in the first two years combined, and Article 2.39 that teaching is provided on at least 189 days per school year. That same Article 2.38 requires the competent authority to hold organised data on how those clock hours are allocated and spread. A timetable that retains its realised form delivers that evidence as a by-product rather than as an annual hunt.
Bear in mind that timetable data is personal data: it shows where an individual teacher or student was at what time. For occupancy analyses you do not need that level of detail. So work with aggregated figures and do not keep traceable data for longer than you use it, in line with what the GDPR asks of you. That is not a brake on the analysis; above all it saves arguments about a dashboard that shows too much.
When an off-the-shelf package is the better choice
Timetabling is not a blank spot in the software market. Mature timetabling packages exist that explicitly target Dutch education, with versions for secondary education, vocational education (mbo) and higher education, and with integrations to the common student administration systems. For a good share of the institutions reading this page, such a package is the wiser route, and we would rather say so now than halfway through a quoting process.
If your education follows the familiar pattern of lesson periods, year groups, clusters and terms, you buy that off the shelf, including maintenance and the adjustments that follow from changed regulations. Your effort shifts from building to configuring. Do not underestimate that second part: the quality of a timetable lies in the constraints and in the source data, and no package fills those in for you.
Custom development pays off in fewer situations than vendors suggest, but there are a few where it is clearly the better choice. The strongest is an educational model that does not fit the thinking behind existing packages: learning paths that students assemble themselves per term, timetables that run in half-days or blocks rather than lesson periods, work-based learning and internships in which external parties take part in the planning, or education that is structurally spread across changing locations. Anyone who tries to squeeze such a model into a package's form loses precisely the distinctive part. The second situation lies on the outside: institutions that are happy with the timetabling core and get stuck on everything around it, that is, the app, the screens, communication with parents and the integrations. The third is the wish to combine timetable data with space management, rentals or facilities planning, which means the timetable is no longer purely an education question.
Often the middle way is the best answer: a package as the scheduling core, custom work at the edges. That raises one question you should ask early: does the package make its data available through a usable API, and are you allowed to write back to it? If the answer is disappointing, the middle way is more expensive than it looks. The downside of building it yourself belongs here too: keeping up with changing rules and with your own education model then becomes your organisation's job, and the school year cycle is unforgiving. The timetable has to be ready when the year starts, and that date does not move because a system is not finished yet.
If you want to weigh this up properly, don't start with a package comparison but with your own rules. Write down which constraints are genuinely hard and which are wishes, name who sets the weights between them, and describe how a change reaches a student today. That document works in both directions: it is the basis for a package selection and, at the same time, the functional design for a custom build. It also exposes where the real pain is, and in a surprising number of institutions it turns out not to be the scheduling itself but the data that comes before it or the communication that follows.
If you use Xedule and want the timetable in your own app or on screens, see our page on a Xedule integration.
If you want to record cancelled lessons and cover straight away, so that your account of teaching time is accurate, take a look at our app for teaching time and cancelled lessons.
For caretakers, teaching assistants, lab technicians and invigilators, there is our software for shift planning of support staff.
- A package if your education follows the usual pattern of lesson periods and clusters
- A package if the source data first needs to be put in order
- Custom if your education model is one that packages don't support
- Custom if publication and communication are the bottleneck
- The middle way: a package as the scheduling core, custom work at the edges
Frequently asked questions about timetabling software
Hard constraints are rules whose violation makes the timetable unworkable: a teacher cannot be in two places at once, a class cannot attend two lessons in the same period, and a room cannot hold more students than it has seats. Soft constraints are wishes that determine quality, such as as few free periods as possible or a subject spread across the week. Hard rules decide whether a timetable exists; soft ones decide whether it is accepted. Be strict about that distinction, because every wish entered as a requirement needlessly shrinks the solution space.
Usually because the problem is over-specified: there are more hard requirements than can all be true at once, often because preferences have been entered as requirements. Sometimes there really is too little capacity, for example one practical room short on a Tuesday afternoon. In both cases the message 'no timetable found' doesn't get you any further. What you need is a diagnosis that shows which requirements exclude each other and which room or teacher falls short, so that you can choose between dropping a requirement, splitting a group or adding capacity.
Students' choices determine two things: how many groups each subject needs and which subjects can be scheduled at the same time. Subjects chosen by different students in the same year group are brought together in a cluster that runs at the same time, so that everyone goes to their own subject in that period. That only works if no student takes two subjects from the same cluster. Good software therefore calculates, on the provisional choices, which combinations clash, so that the programme can adjust before the packages are final.
Each lesson comes down to a choice: cancel it, merge it with a parallel group, have a colleague cover it, let the students work independently under supervision, or move it to another time. The software should show who is free and qualified at that hour, which groups would otherwise be left without a lesson and which room becomes available. More important still is what happens next: the change must reach the app, the portal, the screens in the building and the teachers concerned in a single action, with a timestamp, so that you never end up with two versions of the truth.
In workforce planning, you schedule people against demand that you forecast, and a shift can run with one person fewer if it has to. In education, demand is fixed by the curriculum and there is a second scarce party you cannot duplicate: the group itself. Add the room with the right facilities and the fixed lesson slot, and four elements have to be free at the same time. Availability, qualifications and contract size matter in both puzzles, but software that only looks at staff deployment does not solve the education problem.
Often, yes. Mature timetabling packages exist for Dutch education, with integrations to the common student administration systems. If your teaching follows the pattern of lesson slots, year groups, clusters and periods, you buy that off the shelf. Custom becomes interesting when your education model is one that packages do not support, such as learning paths that students put together themselves or timetables in half-day blocks, and for institutions that are happy with their timetabling engine but get stuck on publishing to the app, screens and parents. The middle way, a package as the core with custom work at the edges, stands or falls with a usable API.
Related services
Student information system
If your question lies in the student administration itself, that is, in enrolment, curriculum, credits and graduation, then you need a student information system for higher education. That is where the enrolments come from on which this timetable is built.
Education ERP
If your question goes beyond the timetable, to enrolment and placement, staff, procurement and the data behind your funding, then building an education ERP is the broader starting point.
Staff scheduling software
If it is about shifts, teams, leave and qualifications in a business environment rather than lessons and groups, then custom workforce planning software is a better fit for your question.
Your timetabling process under the microscope
Tell us how your timetable is currently put together: which rules are truly hard for you, where pupils' or students' choices lock the puzzle in place, and what happens when a teacher calls in sick at ten past seven. Those three answers usually show whether a package, custom software or a combination fits best.