University and college timetabling software: what to look for
5 min read
Most timetabling software was designed for schools, where a few hundred students move through a fixed curriculum in year groups. Universities and further education colleges don't work like that. Students choose modules or follow individual study programmes. Teaching spans several buildings or campuses. Specialist spaces are scarce and expensive, and the timetable is often published to thousands of people who expect it to be right first time.
This guide covers what to look for in timetabling software for colleges and universities, and what to ask suppliers before you commit.
What's different about timetabling a college or university
Scale. A large university schedules tens of thousands of teaching events a year across hundreds of rooms. An FE college might have fewer students but far more programme combinations. Software that is fine for a school can slow to a crawl or give up.
Individual students, not year groups. When students choose optional modules, or combine a main programme with English and maths, enrichment and placements, every student's combination has to work. Checking that each class has a room and a teacher isn't enough. You need to check every student's week for clashes.
Shared, specialist space. Labs, workshops, studios, kitchens and large lecture theatres are booked by many departments. Getting them wrong is expensive, and poor use of them shows up in estates reviews.
Part-time and flexible attendance. Many students work, commute or have caring responsibilities. A timetable that spreads their teaching over five days instead of three makes it harder to attend.
Many stakeholders. Departments, academics, estates, student services and students all have a stake in the timetable, and they all want something different from it.
Features that matter
Student-level clash checking
The single most important question is whether the software checks clashes for every individual student, using real enrolment or module choice data. Without that, clashes surface after publication, when students email to say they can't attend two compulsory sessions at once.
Automatic scheduling that can cope with your size
Manual timetabling with clash warnings works for a small timetable. At university or college scale, you want the software to build the timetable for you within your rules, then let you refine it. Ask for evidence it handles an institution your size, ideally by running your own data. See how an automatic timetable generator actually works for what is going on under the hood.
Clear hard rules and soft goals
Good software separates rules that can never be broken (no double-booked rooms, no lecturer in two places) from goals it should work towards (compact student days, fewer gaps, sensible lecturer loads). You should be able to see and change both. See hard and soft constraints, explained.
Room fit
Every class should go in a room with enough capacity and the right facilities. A lab session can't go in a seminar room, and 80 students can't go in a room for 40.
Compact weeks and gap limits
For FE students especially, the number of days they attend and the length of the gaps between sessions affect attendance and retention. The software should let you set targets for both. See how to reduce stranded free periods for how to measure gaps.
Analytics
You should be able to see room utilisation, lecturer load and student gaps without exporting everything to a spreadsheet. Those numbers are what you will be asked for by senior leaders and estates teams.
Scenarios
You'll want to compare options before committing: a three-day week against four days for a programme, a new building coming online, a change in staffing. Software that keeps separate scenarios side by side makes that easy.
Getting your data in and out
Your student record system (SITS, ebs, Unit-e, Banner or another) holds the students, enrolments and modules. Find out exactly how data gets from there into the timetabling software, and how the finished timetable gets back out to students, staff and room booking. A simple, repeatable export can be more reliable than a complex integration project.
The market you'll be choosing from
UK higher education has long been dominated by a small number of established systems, notably Syllabus Plus (now part of TechnologyOne) and CMIS (OneAdvanced). Other suppliers include Celcat, Semestry TermTime, TimeEdit and EventMAP. Several have changed ownership in recent years, which is worth asking about when you think about long-term support and product direction.
Many institutions buy through frameworks such as G-Cloud, so check whether a supplier is listed on the frameworks your procurement team uses.
Questions to ask every supplier
- Can we run a trial or proof of concept using our own data?
- How long does a full timetable take to generate at our size?
- Does it check clashes for every student, or only for classes?
- What happens when the rules can't all be met? Does it tell us why?
- How does data get in from our student record system, and how often can we refresh it?
- How is the timetable published to students and staff?
- Where is our data hosted, and what security certifications do you hold?
- How long does implementation take, and who on our side needs to be involved?
- How is pricing calculated: per student, per site or a flat fee?
- What does support look like during the peak timetabling period?
For a more general checklist, including pricing models, see choosing timetabling software: a buyer's checklist.
Where Timez fits
Timez builds clash-free weekly teaching timetables automatically, from CSV exports of your students, staff, rooms, modules and enrolments. It's designed for the constraints colleges and universities face:
- No student clashes: every student's combination of modules or courses is checked, not just each class.
- Room fit: classes only go in rooms with enough capacity.
- Compact weeks and fewer gaps: set how many days students should attend, and Timez works to fit their teaching into them.
- Staff availability: part-time and sessional staff are only timetabled when they're available.
- Analytics and scenarios: see room utilisation, teacher load and student gaps, and compare scenarios as separate projects.
If you'd like to see how it handles your institution, request information and we'll be in touch.