University scheduling software
Faculties with scheduling autonomy, shared central resources, and a registrar who has to reconcile the two without a fight every September.
Solutions
Timetabling for the institution you run
One licence and one feature set covers a single faculty and a twelve-site university. What differs is which constraints dominate, and which parts of the system you will lean on hardest. The pages below are the cases we are asked about most often — not a list of who we take.
By institution
Timetable software for colleges
Smaller teams with no dedicated timetabling department, where one administrator has to be able to run the whole thing.
Private university timetabling
Fast-growing institutions where the timetable has to absorb new programmes every intake without a rebuild.
Multi-campus scheduling
Travel time between sites treated as a real constraint, with per-campus and consolidated views of the same timetable.
Specific requirements
Three cases where the constraints are unusual enough to be worth a page of their own. They are not separate products — they are the same system, described in the terms those institutions use.
Medical school timetabling
Clinical rotations, hospital placements, small-group teaching and laboratory sessions alongside conventional lectures.
Engineering faculty timetabling
Laboratory capacity, split cohorts, equipment-bound sessions and unusually heavy practical loads.
Middle East & GCC specifics
A Friday–Saturday weekend, a Ramadan timetable, prayer gaps, gender-segregated sections and rooms, Hijri dates beside Gregorian, and Arabic published alongside English.
What actually differs between them
Less than institutions expect. The engine, the licence and the feature set are the same in every case.
What changes is which constraint you spend your time on. A college with four hundred students and eleven rooms is a room-capacity problem. A research university with distributed scheduling authority is a coordination problem, and the software's job there is to make a clash visible the moment it is created rather than in a reconciliation pass in late August. A medical school is a placement problem, where the scarce resource is a consultant's clinic rather than a lecture theatre.
None of that changes what you buy. It changes which parts of it you will use hardest — constraint depth in one case, lecturer self-service in another, room booking in a third — and it changes what a useful demonstration looks like, which is why we build a fragment of your own timetable during the call rather than showing a prepared one.
It also means the size of the institution is not the deciding question. There is no entity limit in the software and no per-student pricing tier: see pricing for how a licence is actually counted.
Not on this list?
The seven pages above are the cases we are asked about most, not the cases we cover.
Language schools, vocational and technical colleges, nursing and health-science faculties, conservatoires teaching one student at a time, branch campuses running a parent institution's calendar in another time zone, institutions running joint programmes with a partner university — all of them are timetabled with the same software and the same licence, and several of them have been for over a decade.
The quickest way to find out whether yours is awkward is to describe it. Tell us your setup and we will say plainly whether it is routine for us, or book an online demo and we will use your own data in it.
See Wise Timetable on your own data
Book a 45-minute online presentation. We will walk through your institution's scheduling problem, show how Wise Timetable handles it, and answer anything your team wants to test.