One university, many members
Connecting the members of one university
Faculties rarely want to give up their own timetable, their own naming or their own teaching hours — and they should not have to. Wise Timetable joins separate timetables together rather than replacing them with one central grid nobody asked for.
- Each member keeps its own timetable
- Different time grids supported
- Availability visible across all of them
Federation, not amalgamation
The usual proposal is that every faculty moves onto a single shared timetable. It is a clean idea that dies on contact with a real university.
Faculties differ for reasons that are not stubbornness. A medical school runs clinical blocks; an art academy runs studios; an engineering faculty runs laboratory cycles. They keep different teaching hours, different term structures and different names for the same things, because those things genuinely are different in each context.
So Wise Timetable does not require one grid. Each member keeps its own timetable, its own settings and its own timetabling officer, and the system connects them — so that a shared room, a shared lecturer or a shared student cohort is visible to everyone who needs to see it, without anybody surrendering control of their own schedule.
That is also the practical route to a university-wide rollout. Faculties join one at a time, at their own pace, and each one is useful on its own from the first day rather than only once the last one has migrated.
A dictionary for names that do not match
The single biggest obstacle to joining separate timetables is that the same thing is called three different things.
One faculty writes a lecturer as Novak Ana, another as dr. A. Novak, a third holds only a staff number. Room P1 in one building is Predavalnica 1 in another and Lecture Theatre 1 in the English-language records. A subject shared between two programmes carries a different code in each.
Wise Timetable holds a mapping — a dictionary — between those names, so the system knows the entries refer to one person, one room or one subject. Nobody has to rename anything in their own timetable, and each faculty's records keep reading the way its own staff expect.
This is the piece that most integration attempts skip, and it is why they fail. Matching on exact strings works in a demonstration and collapses on real data.
Different time grids, joined honestly
Two faculties can be synchronised even when their teaching hours do not line up at all.
One faculty may start lectures at 08:00 in ninety-minute blocks; another at 07:30 in forty-five-minute periods. Most systems require one of them to change. Wise Timetable does not: the timetables are synchronised across the differing grids, and where a session from another member falls between the local bell lines, the real times are carried on the session card itself.
So a lecturer looking at their own faculty's week sees the visiting session in its true place, labelled with when it actually runs rather than snapped to the nearest local slot. The alternative — rounding somebody else's teaching to fit your grid — produces a timetable that looks tidy and sends people to the wrong room at the wrong time.
Availability across every timetable, not just yours
A lecturer who teaches in three faculties is one person with one week. A room borrowed by a neighbouring department is occupied for everybody, not only for the timetable that booked it.
Wise Timetable shows the occupancy of a lecturer or a room across all the connected timetables, so the person building one faculty's schedule can see what is already committed elsewhere before placing a session. That turns the most common cross-faculty argument — we did not know he was teaching for you on Thursday — into something visible at the moment the decision is made.
The same view is what makes shared teaching space work. Central administration can see genuine utilisation across the whole institution rather than adding up figures each faculty prepared separately. More on utilisation reporting.
One calendar for a lecturer who teaches everywhere
Whatever the administrative arrangement, a lecturer wants one calendar. Wise Timetable publishes each person's own timetable as a subscription feed, which they add once to whichever calendar or mail client they already live in — Outlook, Google Calendar, Apple Calendar, Thunderbird, any client that speaks the standard.
It is a subscription rather than an export, so it keeps itself current. A session moved by a timetabling officer on Tuesday appears in the lecturer's phone without anybody sending a file, and teaching from every faculty they work in arrives in that same calendar alongside their own appointments. How publishing works.
Related capabilities
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.