A university semester timetable is the result of many interdependent decisions: which course runs in which room, at what time, with which lecturer and for which student groups. While the constraints are simple, a spreadsheet can cope, but as the number of faculties, programs and study modes grows, manual planning becomes slow and error-prone.

This article helps you decide whether off-the-shelf timetabling software or custom development is the better route for your institution, and which criteria to weigh.

What is university timetabling software, and what problem does it solve?

A University timetabling software is a system that builds an institution's timetable automatically or semi-automatically from predefined constraints. The goal is a timetable with no room, lecturer or group clashes that satisfies as many institutional rules as possible.

Constraints fall into two groups. Hard constraints must never be broken, for example a lecturer can only teach in one place at a time. Soft constraints are preferences, for example that a student group should not have a long gap between two lectures.

The more soft constraints you need to balance at once, the more important it is that the software's planning logic fits how your institution actually works, not the other way around.

When is off-the-shelf timetabling software enough, and when is it not?

Off-the-shelf timetabling software is enough when your academic structure is simple, your rules can be described with few exceptions, and you do not need deep integration with other systems. In that case, fast implementation and a predictable license fee are genuine advantages.

The limits of an off-the-shelf product typically show in the following situations:

• Several faculties or campuses share rooms but follow different rules.
• Specific rules apply to teaching loads, merged groups or part-time programs.
• The timetable must sync automatically with your student information system (SIS), room booking or HR system.
• Rules change from semester to semester, and changes cannot wait for the vendor's product roadmap.

If several of these apply, an off-the-shelf system will need workarounds such as parallel spreadsheets or manual post-processing. These erode the very efficiency the software was introduced to deliver.

Off-the-shelf or custom timetabling software: how do they differ?

The key difference is who adapts to whom: with an off-the-shelf product, your institution adapts to the software; with custom software development, the software adapts to your institution.

• Constraint handling: an off-the-shelf system works with predefined rule types, while custom development models your institution's own rules.
• Integration: an off-the-shelf system typically offers standard import and export, while custom development builds direct connections to your existing systems.
• Time to launch: an off-the-shelf system starts faster, while custom development is preceded by requirements analysis and a build phase.
• Cost structure: with an off-the-shelf system the main cost is an ongoing license fee, with custom development it is the initial development cost.
• Extensibility: an off-the-shelf system follows the vendor's roadmap, while custom development can be extended as your needs evolve.
• Data handling: with an off-the-shelf system the provider decides where and how data is processed, with custom development your institution decides.

There is also a middle path: bespoke software built on a proven planning engine but tailored to your institution's rules and systems. This often strikes a good balance between time to launch and flexibility.

ASH Szoftverház has already built a timetabling solution of this kind for METU university, and our Chronos timetabling software builds on that experience. You can find more of our custom development work on our Projects page .

How much does custom timetabling software cost?

The cost of custom timetabling software is driven mainly by the complexity of the constraints, the number of integrations and the scope of the user interfaces. An accurate price can only be given after a requirements assessment.

The main cost drivers are:

• the number of faculties, campuses and study modes,
• the number of connected systems, such as the SIS, room booking and HR, and the quality of their interfaces,
• the scope of student and lecturer interfaces, such as a mobile view or personal timetable export,
• security and compliance requirements,
• the hosting model: on-premises servers or a cloud service.

When comparing total cost, look beyond license fees to the time spent on manual post-processing, rescheduling caused by timetable errors and maintaining workarounds. If you opt for a cloud service, publicly funded institutions should complete a compliance review before use.

What security and data protection requirements should you consider?

Timetabling software processes personal data, so security must be designed into the architecture from the outset, not added as an afterthought.

Timetable data can include lecturer names, contact details, teaching loads and student group assignments. Under the GDPR principle of data minimization, the system should only process the data that is genuinely needed to build and publish the timetable.

During design, check the following points:

• Role-based access: planners, faculty administrators, lecturers and students see only the data they need.
• Audit logging: every change records who changed what and when.
• Accessibility: student and lecturer interfaces should follow WCAG guidelines.
• Data retention: it is defined how long data from previous semesters is kept.

Information security practices under ISO 27001 and the requirements of the EU NIS2 Directive may also apply. Which of these are relevant to your institution is best clarified with legal and compliance experts.

Frequently asked questions

Can a university plan its timetable in Excel?

A small institution or a single program can, but a spreadsheet does not automatically check clashes and constraints. As the number of faculties, rooms and merged groups grows, manual checking takes more and more time and the risk of errors rises. At that point, it is worth moving to dedicated timetabling software.

How long does it take to implement timetabling software?

Implementing timetabling software typically takes one to three months; the exact timeline depends on the complexity of the constraints and the number of integrations. With an off-the-shelf system, configuration and data loading are the main tasks; with custom development, these are preceded by requirements analysis and development. Plan the rollout so there is time for a trial timetable before the first live semester.

Can timetabling software be integrated with a student information system?

Yes, and this is one of the most common reasons for custom development. Integration transfers courses, groups and lecturer data into the planner automatically and sends the finished timetable back to the SIS. This removes double data entry and the inconsistencies it causes. The exact solution depends on the interfaces your SIS provides.

What is the difference between hard and soft constraints in timetabling?

A hard constraint is a rule that must never be broken, for example only one class can take place in a room at a time. A soft constraint is a preference that improves timetable quality when met, such as lecturers' requested days off or minimizing gaps between classes. Good timetabling software meets every hard constraint and satisfies as many soft constraints as possible.

Where should you start?

If building the timetable takes significant manual effort every semester, a short requirements assessment is a good first step. Get in touch with us,and we will map your existing rules and systems, then show whether an off-the-shelf, tailored or fully custom solution suits your institution best.